You are not logged in.

Pages: 1

#1 2026-07-06 21:34:40

8ar10der
Member
Registered: 2023-04-20
Posts: 6

[SOLVED] migrate udev HOOK to systemd, boot part mount failed.

Hi all,

Today, I was performing scheduled maintenance on my two-year-old server, merging pacnew files.
Whilst I was at it, I decided to try replacing the udev hooks with systemd hooks to see if that would work better. As a result, the system failed to boot; although the kernel loaded, the filesystem failed to mount. Here is the detailed log:

[OK] Reached target Initrd Root Device.
Mounting / .snapshots.
Mounting /home..
Mounting /var/cache/pacman/pka...
Mounting /var/log...
Starting File System Check on /dev/disk/by-partuuid/537cfa05-Oce7-47e6-a164-d0227918e721..
[FAILED] Failed to mount boot.
See 'systemctl status boot mount' for details.
[DEPEND] Dependency failed for Local File Systems.
[OK] Finished File System Check on /dev/disk/by-partuuid/537cfa05-0ce7-47e6-a161-d0227918e721.
[OK] Started Emergency Shell.
[OK] Reached target Emergence Mode.
[OK] Reached target Initrd File Systems.
.......
[ OK ] Finished Load Kernel Modules.
You are in emergency mode. After logging in, type
"journalctI-xb" to view
system logs,
"systemctI reboot" to reboot, or
'exit'
to continue bootup.
Cannot open access to console, the root account is locked.
See sulog in (8) man page for more details.
Press Enter to continue

Here is how my HOOKS changed in the mkinitcpio.conf:

# NEW but not work
#HOOKS=(base systemd autodetect microcode modconf kms keyboard sd-vconsole block zfs filesystems fsck)

# OLD but work
HOOKS=(base udev autodetect keyboard keymap modconf block zfs filesystems fsck)

I have no idea why the root account is locked in the emergency mode, and also I fsck the boot part before I rerun the mkinitcpio -P, no error on the boot fat.

Here is some more info you may want to check:

❯ cat /etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2
UUID=2f22ffbf-d6a2-4689-8c7c-fe4ccb22e831       /               btrfs           rw,relatime,ssd,discard=async,space_cache=v2,subvolid=256,subvol=/@     0 0

# /dev/sda2
UUID=2f22ffbf-d6a2-4689-8c7c-fe4ccb22e831       /home           btrfs           rw,relatime,ssd,discard=async,space_cache=v2,subvolid=257,subvol=/@home 0 0

# /dev/sda2
UUID=2f22ffbf-d6a2-4689-8c7c-fe4ccb22e831       /var/log        btrfs           rw,relatime,ssd,discard=async,space_cache=v2,subvolid=258,subvol=/@log  0 0

# /dev/sda2
UUID=2f22ffbf-d6a2-4689-8c7c-fe4ccb22e831       /var/cache/pacman/pkg   btrfs           rw,relatime,ssd,discard=async,space_cache=v2,subvolid=259,subvol=/@pkg  0 0

# /dev/sda2
UUID=2f22ffbf-d6a2-4689-8c7c-fe4ccb22e831       /.snapshots     btrfs           rw,relatime,ssd,discard=async,space_cache=v2,subvolid=260,subvol=/@.snapshots   0 0

# /dev/sda1
UUID=D77D-EDA0          /boot           vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro   0 2

# /dev/sdb1
UUID=b1ecb747-c86c-4fd8-9472-4ca0c5d462a7       /data/hgst.10t.hdd      btrfs           rw,relatime,space_cache=v2,subvolid=256,subvol=/@       0 0
UUID=b1ecb747-c86c-4fd8-9472-4ca0c5d462a7       /data/hgst.10t.hdd/backup       btrfs           rw,relatime,space_cache=v2,subvolid=257,subvol=/@backup 0 0
UUID=b1ecb747-c86c-4fd8-9472-4ca0c5d462a7   /data/hgst.10t.hdd/amao btrfs       rw,relatime,space_cache=v2,subvolid=260,subvol=@/amao 0 0

# Cockpit
UUID=5354a609-e9a0-4ffc-b567-4a823a08be5b /data/samsung.256g.ssd auto nofail 0 0

