[SOLVED] ZFS storage "Detail" produces "Result verification failed (400)" error

Cephei · Feb 24, 2021

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:

root@pve:~# pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.98-1-pve)
pve-manager: 6.3-4 (running version: 6.3-4/0a38c56f)
pve-kernel-5.4: 6.3-5
pve-kernel-helper: 6.3-5
pve-kernel-5.4.98-1-pve: 5.4.98-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.0-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.7
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-4
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.8-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-5
pve-cluster: 6.2-1
pve-container: 3.3-4
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.2.0-1
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-5
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.3-pve1

This was working fresh after install/update, not sure what the exact steps that led to this are. Actual pools are operational.

Code:

root@pve:~# zpool status
  pool: sas-backup
 state: ONLINE
config:

        NAME                      STATE     READ WRITE CKSUM
        sas-backup                ONLINE       0     0     0
          scsi-35000c5009699d147  ONLINE       0     0     0

errors: No known data errors

  pool: sas-vmdata
 state: ONLINE
config:

        NAME                        STATE     READ WRITE CKSUM
        sas-vmdata                  ONLINE       0     0     0
          mirror-0                  ONLINE       0     0     0
            scsi-35000cca02c2a3824  ONLINE       0     0     0
            scsi-35000cca02c2a2804  ONLINE       0     0     0

errors: No known data errors

  pool: sata-str0
 state: ONLINE
config:

        NAME                                 STATE     READ WRITE CKSUM
        sata-str0                            ONLINE       0     0     0
          mirror-0                           ONLINE       0     0     0
            ata-ST8000VN004-2M2101_WKD3CXWW  ONLINE       0     0     0
            ata-ST8000VN004-2M2101_WKD3CYB4  ONLINE       0     0     0

errors: No known data errors

Code:

root@pve:~# zpool list
NAME         SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP    HEALTH  ALTROOT
sas-backup  1.62T   804K  1.62T        -         -     0%     0%  1.00x    ONLINE  -
sas-vmdata  1.62T  1.15G  1.62T        -         -     0%     0%  1.00x    ONLINE  -
sata-str0   7.27T   804K  7.27T        -         -     0%     0%  1.00x    ONLINE  -

tafkaz · Feb 24, 2021

same issue here too on a new installation with 6.3-3.
We don't have the problem on a setup that we upgraded to 6.3-3 from an older version.
Any hint appreciated
Sascha

Stoiko Ivanov · Feb 25, 2021

hmm - from a quick glance - yes the zpool output lacks the scan: line (which shows the result of the latest scrub)

since those a fresh systems - if possible would you mind running a zpool scrub on one of the pools and see if the line shows up? (sata-str0 looks quite empty)

Thanks!

Cephei · Feb 25, 2021

Stoiko Ivanov said:
hmm - from a quick glance - yes the zpool output lacks the scan: line (which shows the result of the latest scrub)

since those a fresh systems - if possible would you mind running a zpool scrub on one of the pools and see if the line shows up? (sata-str0 looks quite empty)

Thanks!

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

guerby · Feb 25, 2021

Got the same web UI issue, and scrub fixed it, thanks!

While looking a zpool status I noticed a suggestion about running zpool upgrade:

Code:

pool: rpool
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
    still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
    the pool may no longer be accessible by software that does not support
    the features. See zpool-features(5) for details.
  scan: scrub repaired 0B in 00:00:09 with 0 errors on Thu Feb 25 22:24:26 2021

Is it safe to do it?

Stoiko Ivanov · Feb 25, 2021

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

I could try to argue, that having a zpool, which has never been scrubbed is worth an error message

- but jokes aside - thanks for reporting this (cosmetic) glitch - I sent a patch for discussion:

https://lists.proxmox.com/pipermail/pve-devel/2021-February/047158.html

Stoiko Ivanov · Feb 25, 2021

guerby said:
Got the same web UI issue, and scrub fixed it, thanks!

While looking a zpool status I noticed a suggestion about running zpool upgrade:

please don't hijack threads for unrelated issues, but rather start a new one.

I tried to answer the question here:
https://forum.proxmox.com/threads/z...ppears-to-be-imported-after.84784/post-372922

in any case - if you have a rpool and boot with grub, I would not recommend upgrading the pool - if you boot with systemd-boot (UEFI system, installed with the PVE-installer 5.4 or later) then this should not be problematic

I hope this helps!

guerby · Feb 25, 2021

Stoiko Ivanov said:
please don't hijack threads for unrelated issues, but rather start a new one.

I tried to answer the question here:
https://forum.proxmox.com/threads/z...ppears-to-be-imported-after.84784/post-372922

in any case - if you have a rpool and boot with grub, I would not recommend upgrading the pool - if you boot with systemd-boot (UEFI system, installed with the PVE-installer 5.4 or later) then this should not be problematic

I hope this helps!

Yes it helps a lot, thanks! (we're all UEFI boot without grub, I'll test and report in the other thread)

Cephei · Feb 26, 2021

Stoiko Ivanov said:
I could try to argue, that having a zpool, which has never been scrubbed is worth an error message - but jokes aside - thanks for reporting this (cosmetic) glitch - I sent a patch for discussion:

https://lists.proxmox.com/pipermail/pve-devel/2021-February/047158.html

For sure! Thank you Stoiko!

tafkaz · Feb 26, 2021

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

works as expected now, thanks a lot!

eduncan911 · Mar 26, 2021

V6.3-6
Same issue. Scrubbing fixed it for me as well.

jerrymoushu · Mar 29, 2021

scrubbing fixed for me.

cpzengel · Mar 30, 2021

the pve gui is just checking zpool status for "scan:"
new systems never have been scanned

so for example

zpool scrub rpool && zpool scrub -s rpool

fixes the gui

Search

Search

[SOLVED] ZFS storage "Detail" produces "Result verification failed (400)" error

Cephei

New Member

Attachments

tafkaz

Renowned Member

Stoiko Ivanov

Proxmox Staff Member

Cephei

New Member

guerby

Member

Stoiko Ivanov

Proxmox Staff Member

Stoiko Ivanov

Proxmox Staff Member

guerby

Member

Cephei

New Member

tafkaz

Renowned Member

eduncan911

New Member

jerrymoushu

New Member

cpzengel

Renowned Member