All iscsi from sinology nas is not online

avryanz

New Member
Mar 11, 2025
2
0
1
Hello everyone, newbie here

this morning some vm in my server cannot start because all my iscsi in not online

i have tried restarting both my server and my nas, but the problem is still there

Code:
proxmox-ve: 8.2.0 (running kernel: 6.8.12-3-pve)
pve-manager: 8.2.7 (running version: 8.2.7/3e0176e6bb2ade3b)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-3
proxmox-kernel-6.8.12-3-pve-signed: 6.8.12-3
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
ceph-fuse: 17.2.7-pve1
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.8
libpve-cluster-perl: 8.0.8
libpve-common-perl: 8.2.5
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.10
libpve-storage-perl: 8.2.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-4
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.2.4
pve-cluster: 8.0.8
pve-container: 5.2.0
pve-docs: 8.2.3
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.0.7
pve-firmware: 3.14-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.4
pve-qemu-kvm: 9.0.2-3
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.4
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1

Code:
root@promox:~# journalctl -b -r
Mar 11 09:33:06 promox pvestatd[1015]: mount error: mount.nfs: access denied by server while mounting 192.168.1.241:/volume1/DOMAIN_233
Mar 11 09:33:06 promox pvestatd[1015]: storage 'ISCSI-MKT' is not online
Mar 11 09:33:06 promox pvestatd[1015]: storage 'PROXMOX-SINOLOGY-2' is not online
Mar 11 09:33:06 promox pvestatd[1015]: storage 'ISCSI-MKT' is not online
Mar 11 09:33:06 promox pvestatd[1015]: storage 'PROXMOX-SINOLOGY-2' is not online
Mar 11 09:33:06 promox pvestatd[1015]: storage 'PROXMOX-SINOLOGY' is not online
Mar 11 09:32:56 promox pvestatd[1015]: storage 'PROXMOX-SINOLOGY-2' is not online
Mar 11 09:32:56 promox pvestatd[1015]: storage 'PROXMOX-SINOLOGY' is not online

thank you for your help
 
Hi @avryanz , welcome to the forum.

You, likely, have a network issue. Have you performed any troubleshooting at all? Can you ping the IP of the NAS? Are there any errors in "journalctl -f" ?
Are network ports up?

"is not online" is logged by this code:
Code:
if (! eval { $plugin->check_connection($storeid, $scfg) }) {
        die "connection check for storage '$storeid' failed - $@\n" if $@;
        die "storage '$storeid' is not online\n";
    }

An ISCSI plugin specific check is:
Code:
sub check_connection {
    my ($class, $storeid, $scfg) = @_;
   
    my $portals = iscsi_portals($scfg->{target}, $scfg->{portal});
   
    for my $portal (@$portals) {
        my $result = iscsi_test_portal($portal);
        return $result if $result;
    }  
           
    return 0;
}

So it executes iscsi_test_portal against each IP of your NAS. And the check is:
Code:
sub iscsi_test_portal {
    my ($portal) = @_;
   
    my ($server, $port) = PVE::Tools::parse_host_and_port($portal);
    return 0 if !$server;
    return PVE::Network::tcp_ping($server, $port || 3260, 2);
}

That is a TCP ping to port 3260, unless custom port is used. You can manually run the same check via:
nc -zv <hostname_or_IP> 3260

Good luck


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: UdoB
Thank you for your support, after your guidance and many other toubleshooting, sadly its still not work
so i decided to replace my ssd and perform recovery from my latest img backup and now the iscsi is working again
weird