Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

[Michael Biebl]

control: tags -1 moreinfo unreproducible

Am 18.04.2015 um 02:02 schrieb Rick Thomas:
> 
> On Apr 17, 2015, at 3:44 PM, Michael Biebl <biebl at debian.org> wrote:
>>
>> Thanks for the data.
>> Looks like an lvm issue to me:
>>
>> root at cube:~# lvscan
>>  inactive          '/dev/vg1/backup' [87.29 GiB] inherit
>>
>> and as a result, /dev/disk/by-label/BACKUP is missing.
> 
> Yes, that’s true, of course.  But the question is, what is keeping lvm from activating the volume?
> 
> It works fine for a logical volume on a single physical disk.  And /proc/mdstat shows that the RAID device, /dev/md127, _is_ active.  Or, at least it is when we get to emergency mode… I don’t know if it’s active when the fsck times out, of course… If you know how to figure that out from the systemd journal I attached to the original bug report, or any other way that I can try, I’d appreciate any assistance you can give!

fwiw, I tried to reproduce the problem in a VM with two additional disks
attached and a setup like the following:

ext4 on RAID1 (via mdadm)
ext4 on LVM on RAID1 (mdadm)
ext4 on LVM
ext4 on dos partition.

All partitions were correctly mounted during boot without any issues.


Is this a fresh jessie installation or an upgraded system?
Do you have any custom udev rules in /lib/udev/rules.d or /etc/udev/rules.d?

If it's an upgraded system and you have the sysvinit package installed,
you can try booting with sysvinit temporarily via
init=/lib/sysvinit/init on the kernel command line.

Does that work?



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150421/0c4209f8/attachment-0002.sig>