I’m nowhere near the data center to reseat the drives. Trying to rebuild it 
first using that same drive until I can get there. Last time I did it, it 
lasted a few months. Yes, drive replacement is a definite at this point.

 

Still can’t figure out why I get that error when everything seems to be right 
per the manual.

 

 

Thank you,

Steffan Cline

602-793-0014

 

 

From: <[email protected]> on behalf of Patrick Boutilier 
<[email protected]>
Date: Sunday, June 18, 2017 at 11:10 AM
To: <[email protected]>
Subject: Re: [Linux-PowerEdge] Rebuilding Array

 

Are you trying to rebuild on the same drive without replacing it? Have you 
tried just reseating the drive? That should kick off a rebuild automatically. 
Does in RAID-5, not sure about RAID-6.

On June 18, 2017 2:15:20 PM ADT, Steffan Cline <[email protected]> wrote:

I ran into this issue a while back but completely forgot how I handled it.

 

I have a drive in a RAID 6 config that failed. I was able to just rebuild the 
RAID a while back and it’s been fine for months. I think I ended up doing it 
via the BIOS rather than the tools because I couldn’t get past the error.

 

In running the report I see this:

 

# omreport storage pdisk controller=0

List of Physical Disks on Controller PERC H700 Integrated (Embedded)

 

Controller PERC H700 Integrated (Embedded)

…

ID                              : 0:0:3

Status                          : Critical

Name                            : Physical Disk 0:0:3

State                           : Failed

Power Status                    : Spun Up

Bus Protocol                    : SAS

Media                           : HDD

Part of Cache Pool              : Not Applicable

Remaining Rated Write Endurance : Not Applicable

Failure Predicted               : No

Revision                        : FS64

Driver Version                  : Not Applicable

Model Number                    : Not Applicable

T10 PI Capable                  : No

Certified                       : Yes

Encryption Capable              : No

Encrypted                       : Not Applicable

Progress                        : Not Applicable

Mirror Set ID                   : Not Applicable

Capacity                        : 278.88 GB (299439751168 bytes)

Used RAID Disk Space            : 278.88 GB (299439751168 bytes)

Available RAID Disk Space       : 0.00 GB (0 bytes)

Hot Spare                       : No

Vendor ID                       : DELL(tm)

Product ID                      : ST9300603SS

Serial No.                      : 6SE4DTMB

Part Number                     : CN0T871K7262216J05VHA01

Negotiated Speed                : 6.00 Gbps

Capable Speed                   : 6.00 Gbps

PCIe Negotiated Link Width      : Not Applicable

PCIe Maximum Link Width         : Not Applicable

Sector Size                     : 512B

Device Write Cache              : Not Applicable

Manufacture Day                 : 03

Manufacture Week                : 25

Manufacture Year                : 2011

SAS Address                     : 5000C5003B697F25

Non-RAID HDD Disk Cache Policy  : Not Applicable

Disk Cache Policy               : Not Applicable

Form Factor                     : Not Available

Sub Vendor                      : Not Available

ISE Capable                     : No

…

 

 

So I then try to repair/rebuild it.

# /opt/dell/srvadmin/sbin/omconfig storage pdisk action=rebuild controller=0 
pdisk=0:0:3

Operation disabled. Read, action=rebuild

Refer to the documentation for more information.

 

I seem to recall that when I did it via the BIOS I had to remove the drive and 
then rebuild it as a spare. Is it the same via the CLI. Is there a way to get 
past this?

 

 

Thank you,

Steffan Cline

602-793-0014

 

_______________________________________________ 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

Reply via email to