At Tue, 11 Aug 2015 23:24:13 +0100, Richard Lewis wrote:
Hello ALUG,
For a couple of weeks now I've been getting this problem on my Debian "unstable" laptop. I use LVM for the partitions on my HDD and I'm finding that, maybe three out of four boots, the partition where /home is mounted doesn't get activated.
It uses systemd for booting. The boot sequence continues as normal (AFACT) until after
[ OK ] Mounted /boot
Then it waits for a bit, then I see:
[****] A start job is running for dev-mapper-slab/x2dhome.device (42s / 1min 30s)
Then after the alloted time, it drops me into "emergency mode". I enter the root password and I can then get the logical volume for /home to mount:
# vgchange -ay slab
i.e. I set the slab volume group as active and all its logical volumes become active. I can also see from here that, while the other two logical volumes in my volume group are both
LV status available
(these are /dev/slab/root, where / is mounted, and /dev/slab/swap_1 which is where swap is), the /dev/slab/home logical volume is:
LV status NOT available
After I issue the vgchange command, I see the kernel message:
EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
I can then exit "emergency mode" and booting proceeds to the login prompt. From then onwards everything is normal.
This problem seems to have gone away. There has been a kernel upgrade, a systemd upgrade, and a udev upgrade recently; it's possible that one of those fixed something.
Richard