Am 01.11.2015 um 00:36 schrieb Brian May: > Brian May <b...@debian.org> writes: >>> Can you boot with systemd.log_level=debug on the kernel command line and >>> attach the output of journalctl -alb. >>> >>> The output of udevadm info -e might be helpful as well. >> >> Have a vague feeling I may have tried systemd.log_level=debug and it >> didn't show anything useful. Not sure now. > > Have attached the output from the above commands. Hopefully this > helps... > > I have noticed the three messages at the bottom of the systemd.log keep > repeating every 40 seconds, not sure if this significant or not.
Quickly glancing over the udevadm dump, the following looks suspicious: P: /devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc1 N: sdc1 ... E: ID_BTRFS_READY=0 E: SYSTEMD_READY=0 That's most likely, why the device is not considered ready by udev/systemd, so no mount attempt is made. I vaguely remember issues with btrfs on raid (mirror). To me this looks like an issue with btrfs itself. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=74020 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747629 might be related / the same issue. Michael
signature.asc
Description: OpenPGP digital signature
