Difference between revisions of "Oliebol node type details"

From PDP/Grid Wiki
Jump to navigationJump to search
 
Line 15: Line 15:
  
 
See the [http://www.lsi.com/downloads/Public/RAID%20Controllers/RAID%20Controllers%20Common%20Files/StorCLI_RefMan_revf.pdf StorCLI reference manual] on how to use it.
 
See the [http://www.lsi.com/downloads/Public/RAID%20Controllers/RAID%20Controllers%20Common%20Files/StorCLI_RefMan_revf.pdf StorCLI reference manual] on how to use it.
 +
 +
 +
== Replacing failed drives ==
 +
 +
Normally, a drive replacement should automatically initiate a rebuild of the array. There has been a case where a new drive was not recognised and the StorCLI reported 'No drive found!' no matter what. As a last resort attempt, a complete restart of the controller may get things going again:
 +
/opt/MegaRAID/storcli/storcli64 /c0 restart
 +
This will make the operating system unresponsive for a couple of seconds while the controller restarts and file system operations are not possible, but the system should come back and recognise the newly inserted drive.

Latest revision as of 10:57, 27 March 2018

Hardware configuration

Oliebol nodes are 4u Supermicro diskservers with 24 front-loading and 12 back-loading SAS disks.

The Supermicro chassis type is 847.

There are two internal 3.5" disks that are hard to reach because they're underneath the motherboard subframe, which can be slid out backwards (requires the removal of one additional screw in addition to the four required to remove the top.)

Opening the chassis means removing it from the rack, which requires at least two people.

The RAID controller installed in these systems are of the type LSI MegaRAID SAS 9270-8i, which can be managed with the MegaRAID_Storage_Manager software.

/usr/local/MegaRAID\ Storage\ Manager/StorCLI/storcli64 /c0 show all

See the StorCLI reference manual on how to use it.


Replacing failed drives

Normally, a drive replacement should automatically initiate a rebuild of the array. There has been a case where a new drive was not recognised and the StorCLI reported 'No drive found!' no matter what. As a last resort attempt, a complete restart of the controller may get things going again:

/opt/MegaRAID/storcli/storcli64 /c0 restart

This will make the operating system unresponsive for a couple of seconds while the controller restarts and file system operations are not possible, but the system should come back and recognise the newly inserted drive.