zfs over iscsi problem no luns afer reboot

[BAMBR]

Good afternoon, I tried to implement ZFS over ISCSI and it worked successfully. I transferred virtual machines there, but after rebooting ISCSI server all the disks disappeared. As an ISCSI server, I used targetctl installed on the Proxmox Backup server. The service is there, but when I try to start it says:

Could not create StorageObject vmdisk-vm-121-disk-1: Device /dev/vmdisk/vm-121-disk-1 is not a TYPE_DISK block device, skipped
Could not create StorageObject vmdisk-vm-121-disk-0: Device /dev/vmdisk/vm-121-disk-0 is not a TYPE_DISK block device, skipped
Could not create StorageObject vmdisk-vm-122-disk-1: Device /dev/vmdisk/vm-122-disk-1 is not a TYPE_DISK block device, skipped
Could not create StorageObject vmdisk-vm-122-disk-0: Device /dev/vmdisk/vm-122-disk-0 is not a TYPE_DISK block device, skipped
Could not create StorageObject vmdisk-vm-127-disk-1: Device /dev/vmdisk/vm-127-disk-1 is not a TYPE_DISK block device, skipped
Could not find matching StorageObject for LUN 37, skipped
Could not find matching StorageObject for LUN 36, skipped
Could not find matching StorageObject for LUN 35, skipped
Could not find matching StorageObject for LUN 34, skipped


Is there a solution to this problem? what additionally data is needed?

rtslib-fb-targetctl.service
[Unit]
Description=Restore LIO kernel target configuration
Requires=sys-kernel-config.mount
After=sys-kernel-config.mount network.target local-fs.target zfs-import.target
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=mkdir -p /etc/rtslib-fb-target
ExecStart=/usr/bin/targetctl restore
ExecStop=/usr/bin/targetctl clear
SyslogIdentifier=target

[Install]
WantedBy=multi-user.target

Proxmox 7.4 pbs 8.1

 

[BAMBR]

I found a solution, proxmox 7 wants access to disks along the path /dev/"pool name", on the server side it looks like /dev/zpool/"pool name" in the iscsi service I added the creation of a symlink, everything worked

[Unit]
Description=Restore LIO kernel target configuration
Requires=sys-kernel-config.mount
After=sys-kernel-config.mount network.target local-fs.target zfs-import.target

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStartPre=+/usr/bin/ln -s /dev/zvol/vmdisk /dev/vmdisk
ExecStart=mkdir -p /etc/rtslib-fb-target
ExecStart=/usr/bin/targetctl restore
ExecStop=/usr/bin/targetctl clear
SyslogIdentifier=target

[Install]
WantedBy=multi-user.target



The topic can be closed, but the information can be left for posterity; apparently, in the latest version of ZFS 2.2, a symlink is not created.