[Bug 1987573] Re: /home on btrfs subvolume shared with / stops boot; adding nofail to fstab fixes it
Bill
1987573 at bugs.launchpad.net
Mon Aug 29 15:16:58 UTC 2022
The `journalctl -xb` output is attached. The error is noted at time
"Aug 29 11:12:19". I had to press Ctrl-D at the right moment during
boot so that I could get this output. For clarity, I removed the
"nofail" to get this error again, and it is reproducible by
adding/removing "nofail".
** Attachment added: "journalctl.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1987573/+attachment/5612388/+files/journalctl.txt
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1987573
Title:
/home on btrfs subvolume shared with / stops boot; adding nofail to
fstab fixes it
Status in systemd package in Ubuntu:
Incomplete
Bug description:
After performing `do-release-upgrade` from 20.04 to 22.04.01, the
system failed to boot with a message of:
Failed to mount /home
Dependency failed for Local File Systems.
It took some work to figure out, but adding "nofail" to the fstab line
allowed boot to proceed, and with that, the system appears to be
working without issue.
Both /boot and /home are mounted from subvolumes on the same btrfs
filesystem. The working fstab is below:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
LABEL=Root / btrfs defaults,subvol=@ 0 1
LABEL=Root /home btrfs defaults,subvol=@home,nofail 0 2
LABEL=EscherBackup /mnt/EscherBackup btrfs defaults 0 2
LABEL=PicassoBackup /mnt/PicassoBackup btrfs defaults 0 2
LABEL=scratch /mnt/scratch btrfs defaults 0 2
/dev/mapper/cryptswap1 none swap sw 0 0
/dev/mapper/cryptswap2 none swap sw 0 0
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.13
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
Date: Wed Aug 24 20:16:42 2022
EcryptfsInUse: Yes
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to jammy on 2022-08-24 (0 days ago)
VarLogDistupgradeXorgFixuplog:
INFO:root:/usr/bin/do-release-upgrade running
INFO:root:No xorg.conf, exiting
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1987573/+subscriptions
More information about the foundations-bugs
mailing list