Proxmox booting - zfs [FAILED] file system message shown

R

RainerM

Member
May 12, 2024
4
1
8
When ProxMox (8.4.19) boots, the following messages are shown on console:
Found volume group "svProxHD" using media type lmv2
Found volume group "pve" using media type lmv2
3 logical volume(s) in volume group "svProxHD" now active
6 logical volume(s) in volume group "pve" now active
/dev/mapper/pve-root: clean, 121300/5529600 files, 121300/22114304 blocks
“[FAILED] Failed to start zfs-import-scan.services - Import ZFS pools by device scanning.” appears on the console.
After the initial ProxMox installation, I didn’t get that [FAILED] ... message.


Background:
Some years ago, I installed OpenMediaVault (meanwhile updated to 7.7.24-7 Sandworm) on this ProxMox (meanwhile updated to 8.4.19) server.
The HD's for OVM data storage (5*12T HD's) are handed through to OMV as scsi and they were formated by OVM with zfs.
These HD's are exclusively used by OVM, means ProxMox should probably see the zfs file systems, but don't handle it.

Do I need to be concerned by that [FAILED] .. messge ?
How can / should the problem be handled ?

Are the (by OMV) zfs formated HD's also somehow handled by ProxMox ?
Does a (automatically) export/import function needed to be included somehow in ProxMox ?
If yes, how ?
Shouldn't that export/import be handled by OMV, since OMV is supposed to handle the HD's ?

If I'm correct, the export/import functions are neccessary if I would move the HD's into another computer.
Is that correct ?

Where can I find information / training on these ZFS functions ?

Thanks
Rainer
 
What is the output of systemctl status zfs-import-scan.service on the Proxmox host?
 
Last edited:
systemctl status zfs-import-scan.service
× zfs-import-scan.service - Import ZFS pools by device scanning
Loaded: loaded (/lib/systemd/system/zfs-import-scan.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Tue 2026-05-19 17:33:36 CEST; 1 day 19h ago
Docs: man:zpool(8)
Main PID: 679 (code=exited, status=1/FAILURE)
CPU: 45ms

May 19 17:33:36 svProx1 systemd[1]: Starting zfs-import-scan.service - Import ZFS pools by device scanning...
May 19 17:33:36 svProx1 zpool[679]: cannot import 'ZFSRaidZ2': pool was previously in use from another system.
May 19 17:33:36 svProx1 zpool[679]: Last accessed by sv4000 (hostid=3972ddfa) at Tue May 19 17:22:16 2026
May 19 17:33:36 svProx1 zpool[679]: The pool can be imported, use 'zpool import -f' to import the pool.
May 19 17:33:36 svProx1 systemd[1]: zfs-import-scan.service: Main process exited, code=exited, status=1/FAILURE
May 19 17:33:36 svProx1 systemd[1]: zfs-import-scan.service: Failed with result 'exit-code'.
May 19 17:33:36 svProx1 systemd[1]: Failed to start zfs-import-scan.service - Import ZFS pools by device scanning.

#--

But as I already wrote, does ProxMox also handle the HD's / file systems when the disks are handed over to OMV and they should be controlled by OMV. ?

On OMV I get the following output:

zpool status
pool: ZFSRaidZ2
state: ONLINE
status: Some supported and requested 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(7) for details.
scan: scrub repaired 0B in 15:32:46 with 0 errors on Sun May 10 15:56:47 2026
config:

NAME STATE READ WRITE CKSUM
ZFSRaidZ2 ONLINE 0 0 0
raidz2-0 ONLINE 0 0 0
scsi-0QEMU_QEMU_HARDDISK_drive-scsi1 ONLINE 0 0 0
scsi-0QEMU_QEMU_HARDDISK_drive-scsi2 ONLINE 0 0 0
scsi-0QEMU_QEMU_HARDDISK_drive-scsi3 ONLINE 0 0 0
scsi-0QEMU_QEMU_HARDDISK_drive-scsi4 ONLINE 0 0 0

errors: No known data errors
 
Since I don't use zfs on any other ProxMox disk, I disabled the zfs-import-scan.
Now ProxMox boots without showing any failure.
Thank you very much for your support.

Rainer
 
  • Like
Reactions: daanw
Thanks for the info.
I opted for ZFS with Direct Write-Through, as this seemed best suited for 5* 12 TB hard drives and I wanted OVM to manage the drives directly.

I had hoped to be able to easily move these data drives to another computer should this ProxMox server fail.


There is also one 10-TB hard drive, which is managed by ProxMox for all servers run by ProxMox.
OMV itself is also installed on it.
As described, the 5* 12-TB HDs are used solely for OMV data.

In addition, there is a 320-GB hard drive on which ProxMox itself is installed.


What would be the best methods and file systems to use today?
Any suggestions ?
 
You must log in or register to reply here.
Top Bottom
Back