Old ZFS pool still trying to import

[adresner]

Hello,

In the course of setting up my proxmox I added and deleted a few pools.

Watching my startup, I see:



One of them
(FAILED] Failed to start Import ZFS pool MARS
Is still trying to load at start.

I navigated to
cd /etc/systemd/system/zfs-import.target.wants/

Found
zfs-import@BASEMENT.service zfs-import-cache.service zfs-import@MARS.service zfs-import-scan.service zfs-import@VMDATA.service

zfs-import@MARS.service should not be there?

Any suggestions on how to clean this up? Why is the good pool Basement failing? But actually fine once I log into the GUI

Thank you

 

[adresner]

Following this thread: https://forum.proxmox.com/threads/o...-zfs-pool-that-was-removed.121826/post-529572

root@BKK-PVE:~# zpool get cachefile
NAME PROPERTY VALUE SOURCE
BASEMENT cachefile - default
VMDATA cachefile none local

root@BKK-PVE:~# zpool list
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
BASEMENT 3.62T 173G 3.46T - - 19% 4% 1.00x ONLINE -
VMDATA 1.81T 13.3G 1.80T - - 0% 0% 1.00x ONLINE -

root@BKK-PVE:/etc/systemd/system/zfs-import.target.wants# ls
zfs-import@BASEMENT.service zfs-import@MARS.service zfs-import@VMDATA.service
zfs-import-cache.service zfs-import-scan.service

If I understand correctly, the 2 following commands should clear this up?

systemctl disable zfs-import@pve\MARS.service

rm '/etc/systemd/system/zfs-import.target.wants/zfs-import@pve\MARS.service'

 

[adresner]

If someone gets a moment to look this over? Would appreciate it. Thank you

 

[supermarkert]

@adresner Did this end up working for you? I think I have the same issue.

 

[pgro]

Gday, This is an old Topic I know but what I got is strange.
Proxmox updated from 7 to 8 , then somehow an OLD pool appeared to my /etc/systemd/system/zfs-import.target.wants/

systemctl status zfs-import@backup01.service
○ zfs-import@backup01.service - Import ZFS pool backup01
     Loaded: loaded (/lib/systemd/system/zfs-import@.service; disabled; preset: enabled)
     Active: inactive (dead)
       Docs: man:zpool(8)

But :

 /etc/systemd/system/zfs-import.target.wants$: # ls -lah 
total 10K
drwxr-xr-x  2 root root  4 Sep 27 07:03 .
drwxr-xr-x 21 root root 34 Sep 26 10:29 ..
lrwxrwxrwx  1 root root 44 May  4  2022 zfs-import-cache.service -> /lib/systemd/system/zfs-import-cache.service
lrwxrwxrwx  1 root root 43 May  4  2022 zfs-import-scan.service -> /lib/systemd/system/zfs-import-scan.service

I can't see the service within /etc/systemd/system/zfs-import.target.wants . If I set the service to enabled then I can see it /etc/systemd/system/zfs-import.target.wants.

Just to mention that I have redifned again cachefile for my rpool. Now of course I can't do the same for backup01 since no longer existed

# zpool status
  pool: rpool
 state: ONLINE
  scan: resilvered 498G in 00:29:20 with 0 errors on Tue Sep 10 13:24:04 2024
remove: Removal of vdev 1 copied 7.73M in 0h0m, completed on Tue Sep 10 12:36:45 2024
        1.83K memory used for removed device mappings
config:

        NAME                              STATE     READ WRITE CKSUM
        rpool                             ONLINE       0     0     0
          mirror-0                        ONLINE       0     0     0
            wwn-0x50026b7686bba165-part3  ONLINE       0     0     0
            wwn-0x50026b7686bba1fb-part3  ONLINE       0     0     0

errors: No known data errors

where the heck is backup01 defined? Can't figure out.

Thanx

 

[pgro]

I've played a little bit also with other non existed pools

# systemctl status zfs-import@backup03.service
○ zfs-import@backup03.service - Import ZFS pool backup03
     Loaded: loaded (/lib/systemd/system/zfs-import@.service; disabled; preset: enabled)
     Active: inactive (dead)
       Docs: man:zpool(8)

 # systemctl status zfs-import@test-for-nothing.service 
○ zfs-import@test-for-nothing.service - Import ZFS pool test-for-nothing
     Loaded: loaded (/lib/systemd/system/zfs-import@.service; disabled; preset: enabled)
     Active: inactive (dead)
       Docs: man:zpool(8)

and it always return something, so maybe backup01 might not be defined somewhere.