-----------------------------------

❯ lsblk -f
NAME        FSTYPE     FSVER LABEL  UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1      vfat       FAT32        D77D-EDA0                             365.4M    28% /boot
└─sda2      btrfs            ssd    2f22ffbf-d6a2-4689-8c7c-fe4ccb22e831                /var/lib/containers/storage/overlay
                                                                                        /var/log
                                                                                        /home
                                                                                        /var/cache/pacman/pkg
                                                                                        /.snapshots
                                                                                        /
sdb
└─sdb1      btrfs            hdd    b1ecb747-c86c-4fd8-9472-4ca0c5d462a7    3.2T    65% /data/hgst.10t.hdd/backup
                                                                                        /data/hgst.10t.hdd/amao
                                                                                        /data/hgst.10t.hdd
sdc
├─sdc1      zfs_member 5000  fourzu 10619140639811098791
└─sdc9
sdd
├─sdd1      zfs_member 5000  fourzu 10619140639811098791
└─sdd9
sde
├─sde1      zfs_member 5000  fourzu 10619140639811098791
└─sde9
sdf
├─sdf1      zfs_member 5000  fourzu 10619140639811098791
└─sdf9
zram0       swap       1     zram0  c8c2e98f-0a43-44c6-bf81-aa7fdd86301f                [SWAP]
nvme0n1
└─nvme0n1p1 ext4       1.0          5354a609-e9a0-4ffc-b567-4a823a08be5b   97.9G    53% /data/samsung.256g.ssd

Last edited by 8ar10der (Yesterday 15:34:03)

Offline

#2 2026-07-06 22:06:27

tekstryder
Member
Registered: 2013-02-14
Posts: 582

Re: [SOLVED] migrate udev HOOK to systemd, boot part mount failed.

See:

• https://bbs.archlinux.org/viewtopic.php?id=313945

And new red warning in da wiki:

• https://wiki.archlinux.org/title/Instal … Arch_Linux

Last edited by tekstryder (2026-07-06 22:09:27)

Offline

#3 2026-07-06 23:17:58

8ar10der
Member
Registered: 2023-04-20
Posts: 6

Re: [SOLVED] migrate udev HOOK to systemd, boot part mount failed.

tekstryder wrote:

Oh hi.

I don't think they're related since my root isn't on ZFS. And the mounting failed is pointing to the boot partition.

But I should try to remove ZFS from the array, it shouldn't be there.

Offline

#4 2026-07-06 23:18:53

WorMzy
Administrator
From: Scotland
Registered: 2010-06-16
Posts: 13,579
Website

Re: [SOLVED] migrate udev HOOK to systemd, boot part mount failed.

Mod note: moving to AUR Issues

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Online

#5 2026-07-06 23:26:24

8ar10der
Member
Registered: 2023-04-20
Posts: 6

Re: [SOLVED] migrate udev HOOK to systemd, boot part mount failed.

WorMzy wrote:

Mod note: moving to AUR Issues

Hi,

I think this is a not correct moving. My issue is not related any AUR things, it is about mkinitcpio and hooks.

Offline

#6 2026-07-06 23:55:27

tekstryder
Member
Registered: 2013-02-14
Posts: 582

Re: [SOLVED] migrate udev HOOK to systemd, boot part mount failed.

Arch does not support ZFS via official package repositories.

So how was your previously functional system implemented?

Offline

#7 Yesterday 12:43:15

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,181

Re: [SOLVED] migrate udev HOOK to systemd, boot part mount failed.

Mounting / .snapshots.
Mounting /home..
Mounting /var/cache/pacman/pka...
Mounting /var/log...

/home is normally not needed until later in the start process, and the other 3 mounts suggests you have a non-standard setup .

Please remove the zfs hook to verify if it is involved or not.

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Online

#8 Yesterday 15:31:32

8ar10der
Member
Registered: 2023-04-20
Posts: 6

Re: [SOLVED] migrate udev HOOK to systemd, boot part mount failed.

Yes, removing ZFS from the hooks solved the problem. It never should have been there in the first place; I don't use ZFS as root.

Offline

Pages: 1

Board footer

Powered by FluxBB