ERROR: device 'ZFS=zpcachyos/ROOT/cos/root' not found

Issues & Assistance
1

Upon booting there is the message:

... :: running hook [zfs] ERROR: device 'ZFS=zpcachyos/ROOT/cos/root' not found ZFS: Importing pool packages ...

I’m using grub as my bootloader.

/etc/default/grub:

... GRUB_CMDLINE_LINUX_DEFAULT='zfs=zpcachyos/ROOT/cos/root nowatchdog nvme_load=YES zswap.enabled=1 loglevel=3' ...

/etc/mkinitcpio.conf:

MODULES=(lz4 vmd zfs)
BINARIES=()
FILES=()
#HOOKS=(base udev autodetect microcode kms modconf block keyboard keymap consolefont plymouth zfs filesystems fsck)
HOOKS=(base udev block autodetect microcode kms modconf keyboard keymap zfs filesystems fsck)

COMPRESSION="lz4"

#COMPRESSION_OPTIONS=()
MODULES_DECOMPRESS="no"

zfs list:

NAME                                   USED  AVAIL  REFER  MOUNTPOINT
zpcachyos                             7.11G   454G    96K  none
zpcachyos/ROOT                        7.11G   454G    96K  none
zpcachyos/ROOT/cos                    7.11G   454G    96K  none
zpcachyos/ROOT/cos/root               5.52G   454G  4.98G  /
zpcachyos/ROOT/cos/root@working well   316M      -  4.93G  -
zpcachyos/ROOT/cos/root@setup          234M      -  4.93G  -
zpcachyos/ROOT/cos/varcache           1.59G   454G  1.59G  /var/cache
zpcachyos/ROOT/cos/varlog              204K   454G   204K  /var/log

It should be noted that I did recover a snapshot to make sure the snapshot feature worked, so zpcachyos/ROOT/cos/root is actually recovered, but I think the error was there before I did that (but not 100% sure).

Removing ‘fsck’ from from hooks makes the error message go away, but I’m presuming it’s a good idea to do a fsck at boot, so not sure if that’s an option.

Any ideas?

2

So, without the fsck hook this is away? Then we might remove it for zfs

1 Like
3

Two questions:

1: is this page relevant for you? fsck.zfs.8 — OpenZFS documentation

2: (Newbie question) If fsck is disabled as a hook, would that stop a fsck check on attached non-ZFS volumes?

4

Thanks. I was reinstalling and noticed that the ‘fsck’ hook was already gone on the new install.

You guys are fast! :slight_smile:

5

Yes, this helped a little. So they suggested using ‘zpool scrub zpcachyos’ to check the datasets (for integrity and corruption?).

Think I’ve got some reading to do. So much to learn.