I will try what you mention, to include '-x' in the script. Something I tried, by looking in forums, was to add these 3 lines at the end of the script
lvm vgchange -ay activate_vg "$ROOT" activate_vg "$resume" But that trick sometimes doesn't work. That '-x' will help me have more info. thanks! 2014-03-19 13:50 GMT-03:00 Bas Wijnen <wij...@debian.org>: > I'm running unstable, and have been affected by this bug for a few weeks > now, which is really annoying. After reading this bug report, I decided > to set the -x flag on /usr/share/initramfs-tools/scripts/local-top/lvm2, > the problem was quickly found: this script refuses any path which does > not start with /dev/mapper/. The root device is given as > /dev/disk/by-uuid/*, so it is not activated. > > Simple workaround: change the grub commandline from root=UUID=* to > root=/dev/mapper/vg-root (fill in your volume group and root logical > volume name). Then it will activate and boot normally. > > I expected that this should be done by changing /etc/fstab and running > update-grub, but grub will put UUID values in /boot/grub/grub.conf > anyway. So it must be done in /boot/grub/grub.conf, and repeated every > time update-grub is run (which isn't ideal, but a lot better than typing > commands every time the system boots). > > I'm guessing this bug was triggered by a change in grub to always write > UUIDs to its config. Still, it should be fixed by changing the > initramfs-tools script to make it allow the UUID-based path. > > Thanks, > Bas > -- Wido
