iscsiadm no portal found

Hello, 

 Did it fail to connect before or after you rebooted?    The PS array is not like a basic server rebooting rarely solves an issues. 

 First establish that the array is online.  Copy and past the output (not a screenshot) of the following

  Connect to the CLI and run:     GrpName>show members 

  GrpName>member select MEMBERNAME show 

  e.g  If the MEMBERNAME is PS4000   The command would be  GrpName>member select PS4000 show

  GrpName>show volumes 

  That should show the member and active iSCSI connections, the member status and volume statuses

  Are only the VM affected are there any other servers that CAN connect to their volumes? 

  "iscsiadm" is a Linux tool, so from a Linux VM make sure you can ping the Discovery address AND ALL the physical ports on the array.  

   Regards, 

Don 

it failed before the reboot ! 

the array is surely online and ping is working i tried to access the ssh and it works 

i tried show volume and show member using ssh => "some volumes are offline"" 

some Vms who was connected are now offline !

i tried to access the groupe manager but  after waiting ""impossible"" 

so ssh to array disk is working but groupe manager can't be opened 

Hello, 

 Ping working does not mean the array is online or that all volumes are online. 

If would be helpful if you actually paste the exact output instead of summarizing it. 

"some volumes offline"  is the likely cause of your issue.  The output of the show commands would have provided more information. 

 It's is likely that there are unaccounted for blocks of data for those volumes.  Known as "lost blocks"   When that happens the volume cannot be brought online.  So when you try to connect to them you can't.  they can't be Discovered. 

 Regards, 

Don 

show member
Name Status Version Disks Capacity FreeSpace Connections
---------- ------- ---------- ----- ---------- ---------- -----------
SiF-SAN online V6.0.1 (R2 16 4.7TB 982.91GB 6
02 64419)
SiF02> show volume
Name Size Snapshots Status Permission Connections T
--------------- ---------- --------- ------- ---------- ----------- -
HYP70-ISCSI-Sto 400GB 0 offline read-write 0 N
rage
Hyp190 170GB 0 offline read-write 0 N
Hyp210 400GB 0 online read-write 1 N
Hyp170 400GB 0 online read-write 1 N
hyp240 500GB 0 online read-write 1 N
hyp200-30 500GB 0 offline read-write 0 N
-lost
-cach
ed-bl
ocks
hyp40 600GB 0 online read-write 1 N
Hyp177 350GB 0 online read-write 1 N
Hyp81 200GB 0 online read-write 1 N

Hello, 

 Thank you for the output 

 On the volumes that are offline please run: 

GrpName>volume select VOLUMENAME show

 e.g.   volume select hyp200-30 show 

 Please sent that output as well as: 

 Grpname>su exec "raidtool" 

Don

Hello, 

The "requested target not found" is normal on a volume that is offline, since the initiator can not longer discover (find) or log into it. 

 Don 

su exec "raidtool" You are running a support command, which is normally restricted to PS Series Tec hnical Support personnel. Do not use a support command without instruction from Technical Support. Driver Status: Ok RAID LUN 0 Degraded. *!! RAID LUN contains 43 lost blocks. !!* (raidtool -W 0) clears blocks. (raidtool -w 0) lists blocks. 14 Drives (5,11,4,f,8,10,12,1,3,15,7,9,6,13) RAID 50 (64KB sectPerSU) Capacity 5,185,085,374,464 bytes Unavailable Drives: 0 (history of failure) 2 (history of failure) 14 (history of failure)

now i got this too : 

MgmtExec:14-Jun-2020 09:56:22.290227:targetAttr.cc:532:ERROR:7.4.3:iSCSI login to target '192.168.254.254:3260, iqn.2001-05.com.equallogic:0-8a0906-2220ae603-c9584211776586fc-hyp200' from initiator '192.168.254.200:45962, iqn.1993-08.org.debian:01:fda9669847f5' failed for the following reason:
Requested target not found.

703:228:SiF-SAN02:MgmtExec:14-Jun-2020 09:58:31.990229:targetAttr.cc:532:ERROR:7.4.3:iSCSI login to target '192.168.254.254:3260, iqn.2001-05.com.equallogic:0-8a0906-2220ae603-c9584211776586fc-hyp200' from initiator '192.168.254.200:45982, iqn.1993-08.org.debian:01:fda9669847f5' failed for the following reason:
Requested target not found.

