Just wanted to add that after doing a "vgrename" without first doing a
vgchange -an, I ended up with a system that could not activate the LV's
on boot. I had to drop to a root shell (via 'M') then type "vgchange
-ay" followed by "ctrl+d" to get a system (re)boot to complete
successfully. I'll add that I'm not sure if the vgrename without first
making unavailable caused the issue!!!
Anyhow, after much googling, I came across this bug and after following
the suggestion by Mark Tomich, namely:
SUBSYSTEM=="block", ACTION=="add|change", ENV{ID_TYPE}=="disk", \
RUN+="watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y'"
I can now (re)boot without it stopping to wait for manual intervention.
My system:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.4 LTS
Release: 12.04
Codename: precise
$ uname -a
Linux akk-m6700 3.11.0-19-generic #33~precise1-Ubuntu SMP Wed Mar 12 21:16:27
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
I'm running the kernel from - linux-image-generic-lts-saucy.
Cheers,
ak.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/147216
Title:
LVM filesystems not mounted at boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/147216/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
