Updates after 8-16-26 result in emergency mode and failure to mount home when using non-BTRFS filesystems (ext4/XFS) #124

New issue

Open

opened 2026-08-28 14:53:39 +00:00 by cecoates · 2 comments

cecoates commented

2026-08-28 14:53:39 +00:00

Describe the bug

Starting with the most recent updates, you get dumped into emergency mode after upgrading if you use ext4 or xfs.

You are in emergency mode. After logging in, type “journalctl -xb” to view system logs, “systemctl reboot” to reboot, or “exit” to continue bootup.

Loading any pinned deployment from 8-16-26 or earlier, system boots fine.

Reproduction steps

Install Fedora Silverblue using a filesystem other than BTRFS.
After install, update via rpm-ostree upgrade
Reboot

Expected behavior

System should boot as expected.

Actual behavior

System dumps you in emergency mode.

Journalctl logs indicate errors with mounting Home.

Aug 21 07:33:57 fedora kernel: virt/tdx: TDX not supported by the host platform
Aug 21 12:34:05 fedora systemd-fsck[930]: fsck failed with exit status 8.
Aug 21 12:34:05 fedora systemd[1]: home.mount: Mount path /home is not canonical (contains a symlink).
Aug 21 12:34:05 fedora systemd[1]: Failed to mount home.mount - Home Partition.
Aug 21 12:34:05 fedora systemd[1]: home.mount: Mount path /home is not canonical (contains a symlink).
Aug 21 12:34:05 fedora systemd[1]: Failed to mount home.mount - Home Partition.
Aug 21 12:34:06 fedora kernel: UBSAN: array-index-out-of-bounds in drivers/net/wireless/mediatek/mt76/mt7921/mcu.c:474:15
Aug 21 12:34:06 fedora kernel: index 3 is out of range for type 'void *[3]'
Aug 21 12:34:06 fedora systemd-tmpfiles[1045]: "/home" already exists and is not a directory.
Aug 21 12:34:06 fedora systemd-tmpfiles[1045]: "/srv" already exists and is not a directory.
Aug 21 12:34:06 fedora systemd-tmpfiles[1045]: "/root" already exists and is not a directory.
Aug 21 12:34:06 fedora systemd[1]: home.mount: Mount path /home is not canonical (contains a symlink).
Aug 21 12:34:06 fedora systemd[1]: Failed to mount home.mount - Home Partition.
Aug 21 12:35:12 fedora kernel: watchdog: watchdog0: watchdog did not stop!

System details

Fedora Silverblue version Version: 44.20260816.0 (2026-08-16T00:32:34Z)

Also affects Kinoite, if you upgrade to any version after the 8-16 update.

Desktop version.

Additional information or screenshots

https://discussion.fedoraproject.org/t/silverblue-updates-after-8-16-26-result-in-emergency-mode-and-failure-to-mount-home-when-using-ext4/200074

Even on a fresh install, this happens with any update post 8-16-26 if you do not use BTRFS.

You can initially boot, but after upgrading, you'll only see emergency mode.

Can be further tested by manually installing any update up to 8-16-26, and it will boot after expected. Go beyond 8-16-26, emergency mode.

### Describe the bug Starting with the most recent updates, you get dumped into emergency mode after upgrading if you use ext4 or xfs. ``` You are in emergency mode. After logging in, type “journalctl -xb” to view system logs, “systemctl reboot” to reboot, or “exit” to continue bootup. ``` Loading any pinned deployment from 8-16-26 or earlier, system boots fine. ### Reproduction steps 1. Install Fedora Silverblue using a filesystem other than BTRFS. 2. After install, update via rpm-ostree upgrade 3. Reboot ### Expected behavior System should boot as expected. ### Actual behavior System dumps you in emergency mode. Journalctl logs indicate errors with mounting Home. ``` Aug 21 07:33:57 fedora kernel: virt/tdx: TDX not supported by the host platform Aug 21 12:34:05 fedora systemd-fsck[930]: fsck failed with exit status 8. Aug 21 12:34:05 fedora systemd[1]: home.mount: Mount path /home is not canonical (contains a symlink). Aug 21 12:34:05 fedora systemd[1]: Failed to mount home.mount - Home Partition. Aug 21 12:34:05 fedora systemd[1]: home.mount: Mount path /home is not canonical (contains a symlink). Aug 21 12:34:05 fedora systemd[1]: Failed to mount home.mount - Home Partition. Aug 21 12:34:06 fedora kernel: UBSAN: array-index-out-of-bounds in drivers/net/wireless/mediatek/mt76/mt7921/mcu.c:474:15 Aug 21 12:34:06 fedora kernel: index 3 is out of range for type 'void *[3]' Aug 21 12:34:06 fedora systemd-tmpfiles[1045]: "/home" already exists and is not a directory. Aug 21 12:34:06 fedora systemd-tmpfiles[1045]: "/srv" already exists and is not a directory. Aug 21 12:34:06 fedora systemd-tmpfiles[1045]: "/root" already exists and is not a directory. Aug 21 12:34:06 fedora systemd[1]: home.mount: Mount path /home is not canonical (contains a symlink). Aug 21 12:34:06 fedora systemd[1]: Failed to mount home.mount - Home Partition. Aug 21 12:35:12 fedora kernel: watchdog: watchdog0: watchdog did not stop! ``` ### System details Fedora Silverblue version Version: 44.20260816.0 (2026-08-16T00:32:34Z) Also affects Kinoite, if you upgrade to any version after the 8-16 update. Desktop version. ### Additional information or screenshots https://discussion.fedoraproject.org/t/silverblue-updates-after-8-16-26-result-in-emergency-mode-and-failure-to-mount-home-when-using-ext4/200074 Even on a fresh install, this happens with any update post 8-16-26 if you do not use BTRFS. You can initially boot, but after upgrading, you'll only see emergency mode. Can be further tested by manually installing any update up to 8-16-26, and it will boot after expected. Go beyond 8-16-26, emergency mode.

cecoates added the

kind

bug

label

2026-08-28 14:53:39 +00:00

siosm commented

2026-08-28 15:43:45 +00:00

Owner

You will have similar messages on a working system so it's likely not where the issue is. There should be something else about the mount failure in the logs.

siosm added the

release

f44

label

2026-08-28 15:44:00 +00:00

siosm commented

2026-08-28 15:47:51 +00:00

Owner

Please use triple back quotes when posting logs (```). I've edited your message as an example.

It looks like https://discussion.fedoraproject.org/t/silverblue-updates-after-8-16-26-result-in-emergency-mode-and-failure-to-mount-home-when-using-ext4/200074/2 has more information.

Please use triple back quotes when posting logs (```). I've edited your message as an example. It looks like https://discussion.fedoraproject.org/t/silverblue-updates-after-8-16-26-result-in-emergency-mode-and-failure-to-mount-home-when-using-ext4/200074/2 has more information.

👍 1