Start a Conversation

Unsolved

This post is more than 5 years old

13657

June 24th, 2015 07:00

PERC H710 seems damaging my drives

Hello all.

I bought a new PET320 with PERC H710 controller.
I installed into the chassis 3xWD4000FYYZ disks and created a RAID5 volume.

When I tried to format the volume, one drive immediately failed. Then I tried to turn off the system, check cable connections, and reseat physical disks. After reboot I pressed CTRL+R, and re-created the volume. Same issue.
Then I tried to create a RAID1 volume with 2 of these disks, and it resulted again in the same issue (i.e. another drive immediately failed after trying to access to the volume from the OS).
I tried to connect these 2 failed drives to another PC and they result bad drives even if they're just unboxed.

I'm really frightened keeping on doing RAID experiments. Anyone experienced such a problem? Could it be a controller issue?
Any idea?

9 Legend

 • 

47K Posts

June 24th, 2015 07:00

Drives being swapped into a raid will have to be initialized and containers created.  You cant just willy nilly toss drives into a raid and it works.  All of these operations are done from the Raid Firmware not an os.

9 Legend

 • 

16.3K Posts

June 24th, 2015 08:00

As unlikely as it sounds, it looks like you got bad drives. The PERC won't "damage" them, even if there was something wrong with it.

9 Legend

 • 

16.3K Posts

June 24th, 2015 08:00

Did you also check the Advanced and Initialize boxes when you created the arrays (you initialize arrays, not individual disks)?

When you put them into "another PC", how did you determine that "they result bad drives"? If you took them straight out of the box and they are bad, whether on a server or PC, sounds like  you received defective drive(s).

8 Posts

June 24th, 2015 08:00

I initialized (fast) the array, not individual disks.

When I put disks into another PC (Win764bit Pro), I did the following:

1) Checked if Win was able to detect disks. It detected both.

2) Try to create both a GPT or MBR partition table, create a partition and format it as NTFS: for one of the 2 drives I was able to create and format the partition, for the other one I wasn't even able to create the partition table.

3) Launched WD WinDLG ( support.wdc.com/.../download.asp;sid=3&lang=en ) and found the first drive as FAILED, the second one not even accessible by WD software.

4) Launched Both Quick and Extended tests on the only accessible drive, and it resulted with "FAIL: too many bad sectors detected".

Then I concluded the drives were failed.

9 Legend

 • 

16.3K Posts

June 24th, 2015 09:00

I'm not one to say a thing is "impossible", but that is just about as close as it comes. The controller is not damaging your drives. The power doesn't come from the controller anyway - it comes from the backplane (or cables) from the system's power distribution nodes. Test a new drive in your PC first next time, so you know it's good before using, then put it in the server. Dell does not guarantee those drives will work in their server, but according to the specs, WD has tested it on an H710 to work.

8 Posts

June 24th, 2015 09:00

Thanks.

Then you think it's really difficult that PERC H710 generated wrong volgages/currents able to kill my drives? I'm quite frightened to insert a new set of drives and test if they work...

Any electric-related known issue with that controller?

4 Operator

 • 

1.8K Posts

June 24th, 2015 12:00

Agree with Flash, in 25 years never had a LSIlogic based adapter destroy a disk.

I just have ask.... were these NEW retail disks, where did you get them?

Why fear inserting another drive, almost all retailers warranty the drives

8 Posts

June 25th, 2015 01:00

Thank you. Well, my fear is because if the problem is due to a controller/backplane/power supply electrical issue on the server that "destroys" my disks, I'm fear the disk retailer or manufacturer won't give warranty.
These drives have 5-years warranty.

Any way to troubleshoot electrical issues on the server without "killing" other drives?
I'm astonished if a so said "high-quality" server has no electrical protection system to avoid burning devices...
Thank you in advance.

9 Legend

 • 

16.3K Posts

June 25th, 2015 09:00

Any way to troubleshoot electrical issues on the server without "killing" other drives?
I'm astonished if a so said "high-quality" server has no electrical protection system to avoid burning devices...

There are many protections and monitors for such situations. You would get an error like E1000 FAILSAFE if there were such an issue. It just is extremely, EXTREMELY unlikely (impossible, really) for the server to cause the kind of damage you describe. Where did you buy them? Are you sure they are legit? You could always hire a PC electrician if you really think it is the server.

9 Legend

 • 

16.3K Posts

June 25th, 2015 10:00

1. No, the OS could not do this.

2. See below and my previous posts.

I only asked about the disks because I have seen cheap Chinese knock-offs floating around - relabeled, etc.

It sounds also really unlikely that if the drive were unsupported by the controller (even if WD indicates it is), it would have been damaged in such a way. Do you agree?

Yes, I agree: It is really unlikely (impossible) IN ANY CONCEIVABLE SCENARIO (supported or unsupported) that it could damage the drives in such a way without getting some kind of warning on the server hardware. As I said, there are server errors that would be tripped (and the system shutdown and prevented from booting/POST) in such an event.

8 Posts

June 25th, 2015 10:00

Thanks,
This is my real opinion:
1) The OS can't damage disks as it needs to "bypass" 2 firmwares (i.e. the PERC firmware and the WD firmware) to be able to execute activities as low level as needed to damage a disk. I think for an enterprise class disk like my WD4000FYYZ also a bugged PERC firmware shouldn't be able to damage the disk.

2) Electrically damage a disk is still possible if the data interface or power interface on the backplane supplies wrong currents/voltages to the disks interfaces. One who wants to sizzle a disk can supply an higher power than that supported by the interface or probably also an out of tolerance variable  power.

Disks are new and bought from amazon, I hope they're legit.

It sounds also really unlikely that if the drive were unsupported by the controller (even if WD indicates it is), it would have been damaged in such a way. Do you agree?

Thank you in advance.

4 Operator

 • 

1.8K Posts

June 25th, 2015 11:00

Really easy to test voltage on a server if you have a volt ohm meter.

pcsupport.about.com/.../power-supply-test-multimeter.htm

Power anomalies due to power utilities or lightning can mess with disks, but they generally occur between 1am and 6am and are rare ( due to switching on the grid). Building machinery can cause them rarely, but not enough to effect disks (generally).

" I'm fear the disk retailer or manufacturer won't give warranty. These drives have 5-years warranty.

Do you rally think retailer/manufacturers test returned disk as to the cause of failure? Possible, but an electronics Engineer with a high degree of training in the area of chip design would be needed, plus many hours, not likely. Been returning disks under warranty for >28 years, never had a denial of claim.

No Events found!

Top