In regard to: RE: [E] [Linux-PowerEdge] replacing a failed hard drive with...:

> Without having OMSA installed on the server, I believe that you have 3
> options to recreate the vdisk.  You can either use the iDRAC and go to
> the Storage > Virtual Disks and section and select the Create tab.
> This page should allow you to create the vdisk.

A colleague and I looked all over in the iDRAC 7 interface and we cannot
find a "Create" tab anywhere in either the Virtual Disks section or even
the Physical Disks section.  He too was expecting there to be something
exposed by iDRAC that would allow us to do it, but it appears to be
missing for some reason.

Now that you've given me something specific to search on, it looks like
this is just something that's missing from iDRAC 7:

I'm following that trail now, to see if I can make that work.

> The other option is to go in through the LC and drill into the storage
> section to create the vdisk. This is my least favorite option.
> Lastly, you could use the CRTL-R option during boot to open the Raid
> Controller setup page to re-create the vdisk.

I'm familiar with both of these options.  In this case, it's probably what
I'll end up doing, just to get the replacement drive visible to the OS.

I very much appreciate your response!  It's given me a few different
avenues to pursue.


> -----Original Message-----
> From: 
> [] On Behalf Of Tim Mooney
> Sent: Wednesday, August 9, 2017 6:15 PM
> To:
> Subject: [E] [Linux-PowerEdge] replacing a failed hard drive with PERC HBA 
> mode
> Hi All!
> I need to replace a hard drive in a Dell R720 that's running RHEL 6.9.
> The problem is that the replacement drive shows up as "Ready" in the physical 
> disks area of iDRAC, instead of "Online".  It does not automatically show up 
> as a vdisk in the virtual disks area.
> The PERC H710 mini is in HBA mode, not RAID mode, so it's not handling the 
> mirroring.  That's being done at the OS level with Linux's mdadm.
> This hard drive is part of an mdadm RAID1.  The drive failed completely, so 
> mdadm failed each of the partitions out of the individual MD devices.
> I removed the failed MD components and then forced the OS to forget about 
> /dev/sdb, with
>       # echo 1 > /sys/block/sdb/device/delete
> I pulled the failed hard drive from the hot-swap bay, installed the Dell 
> replacement drive in the carrier, and inserted the replacement hard drive 
> into the bay.  The drive LED blinked and went green, and iDRAC shows the 
> physical disk as "Ready", instead of "Online", and the replacement is missing 
> completely from the vdisk area.
> The OS did not auto-detect a hard drive being added to the bus, and even a 
> rescan via
>       # echo '- - -' > /sys/class/scsi_host/host0/scan
> does not trigger it to recognize the replacement drive is there.  I'm 
> guessing that's because I need to do something at the PERC/iDRAC/Lifecycle 
> level to get the drive to switch to "Online" and make it a vdisk.
> How do I go about doing that?
> We do not currently have any Dell OS-level RPMs installed, so no omsa or 
> srv-admin or whatever.  After being on this list for a couple of years, my 
> confidence in those tools is extremely limited.
> It seems like 'megaclisas' might be able to help, but I have been completely 
> unable to find a working link to that tool, after the
> LSI->Avago->Broadcomm transition.  If anyone has a working link to get
> it, I would appreciate seeing it.
> Could 'racadm' via ssh perform the necessary magic to get this drive so that 
> the PERC is presenting it as a disk to the OS?  Is there something easier 
> than that, that also doesn't require a huge mess of questionable Dell RPMs be 
> installed?
> Any suggestions are much appreciated,
> Tim

Tim Mooney                                   
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

Linux-PowerEdge mailing list

Reply via email to