I use the same btrfs layout (our installer creates @ and @home subvolumes automatically), with a similar fstab except for these weird device= options, and it works just fine. So I can't reproduce this yet. Can you please boot up to the point where you get into the rescue shell, then do
systemctl status -l systemd-fsck-root.service > /root/fsck-root-status.txt
journalctl -b > /root/journal.txt
then reboot back to upstart and attach the two files here? Thanks!
I use the same btrfs layout (our installer creates @ and @home subvolumes automatically), with a similar fstab except for these weird device= options, and it works just fine. So I can't reproduce this yet. Can you please boot up to the point where you get into the rescue shell, then do
systemctl status -l systemd- fsck-root. service > /root/fsck- root-status. txt
journalctl -b > /root/journal.txt
then reboot back to upstart and attach the two files here? Thanks!