You are not logged in.

#1 2025-02-14 22:41:05

piperfw
Member
Registered: 2021-01-08
Posts: 30

[SOLVED] Failed to mount Huge File System Unable to boot (systemd bug)

Hi,

I am looking for advice on how to troubleshoot being unable to boot into my system after a (possibly botched) system upgrade.
This occurred after I was testing using the ansible syu.yml playbook to upgrade the system targeting localhost with ansible_conection=local. The Playbook reported running successfully, however I noticed my wired network wasn't operable, so I tried rebooting the system, only to encounter a series of [FAILURE] error messages starting from Failed to mount Huge File System, please see image at url below.

Booting from a live-USB, I can mount all the normal partitions (including /boot) and /etc/fstab looks fine. I can chroot also. So far I have tried reinstalling linux and regenerating intramfs, but not touched the bootloader (GRUB).

Any suggestions on what is causing this error or where to look would be appreciated. I had to go to work but the next things I was going to look at was: i. the pacman log to try to determine what exactly was upgraded (or not) when I ran the upgrade Playbook and ii. the system journal to see if there is more information on these failures.

An addition point of information is that I am using btrfs.

https://ibb.co/nNBd04WR

Last edited by piperfw (2025-02-15 12:24:02)

Offline

#2 2025-02-15 00:49:18

jupjohn
Member
Registered: 2025-02-14
Posts: 3

Re: [SOLVED] Failed to mount Huge File System Unable to boot (systemd bug)

You're potentially running into the same problem reported under https://bbs.archlinux.org/viewtopic.php?id=303424

From your live USB, downgrade systemd to 257.2 and see if it works. I'll report this on GitLab now.

EDIT: I thought I had an account but I don't, so I can't report until my account request is looked into :\

Last edited by jupjohn (2025-02-15 00:57:20)

Offline

#3 2025-02-15 01:47:10

piperfw
Member
Registered: 2021-01-08
Posts: 30

Re: [SOLVED] Failed to mount Huge File System Unable to boot (systemd bug)

That was it, thank you @jupjohn for noticing this for me.

It would explain why my network service went down, and in fact I remember trying to restart it with systemctl and nothing happened. I'll mark as solved and indicate I also have the issue in the linked thread.

For reference, due to dependencies I had to downgrade the following: systemd, systemd-libs, systemd-resolvconf, systemd-sysvcompat, all from 257.3-1 to 257.2-2,

Offline

Board footer

Powered by FluxBB