Bug#509523: lvm2: LV is not recognized anymore
Hi all, I finally resolved my issue here. In my case, my LVM was on a raid array (/dev/md0). Somewhere along the way a partition table got created on /dev/md0. Newer versions of lvm automatically skip devices with partition tables which lead to the LV not being recognized. I zeroed out the partition table with dd if=/dev/zero of=/dev/md0 bs=512 count=1 and everything was detected again. This may be a problem for anyone upgrading from lenny, since 2.02.39 doesn't make this check and thus works, but once they upgrade to squeeze they may no longer have a working system. I'm not sure if there's any way to prevent this from biting anyone else when they upgrade. It certainly wasn't a pleasant experience for me. Thanks. Todd -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509523: lvm2: LV is not recognized anymore
Hi all, I've got the same problem. On my sid system with lvm2 version 2.02.62-1 lvscan output is empty. If I downgrade to 2.02.39-7 lvscan output is correct. If I reboot after installing 2.02.62-1 I get the volume group not found error and can't boot. Downgrade and re-rerun upgrade-initramfs -u and it's fine. Is there any major change/config file changes that have to be made between versions that need to be made to allow the lvm to be detected again? Let me know any other details you need. Thanks. Todd -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509523: lvm2: LV is not recognized anymore
be sure to check that you have the wanted keymap loaded otherwise you can be easily trapped! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509523: lvm2: LV is not recognized anymore
Thanks a lot for answering. Version: sid This is no valid version. Please be more accurate. Sorry, I cannot access the filesystem to check. I dist-upgraded the whole system from Sid on Thursday if that helps. Works flawless on my testsystem. Maybe you need a rootdelay=10. I tried that, but it did not help. Same error and ALERT! /dev/mapper/vg1_lv1 does not exist. Dropping to shell. I now think it could also be something with the encryption. With live CDs I can't cryptsetup luksOpen /dev/sda2 root although I am sure I know the password. I entered it a thousand times. My other password encrypted drive mounts fine from a rescue system.
Bug#509523: lvm2: LV is not recognized anymore
Package: lvm2 Version: sid Severity: critical Justification: breaks the whole system I updated the system and now this appears when I boot: Volume group vg1 not found File descriptor 3 left open Volume group vg1 not found cryptsetup: source device /dev/mapper/vg1-lv1 not found This is from my menu.lst: root(0,0) kernel /vmlinuz-2.6.26-1-amd64 root=/dev/mapper/vg1-lv1_crypt ro quiet initrd /initrd.img-2.6.26-1-amd64 I tried mounting the volume with the Lenny install CD, the live CD and with the two last versions of Ubuntu, but nothing seems to work. I saw a cryptsetup and a kernel update. Might that be the problem? I also checked the disk but it seems fine. -- System Information Debian Release: 5.0 Architecture: X86_64 Kernel: 2.6.26-1-amd64
Bug#509523: lvm2: LV is not recognized anymore
severity 509523 important tags 509523 moreinfo thanks On Tue, Dec 23, 2008 at 12:21:08AM +0100, Tom Arnold wrote: Package: lvm2 Version: sid This is no valid version. Please be more accurate. I updated the system and now this appears when I boot: I doubt that this is anything. This is from my menu.lst: root(0,0) kernel /vmlinuz-2.6.26-1-amd64 root=/dev/mapper/vg1-lv1_crypt ro quiet initrd /initrd.img-2.6.26-1-amd64 Works flawless on my testsystem. Maybe you need a rootdelay=10. Bastian -- Get back to your stations! We're beaming down to the planet, sir. -- Kirk and Mr. Leslie, This Side of Paradise, stardate 3417.3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
