HP ProLiant ML350 G6 RAID Auto-Rebuild: Hot-Swap SAS HDD Replacement Guide for System Administrators


2 views

The HP ProLiant ML350 G6 server with Smart Array controllers (P410/P411) typically supports automatic RAID rebuild when using hot-swappable SAS drives. The process varies slightly depending on your RAID level configuration:


# Example CLI command to check RAID status (HPSSACLI)
hpssacli ctrl all show config detail

# Expected output snippet for degraded array:
# logicaldrive 1 (72.0 GB, RAID 1, Degraded)
# physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SAS, 72.0 GB, Failed)

For RAID 1/5/6 configurations, follow this sequence:

  1. Identify the failed drive using the array's amber fault LED
  2. Prepare the replacement drive (same or larger capacity)
  3. While system is powered on, extract the failed drive vertically
  4. Insert the new drive within 60 seconds (controller timeout window)

The Smart Array controller should automatically initiate rebuild. Monitor progress via:


# Linux: Install hpacucli package first
hpacucli ctrl slot=0 pd all show status

# Windows PowerShell alternative:
Get-PhysicalDisk | Where-Object { $_.OperationalStatus -ne "OK" } | 
Format-List FriendlyName,SerialNumber,HealthStatus

These situations may need CLI commands:

  • If automatic rebuild doesn't start within 5 minutes
  • When replacing with a different drive model
  • If the logical drive shows "Failed" state

# Force array rebuild manually (example):
hpssacli ctrl slot=0 pd 1I:1:1 modify forced reenable
hpssacli ctrl slot=0 array A modify preserve=FALSE

Expect 30-90MB/s rebuild speed depending on:

Factor Impact
RAID Level RAID 5 slower than RAID 1
Drive Size 1TB takes ~4 hours, 4TB ~16 hours
Workload Heavy I/O slows rebuild

html

The HP ProLiant ML350 G6 server with Smart Array controllers typically supports automatic RAID rebuild when replacing failed drives, but there are important technical considerations for programmers managing infrastructure:

For a standard RAID 1/5/6 configuration, follow these steps:

1. Identify failed drive using HP Array Configuration Utility:
   # hpacucli ctrl all show config

2. Physically remove the failed drive (amber light indicates safe removal)

3. Insert new SAS HDD of equal or greater capacity

4. Monitor rebuild progress:
   # hpacucli ctrl slot=0 pd all show status

Here's a Python script to monitor RAID rebuild status:

import subprocess
import time

def monitor_raid_rebuild():
    while True:
        result = subprocess.run(
            ["hpacucli", "ctrl", "all", "show", "config"],
            capture_output=True,
            text=True
        )
        
        if "Rebuilding" in result.stdout:
            print("Rebuild in progress...")
        elif "OK" in result.stdout:
            print("RAID array healthy")
            break
            
        time.sleep(300)  # Check every 5 minutes

if __name__ == "__main__":
    monitor_raid_rebuild()

Cases requiring CLI commands:

  • When the controller doesn't automatically detect the new drive
  • When dealing with non-HP branded replacement drives

Manual rebuild command example:

# hpacucli ctrl slot=0 array A logicaldrive 1 modify drives=1I:1:5 forced

For production systems, consider these optimizations:

# Set rebuild priority (higher = faster)
hpacucli ctrl slot=0 modify rebuildpriority=high

# For critical systems, schedule rebuild during off-hours:
echo "hpacucli ctrl slot=0 array A logicaldrive 1 modify rebuild" | at 2am

Common issues and solutions:

# If drive isn't recognized:
hpacucli ctrl slot=0 rescan

# If rebuild stalls:
hpacucli ctrl slot=0 array A logicaldrive 1 modify rebuild restart

# To check controller logs:
hpacucli ctrl slot=0 show logs