On installing a drive to rebuild, s100/110/300 usually make own array, but no drive in it in OMSA and controller bios : delete dummy array. Sometimes have to reboot to perc BIOS/control_R to see drive fail id'd in red. Failed drive can show online, and yet array degraded:Ĭheck hardware/esm logs AND alert logs AND win logs to id failed drive.

S100/110/300 Don't always show drives in OMSA as should.

Parity overhead (RAID_5/6 based) seems too much for controllers w/o memory battery, especially Windows driver dependent, especially on OS array(for any controller) as it bogs the box down. Next would be h200(nonParity RAID_0,1,10 only). Worst of perc's, best to get RAID controller with battery/memory. I have a 3 year old Dell PowerEdge T110 with Windows Server 2008, RAID 1 with 2x146gb serial SCSI drives and a PERC S100 controller. Thus might take driver refresh/reboot to : see problems, start rebuild etc. S100(embedded), s110(embedded), s300(card) not like rest of perc's run thru a Windows driver to OS, with hardware for preBoot BIOS only.

Perc s100 raid controller