ESXi 6.7 monitor hardware storage not showing usual results The Next CEO of Stack...
How can the PCs determine if an item is a phylactery?
Could a dragon use hot air to help it take off?
Find the majority element, which appears more than half the time
What steps are necessary to read a Modern SSD in Medieval Europe?
Is a distribution that is normal, but highly skewed, considered Gaussian?
How can I separate the number from the unit in argument?
Identify and count spells (Distinctive events within each group)
Why did early computer designers eschew integers?
Find a path from s to t using as few red nodes as possible
Do I need to write [sic] when including a quotation with a number less than 10 that isn't written out?
Another proof that dividing by 0 does not exist -- is it right?
Car headlights in a world without electricity
Why does the freezing point matter when picking cooler ice packs?
Creating a script with console commands
Free fall ellipse or parabola?
Prodigo = pro + ago?
Upgrading From a 9 Speed Sora Derailleur?
How did scripture get the name bible?
My ex-girlfriend uses my Apple ID to login to her iPad, do I have to give her my Apple ID password to reset it?
How does a dynamic QR code work?
Calculate the Mean mean of two numbers
How do I secure a TV wall mount?
Is it possible to create a QR code using text?
Mathematica command that allows it to read my intentions
ESXi 6.7 monitor hardware storage not showing usual results
The Next CEO of Stack OverflowMeasuring SSD wear out behind LSI MegaRAID controller?Centralized LSI RAID controller managementFlashing firmware to hard disks behind LSI controllerStorCLI: storcli show and “Hlth: Opt”: how exhaustive is this?Dell MD1200 (6gb/s jbod enclosure) and 12 Gb/s drivesHard Disc Failure or RAID GlitchPSOD vmwar eSXi 6.7 U1See Pike raid status in ESXi 6.7Can't upgrade ESXI from 6.0 to 6.7
Yesterday 2 of our ESXi hosts were updated from 6.5 to 6.7 (build 8169922), though after doing this we noticed a few quirks when trying to access the storage hardware monitoring.
In the web UI typically we'd only see elements listed for the Avago/LSI hardware RAID here, with a clear indicator of its overall health, each logical volume's health, and each physical disk's health. Now though all sorts of hardware is showing up that isn't even storage related. (Such as the GPU, Ethernet controllers, and Thunderbolt controllers.)
I've updated the LSI SIMS provider to version 7.6 (30/May/2018), along with MegaCLI utility version 8-07-07, and the storcli utility version 007.0606.0000.0000 (20/Mar/2018). The host has been rebooted after installing each VIB. Looks like the CIM service just doesn't want to know though.
The servers work very fine indeed, VMs are operating as normal. They just lack RAID monitoring and management now, so if an issue happens we just get a buzzer and LED blink, and have to reboot to the LSI WebBIOS to see what it's for to resolve it.
I saw from the VMWare hardware compatibility that our LSI RAID controller models are supported with an official driver so I don't think there is any compatibility issue.
The MegaCLI command is also useless likely because of the same CIM issue. ./MegaCli -adpCount
shows Controller Count: 0
, which also means that the MegaRAID Storage Manager utility no longer detects ESXi hosts for management too.
--
Finally with the storcli only some parts of it work. This is probably a separate issue though. (Bug in the tool?) It seems if you are specifying command arguments that contain a forward slash '/' it is ignored.
For example, "storcli show" works:
[root@nexus:/opt/lsi/storcli] ./storcli show
CLI Version = 007.0606.0000.0000 Mar 20, 2018
Operating system = VMkernel 6.7.0
Status Code = 0
Status = Success
Description = None
Number of Controllers = 1
Host Name = nexus.***
Operating System = VMkernel 6.7.0
StoreLib IT Version = 07.0603.0200.0000
StoreLib IR3 Version = 15.53-0
System Overview :
===============
------------------------------------------------------------------------------------
Ctl Model Ports PDs DGs DNOpt VDs VNOpt BBU sPR DS EHS ASOs Hlth
------------------------------------------------------------------------------------
0 LSIMegaRAIDSAS9271-8i 8 4 1 1 1 1 Msng On 1&2 Y 4 NdAtn
------------------------------------------------------------------------------------
Ctl=Controller Index|DGs=Drive groups|VDs=Virtual drives|Fld=Failed
PDs=Physical drives|DNOpt=DG NotOptimal|VNOpt=VD NotOptimal|Opt=Optimal
Msng=Missing|Dgd=Degraded|NdAtn=Need Attention|Unkwn=Unknown
sPR=Scheduled Patrol Read|DS=DimmerSwitch|EHS=Emergency Hot Spare
Y=Yes|N=No|ASOs=Advanced Software Options|BBU=Battery backup unit
Hlth=Health|Safe=Safe-mode boot
However, using another command such as "storcli /cx show alarm" does not:
[root@nexus:/opt/lsi/storcli] ./storcli /cx show alarm
syntax error, unexpected $end
Storage Command Line Tool Ver 007.0606.0000.0000 Mar 20, 2018
(c)Copyright 2018, AVAGO Technologies, All Rights Reserved.
help - lists all the commands with their usage. E.g. storcli help
<command> help - gives details about a particular command. E.g. storcli add help
List of commands:
That syntax error, unexpected $end
suggests something in the command parser is not right. (I've tried from both the DCUI and SSH.) Weirdly storcli cx show help
does work, only showing controller specific commands, but storcli cx show all
does not.
(The fact that storcli is able to see the controller at all and query it tells me the driver is fine and compatible.)
vmware-esxi lsi megaraid storcli
bumped to the homepage by Community♦ 6 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
Yesterday 2 of our ESXi hosts were updated from 6.5 to 6.7 (build 8169922), though after doing this we noticed a few quirks when trying to access the storage hardware monitoring.
In the web UI typically we'd only see elements listed for the Avago/LSI hardware RAID here, with a clear indicator of its overall health, each logical volume's health, and each physical disk's health. Now though all sorts of hardware is showing up that isn't even storage related. (Such as the GPU, Ethernet controllers, and Thunderbolt controllers.)
I've updated the LSI SIMS provider to version 7.6 (30/May/2018), along with MegaCLI utility version 8-07-07, and the storcli utility version 007.0606.0000.0000 (20/Mar/2018). The host has been rebooted after installing each VIB. Looks like the CIM service just doesn't want to know though.
The servers work very fine indeed, VMs are operating as normal. They just lack RAID monitoring and management now, so if an issue happens we just get a buzzer and LED blink, and have to reboot to the LSI WebBIOS to see what it's for to resolve it.
I saw from the VMWare hardware compatibility that our LSI RAID controller models are supported with an official driver so I don't think there is any compatibility issue.
The MegaCLI command is also useless likely because of the same CIM issue. ./MegaCli -adpCount
shows Controller Count: 0
, which also means that the MegaRAID Storage Manager utility no longer detects ESXi hosts for management too.
--
Finally with the storcli only some parts of it work. This is probably a separate issue though. (Bug in the tool?) It seems if you are specifying command arguments that contain a forward slash '/' it is ignored.
For example, "storcli show" works:
[root@nexus:/opt/lsi/storcli] ./storcli show
CLI Version = 007.0606.0000.0000 Mar 20, 2018
Operating system = VMkernel 6.7.0
Status Code = 0
Status = Success
Description = None
Number of Controllers = 1
Host Name = nexus.***
Operating System = VMkernel 6.7.0
StoreLib IT Version = 07.0603.0200.0000
StoreLib IR3 Version = 15.53-0
System Overview :
===============
------------------------------------------------------------------------------------
Ctl Model Ports PDs DGs DNOpt VDs VNOpt BBU sPR DS EHS ASOs Hlth
------------------------------------------------------------------------------------
0 LSIMegaRAIDSAS9271-8i 8 4 1 1 1 1 Msng On 1&2 Y 4 NdAtn
------------------------------------------------------------------------------------
Ctl=Controller Index|DGs=Drive groups|VDs=Virtual drives|Fld=Failed
PDs=Physical drives|DNOpt=DG NotOptimal|VNOpt=VD NotOptimal|Opt=Optimal
Msng=Missing|Dgd=Degraded|NdAtn=Need Attention|Unkwn=Unknown
sPR=Scheduled Patrol Read|DS=DimmerSwitch|EHS=Emergency Hot Spare
Y=Yes|N=No|ASOs=Advanced Software Options|BBU=Battery backup unit
Hlth=Health|Safe=Safe-mode boot
However, using another command such as "storcli /cx show alarm" does not:
[root@nexus:/opt/lsi/storcli] ./storcli /cx show alarm
syntax error, unexpected $end
Storage Command Line Tool Ver 007.0606.0000.0000 Mar 20, 2018
(c)Copyright 2018, AVAGO Technologies, All Rights Reserved.
help - lists all the commands with their usage. E.g. storcli help
<command> help - gives details about a particular command. E.g. storcli add help
List of commands:
That syntax error, unexpected $end
suggests something in the command parser is not right. (I've tried from both the DCUI and SSH.) Weirdly storcli cx show help
does work, only showing controller specific commands, but storcli cx show all
does not.
(The fact that storcli is able to see the controller at all and query it tells me the driver is fine and compatible.)
vmware-esxi lsi megaraid storcli
bumped to the homepage by Community♦ 6 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Go to the 6.7 HCL, check EVERY SINGLE component is supported by 6.7, they stopped supporting a LOT of kit between 6.5 and 6.7, like a lot.
– Chopper3
Jun 21 '18 at 8:45
I did check the CPU and RAID in advance, they were listed on 6.5, 6.5U1, 6.5U2, and 6.7. The only component I know of that isn't supported is the Atheros Killer NIC on the motherboard.
– Adambean
Jun 21 '18 at 9:23
what sort of server systemboard are you using that's got an Atheros Killer NIC on it?!?!
– Chopper3
Jun 21 '18 at 9:44
Heh, the server for our office actually has a workstation type motherboard. (It's a Gigabyte GA-X170-EXTREME ECC.) It has a Xeon E3-1270 v5 CPU though with ECC memory, and an LSI MegaRAID 9260-8i. --- The other server at our DC doesn't have a Killer NIC though. ;) That has a Xeon E3-1245 v2 CPU with ECC memory, and an LSI MegaRAID 9260-4i. --- Both use Intel NICs, which definitely work, as I can talk to the servers fine.
– Adambean
Jun 21 '18 at 9:50
Silly me. "storcli" appears to work fine, I didn't realise "/cx" should actually be "/c0" to mean "use controller at index 0". I'm not bothered if MegaCLI doesn't work any more as storcli is the later product. Bit weird about the web UI and MSM utility though.
– Adambean
Jun 21 '18 at 14:55
add a comment |
Yesterday 2 of our ESXi hosts were updated from 6.5 to 6.7 (build 8169922), though after doing this we noticed a few quirks when trying to access the storage hardware monitoring.
In the web UI typically we'd only see elements listed for the Avago/LSI hardware RAID here, with a clear indicator of its overall health, each logical volume's health, and each physical disk's health. Now though all sorts of hardware is showing up that isn't even storage related. (Such as the GPU, Ethernet controllers, and Thunderbolt controllers.)
I've updated the LSI SIMS provider to version 7.6 (30/May/2018), along with MegaCLI utility version 8-07-07, and the storcli utility version 007.0606.0000.0000 (20/Mar/2018). The host has been rebooted after installing each VIB. Looks like the CIM service just doesn't want to know though.
The servers work very fine indeed, VMs are operating as normal. They just lack RAID monitoring and management now, so if an issue happens we just get a buzzer and LED blink, and have to reboot to the LSI WebBIOS to see what it's for to resolve it.
I saw from the VMWare hardware compatibility that our LSI RAID controller models are supported with an official driver so I don't think there is any compatibility issue.
The MegaCLI command is also useless likely because of the same CIM issue. ./MegaCli -adpCount
shows Controller Count: 0
, which also means that the MegaRAID Storage Manager utility no longer detects ESXi hosts for management too.
--
Finally with the storcli only some parts of it work. This is probably a separate issue though. (Bug in the tool?) It seems if you are specifying command arguments that contain a forward slash '/' it is ignored.
For example, "storcli show" works:
[root@nexus:/opt/lsi/storcli] ./storcli show
CLI Version = 007.0606.0000.0000 Mar 20, 2018
Operating system = VMkernel 6.7.0
Status Code = 0
Status = Success
Description = None
Number of Controllers = 1
Host Name = nexus.***
Operating System = VMkernel 6.7.0
StoreLib IT Version = 07.0603.0200.0000
StoreLib IR3 Version = 15.53-0
System Overview :
===============
------------------------------------------------------------------------------------
Ctl Model Ports PDs DGs DNOpt VDs VNOpt BBU sPR DS EHS ASOs Hlth
------------------------------------------------------------------------------------
0 LSIMegaRAIDSAS9271-8i 8 4 1 1 1 1 Msng On 1&2 Y 4 NdAtn
------------------------------------------------------------------------------------
Ctl=Controller Index|DGs=Drive groups|VDs=Virtual drives|Fld=Failed
PDs=Physical drives|DNOpt=DG NotOptimal|VNOpt=VD NotOptimal|Opt=Optimal
Msng=Missing|Dgd=Degraded|NdAtn=Need Attention|Unkwn=Unknown
sPR=Scheduled Patrol Read|DS=DimmerSwitch|EHS=Emergency Hot Spare
Y=Yes|N=No|ASOs=Advanced Software Options|BBU=Battery backup unit
Hlth=Health|Safe=Safe-mode boot
However, using another command such as "storcli /cx show alarm" does not:
[root@nexus:/opt/lsi/storcli] ./storcli /cx show alarm
syntax error, unexpected $end
Storage Command Line Tool Ver 007.0606.0000.0000 Mar 20, 2018
(c)Copyright 2018, AVAGO Technologies, All Rights Reserved.
help - lists all the commands with their usage. E.g. storcli help
<command> help - gives details about a particular command. E.g. storcli add help
List of commands:
That syntax error, unexpected $end
suggests something in the command parser is not right. (I've tried from both the DCUI and SSH.) Weirdly storcli cx show help
does work, only showing controller specific commands, but storcli cx show all
does not.
(The fact that storcli is able to see the controller at all and query it tells me the driver is fine and compatible.)
vmware-esxi lsi megaraid storcli
Yesterday 2 of our ESXi hosts were updated from 6.5 to 6.7 (build 8169922), though after doing this we noticed a few quirks when trying to access the storage hardware monitoring.
In the web UI typically we'd only see elements listed for the Avago/LSI hardware RAID here, with a clear indicator of its overall health, each logical volume's health, and each physical disk's health. Now though all sorts of hardware is showing up that isn't even storage related. (Such as the GPU, Ethernet controllers, and Thunderbolt controllers.)
I've updated the LSI SIMS provider to version 7.6 (30/May/2018), along with MegaCLI utility version 8-07-07, and the storcli utility version 007.0606.0000.0000 (20/Mar/2018). The host has been rebooted after installing each VIB. Looks like the CIM service just doesn't want to know though.
The servers work very fine indeed, VMs are operating as normal. They just lack RAID monitoring and management now, so if an issue happens we just get a buzzer and LED blink, and have to reboot to the LSI WebBIOS to see what it's for to resolve it.
I saw from the VMWare hardware compatibility that our LSI RAID controller models are supported with an official driver so I don't think there is any compatibility issue.
The MegaCLI command is also useless likely because of the same CIM issue. ./MegaCli -adpCount
shows Controller Count: 0
, which also means that the MegaRAID Storage Manager utility no longer detects ESXi hosts for management too.
--
Finally with the storcli only some parts of it work. This is probably a separate issue though. (Bug in the tool?) It seems if you are specifying command arguments that contain a forward slash '/' it is ignored.
For example, "storcli show" works:
[root@nexus:/opt/lsi/storcli] ./storcli show
CLI Version = 007.0606.0000.0000 Mar 20, 2018
Operating system = VMkernel 6.7.0
Status Code = 0
Status = Success
Description = None
Number of Controllers = 1
Host Name = nexus.***
Operating System = VMkernel 6.7.0
StoreLib IT Version = 07.0603.0200.0000
StoreLib IR3 Version = 15.53-0
System Overview :
===============
------------------------------------------------------------------------------------
Ctl Model Ports PDs DGs DNOpt VDs VNOpt BBU sPR DS EHS ASOs Hlth
------------------------------------------------------------------------------------
0 LSIMegaRAIDSAS9271-8i 8 4 1 1 1 1 Msng On 1&2 Y 4 NdAtn
------------------------------------------------------------------------------------
Ctl=Controller Index|DGs=Drive groups|VDs=Virtual drives|Fld=Failed
PDs=Physical drives|DNOpt=DG NotOptimal|VNOpt=VD NotOptimal|Opt=Optimal
Msng=Missing|Dgd=Degraded|NdAtn=Need Attention|Unkwn=Unknown
sPR=Scheduled Patrol Read|DS=DimmerSwitch|EHS=Emergency Hot Spare
Y=Yes|N=No|ASOs=Advanced Software Options|BBU=Battery backup unit
Hlth=Health|Safe=Safe-mode boot
However, using another command such as "storcli /cx show alarm" does not:
[root@nexus:/opt/lsi/storcli] ./storcli /cx show alarm
syntax error, unexpected $end
Storage Command Line Tool Ver 007.0606.0000.0000 Mar 20, 2018
(c)Copyright 2018, AVAGO Technologies, All Rights Reserved.
help - lists all the commands with their usage. E.g. storcli help
<command> help - gives details about a particular command. E.g. storcli add help
List of commands:
That syntax error, unexpected $end
suggests something in the command parser is not right. (I've tried from both the DCUI and SSH.) Weirdly storcli cx show help
does work, only showing controller specific commands, but storcli cx show all
does not.
(The fact that storcli is able to see the controller at all and query it tells me the driver is fine and compatible.)
vmware-esxi lsi megaraid storcli
vmware-esxi lsi megaraid storcli
asked Jun 21 '18 at 8:16
AdambeanAdambean
10616
10616
bumped to the homepage by Community♦ 6 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 6 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Go to the 6.7 HCL, check EVERY SINGLE component is supported by 6.7, they stopped supporting a LOT of kit between 6.5 and 6.7, like a lot.
– Chopper3
Jun 21 '18 at 8:45
I did check the CPU and RAID in advance, they were listed on 6.5, 6.5U1, 6.5U2, and 6.7. The only component I know of that isn't supported is the Atheros Killer NIC on the motherboard.
– Adambean
Jun 21 '18 at 9:23
what sort of server systemboard are you using that's got an Atheros Killer NIC on it?!?!
– Chopper3
Jun 21 '18 at 9:44
Heh, the server for our office actually has a workstation type motherboard. (It's a Gigabyte GA-X170-EXTREME ECC.) It has a Xeon E3-1270 v5 CPU though with ECC memory, and an LSI MegaRAID 9260-8i. --- The other server at our DC doesn't have a Killer NIC though. ;) That has a Xeon E3-1245 v2 CPU with ECC memory, and an LSI MegaRAID 9260-4i. --- Both use Intel NICs, which definitely work, as I can talk to the servers fine.
– Adambean
Jun 21 '18 at 9:50
Silly me. "storcli" appears to work fine, I didn't realise "/cx" should actually be "/c0" to mean "use controller at index 0". I'm not bothered if MegaCLI doesn't work any more as storcli is the later product. Bit weird about the web UI and MSM utility though.
– Adambean
Jun 21 '18 at 14:55
add a comment |
Go to the 6.7 HCL, check EVERY SINGLE component is supported by 6.7, they stopped supporting a LOT of kit between 6.5 and 6.7, like a lot.
– Chopper3
Jun 21 '18 at 8:45
I did check the CPU and RAID in advance, they were listed on 6.5, 6.5U1, 6.5U2, and 6.7. The only component I know of that isn't supported is the Atheros Killer NIC on the motherboard.
– Adambean
Jun 21 '18 at 9:23
what sort of server systemboard are you using that's got an Atheros Killer NIC on it?!?!
– Chopper3
Jun 21 '18 at 9:44
Heh, the server for our office actually has a workstation type motherboard. (It's a Gigabyte GA-X170-EXTREME ECC.) It has a Xeon E3-1270 v5 CPU though with ECC memory, and an LSI MegaRAID 9260-8i. --- The other server at our DC doesn't have a Killer NIC though. ;) That has a Xeon E3-1245 v2 CPU with ECC memory, and an LSI MegaRAID 9260-4i. --- Both use Intel NICs, which definitely work, as I can talk to the servers fine.
– Adambean
Jun 21 '18 at 9:50
Silly me. "storcli" appears to work fine, I didn't realise "/cx" should actually be "/c0" to mean "use controller at index 0". I'm not bothered if MegaCLI doesn't work any more as storcli is the later product. Bit weird about the web UI and MSM utility though.
– Adambean
Jun 21 '18 at 14:55
Go to the 6.7 HCL, check EVERY SINGLE component is supported by 6.7, they stopped supporting a LOT of kit between 6.5 and 6.7, like a lot.
– Chopper3
Jun 21 '18 at 8:45
Go to the 6.7 HCL, check EVERY SINGLE component is supported by 6.7, they stopped supporting a LOT of kit between 6.5 and 6.7, like a lot.
– Chopper3
Jun 21 '18 at 8:45
I did check the CPU and RAID in advance, they were listed on 6.5, 6.5U1, 6.5U2, and 6.7. The only component I know of that isn't supported is the Atheros Killer NIC on the motherboard.
– Adambean
Jun 21 '18 at 9:23
I did check the CPU and RAID in advance, they were listed on 6.5, 6.5U1, 6.5U2, and 6.7. The only component I know of that isn't supported is the Atheros Killer NIC on the motherboard.
– Adambean
Jun 21 '18 at 9:23
what sort of server systemboard are you using that's got an Atheros Killer NIC on it?!?!
– Chopper3
Jun 21 '18 at 9:44
what sort of server systemboard are you using that's got an Atheros Killer NIC on it?!?!
– Chopper3
Jun 21 '18 at 9:44
Heh, the server for our office actually has a workstation type motherboard. (It's a Gigabyte GA-X170-EXTREME ECC.) It has a Xeon E3-1270 v5 CPU though with ECC memory, and an LSI MegaRAID 9260-8i. --- The other server at our DC doesn't have a Killer NIC though. ;) That has a Xeon E3-1245 v2 CPU with ECC memory, and an LSI MegaRAID 9260-4i. --- Both use Intel NICs, which definitely work, as I can talk to the servers fine.
– Adambean
Jun 21 '18 at 9:50
Heh, the server for our office actually has a workstation type motherboard. (It's a Gigabyte GA-X170-EXTREME ECC.) It has a Xeon E3-1270 v5 CPU though with ECC memory, and an LSI MegaRAID 9260-8i. --- The other server at our DC doesn't have a Killer NIC though. ;) That has a Xeon E3-1245 v2 CPU with ECC memory, and an LSI MegaRAID 9260-4i. --- Both use Intel NICs, which definitely work, as I can talk to the servers fine.
– Adambean
Jun 21 '18 at 9:50
Silly me. "storcli" appears to work fine, I didn't realise "/cx" should actually be "/c0" to mean "use controller at index 0". I'm not bothered if MegaCLI doesn't work any more as storcli is the later product. Bit weird about the web UI and MSM utility though.
– Adambean
Jun 21 '18 at 14:55
Silly me. "storcli" appears to work fine, I didn't realise "/cx" should actually be "/c0" to mean "use controller at index 0". I'm not bothered if MegaCLI doesn't work any more as storcli is the later product. Bit weird about the web UI and MSM utility though.
– Adambean
Jun 21 '18 at 14:55
add a comment |
2 Answers
2
active
oldest
votes
You should use
./storcli /c0 show
(O = number of the controler, you see it in your first command ./storcli show -> Ctl 0)
If you want to see every controller you can use :
./storcli /call show
If you want to see every virtual drive you can use :
./storcli /call/eall show
If you want to see every physical drive you can use :
./storcli /call/eall/sall show
Or you can use :
./storcli /call show all
for every informations of all controllers.
In your case you have 1 controller, so you can use
./storcli /c0 show all
For alarm status/control you can use :
./storcli /c0 show alarm (show alarm status)
./storcli /c0 set alarm=silence (mute buzer alarm)
./storcli /c0 set alarm=off (shutdown alarm)
Thanks, I got this working already. (Comment 21 Jun at 14:55) This won't fix the ESXi UI though.
– Adambean
Aug 15 '18 at 17:35
Yes same issue here with a 9260-8i on ESXi 6.7. I use a script for check the raid status with nagios but you can use directly on a linux machine with an ssh acces to the ESXi.
– IceCubee-FR
Aug 15 '18 at 17:59
add a comment |
I was unable to get storcli or MegaCLI to display my H200 (crossflashed to 9211-8i in IR mode) adapter information:
[root@hostname:~] esxcli storage core adapter list | grep mpt
vmhba2 mpt2sas link-n/a sas.xx (0000:02:00.0) LSI Logic / Symbios Logic Dell 6Gbps SAS HBA Adapter
[root@hostname:~] /opt/lsi/storcli/storcli /c0 show
CLI Version = 007.0606.0000.0000 Mar 20, 2018
Operating system = VMkernel 6.7.0
Controller = 0
Status = Failure
Description = Controller 0 not found
[root@hostname:/opt/lsi/MegaCLI] ./MegaCli -adpCount
Controller Count: 0.
I found sas2ircu P20 on the Broadcom website which seems to work (as of 6.7.0 Update 1 Build 11675023):
Download location: https://docs.broadcom.com/docs-and-downloads/host-bus-adapters/host-bus-adapters-common-files/sas_sata_6g_p20/SAS2IRCU_P20.zip
Extract the vmware-esx-sas2ircu.vib from this file and upload it to your ESXi host. Install it using the following command (change path to match your datastore):
[root@hostname:~] esxcli software vib install -v /vmfs/volumes/Datastore/vmware-esx-sas2ircu.vib --no-sig-check
Installation Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: LSI_bootbank_vmware-esx-sas2ircu_20.00.00.00-03
VIBs Removed:
VIBs Skipped:
I was then able to use sas2ircu to display my adapter information:
[root@hostname:~] /opt/lsi/bin/sas2ircu 0 display
LSI Corporation SAS2 IR Configuration Utility.
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved.
Read configuration has been initiated for controller 0
------------------------------------------------------------------------
Controller information
------------------------------------------------------------------------
Controller type : SAS2008
BIOS version : 7.39.02.00
Firmware version : 20.00.07.00
Channel description : 1 Serial Attached SCSI
Initiator ID : 0
Maximum physical devices : 255
Concurrent commands supported : 1720
Slot : 4
Segment : 0
Bus : 2
Device : 0
Function : 0
RAID Support : Yes
------------------------------------------------------------------------
IR Volume information
------------------------------------------------------------------------
IR volume 1
Volume ID : 286
Status of volume : Okay (OKY)
Volume wwid :
RAID level : RAID1
Size (in MB) : 113487
Physical hard disks :
PHY[0] Enclosure#/Slot# : 1:4
PHY[1] Enclosure#/Slot# : 1:5
------------------------------------------------------------------------
Physical device information
------------------------------------------------------------------------
Initiator at ID #0
Device is a Hard disk
Enclosure # : 1
Slot # : 4
SAS Address :
State : Optimal (OPT)
Size (in MB)/(in sectors) : 114473/234441647
Manufacturer : ATA
Model Number : KINGSTON SA400S3
Firmware Revision : B1D1
Serial No :
GUID :
Protocol : SATA
Drive Type : SATA_SSD
Device is a Hard disk
Enclosure # : 1
Slot # : 5
SAS Address :
State : Optimal (OPT)
Size (in MB)/(in sectors) : 114473/234441647
Manufacturer : ATA
Model Number : KINGSTON SA400S3
Firmware Revision : B1D1
Serial No :
GUID :
Protocol : SATA
Drive Type : SATA_SSD
------------------------------------------------------------------------
Enclosure information
------------------------------------------------------------------------
Enclosure# : 1
Logical ID :
Numslots : 8
StartSlot : 0
------------------------------------------------------------------------
SAS2IRCU: Command DISPLAY Completed Successfully.
SAS2IRCU: Utility Completed Successfully.
I'll grab this information via SSH and monitor my array this way.
add a comment |
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f917601%2fesxi-6-7-monitor-hardware-storage-not-showing-usual-results%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You should use
./storcli /c0 show
(O = number of the controler, you see it in your first command ./storcli show -> Ctl 0)
If you want to see every controller you can use :
./storcli /call show
If you want to see every virtual drive you can use :
./storcli /call/eall show
If you want to see every physical drive you can use :
./storcli /call/eall/sall show
Or you can use :
./storcli /call show all
for every informations of all controllers.
In your case you have 1 controller, so you can use
./storcli /c0 show all
For alarm status/control you can use :
./storcli /c0 show alarm (show alarm status)
./storcli /c0 set alarm=silence (mute buzer alarm)
./storcli /c0 set alarm=off (shutdown alarm)
Thanks, I got this working already. (Comment 21 Jun at 14:55) This won't fix the ESXi UI though.
– Adambean
Aug 15 '18 at 17:35
Yes same issue here with a 9260-8i on ESXi 6.7. I use a script for check the raid status with nagios but you can use directly on a linux machine with an ssh acces to the ESXi.
– IceCubee-FR
Aug 15 '18 at 17:59
add a comment |
You should use
./storcli /c0 show
(O = number of the controler, you see it in your first command ./storcli show -> Ctl 0)
If you want to see every controller you can use :
./storcli /call show
If you want to see every virtual drive you can use :
./storcli /call/eall show
If you want to see every physical drive you can use :
./storcli /call/eall/sall show
Or you can use :
./storcli /call show all
for every informations of all controllers.
In your case you have 1 controller, so you can use
./storcli /c0 show all
For alarm status/control you can use :
./storcli /c0 show alarm (show alarm status)
./storcli /c0 set alarm=silence (mute buzer alarm)
./storcli /c0 set alarm=off (shutdown alarm)
Thanks, I got this working already. (Comment 21 Jun at 14:55) This won't fix the ESXi UI though.
– Adambean
Aug 15 '18 at 17:35
Yes same issue here with a 9260-8i on ESXi 6.7. I use a script for check the raid status with nagios but you can use directly on a linux machine with an ssh acces to the ESXi.
– IceCubee-FR
Aug 15 '18 at 17:59
add a comment |
You should use
./storcli /c0 show
(O = number of the controler, you see it in your first command ./storcli show -> Ctl 0)
If you want to see every controller you can use :
./storcli /call show
If you want to see every virtual drive you can use :
./storcli /call/eall show
If you want to see every physical drive you can use :
./storcli /call/eall/sall show
Or you can use :
./storcli /call show all
for every informations of all controllers.
In your case you have 1 controller, so you can use
./storcli /c0 show all
For alarm status/control you can use :
./storcli /c0 show alarm (show alarm status)
./storcli /c0 set alarm=silence (mute buzer alarm)
./storcli /c0 set alarm=off (shutdown alarm)
You should use
./storcli /c0 show
(O = number of the controler, you see it in your first command ./storcli show -> Ctl 0)
If you want to see every controller you can use :
./storcli /call show
If you want to see every virtual drive you can use :
./storcli /call/eall show
If you want to see every physical drive you can use :
./storcli /call/eall/sall show
Or you can use :
./storcli /call show all
for every informations of all controllers.
In your case you have 1 controller, so you can use
./storcli /c0 show all
For alarm status/control you can use :
./storcli /c0 show alarm (show alarm status)
./storcli /c0 set alarm=silence (mute buzer alarm)
./storcli /c0 set alarm=off (shutdown alarm)
edited Aug 15 '18 at 8:49
answered Aug 15 '18 at 8:34
IceCubee-FRIceCubee-FR
11
11
Thanks, I got this working already. (Comment 21 Jun at 14:55) This won't fix the ESXi UI though.
– Adambean
Aug 15 '18 at 17:35
Yes same issue here with a 9260-8i on ESXi 6.7. I use a script for check the raid status with nagios but you can use directly on a linux machine with an ssh acces to the ESXi.
– IceCubee-FR
Aug 15 '18 at 17:59
add a comment |
Thanks, I got this working already. (Comment 21 Jun at 14:55) This won't fix the ESXi UI though.
– Adambean
Aug 15 '18 at 17:35
Yes same issue here with a 9260-8i on ESXi 6.7. I use a script for check the raid status with nagios but you can use directly on a linux machine with an ssh acces to the ESXi.
– IceCubee-FR
Aug 15 '18 at 17:59
Thanks, I got this working already. (Comment 21 Jun at 14:55) This won't fix the ESXi UI though.
– Adambean
Aug 15 '18 at 17:35
Thanks, I got this working already. (Comment 21 Jun at 14:55) This won't fix the ESXi UI though.
– Adambean
Aug 15 '18 at 17:35
Yes same issue here with a 9260-8i on ESXi 6.7. I use a script for check the raid status with nagios but you can use directly on a linux machine with an ssh acces to the ESXi.
– IceCubee-FR
Aug 15 '18 at 17:59
Yes same issue here with a 9260-8i on ESXi 6.7. I use a script for check the raid status with nagios but you can use directly on a linux machine with an ssh acces to the ESXi.
– IceCubee-FR
Aug 15 '18 at 17:59
add a comment |
I was unable to get storcli or MegaCLI to display my H200 (crossflashed to 9211-8i in IR mode) adapter information:
[root@hostname:~] esxcli storage core adapter list | grep mpt
vmhba2 mpt2sas link-n/a sas.xx (0000:02:00.0) LSI Logic / Symbios Logic Dell 6Gbps SAS HBA Adapter
[root@hostname:~] /opt/lsi/storcli/storcli /c0 show
CLI Version = 007.0606.0000.0000 Mar 20, 2018
Operating system = VMkernel 6.7.0
Controller = 0
Status = Failure
Description = Controller 0 not found
[root@hostname:/opt/lsi/MegaCLI] ./MegaCli -adpCount
Controller Count: 0.
I found sas2ircu P20 on the Broadcom website which seems to work (as of 6.7.0 Update 1 Build 11675023):
Download location: https://docs.broadcom.com/docs-and-downloads/host-bus-adapters/host-bus-adapters-common-files/sas_sata_6g_p20/SAS2IRCU_P20.zip
Extract the vmware-esx-sas2ircu.vib from this file and upload it to your ESXi host. Install it using the following command (change path to match your datastore):
[root@hostname:~] esxcli software vib install -v /vmfs/volumes/Datastore/vmware-esx-sas2ircu.vib --no-sig-check
Installation Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: LSI_bootbank_vmware-esx-sas2ircu_20.00.00.00-03
VIBs Removed:
VIBs Skipped:
I was then able to use sas2ircu to display my adapter information:
[root@hostname:~] /opt/lsi/bin/sas2ircu 0 display
LSI Corporation SAS2 IR Configuration Utility.
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved.
Read configuration has been initiated for controller 0
------------------------------------------------------------------------
Controller information
------------------------------------------------------------------------
Controller type : SAS2008
BIOS version : 7.39.02.00
Firmware version : 20.00.07.00
Channel description : 1 Serial Attached SCSI
Initiator ID : 0
Maximum physical devices : 255
Concurrent commands supported : 1720
Slot : 4
Segment : 0
Bus : 2
Device : 0
Function : 0
RAID Support : Yes
------------------------------------------------------------------------
IR Volume information
------------------------------------------------------------------------
IR volume 1
Volume ID : 286
Status of volume : Okay (OKY)
Volume wwid :
RAID level : RAID1
Size (in MB) : 113487
Physical hard disks :
PHY[0] Enclosure#/Slot# : 1:4
PHY[1] Enclosure#/Slot# : 1:5
------------------------------------------------------------------------
Physical device information
------------------------------------------------------------------------
Initiator at ID #0
Device is a Hard disk
Enclosure # : 1
Slot # : 4
SAS Address :
State : Optimal (OPT)
Size (in MB)/(in sectors) : 114473/234441647
Manufacturer : ATA
Model Number : KINGSTON SA400S3
Firmware Revision : B1D1
Serial No :
GUID :
Protocol : SATA
Drive Type : SATA_SSD
Device is a Hard disk
Enclosure # : 1
Slot # : 5
SAS Address :
State : Optimal (OPT)
Size (in MB)/(in sectors) : 114473/234441647
Manufacturer : ATA
Model Number : KINGSTON SA400S3
Firmware Revision : B1D1
Serial No :
GUID :
Protocol : SATA
Drive Type : SATA_SSD
------------------------------------------------------------------------
Enclosure information
------------------------------------------------------------------------
Enclosure# : 1
Logical ID :
Numslots : 8
StartSlot : 0
------------------------------------------------------------------------
SAS2IRCU: Command DISPLAY Completed Successfully.
SAS2IRCU: Utility Completed Successfully.
I'll grab this information via SSH and monitor my array this way.
add a comment |
I was unable to get storcli or MegaCLI to display my H200 (crossflashed to 9211-8i in IR mode) adapter information:
[root@hostname:~] esxcli storage core adapter list | grep mpt
vmhba2 mpt2sas link-n/a sas.xx (0000:02:00.0) LSI Logic / Symbios Logic Dell 6Gbps SAS HBA Adapter
[root@hostname:~] /opt/lsi/storcli/storcli /c0 show
CLI Version = 007.0606.0000.0000 Mar 20, 2018
Operating system = VMkernel 6.7.0
Controller = 0
Status = Failure
Description = Controller 0 not found
[root@hostname:/opt/lsi/MegaCLI] ./MegaCli -adpCount
Controller Count: 0.
I found sas2ircu P20 on the Broadcom website which seems to work (as of 6.7.0 Update 1 Build 11675023):
Download location: https://docs.broadcom.com/docs-and-downloads/host-bus-adapters/host-bus-adapters-common-files/sas_sata_6g_p20/SAS2IRCU_P20.zip
Extract the vmware-esx-sas2ircu.vib from this file and upload it to your ESXi host. Install it using the following command (change path to match your datastore):
[root@hostname:~] esxcli software vib install -v /vmfs/volumes/Datastore/vmware-esx-sas2ircu.vib --no-sig-check
Installation Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: LSI_bootbank_vmware-esx-sas2ircu_20.00.00.00-03
VIBs Removed:
VIBs Skipped:
I was then able to use sas2ircu to display my adapter information:
[root@hostname:~] /opt/lsi/bin/sas2ircu 0 display
LSI Corporation SAS2 IR Configuration Utility.
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved.
Read configuration has been initiated for controller 0
------------------------------------------------------------------------
Controller information
------------------------------------------------------------------------
Controller type : SAS2008
BIOS version : 7.39.02.00
Firmware version : 20.00.07.00
Channel description : 1 Serial Attached SCSI
Initiator ID : 0
Maximum physical devices : 255
Concurrent commands supported : 1720
Slot : 4
Segment : 0
Bus : 2
Device : 0
Function : 0
RAID Support : Yes
------------------------------------------------------------------------
IR Volume information
------------------------------------------------------------------------
IR volume 1
Volume ID : 286
Status of volume : Okay (OKY)
Volume wwid :
RAID level : RAID1
Size (in MB) : 113487
Physical hard disks :
PHY[0] Enclosure#/Slot# : 1:4
PHY[1] Enclosure#/Slot# : 1:5
------------------------------------------------------------------------
Physical device information
------------------------------------------------------------------------
Initiator at ID #0
Device is a Hard disk
Enclosure # : 1
Slot # : 4
SAS Address :
State : Optimal (OPT)
Size (in MB)/(in sectors) : 114473/234441647
Manufacturer : ATA
Model Number : KINGSTON SA400S3
Firmware Revision : B1D1
Serial No :
GUID :
Protocol : SATA
Drive Type : SATA_SSD
Device is a Hard disk
Enclosure # : 1
Slot # : 5
SAS Address :
State : Optimal (OPT)
Size (in MB)/(in sectors) : 114473/234441647
Manufacturer : ATA
Model Number : KINGSTON SA400S3
Firmware Revision : B1D1
Serial No :
GUID :
Protocol : SATA
Drive Type : SATA_SSD
------------------------------------------------------------------------
Enclosure information
------------------------------------------------------------------------
Enclosure# : 1
Logical ID :
Numslots : 8
StartSlot : 0
------------------------------------------------------------------------
SAS2IRCU: Command DISPLAY Completed Successfully.
SAS2IRCU: Utility Completed Successfully.
I'll grab this information via SSH and monitor my array this way.
add a comment |
I was unable to get storcli or MegaCLI to display my H200 (crossflashed to 9211-8i in IR mode) adapter information:
[root@hostname:~] esxcli storage core adapter list | grep mpt
vmhba2 mpt2sas link-n/a sas.xx (0000:02:00.0) LSI Logic / Symbios Logic Dell 6Gbps SAS HBA Adapter
[root@hostname:~] /opt/lsi/storcli/storcli /c0 show
CLI Version = 007.0606.0000.0000 Mar 20, 2018
Operating system = VMkernel 6.7.0
Controller = 0
Status = Failure
Description = Controller 0 not found
[root@hostname:/opt/lsi/MegaCLI] ./MegaCli -adpCount
Controller Count: 0.
I found sas2ircu P20 on the Broadcom website which seems to work (as of 6.7.0 Update 1 Build 11675023):
Download location: https://docs.broadcom.com/docs-and-downloads/host-bus-adapters/host-bus-adapters-common-files/sas_sata_6g_p20/SAS2IRCU_P20.zip
Extract the vmware-esx-sas2ircu.vib from this file and upload it to your ESXi host. Install it using the following command (change path to match your datastore):
[root@hostname:~] esxcli software vib install -v /vmfs/volumes/Datastore/vmware-esx-sas2ircu.vib --no-sig-check
Installation Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: LSI_bootbank_vmware-esx-sas2ircu_20.00.00.00-03
VIBs Removed:
VIBs Skipped:
I was then able to use sas2ircu to display my adapter information:
[root@hostname:~] /opt/lsi/bin/sas2ircu 0 display
LSI Corporation SAS2 IR Configuration Utility.
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved.
Read configuration has been initiated for controller 0
------------------------------------------------------------------------
Controller information
------------------------------------------------------------------------
Controller type : SAS2008
BIOS version : 7.39.02.00
Firmware version : 20.00.07.00
Channel description : 1 Serial Attached SCSI
Initiator ID : 0
Maximum physical devices : 255
Concurrent commands supported : 1720
Slot : 4
Segment : 0
Bus : 2
Device : 0
Function : 0
RAID Support : Yes
------------------------------------------------------------------------
IR Volume information
------------------------------------------------------------------------
IR volume 1
Volume ID : 286
Status of volume : Okay (OKY)
Volume wwid :
RAID level : RAID1
Size (in MB) : 113487
Physical hard disks :
PHY[0] Enclosure#/Slot# : 1:4
PHY[1] Enclosure#/Slot# : 1:5
------------------------------------------------------------------------
Physical device information
------------------------------------------------------------------------
Initiator at ID #0
Device is a Hard disk
Enclosure # : 1
Slot # : 4
SAS Address :
State : Optimal (OPT)
Size (in MB)/(in sectors) : 114473/234441647
Manufacturer : ATA
Model Number : KINGSTON SA400S3
Firmware Revision : B1D1
Serial No :
GUID :
Protocol : SATA
Drive Type : SATA_SSD
Device is a Hard disk
Enclosure # : 1
Slot # : 5
SAS Address :
State : Optimal (OPT)
Size (in MB)/(in sectors) : 114473/234441647
Manufacturer : ATA
Model Number : KINGSTON SA400S3
Firmware Revision : B1D1
Serial No :
GUID :
Protocol : SATA
Drive Type : SATA_SSD
------------------------------------------------------------------------
Enclosure information
------------------------------------------------------------------------
Enclosure# : 1
Logical ID :
Numslots : 8
StartSlot : 0
------------------------------------------------------------------------
SAS2IRCU: Command DISPLAY Completed Successfully.
SAS2IRCU: Utility Completed Successfully.
I'll grab this information via SSH and monitor my array this way.
I was unable to get storcli or MegaCLI to display my H200 (crossflashed to 9211-8i in IR mode) adapter information:
[root@hostname:~] esxcli storage core adapter list | grep mpt
vmhba2 mpt2sas link-n/a sas.xx (0000:02:00.0) LSI Logic / Symbios Logic Dell 6Gbps SAS HBA Adapter
[root@hostname:~] /opt/lsi/storcli/storcli /c0 show
CLI Version = 007.0606.0000.0000 Mar 20, 2018
Operating system = VMkernel 6.7.0
Controller = 0
Status = Failure
Description = Controller 0 not found
[root@hostname:/opt/lsi/MegaCLI] ./MegaCli -adpCount
Controller Count: 0.
I found sas2ircu P20 on the Broadcom website which seems to work (as of 6.7.0 Update 1 Build 11675023):
Download location: https://docs.broadcom.com/docs-and-downloads/host-bus-adapters/host-bus-adapters-common-files/sas_sata_6g_p20/SAS2IRCU_P20.zip
Extract the vmware-esx-sas2ircu.vib from this file and upload it to your ESXi host. Install it using the following command (change path to match your datastore):
[root@hostname:~] esxcli software vib install -v /vmfs/volumes/Datastore/vmware-esx-sas2ircu.vib --no-sig-check
Installation Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: LSI_bootbank_vmware-esx-sas2ircu_20.00.00.00-03
VIBs Removed:
VIBs Skipped:
I was then able to use sas2ircu to display my adapter information:
[root@hostname:~] /opt/lsi/bin/sas2ircu 0 display
LSI Corporation SAS2 IR Configuration Utility.
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved.
Read configuration has been initiated for controller 0
------------------------------------------------------------------------
Controller information
------------------------------------------------------------------------
Controller type : SAS2008
BIOS version : 7.39.02.00
Firmware version : 20.00.07.00
Channel description : 1 Serial Attached SCSI
Initiator ID : 0
Maximum physical devices : 255
Concurrent commands supported : 1720
Slot : 4
Segment : 0
Bus : 2
Device : 0
Function : 0
RAID Support : Yes
------------------------------------------------------------------------
IR Volume information
------------------------------------------------------------------------
IR volume 1
Volume ID : 286
Status of volume : Okay (OKY)
Volume wwid :
RAID level : RAID1
Size (in MB) : 113487
Physical hard disks :
PHY[0] Enclosure#/Slot# : 1:4
PHY[1] Enclosure#/Slot# : 1:5
------------------------------------------------------------------------
Physical device information
------------------------------------------------------------------------
Initiator at ID #0
Device is a Hard disk
Enclosure # : 1
Slot # : 4
SAS Address :
State : Optimal (OPT)
Size (in MB)/(in sectors) : 114473/234441647
Manufacturer : ATA
Model Number : KINGSTON SA400S3
Firmware Revision : B1D1
Serial No :
GUID :
Protocol : SATA
Drive Type : SATA_SSD
Device is a Hard disk
Enclosure # : 1
Slot # : 5
SAS Address :
State : Optimal (OPT)
Size (in MB)/(in sectors) : 114473/234441647
Manufacturer : ATA
Model Number : KINGSTON SA400S3
Firmware Revision : B1D1
Serial No :
GUID :
Protocol : SATA
Drive Type : SATA_SSD
------------------------------------------------------------------------
Enclosure information
------------------------------------------------------------------------
Enclosure# : 1
Logical ID :
Numslots : 8
StartSlot : 0
------------------------------------------------------------------------
SAS2IRCU: Command DISPLAY Completed Successfully.
SAS2IRCU: Utility Completed Successfully.
I'll grab this information via SSH and monitor my array this way.
answered Mar 2 at 16:40
JeffWDHJeffWDH
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f917601%2fesxi-6-7-monitor-hardware-storage-not-showing-usual-results%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Go to the 6.7 HCL, check EVERY SINGLE component is supported by 6.7, they stopped supporting a LOT of kit between 6.5 and 6.7, like a lot.
– Chopper3
Jun 21 '18 at 8:45
I did check the CPU and RAID in advance, they were listed on 6.5, 6.5U1, 6.5U2, and 6.7. The only component I know of that isn't supported is the Atheros Killer NIC on the motherboard.
– Adambean
Jun 21 '18 at 9:23
what sort of server systemboard are you using that's got an Atheros Killer NIC on it?!?!
– Chopper3
Jun 21 '18 at 9:44
Heh, the server for our office actually has a workstation type motherboard. (It's a Gigabyte GA-X170-EXTREME ECC.) It has a Xeon E3-1270 v5 CPU though with ECC memory, and an LSI MegaRAID 9260-8i. --- The other server at our DC doesn't have a Killer NIC though. ;) That has a Xeon E3-1245 v2 CPU with ECC memory, and an LSI MegaRAID 9260-4i. --- Both use Intel NICs, which definitely work, as I can talk to the servers fine.
– Adambean
Jun 21 '18 at 9:50
Silly me. "storcli" appears to work fine, I didn't realise "/cx" should actually be "/c0" to mean "use controller at index 0". I'm not bothered if MegaCLI doesn't work any more as storcli is the later product. Bit weird about the web UI and MSM utility though.
– Adambean
Jun 21 '18 at 14:55