[SOLVED] iSCSI in Synology. Recurrent error in log

jmcanedo · Mar 8, 2025

Hi all:
I have a ProxmoxVE installation and I'm using a Synology as iSCSI destination for a LVM.
I have created successfully the iSCSI Target and the LUN in my Synology. And connected also in the Proxmox server, It's working fine, I have several LXC using this LVM over iSCSI without problems.

However, I'm seeing recurrent errors in the log, related to a connetion error to the iSCSI destination in Synology.

Code:

Mar 08 10:43:57 proxmox iscsid[945]: Connection-1:0 to [target: iqn.2000-01.com.synology:DiskStation.Target-1.56b3371b4b7, portal: fe80::211:32ff:feb6:6af2,3260] through [iface: default] is shutdown.
Mar 08 10:43:58 proxmox pvestatd[902]: status update time (5.395 seconds)
Mar 08 10:44:05 proxmox iscsid[945]: connection-1:0 cannot make a connection to fe80::211:32ff:feb6:6af2:3260 (-1,22)
Mar 08 10:44:07 proxmox pvestatd[902]: command '/usr/bin/iscsiadm --mode node --targetname iqn.2000-01.com.synology:DiskStation.Target-1.56b3371b4b7 --login' failed: exit code 15

These are my configurations:

Code:

/etc/pve/storage.cfg
dir: local
        path /var/lib/vz
        content vztmpl,iso,backup

lvmthin: local-lvm
        thinpool data
        vgname pve
        content rootdir,images

nfs: SynologyNFS
        export /volume2/Proxmox
        path /mnt/pve/SynologyNFS
        server 192.168.1.10
        content images,backup,iso,vztmpl
        prune-backups keep-all=1

iscsi: SynologyiSCSI
        portal 192.168.1.10
        target iqn.2000-01.com.synology:DiskStation.Target-1.56b3371b4b7
        content none

lvm: SynologyLVM
        vgname SynologyiSCSI
        base SynologyiSCSI:0.0.1.scsi-3600140584963cbade0e7d4f60d823dd4
        content images,rootdir
        saferemove 0
        shared 1

nfs: SynologyVideo
        export /volume2/video
        path /mnt/pve/SynologyVideo
        server 192.168.1.10
        content images
        prune-backups keep-all=1

Code:

pvesm status

iscsiadm: default: 1 session requested, but 1 already present.
iscsiadm: Could not login to [iface: default, target: iqn.2000-01.com.synology:DiskStation.Target-1.56b3371b4b7, portal: fe80::211:32ff:feb6:6af2,3260].
iscsiadm: initiator reported error (8 - connection timed out)
iscsiadm: Could not log into all portals
Logging in to [iface: default, target: iqn.2000-01.com.synology:DiskStation.Target-1.56b3371b4b7, portal: fe80::211:32ff:feb6:6af2,3260]
command '/usr/bin/iscsiadm --mode node --targetname iqn.2000-01.com.synology:DiskStation.Target-1.56b3371b4b7 --login' failed: exit code 15
Name                 Type     Status           Total            Used       Available        %
SynologyLVM           lvm     active       524283904       140509184       383774720   26.80%
SynologyNFS           nfs     active      7742770688      3837821568      3904830336   49.57%
SynologyVideo         nfs     active      7742770688      3837821568      3904830336   49.57%
SynologyiSCSI       iscsi     active               0               0               0    0.00%
TuxisPBS              pbs     active       157286400        23268608       134017792   14.79%
local                 dir     active        40610280        20052840        18462336   49.38%
local-lvm         lvmthin     active        56836096               0        56836096    0.00%

Code:

pvesm list SynologyLVM

iscsiadm: default: 1 session requested, but 1 already present.
iscsiadm: Could not login to [iface: default, target: iqn.2000-01.com.synology:DiskStation.Target-1.56b3371b4b7, portal: fe80::211:32ff:feb6:6af2,3260].
iscsiadm: initiator reported error (8 - connection timed out)
iscsiadm: Could not log into all portals
Logging in to [iface: default, target: iqn.2000-01.com.synology:DiskStation.Target-1.56b3371b4b7, portal: fe80::211:32ff:feb6:6af2,3260]
command '/usr/bin/iscsiadm --mode node --targetname iqn.2000-01.com.synology:DiskStation.Target-1.56b3371b4b7 --login' failed: exit code 15
Volid                       Format  Type             Size VMID
SynologyLVM:vm-20160-disk-0 raw     rootdir   53687091200 20160
SynologyLVM:vm-20161-disk-0 raw     rootdir    8589934592 20161
SynologyLVM:vm-20163-disk-0 raw     rootdir    6442450944 20163
SynologyLVM:vm-20166-disk-0 raw     rootdir    8589934592 20166
SynologyLVM:vm-20168-disk-0 raw     rootdir    2147483648 20168
SynologyLVM:vm-20169-disk-0 raw     rootdir    4294967296 20169
SynologyLVM:vm-20171-disk-0 raw     rootdir    7516192768 20171
SynologyLVM:vm-20172-disk-0 raw     rootdir   16106127360 20172
SynologyLVM:vm-20173-disk-0 raw     rootdir   16106127360 20173
SynologyLVM:vm-20175-disk-0 raw     rootdir    2147483648 20175
SynologyLVM:vm-20176-disk-0 raw     rootdir    2147483648 20176
SynologyLVM:vm-20177-disk-0 raw     rootdir    5368709120 20177
SynologyLVM:vm-20178-disk-0 raw     rootdir   10737418240 20178

Code:

iscsiadm -m node

