Hello Brian, Brian May [2015-11-01 10:36 +1100]: > Brian May <[email protected]> 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...
Ah, ignore my previous reply, I didn't look at this bug too closely yet. | P: /devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb/sdb1 | E: ID_FS_UUID=f77d6ce8-12bf-476a-8276-2031ce3e3c42 | E: ID_BTRFS_READY=1 | | P: /devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc1 | E: ID_FS_UUID=f77d6ce8-12bf-476a-8276-2031ce3e3c42 | E: ID_BTRFS_READY=0 It's indeed very likely that this is due to the "mirrored" mode and both partitions have the same UUID. I guess this confuses the kernel driver and/or udev somehow? This ought to be reproducible in a VM. (Won't do it right now myself; too late, sorry.) To clarify, how exactly did you create this "mirrored" btrfs mode, to ensure we try the same thing for reproducing? Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) _______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
