Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This question already has an answer here:

I've a failed drive reported in my RAID5 running on a Dell R710 using RHEL5 with a DELL PERC controller. Is there a method to determine which drive it is? Can I do this at the command line?

share|improve this question

marked as duplicate by Andrew Schulman, mdpc, Jenny D, dawud, Dave M Jun 12 '15 at 14:16

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

I'd normally look at the server's OMSA page at https://server.ip:1311, But that depends on the Dell agents being installed. Do you have the management agents installed? – ewwhite Jun 7 '12 at 22:24
There are no management agents installed. – dacracot Jun 7 '12 at 22:34

I know this isn't the quickest solution, but I'd recommend downloading the OMSA management utilities to the system and using the status page I mentioned earlier at http://server.ip:1311 or using the omreport command line utility to obtain the RAID array's status.

This is assuming that you don't have any physical access to the system. If you do, there should be an amber light illuminated on the failed drive.

share|improve this answer
omreport storage controller to get a list of controllers, then omreport storage pdisk controller=0, or a more appropriate controller number. YMMV as this was done on a PE2950. Due to the system age, I used OMSA_5.4.1 instead of the latest OMSA_7.1 so some differences in commands could exist. Installing applicable packages from srvadmin-* folders beneath the most compatible OS subfolder of and starting the dataeng service should get one going. Packages installed fine for me on an operating system not listed as supported. – kbulgrien Oct 19 '12 at 17:32

The orange light on the caddy should be illuminated on the bad drive. If you don't have management agents installed, this is the best way. Good old visual inspection.

share|improve this answer

If nothing else, you can try looking for a serial number:

smartctl -a /dev/sdX

where /dev/sdX is a failed device. You'll see a device serial number (near the top). The serial number should also be written on the sticker on the drive itself.

ps: you might need to install "smartmontools" to get "smartctl"

share|improve this answer
oh :/ no idea then :( – mulaz Jun 7 '12 at 22:27
# smartctl -a /dev/sda smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen Home page is Device: DELL PERC H700 Version: 2.10 DELL PERC controllers are not supported. – dacracot Jun 7 '12 at 22:28
@dacracot yeah, if you're using Dell PERC (or pretty much any hardware raid card) the sdX devices are going to be virtual drives and not the actual spinning disks. Some drivers can allow access to the spinning disks via sg# devices, but I don't think the H700 supports it. – DerfK Jun 8 '12 at 3:02

You can run the omreport from the command line to find failed disk on Dell servers. For example to display all physical disks on controller 1, run:

omreport storage pdisk controller=1


share|improve this answer

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