Seagate ST2000DL003-9VT166

You could open a Netgear support case.

StephenB wrote:
You could open a Netgear support case.

I did a bit for bit copy from original drives to the new ones using r-studio. Incidentally when I load the new drives in the system, drives 2,3,4 appear as "dead" but they are brand new. I tried OS reload and disk scan from boot menu and still same issues.
Something is amiss. I just opened a support case with netgear #19947461. I am beginning to wonder if its chassis related...

They are sending me an RMA chassis. I will provide an update of my findings on both old and new (copy) drives.

these drives are really bad news. i bought 2 of them to put in a desktop raid10 some time back and never deployed them. now i can't return them and from the looks of it, RMA-ing them to seagate won't do anything.

i happen to have the -302 versions of these drives. they shipped with CC3C, but last night i upgraded both of them to CC3D. that was no help, they keep dropping out of an apple software raid on a cineRAID box set to JBOD. same behavior with CC3C.

i'm not sure getting 302 will help anyone if my drives are representative.

pfile wrote:

these drives are really bad news. i bought 2 of them to put in a desktop raid10 some time back and never deployed them. now i can't return them and from the looks of it, RMA-ing them to seagate won't do anything. i happen to have the -302 versions of these drives. they shipped with CC3C, but last night i upgraded both of them to CC3D. that was no help, they keep dropping out of an apple software raid on a cineRAID box set to JBOD. same behavior with CC3C. i'm not sure getting 302 will help anyone if my drives are representative.

to my knowledge we havent received any negative reports of anyone who has been using the cc3d drives (except for real drive failures).
so whatever causes them to drop from the apple raid must be something different from what caused them to drop from a linux based md-raid.

After all the problems reported here about the ST2000DL003 (9VT166-301), I´m wondering why it is still on the HCL of the ReadyNAS NV+. No problems there?

addendum:

I was talking about ReadyNAS NV+(V1). From the HCL of ReadyNAS NV+(V2) it´s already removed.

beisser wrote:

pfile wrote: these drives are really bad news. i bought 2 of them to put in a desktop raid10 some time back and never deployed them. now i can't return them and from the looks of it, RMA-ing them to seagate won't do anything. i happen to have the -302 versions of these drives. they shipped with CC3C, but last night i upgraded both of them to CC3D. that was no help, they keep dropping out of an apple software raid on a cineRAID box set to JBOD. same behavior with CC3C. i'm not sure getting 302 will help anyone if my drives are representative. to my knowledge we havent received any negative reports of anyone who has been using the cc3d drives (except for real drive failures). so whatever causes them to drop from the apple raid must be something different from what caused them to drop from a linux based md-raid.

in fact, i think you are right. these disks were originally dropping out of a linux md-raid. i thought it was some kind of kernel incompatibility, so i thought i'd try the apple JBOD raid. had double failures until after the firmware upgrade, after which point i was having failures on only one disk.

as it turns out, it looks like one slot of the cineraid box might be bad - whatever disk is in the top slot seems to be giving errors at spin-up time. i've tried now with the suspect seagate drives, and a hitachi drive. right now i'm trying with a WD drive as well, just to see... and then i guess bye bye Cineraid (should have just bought another readynas :) )

edit: i think the jmicron USB3.0 - esata raid controller in these enclosures is incompatible with macosx. the slot does not have any bearing on the problem - eventually one or more of the disks returns some kind of error when undergoing spinup which causes the apple raid software to mark the disk as failed.

So I have been running 2 of these drives as X-RAID2 with cc3c fw in an Ultra4+ w/ RAIDiator 4.2.20 since July 2012 with no issues. I think I will grab the FW in the sticky & hold on to it just in case, I'm not going to do anything until/unless I have a problem.

I'm assuming a 2 drive array is just as susceptible to this issue?

Just had a cc32 drive drop out. I am NOT a happy bunny. Have emailed Seagate with this thread link, but unless they send some new drives pronto I will be buying some WD Red and sending Seagate the bill. It's quite ridiculous that their support site doesn't acknowledge it. Good companies admit their mistakes and correct the problems.