Hardware Raid mit eingebautem Adaptec Controller administrieren

Für Dedicated Server mit Adaptec Raid Controller

In diesem Artikel erfahren Sie, wie Sie Ihr Hardware Raid überwachen und wiederaufbauen, wenn Ihr Linux Server über einen Adaptec Raid Controler verfügt.

Mit der Software arcconf64 haben Sie die Möglichkeit, den Raid Controller Ihres Servers zu steuern. So können Sie zum Beispiel Informationen auslesen und bei Bedarf ein Hardware Raid wieder aufbauen. arcconf64 wird standardmäßig auf dem Server installiert.

Loggen Sie sich per SSH auf Ihrem Linux Server ein und werden Sie Root.
Lesen Sie Informationen über Ihren Server mit dem Befehl arcconf64 getconfig 1 aus. Hier ein Beispiel:

Controllers found: 1
----------------------------------------------------------------------
Controller information
----------------------------------------------------------------------
Controller Status : Optimal
Channel description : SAS/SATA
Controller Model : Adaptec 6805E R5
Controller Serial Number : 4A12135DADB
Controller World Wide Name : 50000D1107D73700
Physical Slot : 6
Temperature : 60 C/ 140 F (Normal)
Installed memory : 128 MB
Copyback : Disabled
Background consistency check : Disabled
Background consistency check period : 30
Automatic Failover : Enabled
Global task priority : High
Performance Mode : Default/Dynamic
Host bus type : PCIe
Host bus speed : 5000 MHz
Host bus link width : 4 bit(s)/link(s)
Stayawake period : Disabled
Spinup limit internal drives : 0
Spinup limit external drives : 0
Defunct disk drive count : 0
Logical devices/Failed/Degraded : 2/0/0
NCQ status : Enabled
Statistics data collection mode : Enabled
--------------------------------------------------------
Controller Version Information
--------------------------------------------------------
BIOS : 5.2-0 (19109)
Firmware : 5.2-0 (19109)
Driver : 1.2-0 (30200)
Boot Flash : 5.2-0 (19109)

----------------------------------------------------------------------
Logical device information
----------------------------------------------------------------------
Logical device number 0
Logical device name : Volume#0
Block Size of member drives : 512 Bytes
RAID level : 1
Unique Identifier : D605B3AA
Status of logical device : Optimal
Size : 228342 MB
Parity space : 228352 MB
Read-cache setting : Enabled
Read-cache status : On
Write-cache setting : Enabled
Write-cache status : On
Partitioned : Yes
Protected by Hot-Spare : No
Bootable : Yes
Failed stripes : No
Power settings : Disabled
--------------------------------------------------------
Logical device segment information
--------------------------------------------------------
Segment 0 : Present (Controller:1,Connector:0,Device:0) WD-WCC131993448
Segment 1 : Present (Controller:1,Connector:0,Device:1) WD-WCC132055406

Logical device number 1
Logical device name : Volume#1
Block Size of member drives : 512 Bytes
RAID level : 1
Unique Identifier : 4F0DB3AA
Status of logical device : Optimal
Size : 3586038 MB
Parity space : 3586048 MB
Read-cache setting : Enabled
Read-cache status : On
Write-cache setting : Enabled
Write-cache status : On
Partitioned : Yes
Protected by Hot-Spare : No
Bootable : No
Failed stripes : No
Power settings : Disabled
--------------------------------------------------------
Logical device segment information
--------------------------------------------------------
Segment 0 : Present (Controller:1,Connector:0,Device:0) WD-WCC131993448
Segment 1 : Present (Controller:1,Connector:0,Device:1) WD-WCC132055406


----------------------------------------------------------------------
Physical Device information
----------------------------------------------------------------------
Device #0
Device is a Hard drive
State : Online
Block Size : 512 Bytes
Supported : Yes
Transfer Speed : SATA 6.0 Gb/s
Reported Channel,Device(T:L) : 0,0(0:0)
Reported Location : Connector 0, Device 0
Vendor : WDC
Model : WD4000F9YZ-09N20
Firmware : 01.01A01
Serial number : WD-WCC131993448
World-wide name : 50014EE25F66F1E0
Reserved Size : 1072920 KB
Used Size : 3814400 MB
Unused Size : 64 KB
Total Size : 3815447 MB
Write Cache : Enabled (write-back)
FRU : None
S.M.A.R.T. : No
S.M.A.R.T. warnings : 0
Power State : Full rpm
Supported Power States : Full rpm,Powered off,Reduced rpm
SSD : No
NCQ status : Enabled
Device #1
Device is a Hard drive
State : Online
Block Size : 512 Bytes
Supported : Yes
Transfer Speed : SATA 6.0 Gb/s
Reported Channel,Device(T:L) : 0,1(1:0)
Reported Location : Connector 0, Device 1
Vendor : WDC
Model : WD4000F9YZ-09N20
Firmware : 01.01A01
Serial number : WD-WCC132055406
World-wide name : 50014EE25F678455
Reserved Size : 1072920 KB
Used Size : 3814400 MB
Unused Size : 64 KB
Total Size : 3815447 MB
Write Cache : Enabled (write-back)
FRU : None
S.M.A.R.T. : No
S.M.A.R.T. warnings : 0
Power State : Full rpm
Supported Power States : Full rpm,Powered off,Reduced rpm
SSD : No
NCQ status : Enabled



Command completed successfully.

Lassen Sie sich die Serverereignisse mit dem Befehl arcconf64 getlogs event anzeigen. Ein Beispiel sieht dann etwa so aus:

Controllers found: 1
<ControllerLog controllerID="0" type="6" time="1406893517">
<eventlog>
<event Date="1406027447" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406027451" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406027455" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406027459" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406030050" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406030054" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406030058" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406032580" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406036751" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406036755" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406439877" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406439881" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406439885" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406439889" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406442128" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406442132" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406442136" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406452738" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406452742" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
<event Date="1406452746" eventType="FSA_EM_BATTERY_CHANGE" eventCode="0x4000" batteryEventType="FSA_BATTERY_DEAD" batteryEventCode="1" priorState="0"
currentState="0" controllerID="0"/>
</eventlog>
</ControllerLog>

Lassen Sie sich Ereignisse für die Festplatte mit dem Befehl getlogs 1 device anzeigen.

Achtung

Stellen Sie vor dem Wiederaufbau eines Hardware Raids sicher, dass die Option Automatic Failover eingeschaltet ist. Standardmäßig ist dies der Fall. Sie können die Option mit dem Befehl arcconf64 failover 1 on einschalten.

Geben Sie den Befehl arcconf64 rescan 1 ein. In den meisten Fällen startet der Wiederaufbau des Raids automatisch. Der Vorgang wird im Hintergrund durchgeführt und kann mehrere Minuten dauern.
Startet der Wiederaufbau beim Rescan nicht automatisch, löschen Sie die Metadaten der Festplatte mit folgendem Befehl: arcconf64 TASK START 1 DEVICE 0 2 CLEAR, dabei steht 0 für den Controller-Channel, 2 für den Festplattenport.
Binden Sie die getauschte Festplatte mit folgendem Befehl als Hotspare ein: arcconf64 SETSTATE 1 DEVICE 0 1 HSP LOGICALDRIVE 1. Der Wiederaufbau startet jetzt automatisch.