Archive for June, 2013
Newer Supermicro IPMI interfaces come configured by default in “failover” mode which means that the IPMI will bind to either the dedicated IPMI NIC port or share with one the the machine NIC ports.
This can cause IPMI to come up on wrong NIC and hence be inaccessible if the dedicated NIC doesn’t detect a link.
You can use ipmitool to change this behavour
First query the current setting:
ipmitool raw 0x30 0x70 0x0c 0
The result will be one of the following
0x00 = Dedicated
0x01 = Onboard / Shared
0x02 = Failover
Next to configure it you can use one of the following.
For older models:
ipmitool raw 0x30 0x70 0x0c 1 1 0
For X9 motherboards:
ipmitool raw 0x30 0x70 0x0c 1 0
References for this can be found here:
Sometimes a disk may be failing and timing out yet still working enough so that the RAID controller doesn’t drop it from the array.
This results in very poor performance from the entire array as the controller waits for timeout’s on the problem disk.
If your using an Areca controller there’s a command that can be used to manually fail such a disk allow it to rebuild onto an available Hotspare without having to have someone onsite to remove the problem disk.
WARNING – Using these commands can damage your array so be very sure before using them!
This can be achieved via the Areca web interface from the Raidset Functions -> Rescue Raidset option. In the text entry field enter the following command:-
FailDisk <disk channel>
The <disk channel> MUST be entered correctly otherwise you could fail the wrong disk for example entering
FailDisk Ch2 will fail disk attached to Channel 4 and not Channel 2.
The correct input is includes the 0 i.e.
Ch02 you see in the Hierarchy display so in full:
The areca-cli also provides a similar option e.g.
disk fail drv=2 but this only works on new controllers and not older ones e.g. ARC-1220 (at least not with FW 1.49)
Note a rather confusing version of this information can be found on Areca’s FAQ