[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Hardware upgrade -> Volume Group "VolGroup00" not found. [SOLVED]



On Sun, Mar 8, 2009 at 10:11 AM, Mikkel L. Ellertson
<mikkel infinity-ltd com> wrote:
> Richard Shaw wrote:
>> On Sun, Mar 8, 2009 at 9:49 AM, Mikkel L. Ellertson
>> <mikkel infinity-ltd com> wrote:
>>> Richard Shaw wrote:
>>>> Some other thoughts about hardware upgrades:
>>>>
>>>> Both machines I upgraded the ethernet changed to "eth1" but I'm not
>>>> sure where to get rid of the old settings but it's working so I may
>>>> leave it alone.
>>>>
>>> Udev keeps tract of some hardware. It is mainly so things like
>>> network interfaces and CD/DVD drives retain the same label when you
>>> add new hardware. (It is a pain when you add another NIC, and it
>>> becomes eth0...) You can fix it by deleting the
>>> *-persistent-*.rules. For NICs, it is 70-persistent-net.rules.
>>> Unless you transfered CD/DVD drives with the hard drives, you are
>>> going to find that the CD/DVD symlinks are wrong as well.
>>>
>>>> Maybe there could be some sort of hardware upgrade helper to help with
>>>> this process? It could install itself on your system as a rescue image
>>>> to help walk you though the process like preupgrade but for hardware.
>>>>
>>> That sounds like a good idea. Maybe an option in the rescue mode to
>>> rebuild the initrd image. Also a command in /sbin to delete the
>>> persistent rules...
>>>
>>> Mikkel
>>
>> Thanks, I forgot about that. I had a similar thing happen when I
>> upgraded DVD burners and completely forgot about udev rules. Hmm...
>> along with a hw version of preupgrade maybe a udev device editor would
>> be nice too?
>>
>> Richard
>>
> Well, you can edit the rules by hand. But it is just as easy to
> delete them. Udev will the re-create them on boot for the new
> hardware. The first NIC it finds will be eth0, the first CD/DVD with
> be cdrom and cdrom0, etc...
>
> Mikkel

Well since we're talking about a tool that doesn't exist yet, maybe
the yet to exist program hw-preupgrade could just clear all the system
specific rules out as a standard practice?

Richard


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]