Re: Issue with replaced HD not coming on-line

I have seen similar issue when a SATA is mistakenly replaced for a SAS. If
you have OMSA installed you can compare working drive details against this
new drive with omreport commands.

# omreport storage pdisk controller=0 |grep Bus


Cameron Smith
Technical Operations Manager
Network Redux, LLC
5200 SW Macadam Ave Ste 450
Portland, Oregon 97239
Cell:   503-926-4928

On Fri, Oct 30, 2015 at 3:19 PM, Jeff Boyce <[email protected]> wrote:

> Greetings -
>
> I have PET610 with a PERC H700 controller that a hard drive fail
> recently.  The drives are setup in a RAID5 (3 drives) with a single hot
> spare.  The hot spare was engaged and the failed drive was automatically
> taken off-line after the virtual drive rebuild was completed.  Today I
> receive a replacement drive of the same specs as the failed drive
> (manufacturer, model, etc.).  I reviewed the instructions to replace the
> drive, which were,
>
> 1.  If drive is identified as off-line and the status lights on the
> drive are out, manually pull the drive from the chassis.
> 2.  Unscrew and remove the failed drive from the carrier, and install
> the new drive in the carrier.
> 3.  Wait a minimum of 30 seconds between taking the failed drive out and
> inserting the new drive and carrier.
> 4.  Slide the new drive into the same slot and lock into place.
>
> I have also read that with the H700 controller, if the new drive is
> replaced into the same slot as the removed failed drive, that the new
> drive will be reinserted into the RAID virtual drive, and the hot spare
> that was used will revert back to a hot spare again.
>
> The issue that I am having is that the newly installed drive is not
> being recognized at all.
> 1.  The drive status indicator light and the drive activity light both
> remain out.
> 2.  /var/log/messages show the drive removed, but not inserted.
> Oct 30 12:17:30 earth Server Administrator: Storage Service EventID:
> 2049 Physical device removed: Physical Disk 0:0:2 Controller 0, Connector 0
> 3.  The hardware ESM log in OMSA shows the following two events (the
> last two events listed) at the time the drive was removed.  No
> additional events show the new drive installed.
> Ok;Fri Oct 30 12:17:33 2015;Drive 2 in disk drive bay 1 is operating
> normally.
> Critical;Fri Oct 30 12:17:33 2015;Drive 2 is removed from disk drive bay 1.
> 4. The LCD panel on the front of the chassis remains an amber color with
> the following message.
> E1812 Hard drive 2 removed. Check drive
>
> I can't find anything that indicates I haven't done this replacement the
> proper way.  But need to figure out how to get this drive back on-line
> and at least assigned as a hot spare.  I have not power cycled the
> server and would like to avoid doing that if possible. The only idea
> that pops into my head right now is possibly some dust bunnies took up
> residence in the hard drive connector slot as I slide the new drive into
> place.  So I am looking for ideas.  What should I do to further diagnose
> what my problem is and resolve it. Thanks.
>
> I only receive the daily digest of this mailing list, so please CC me
> directly with any replies.  Thanks.
>
> Jeff
>
> --
>
> Jeff Boyce
> Meridian Environmental
> www.meridianenv.com
>
> _______________________________________________
> Linux-PowerEdge mailing list
> [email protected]
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>

_______________________________________________
Linux-PowerEdge mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/linux-poweredge