Recent content by Cephei

For sure! Thank you Stoiko!

Scrubbing definitely fixes it for the scrubbed pool. I guess the error message isn't joking about scan property not being optional.

Proxmox is installed on a single sata ssd in ext4. I do see the blue grub menu on boot. root@pve:~# efibootmgr -v BootCurrent: 0011 Timeout: 5 seconds BootOrder: 0011,0000,0005 Boot0000* Hard Drive BBS(HD,,0x0)P0: INTEL SSDSC2MH120A2 . Boot0005* Internal EFI Shell...

Thank you for your hard work!!! :)

I have just tried adding a delay to zfs-import@.service (30 sec) and now the service started 30 seconds after the disk was attached. Still failed though. But now because the pool was imported by something else by then - "cannot import 'sas-backup': a pool with that name already exists". Btw, I...

The timeout was set by adding ZFS_INITRD_PRE_MOUNTROOT_SLEEP='10' to /etc/default/zfs and I then ran "update-initramfs -k all -u" and reboot - same issue. I have also tried adding GRUB_CMDLINE_LINUX_DEFAULT="rootdelay=10 quiet" in grub config and updating grub - same issue. root@pve:~# zfs...

Just tried the fix - still experiencing the same issue. Tried adding the drop-in for both zfs-import@.service and my pool specifically zfs-import@sas\\x2dbackup.service. There's already "After=systemd-udev-settle.service" requirement though, so unless systemd-udev-settle.servicefails to start, I...

Getting "Result verification failed (400) scan: property is missing and it is not optional" error when trying to open details for ZFS storage. Fairly fresh install of proxmox with latest updates. Version info: This was working fresh after install/update, not sure what the exact steps that led...

@Stoiko Ivanov Thank you for your response. Just rebooted the system, attached are 'journalctl -b 'and 'dmesg'. I wasn't aware that you need to disable the pool specific import service if the pool is deleted. I guess it makes sense since the pool is deleted from CLI directly. I have also...

Thanks for your feedback. I see what you mean, however this is a new install of proxmox, all the drives have been wiped of all partitions and zapped with gdisk. "sas-backup" pool is brand new to this system and there should be no reason to disable the service. All the pools are imported after...

I have 3 SAS drives connected through a RAID card in JBOD, proxmox can see the drives properly, pool 'sas-backup' is made up of 1 vdev with single SAS drive and pool 'sas-vmdata' is made up of single vdev which in turn is built from 2 mirrored SAS drives. Everything seems to be working fine...