I also got the status for dev-disk-by\x2duuid- 3ff68715\x2d0daa\x2d4e44\x2d8de2\x2d0997f36d8ab6.device/start which just had messages about file/directory not found without saying which ones it was looking for. (To be clear the status for that job was found just fine - the contents of the status is what complained. I lost the file due to rebooting etc.)
The uuid it is stuck on there is the one of the filesystem containing subvols @ and @home, and is shared by both parts - /dev/sda1 and /dev/sdb1. Also note that reverse lookups such as /dev/disk/by- uuid/3ff68715-0daa-4e44-8de2-0997f36d8ab6 can only point to one those two (sdb1 right now). And just to make life more interesting the SSDs are one set of two identical 256GB and one set of two identical 960GB. ** Attachment added: "blkid.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+attachment/4383539/+files/blkid.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: fscking btrfs mount fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
