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

Re: [linux-lvm] Uuid for unknown device blows up VolGroup00

Teak Billard wrote:
> I recently tried to add an old 30 GB hard drive lying in my machine to
> my FC5 system.  I was trying to add the 30 GB to VolGroup00.  I failed
> somehow and now the entire VolGroup00 is inaccessible.  When booting I
> get a Kernel panic - not syncing: Attempted to kill init!  I think if I
> removed the offending Uuid from VolGroup00 things would go back to normal.
> ....
> When I do an lvm pvdisplay, it reveals that VolGroup00 has two uuid's in
> it. One is /dev/hdb3 with uuid M3CWKv-a2yK-b5Qu-rLzq-Aj27-lXxE-WzvkWE
> and the other is unknown device with uuid
> 8YsyEa-r5RX-2LLI-Zz7n-Xr8s-VksP-Mhs0Wi.

seems you did NOT fail adding the new disk. Have a look into your 
/etc/lvm/backup/VolGroup00 to find how your VG is composed.

It seems, you succeed in adding the disk, but you finally did
not use it and disconnected it. LVM however has registered
the new disk, even if you did not copy any data to it.

You should reconnect the formerly added disk and unregister
it from your volume group by "vgreduce". If you don't have the
disk any more or used it elsewhere, you may try the option
"vgreduce --removemissing".

> I failed somehow and now ...

can you tell us, why it did not work as you expected?


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