You are not logged in.
While testing on a separate disk and in virtual machines I didn't see these errors, but now that I'm reinstalling my main PC I am getting the following:
:: running early hook [udev]
starting version 229
:: running hook [udev]
:: triggering uevents...
ash: 1: unknown operand
cannot open 'zroot': no such pool
ZFS: importing pool zroot
:: running late hook [zfs]
:: running cleanup hook [udev]
Welcome to Arch Linux!
System boots fine. except that my second pool 'data' does not automount. It is imported and has its mountpoint set correctly, and I've set the cachefile using zpool set cachefile=/etc/zfs/zpool.cache data. When I check the parameter with zpool get cachefile data, the property is empty but while setting it no error is generated. --> forgot systemctl enable zfs.service
But more to the point, why am I seeing that 'ash: 1: unknown operand' and why does it say that it cannot open zroot 'no such pool', but continues to import pool zroot and seems to work fine?
I am using UEFI with systemd-boot, GPT disk and my boot partition is ext4. /boot/loader/entries/arch.conf contains
title arch linux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
options zfs=zroot/ROOT/default rw
Thanks in advance!
Last edited by mouseman (2016-04-28 21:17:56)
Offline
Thanks to a helpful guy on another forum I was directed to the following:
Prevent 'ash: 1: unknown operand' error when zfs_force option is not …
https://github.com/archzfs/archzfs/pull … ad22c67bd4
Script cleanup for zfs-utils.initcpio.hook #48
https://github.com/archzfs/archzfs/issues/48
Both my issues seem to be cosmetic and bugs in the script.
I suppose both are safe to ignore and hopefully get fixed.
Offline