Michael Biebl <bi...@debian.org> writes:
> Can you attach your /etc/fstab please.
UUID=1308477f-22a4-48d7-9b82-8ff29e115234 / ext4
errors=remount-ro 0 1
UUID=AC4D-F9EE /boot/efi vfat defaults 0 1
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/sdc1 /btrfs btrfs defaults,noatime 0 0
/dev/sdc1 /home btrfs defaults,subvol=home,noatime 0 0
/dev/sdc1 /videos btrfs defaults,subvol=videos,noatime 0 0
> Also can you describe how your btrfs setup looks like.
/btrfs is mirrored on both /dev/sdb1 and /dev/sdc1
falidae# btrfs filesystem show /btrfs
Label: none uuid: f77d6ce8-12bf-476a-8276-2031ce3e3c42
Total devices 2 FS bytes used 978.25GiB
devid 1 size 1.82TiB used 981.03GiB path /dev/sdb1
devid 2 size 1.82TiB used 981.03GiB path /dev/sdc1
Thought there was a way to show it was mirrored, can't remember it right
now.
> After the 90 second timeout, are you dumped into the emergency
> console?
Yes.
> 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.
In any case, presumably you want these when it isn't working, so will
try to get it to fail again with the debug option and let you know.
--
Brian May <b...@debian.org>
