New disk failed after sync. How do I recover?

kossboss,

Sorry, I don't know how I missed your post. The forum was showing no replies after my comment on the 5th. Now they are there. :?

I'm willing to test the slot, but first here is/was my setup...

I have always had been using the 3 slots, just upgrading to larger drives to increase capacity.
Up until 2 weeks ago, I had this setup:

Slot 1 - 1TB drive
Slot 2 - 1TB drive
Slot 3 - 1TB drive

Two weeks ago, I started replacing the drives one by one, letting them resync each time. So when I reached the 3rd drive, it was like this:

Slot 1 - 2TB drive
Slot 2 - 2TB drive
Slot 3 - 1TB drive

I then replaced the drive in Slot 3 with the Seagate. It resynced overnight and reported success the next morning. That evening, RAIDAR reported the drive as failed.

So, for years, I've been using that slot...ever since buying the NV+ back in 2007.

Based on that knowledge, if you still think it might be a bad slot, let me know and I will do the test you recommend. I just wanted to make sure you weren't thinking I was using the slot for the first time.

Thanks!

Also, FYI, after the failure, I put the original 1TB drive back in slot 3 (I had not power-cycled the NV+ yet, so it hadn't run through the expansion process yet), which resynced and everything is running fine at:

Slot 1 - 2TB
Slot 2 - 2TB
Slot 3 - 1TB

Ok. It's not the slot, and the drive passes Seatools.

Can you still return it to the reseller, or do you need to go through Seagate?

Yes, in fact I already have the RMA. I will send it off to them tomorrow. I also ordered a WD RED drive which should get here in a few days.

Thanks for all the help!

MORE HELP PLEASE!!

Okay, I was able to get them to accept back all the Seagate 2TBs...even the one that hadn't failed yet.

I had replaced all but that one in the NV+ and it was working fine.

So, I removed the good 2TB drive and replaced it with one of the previous 1TBs.

I let it Sync overnight.

It's been 2 days. The drive light on the NV+ is flashing and the LCD screen says Disk 2 Sync.

I cannot access the NV+ from my computers and RAIDar does not see the NV+.

Would it be safe to try and reboot it?


What should I do???

I have the same drives, 12 of them with a ReadyNAS3200 and am experiencing the same issue. Three NAS have all displayed this problem with these drives. The first one was Bay 8, the second was 5 and 11, now its 5 8 and 12. Disks show up and work fine in windows machines, they work fine in other slots on the NAS, they just will not work in the NAS, other disks known good disks of the same model dont work in 5 8 or 12. seems pretty freakin odd to me. :x

WTF.

Even if i get it working at this point there is no way im putting this thing in production.

I have an Ultra4+ populated with those drives, though a different firmware revision. I upgraded from what I think was 4.2.19 to 4.2.22 (not sure, but I had skipped a couple of versions) and began having all kinds of trouble with the drives. I found from this forum that I was not alone. I backed off to 4.2.21 and all is well except that it mis-reports some SMART data. I have not tried 4.2.23. I suggest you back down to 4.2.21 and then try the "bad" drive again.

Many of my problems seemed to be when spinning up from a sleep cycle, so originally I also disabled drive spin-down. I've since re-anabled it and there do not seem to be any problems, but it also sees a lot less use since I added a 6-bay Pro to the mix.

I wish I had known about this quirky issue before I bought 2 brand new same model of Seagate 2TB ST2000DM001 drives that OP reported issues with. I have a ReadyNAS RND-4000 4 bay unit that was using a single 1.5TB Seagate drive for a few years.
I decided to up my capacity and inserted one of the new Seagate 2TB drives into slot 2 and waited all day for it to finish sync'ing up and initializing it. After it completed, I started transferring some files over to the ReadyNAS and BOOM, the file transfers halted in the middle of the transfer and my Windows 8.1 PRO system reported that it was having connection problems with the ReadNAS. After a few minutes, the ReadyNAS came back online connected again and I got error notification email from it saying:
"A SATA reset has been performed on one or more of your disks that may have affected the RAID parity integrity. It is recommended that you perform a RAID volume resync from the RAID Settings tab ( accessible in the Volumes page => Volume tab in FrontView ). The resync process will run in the background, and you can continue to use the ReadyNAS in the meantime."

I log into the ReadyNAS unit to do the recommended resync, but it won't let me! The resync button is greyed out and it does not let me manipulate the new 2nd drive saying that it is "DEAD".
With that disappointment, I submitted for an RMA for the two new 2TB Seagate drives I bought from newegg.
Meanwhile, I tried to connect the supposedly bad "DEAD" drive to my Windows PC via USB adpapter and proceeded to format it. It finished formatting and I've copied tons of files over to it without a problem. The disk check report no problems found with the hard drive!
So, conclusion? I think it is the ReadyNAS unit that is quirky and not the Seagate 2TB hard drives (this particular Seagate model ST2000DM001). The firmware version on each drive says it is CC27.
Date says: 14051 Site: WU. Whatever that means. Did I get old firmware drives that don't work in RAID mode? Got them on sale from newegg.com and they did not come in sealed antistatic bags but rather taped shut bags. Are these old or refurbed drives they sold me maybe, thus the deep discount sale price? (But they claimed to be new).
I am thinking of cancelling my RMA now but it still leaves me wondering and worried if these drives I got might have something wrong with them or was it just the flaky Netgear ReadyNAS unit that is at fault!

Did you check the disks using SeaTools? Formatting a disk and writing to it is not enough to verify the disk is O.K.

Hi, no not yet. Have not got the chance. I have to down load the tool and install it and then connect the drive internally before I can test it like that.
Unless it will be just as a reliable test working through my USB drive adapter. I will try to get around to doing this test if I can find the time. Too busy I am.
And all this is really a hassle to me getting in my way (time wise). sigh!