vSphere Storage Appliance

 View Only
  • 1.  VMware ESXi 6.5 booting problem, probably old storage is holding it

    Posted Feb 17, 2025 12:41 PM

    We have a VM setup running on 3 hosts Dell PowerEdge R620 and VMware ESXi 6.5  with vcenter. 
    In this setup we have also IBM Storwize V5000E, Synology storage and 2 ISCI switches dellN4032- all  devices are working fine.  
    In the past we had also another storage configured for this setup EqualLogic PS6210E. 
    It was removed from UI and I think it was done in the proper way, but somehow when we restarting the VM hosts, they do not start properly (gui is unavailable) until PS6210E is connected back online to ISCI network.  Ho
    Probably this storage is not properly removed from the environment, what are the steps to check that and remove that, so the hosts are not interrupted by this old retired device?
    I tried to troubleshoot this using following commands:


    esxcli storage core adapter list
    esxcli storage core device list
    esxcli storage nmp device list
    esxcli iscsi session list

    Nothing found related to old PS6210E (EQLOGIC). The only place I can see something is in the configuration file (/etc/vmware/esx.conf)
    See below. These records needs to be maybe removed, but I do not dare to edit this file. I'm looking for help on this forum with that. Can anyone suggest how to resolve this. 
    This is serious problem for us, and causing a lot of headache.
    Can be that the old datastores are still orphaned in vCenter ? But how to cleanup this?

    "
    /vvol/domainId = "4A8B0771-A669-45FE-A920-4C5B4A1EE087"
    /storage/PSA/Filter/claimrule[65432]/plugin = "VAAI_FILTER"
    /storage/PSA/Filter/claimrule[65432]/type = "vendor"
    /storage/PSA/Filter/claimrule[65432]/match/vendor = "EQLOGIC"
    /storage/PSA/Filter/claimrule[65435]/plugin = "VAAI_FILTER"
    /storage/PSA/Filter/claimrule[65435]/type = "vendor"
    /storage/PSA/Filter/claimrule[65435]/match/vendor = "LEFTHAND"
    /storage/PSA/Filter/claimrule[65434]/plugin = "VAAI_FILTER"
    /storage/PSA/Filter/claimrule[65434]/type = "vendor"
    /storage/PSA/Filter/claimrule[65434]/match/vendor = "HITACHI"
    /storage/PSA/Filter/claimrule[65431]/plugin = "VAAI_FILTER"
    /storage/PSA/Filter/claimrule[65431]/type = "vendor"
    /storage/PSA/Filter/claimrule[65431]/match/vendor = "DGC"
    /storage/PSA/Filter/claimrule[65433]/match/model = "LUN*"
    /storage/PSA/Filter/claimrule[65433]/match/vendor = "NETAPP"
    /storage/PSA/Filter/claimrule[65433]/plugin = "VAAI_FILTER"
    /storage/PSA/Filter/claimrule[65433]/type = "vendor"
    /storage/PSA/Filter/claimrule[65430]/plugin = "VAAI_FILTER"
    /storage/PSA/Filter/claimrule[65430]/type = "vendor"
    /storage/PSA/Filter/claimrule[65430]/match/model = "SYMMETRIX"
    /storage/PSA/Filter/claimrule[65430]/match/vendor = "EMC"
    /storage/PSA/Filter/claimrule[65429]/plugin = "VAAI_FILTER"
    /storage/PSA/Filter/claimrule[65429]/type = "vendor"
    /storage/PSA/Filter/claimrule[65429]/match/model = "Virtual HD"
    /storage/PSA/Filter/claimrule[65429]/match/vendor = "MSFT"
    /storage/PSA/VAAI/claimrule[65432]/plugin = "VMW_VAAIP_EQL"
    /storage/PSA/VAAI/claimrule[65432]/type = "vendor"
    /storage/PSA/VAAI/claimrule[65432]/match/vendor = "EQLOGIC"
    /storage/PSA/VAAI/claimrule[65435]/plugin = "VMW_VAAIP_LHN"
    /storage/PSA/VAAI/claimrule[65435]/type = "vendor"
    /storage/PSA/VAAI/claimrule[65435]/match/vendor = "LEFTHAND"
    /storage/PSA/VAAI/claimrule[65434]/plugin = "VMW_VAAIP_HDS"
    /storage/PSA/VAAI/claimrule[65434]/type = "vendor"
    /storage/PSA/VAAI/claimrule[65434]/match/vendor = "HITACHI"
    /storage/PSA/VAAI/claimrule[65433]/type = "vendor"
    /storage/PSA/VAAI/claimrule[65433]/plugin = "VMW_VAAIP_NETAPP"
    /storage/PSA/VAAI/claimrule[65433]/match/vendor = "NETAPP"
    /storage/PSA/VAAI/claimrule[65433]/match/model = "LUN*"
    /storage/PSA/VAAI/claimrule[65431]/plugin = "VMW_VAAIP_CX"
    /storage/PSA/VAAI/claimrule[65431]/type = "vendor"



  • 2.  RE: VMware ESXi 6.5 booting problem, probably old storage is holding it

    Posted Feb 17, 2025 01:01 PM

    Only guessing.

    To remove an old iSCSI storage, you'd usually make sure that the volumes are not in use anymore (by e.g. VMs, snapshots, mapped ISO images,  etc.), and then unmount&detach the LUNs from the hosts, delete its static&dynamic target settings from the hosts' iSCSI initiator, unpresent the LUNs from the storage side, and do a rescan on the ESXi hosts.

    Finally - for house keeping - you may want to delete the detached devices from the ESXi hosts.

    esxcli storage core device detached list

    esxcli storage core device detached remove -d <NAA_ID>

    André




  • 3.  RE: VMware ESXi 6.5 booting problem, probably old storage is holding it

    Posted Feb 18, 2025 08:23 AM
    Edited by Jason McClellan Feb 18, 2025 01:41 PM

    HI André

    There is nothing listed to be removed, after applying this command:
    esxcli storage core device detached list
    [image: image.png]

    Sorry for duplicated posts


    GK



  • 4.  RE: VMware ESXi 6.5 booting problem, probably old storage is holding it

    Posted Feb 18, 2025 08:23 AM

    HI. After applying command 
    esxcli storage core device detached list
    There is no output. Nothing is listed.




  • 5.  RE: VMware ESXi 6.5 booting problem, probably old storage is holding it

    Posted Feb 18, 2025 08:24 AM

    I just disconnected the old storage (EqualLogic PS6210E) from SCSI  and tried this command on all 3 hosts.

    esxcli storage core device detached list

    No output.