Changes between Version 42 and Version 43 of LSIMegaRAIDSAS

Timestamp:

10/14/09 15:22:43 (15 years ago)

Author:

Adam Cécile

Comment:

Add a section to rebuild a drive by hand

LSIMegaRAIDSAS

@@ -395 +395 @@
 }}}
 
-
 '''References (extracted from Dell !OpenManage doc):'''
 
@@ -413 +412 @@
     * Cache I/O. Specifies that all reads are buffered in cache memory.
     * Direct I/O. Specifies that reads are not buffered in cache memory. When using direct I/O, data is transferred to the controller cache and the host system simultaneously during a read request. If a subsequent read request requires data from the same data block, it can be read directly from the controller cache. The direct I/O setting does not override the cache policy settings. Direct I/O is also the default setting. 
+
+==== Rebuilding a disk by hand when it doesn't occur automatically ====
+
+I noticed that strange behavior on an IBM controller. Unplugging and pluging back a disk from an array doesn't make the controller rebuild the array with that disk.[[BR]]
+Here is what to do:
+
+{{{
+server:~# megacli -PDlist -a0
+[...]
+Enclosure Device ID: 252
+Slot Number: 4          
+Device Id: 3            
+[...]
+Firmware state: Unconfigured(bad)
+[...]
+Secured: Unsecured
+Locked: Unlocked
+Foreign State: Foreign
+Foreign Secure: Drive is not secured by a foreign lock key
+Device Speed: 6.0Gb/s
+Link Speed: 3.0Gb/s
+Media Type: Hard Disk Device
+[...]
+}}}
+The disk drive identified as ![252:4] ([enclosureid:slotnumber]) is currently 'Unconfigured(bad)'.
+
+Make the drive online again:
+{{{
+server:~# megacli -PDMakeGood -PhysDrv[252:4] -a0
+Adapter: 0: EnclId-252 SlotId-4 state changed to Unconfigured-Good.
+}}}
+
+The controller will now recognise the disk as being a "foreign" one. It means it has detected some RAID informations on it, and thus, considers it as a disk being part of an array that may be imported into current controller configuration.[[BR]]
+
+We will now ask the controller to scan for foreign configuration and drop it:
+{{{
+server:~# megacli -CfgForeign -Scan -a0
+There are 1 foreign configuration(s) on controller 0.
+
+server:~# megacli -CfgForeign -Clear -a0
+Foreign configuration 0 is cleared on controller 0.
+}}}
+
+The disk should now be available for getting back into the array.[[BR]]
+Let's check it:
+{{{
+server:~# megacli -PDList -a0
+[...]
+Enclosure Device ID: 252
+Slot Number: 4          
+[...]
+Firmware state: Unconfigured(good), Spun Up
+Foreign State: None
+[...]
+}}}
+
+We now need to figure out how that disk was identified inside the RAID array:
+{{{
+server:~# megacli -CfgDsply -a0
+[...]
+DISK GROUPS: 1
+Number of Spans: 1
+SPAN: 0           
+Span Reference: 0x01
+Number of PDs: 4    
+Number of VDs: 1    
+Number of dedicated Hotspares: 0
+Virtual Disk Information:       
+Virtual Disk: 0 (Target Id: 1) 
+[...]
+
+Physical Disk: 2
+
+Physical Disk: 3
+Enclosure Device ID: 252
+Slot Number: 5          
+Device Id: 4            
+[...]
+}}}
+
+Here is what's important here:
+
+''Span Reference: 0x01'' is the number of the array (strip the 0x0 part).[[BR]]
+We can see that ''Physical Disk: 2'' has no information, which means the drive is missing.[[BR]]
+
+Now we have all we need to add the disk back into the array.
+
+Get the disk [252:4] back into array 1, as disk 2:
+{{{
+server:~# megacli -PdReplaceMissing -PhysDrv[252:4] -array1 -row2 -a0
+Adapter: 0: Missing PD at Array 1, Row 2 is replaced
+}}}
+
+And finally start rebuilding:
+{{{
+server:~# megacli -PDRbld -Start -PhysDrv[252:4] -a0
+Started rebuild progress on device(Encl-252 Slot-4)
+}}}
 
 === 3.3.3. Periodic checks ===