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
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
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
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
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
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
6 matches
Mail list logo
