I have a Dell Poweredge R710 with a Perc H700 Raid controller. It's in a RAID 6 configuration currently with 2 failed disks. It does boot to CentOS in it's currently degraded state.

I would like to replace the disks, but whenever I add a new one and run a rebuild it runs for a few minutes then puts the new disk offline. It does this for both slots on the controller and for two brand new disks (same model as existing).

I think the battery on the controller needs replacing, but I wouldn't think this would affect the ability to run a rebuild.

Any ideas on how to get a rebuild to complete?

  • 1
    You have a RAID 6 with two failed disks. I.e., no redundancy. Are you absolutely positively certain that the problem isn't a simple read error on any of the remaining disks? – user Aug 19 '15 at 11:10
  • I'm not sure how I'd go about even finding this out. Also would a read error force the new disks in to an offline state? – Meep3D Aug 19 '15 at 11:13
  • I'm not familiar with the H700 (or really even Percs in general), but a read error with no redundancy would likely abort the rebuild. Does the controller itself have any usable logs? – user Aug 19 '15 at 11:15
  • There may be something wrong with the backplane. Low/faulty battery shouldn't stop a rebuild. – JamesRyan Aug 19 '15 at 11:16
  • Well it boots at least. Backup and rebuild I think. Hopefully the error will reveal itself at some point. – Meep3D Aug 19 '15 at 11:21

You're most likely encountering read errors on one of the remaining online drives. If you have Dell's OpenManage Server Administrator installed, you can use it to export a controller log, which should contain details about any errors that occurred during the rebuild process.

Exporting a Controller Log in OpenManage Server Administrator:

  1. Expand the Storage tree in the left pane
  2. Select the H700
  3. Select the Information/Configuration sub-tab at the top
  4. Select "Export Log" from the Available Tasks drop-down menu
  5. Click Execute. The log name and location should be shown before executing 
  6. Click Export Log to complete the export process and save the file

If you don't have a GUI but do have OpenManage installed, you can also use this CLI syntax to export a controller log:

omconfig storage controller action=exportlog controller=id

where id is the controller ID number as reported by the omreport storage controller command.

The log file is exported to either /var/log or <install-directory>/sm, and is named lsi_<mmdd>.log where <mmdd> is the month and date.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.