Re-enabling a failed RAID Array HP410

Sometimes a disk will drop out a RAID array, especially if you have drives that don’t support a low latency error recovery such as the Seagate Barracuda SFF drives.  You should notice an alarm in ESX or your operating system that says the Logical Drive has failed.  Associated with this will be a physical drive failure too.

To recovery from the problem you will need to remove the affected drive for 10 seconds and then re-insert the drive into the slot it came from.  You can do all of this while the system is booted into the array management software.

Once you have the physical drive recognised as operational again then you can make steps to recover the logical drive.  In my case I am using ESX but any other operating system that can use the hpssacli utility should be the same.

First show the status of the logical drive:

./hpssacli ctrl slot=0 ld 1 show status

logicaldrive 1 (14.6 TB, 0): Failed

Now re-enable the logical drive:

./hpssacli ctrl slot=0 ld 1 modify reenable forced

Now check the logical drive again:

./hpssacli ctrl slot=0 ld 1 show status

logicaldrive 1 (14.6 TB, 0): OK

For most people the solution to this ongoing problem would be to use drives that support a lower recovery latency such as WD Reds but until they do them in large capacities I will be sticking with my 4TB Barracudas.


Checking an ansible playbook

ansible-playbook –check playbook.yml –diff –connection=local

Show used and provisioned disk sizes in ESX

Some simple powershell to show the used and provisioned size of disks in VMware

$report = @()
foreach ($vm in Get-VM){
$view = Get-View $vm
$row = ” | select Name, Provisioned, Actual, Thin
$row.Name = $vm.Name
$row.Provisioned = [math]::round($vm.ProvisionedSpaceGB , 2)
$row.Actual = [math]::round(($vm.UsedSpaceGB ) , 2)
$row.Thin = $view.config.hardware.Device.Backing.ThinProvisioned | Out-String
$report += $row
$report | Sort Actual