192.168.1.10:3260,1 iqn.2000-01.com.synology:DiskStation.Target-1.56b3371b4b7
[fe80::211:32ff:feb6:6af2]:3260,1 iqn.2000-01.com.synology:DiskStation.Target-1.56b3371b4b7
192.168.1.10:3260,1 iqn.2000-01.com.synology:DiskStation.Target-11.56b3371b4b7
[fe80::211:32ff:feb6:6af2]:3260,1 iqn.2000-01.com.synology:DiskStation.Target-11.56b3371b4b7

Code:

iscsiadm -m session

tcp: [1] 192.168.1.10:3260,1 iqn.2000-01.com.synology:DiskStation.Target-1.56b3371b4b7 (non-flash)

Code:

root@proxmox:~# lsblk
NAME                               MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda                                  8:0    0 119.2G  0 disk
├─sda1                               8:1    0  1007K  0 part
├─sda2                               8:2    0     1G  0 part /boot/efi
└─sda3                               8:3    0 118.2G  0 part
  ├─pve-swap                       252:0    0   7.6G  0 lvm  [SWAP]
  ├─pve-root                       252:1    0  39.6G  0 lvm  /
  ├─pve-data_tmeta                 252:2    0     1G  0 lvm 
  │ └─pve-data-tpool               252:4    0  54.2G  0 lvm 
  │   └─pve-data                   252:5    0  54.2G  1 lvm 
  └─pve-data_tdata                 252:3    0  54.2G  0 lvm 
    └─pve-data-tpool               252:4    0  54.2G  0 lvm 
      └─pve-data                   252:5    0  54.2G  1 lvm 
sdb                                  8:16   0   500G  0 disk
├─SynologyiSCSI-vm--20166--disk--0 252:6    0     8G  0 lvm 
├─SynologyiSCSI-vm--20168--disk--0 252:7    0     2G  0 lvm 
├─SynologyiSCSI-vm--20163--disk--0 252:8    0     6G  0 lvm 
├─SynologyiSCSI-vm--20169--disk--0 252:9    0     4G  0 lvm 
├─SynologyiSCSI-vm--20173--disk--0 252:10   0    15G  0 lvm 
├─SynologyiSCSI-vm--20175--disk--0 252:11   0     2G  0 lvm 
├─SynologyiSCSI-vm--20171--disk--0 252:12   0     7G  0 lvm 
├─SynologyiSCSI-vm--20176--disk--0 252:13   0     2G  0 lvm 
├─SynologyiSCSI-vm--20177--disk--0 252:14   0     5G  0 lvm 
├─SynologyiSCSI-vm--20161--disk--0 252:15   0     8G  0 lvm 
├─SynologyiSCSI-vm--20160--disk--0 252:16   0    50G  0 lvm 
├─SynologyiSCSI-vm--20172--disk--0 252:17   0    15G  0 lvm 
└─SynologyiSCSI-vm--20178--disk--0 252:18   0    10G  0 lvm 
sdc                                  8:32   0   400G  0 disk

The Target in Synology seems OK

And also the LUN:

As I said, the LXC are working well in general, although when I do the night backups I frequently have problems with the LXC. Some of them blocks... I don't know it it's related to these log errors with the iSCSI config.

Thanks for your help.

floh8 · Mar 8, 2025

Iscsi implementation of synology is a little bit buggy. Why you didnt use NFS for lxc and VMS?

Gilberto Ferreira · Mar 8, 2025

jmcanedo said:
Mar 08 10:44:05 proxmox iscsid[945]: connection-1:0 cannot make a connection to fe80::211:32ff:feb6:6af2:3260 (-1,22)

It seems some issue with IPv6.
Did you tried to disable IPv6?

jmcanedo · Mar 8, 2025

Hi @Gilberto Ferreira
Yes, I have seen that is a problem with IPv6. My LAN interface of Synology had activated this and it was the reason for the leg error messages.
I have disable IPv6 in the LAN interface of Synology and the messages have disappear.
In any case I'm a llitle worried solving this diabling IPv6... I don't know if I can solve it in the Proxmox side, maintaning the IPv6 enabled.

@floh8 Well, I'm testing things... Do you think it's better solution to use NFS to store my LXC and VM? Because in this case, I can test it, of coure.

Thanks both for your quick responses.

floh8 · Mar 8, 2025

Synology and pve lvm use mdadm->btrfs->loopdevicefile->iscsi->lvm->your filesystem
With NFS its 1 level less: mdadm->btrfs->NFS->qcow2/raw->your filesystem
So its similar, but a little bit simpler, I think and you get additionally snapshots and thinprovisioning for your VMS.

Gilberto Ferreira · Mar 8, 2025

floh8 said:
So its similar, but a little bit simpler, I think and you get snapshots and thinprovisioning for your VMS.

Yes is true about snapshot but needs to use qcow2 image format.
Also, remember to check preallocation to off, in order to thinprovisin works properly.

https://pve.proxmox.com/pve-docs/chapter-pvesm.html

floh8 · Mar 8, 2025

Whats your question? Do you hate qcow2? Its automatically thin provisioned.

Gilberto Ferreira · Mar 8, 2025

floh8 said:
Whats your question? Do you hate qcow2? Its automatically thin provisioned.

I didn't said nothing of the kind.
I just pointed out that the only way to get snapshot in file storage based is in qcow2 format. That's all.

Search

Search

[SOLVED] iSCSI in Synology. Recurrent error in log

jmcanedo

New Member

floh8

Renowned Member

Gilberto Ferreira

Renowned Member

jmcanedo

New Member

floh8

Renowned Member

Gilberto Ferreira

Renowned Member

floh8

Renowned Member

Gilberto Ferreira

Renowned Member

We value your privacy