Building/testing a server, running proxmox-ve: 9.1.0 (kernel: 6.17.9-1-pve), machine have 5 disks: 3x ssd, 1x nvme, 1x sata.
Disk1-ssd (OS), efi and boot partition are not encrypted, root file system (ext4) is on a luks encrypted partition, clevis/tang decrypt the luks partition so machine starts without user intervention.
Disks 2-ssd, disk3-ssd, disk-4-ssd are full disk luks encrypted, with zfs on top, on each disk a zfs pool is created (striped, so only 1 disk per pool, disk5-sata ext4 is for storing proxmox backup server encrypted backups only, so need to encrypt the sata disk in my opinion.
Every time the system boots, there are 3 errors (1 error per zfs pool) at the end in the journal log.
Those errors are only at boot, and not duplicated, so 1 error per pool after each boot.
There are no other errors related to this in the journal log, no errors in pools, status is healthy and online, I could open de storage in GUI and shell, vm's starts (at boot) runs fine, so no issue at all.
I added delays in /etc/default/grub and /etc/default/zfs, executed pve-efiboot-tool refresh, update-grub, update-initramfs -u -k all, reboot machine but still errors are shown.
I have no clue if I need to worry about those errors, or that I could ignore those safely?
It annoys me that those errors popup and that I don't get rid of them.
Could someone help me with this, or I am overprotective?
Have a nice day
Grt,
René
Feb 14 10:29:30 jupiter pvestatd[5517]: zfs error: cannot open 'disk4_ssd3': no such pool
Feb 14 10:29:31 jupiter zed[5836]: eid=2 class=config_sync pool='disk4_ssd3'
Feb 14 10:29:31 jupiter zed[5837]: eid=3 class=pool_import pool='disk4_ssd3'
Feb 14 10:29:31 jupiter zed[5870]: eid=5 class=config_sync pool='disk4_ssd3'
Feb 14 10:29:31 jupiter pvestatd[5517]: zfs error: cannot open 'disk1_nvme': no such pool
Feb 14 10:29:31 jupiter zed[6080]: eid=7 class=config_sync pool='disk1_nvme'
Feb 14 10:29:31 jupiter zed[6083]: eid=8 class=pool_import pool='disk1_nvme'
Feb 14 10:29:31 jupiter zed[6114]: eid=10 class=config_sync pool='disk1_nvme'
Feb 14 10:29:31 jupiter pvestatd[5517]: zfs error: cannot open 'disk3_ssd2': no such pool
Feb 14 10:29:31 jupiter zed[6329]: eid=12 class=config_sync pool='disk3_ssd2'
Feb 14 10:29:31 jupiter zed[6330]: eid=13 class=pool_import pool='disk3_ssd2'
Feb 14 10:29:31 jupiter zed[6361]: eid=15 class=config_sync pool='disk3_ssd2'
Disk1-ssd (OS), efi and boot partition are not encrypted, root file system (ext4) is on a luks encrypted partition, clevis/tang decrypt the luks partition so machine starts without user intervention.
Disks 2-ssd, disk3-ssd, disk-4-ssd are full disk luks encrypted, with zfs on top, on each disk a zfs pool is created (striped, so only 1 disk per pool, disk5-sata ext4 is for storing proxmox backup server encrypted backups only, so need to encrypt the sata disk in my opinion.
Every time the system boots, there are 3 errors (1 error per zfs pool) at the end in the journal log.
Those errors are only at boot, and not duplicated, so 1 error per pool after each boot.
There are no other errors related to this in the journal log, no errors in pools, status is healthy and online, I could open de storage in GUI and shell, vm's starts (at boot) runs fine, so no issue at all.
I added delays in /etc/default/grub and /etc/default/zfs, executed pve-efiboot-tool refresh, update-grub, update-initramfs -u -k all, reboot machine but still errors are shown.
I have no clue if I need to worry about those errors, or that I could ignore those safely?
It annoys me that those errors popup and that I don't get rid of them.
Could someone help me with this, or I am overprotective?
Have a nice day
Grt,
René
Feb 14 10:29:30 jupiter pvestatd[5517]: zfs error: cannot open 'disk4_ssd3': no such pool
Feb 14 10:29:31 jupiter zed[5836]: eid=2 class=config_sync pool='disk4_ssd3'
Feb 14 10:29:31 jupiter zed[5837]: eid=3 class=pool_import pool='disk4_ssd3'
Feb 14 10:29:31 jupiter zed[5870]: eid=5 class=config_sync pool='disk4_ssd3'
Feb 14 10:29:31 jupiter pvestatd[5517]: zfs error: cannot open 'disk1_nvme': no such pool
Feb 14 10:29:31 jupiter zed[6080]: eid=7 class=config_sync pool='disk1_nvme'
Feb 14 10:29:31 jupiter zed[6083]: eid=8 class=pool_import pool='disk1_nvme'
Feb 14 10:29:31 jupiter zed[6114]: eid=10 class=config_sync pool='disk1_nvme'
Feb 14 10:29:31 jupiter pvestatd[5517]: zfs error: cannot open 'disk3_ssd2': no such pool
Feb 14 10:29:31 jupiter zed[6329]: eid=12 class=config_sync pool='disk3_ssd2'
Feb 14 10:29:31 jupiter zed[6330]: eid=13 class=pool_import pool='disk3_ssd2'
Feb 14 10:29:31 jupiter zed[6361]: eid=15 class=config_sync pool='disk3_ssd2'