Working with iSCSI

[Mike Leone]

So I have a cluster, and there are 7 targets (disks) presented to each node. However, only 4 are currently connected, because the cluster only needs those 4 (it used to need the other 3, I removed those disks from the cluster).

So what I want to do is disconnect the unused targets (on both nodes), and then I will stop presenting the targets to the cluster completely.

The problem is ... how to identify which target is which disk. :-)

For instance, here are the offline disks:

PS C:\Windows\system32> get-disk | Where {$_.BusType -eq 'iSCSI' -and $_.OperationalStatus -eq 'Offline'}

Number Friendly Name Serial Number                    HealthStatus         OperationalStatus      Total Size Partition
                                                                                                             Style
------ ------------- -------------                    ------------         -----------------      ---------- ----------
4      NUTANIX VDISK NFS_16_0_779_bd560010_156c_4e... Healthy              Offline                   1.46 TB GPT
5      NUTANIX VDISK NFS_16_0_43617_a0a9015b_912b_... Healthy              Offline                    100 GB GPT
2      NUTANIX VDISK NFS_16_0_747_2cde964b_8f60_49... Healthy              Offline                   1000 GB GPT
10     NUTANIX VDISK NFS_16_0_43616_7ba3a064_2eaa_... Healthy              Offline                      5 GB GPT

They're all offline, which is correct. But how can I map those disks to the iSCSI targets, so I can disconnect them? I know how to do it manually (in iSCSI Initiator,. you can look at the "Devices" of each target, and it will show a drive letter for the online ones). You can also see that the "Name" there matches the "Disk Number" column in Failover Cluster Manager's "Disks" section. But only if the cluster role is mounted on that node. LOL

So, for example, on node #1, I see that target #2 is mounted as the quorum drive. So I don't wanna disconnect that. But conversely, on node #2 I don't want to disconnect the same target, because I'll need it connected, if I fail 1 node over to the other.

So what I need to do is: 

Make sure all disks (including quorum) are on 1 node

Match the iSCSI target to the ONLINE DISK, and disconnect everything else.

Save that list of targets

Go to node #2

Disconnect all targets EXCEPT for the targets I just identified from node #1 (because I'll need those, for the cluster to fail over).

Then I can go and stop presenting the other targets completely, without any problems, since those targets have been disconnected anyway.

So ... how do I do that? LOL Find the iSCSI target associated with a disk?

OR

Can I simply just stop presenting the storage, and then refresh the initiator, and hope those non-presented targets just drop away? That would be a lot easier. But I don't want to do that, until I know that it won't cause issues.

What do you think?

--

Mike. Leone, <mailto:tur...@mike-leone.com>

PGP Fingerprint: 0AA8 DC47 CB63 AE3F C739 6BF9 9AB4 1EF6 5AA5 BCDF
Photo Gallery: <http://www.flickr.com/photos/mikeleonephotos>

[Helton, Matt]

I’m no PowerShell pro, but most cmdlets only return a fraction of the data they could return. Couldn’t you pipe `Select-Object -Property *` to see all properties of the disks and then compare some output from the all properties, like `Location`, to verify the correct drives? I don’t have iSCSI drives to test if this will work or not.

 

Later,

Matt Helton

(he/him/his)

Assistant System Administrator

Library Information Technology Services

Milner Library

Illinois State University

 

From: ntpowe...@googlegroups.com <ntpowe...@googlegroups.com> On Behalf Of Mike Leone
Sent: Thursday, January 15, 2026 14:06
To: NTPowershell Mailing List <ntpowe...@googlegroups.com>
Subject: [ntpowershell] Working with iSCSI

 

This message originated from outside of the Illinois State University email system. Learn why this is important

--
You received this message because you are subscribed to the Google Groups "ntpowershell" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ntpowershell...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ntpowershell/CAHBr%2B%2Bg2sUJ1v61GYD59gOUiCTgx3en%3DmeRS7aQNXhiOXTOmTA%40mail.gmail.com.

[Mike Leone]

On Fri, Jan 16, 2026 at 9:29 AM 'Helton, Matt' via ntpowershell <ntpowe...@googlegroups.com> wrote:

I’m no PowerShell pro, but most cmdlets only return a fraction of the data they could return. Couldn’t you pipe `Select-Object -Property *` to see all properties of the disks and then compare some output from the all properties, like `Location`, to verify the correct drives?

I did. Get-Disk doesn't return anything about iSCSI.

 

I don’t have iSCSI drives to test if this will work or not.

I ended up just doing it manually, since this is (hopefully) just a one-off. I stopped presenting the storage, refreshed the connections, and any storage that wasn't being presented showed up as completely empty. So I disconnected that connection.

Then I failed the cluster over to the other node, and did the same.

And now the only connections listed are the ones that correspond to the currently presented storage.

So, for me, this is what I needed. It might be nice to know how to do it with PS, as an intellectual exercise, but I don't need it anymore.