705:44:SiF-SAN02:netmgtd:14-Jun-2020 10:01:56.910045:rcc_util.c:1029:INFO:25.2.9:CLI: Login to account grpadmin succeeded, using local authentication. User privilege is group-admin.

This terminal has been idle for 30 minutes.
It will be logged out if it remains idle for another 30 minutes.

volume select Hyp190 show

_____________________________ Volume Information ______________________________ Name: Hyp190 Size: 170GB VolReserve: 170.01GB VolReserveInUse: 151.73GB ReplReserveInUse: 0MB iSCSI Alias: Hyp190 iSCSI Name: ActualMembers: 1 iqn.2001-05.com.equallogic:0-8a0906- Snap-Warn: 10% b050ae603-105844004155b313-hyp190 Snap-Depletion: delete-oldest Description: Hyperviseur 190 Snap-Reserve: 0% Snap-Reserve-Avail: 0% (0MB) Permission: read-write DesiredStatus: offline Status: offline Connections: 0 Snapshots: 0 Bind: Type: not-replicated ReplicationReserveSpace: 0MB Replicas: 0 ReplicationPartner: Pool: default Transmitted-Data: 3.97TB Received-Data: 1.09TB Pref-Raid-Policy: none Pref-Raid-Policy-Status: none Thin-Provision: disabled Thin-Min-Reserve: 0% (0MB) Thin-Growth-Warn: 0% (0MB) Thin-Growth-Max: 0% (0MB) ReplicationTxData: 0MB MultiHostAccess: disabled iSNS-Discovery: disabled Replica-Volume-Reserve: 0MB Thin-Clone: N Template: N NAS Container: N Administrator: SyncReplStatus: SyncReplTxData: 0MB Thin-Warn-Mode: offline Snap-space Borrowing: enabled Space Borrowed: 0MB Folder:

Hello, 

 thank you also please do: 

GrpName>volume select hyp200-30  show 

So this RAIDset too is faulted and another drive failure will bring it offline as well. 

 Failing drives is likely the cause of the lost block condition.  

 You need to replace the failed and spares as soon as possible. 

 Does this array have dual controllers? 

 Don 

yes it has dual controller 

volume select hyp200-30 show
_____________________________ Volume Information ______________________________
Name: hyp200-30 Size: 500GB
VolReserve: 500.01GB VolReserveInUse: 250.06GB
ReplReserveInUse: 0MB iSCSI Alias: hyp200-30
iSCSI Name: ActualMembers: 1
iqn.2001-05.com.equallogic:0-8a0906- Snap-Warn: 10%
4340ae603-1498440046c5b8fa-hyp200-30 Snap-Depletion: delete-oldest
Description: Snap-Reserve: 0%
Snap-Reserve-Avail: 0% (0MB) Permission: read-write
DesiredStatus: offline Status: offline-lost-cached-blocks
Connections: 0 Snapshots: 0
Bind: Type: not-replicated
ReplicationReserveSpace: 0MB Replicas: 0
ReplicationPartner: Pool: default
Transmitted-Data: 117.26TB Received-Data: 19.48TB
Pref-Raid-Policy: none Pref-Raid-Policy-Status: none
Thin-Provision: disabled Thin-Min-Reserve: 0% (0MB)
Thin-Growth-Warn: 0% (0MB) Thin-Growth-Max: 0% (0MB)
ReplicationTxData: 0MB MultiHostAccess: disabled
iSNS-Discovery: disabled Replica-Volume-Reserve: 0MB
Thin-Clone: N Template: N
NAS Container: N Administrator:
SyncReplStatus: SyncReplTxData: 0MB
Thin-Warn-Mode: offline Snap-space Borrowing: enabled
Space Borrowed: 0MB Folder:

Hello, 

 Thank you. If that array has both controllers, the first step will be a restart of the primary to force a failover. It is possible, that the missing data is in the cache of the other controller.  If that's the case the volumes will come back online.  

Don