NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Help swapping "dead" drive? [Case #15693780]
Hey all, I have an NV+ that is about 2 months old. I fired it up and loaded it with all of our data, backed up all files from PC's etc...it has 4 x 2TB WD Green Caviar drives at this point. All is wel...
Removed the problem drive, installed in to this PC as a secondary and ran the vendor tools. Result was "passed" and the drive appears fine with no errors.
So I spent way too long trying to make a bootable CD with the WDIDLE tool on it. Took a few tries due to having 64 bit windows 7 and no floppy disk.
THEN, I could not get WDIDLE to recognize my disk because I have a stupid Gateway with the BIOS setting to change the SATA mode from Onboard to RAID [or in my case, RAID to onboard] greyed out from the factory. So my options at this point are flash BIOS with unpredictable results, or try another machine. No use in potentially destroying a machine for days to troubleshoot a "dead" disk right?
I put the WD20EADS in a different PC as the only disk, booted to CD and ran wdidle3 /d and it ran for approx 1 second, showed the drive model and serial numbers then a message stating that the timer had been disabled. I think this is good, but the program did not return and spit out a "could not read from drive a:" which was probably an issue with the boot CD. So I exited out of the program and powered off the machine, insert that disk in to NAS [powered off] and start it up.
Same issue now. RAIDar shows the drive as normal and fine. Frontview reports the drive as not present and my shares are missing since the volume choked as it has been. So is the issue with these "incompatible drives" related to a setting in the drive that is detected early on and remembered so the NAS will ignore it from that point forward? This seems very strange to me, but I am not familiar with how the RAID controller communicates with the hardware.
I will let it run for another hour to see if anything happens, but it appears nothing has changed. I did discover that this PC has 2 open screwless bays for SATA hard disks. That has made it easy to work with the vendor tools. What are my options now? Should I try using the vendor tools to zero fille one of my brand new disks to see if that improves things? Should I connect them to the other PC to run WDIDLE on those too before I zero fill/try them in the ReadyNAS?
I'm starting to feel like this is not going to end well, but maybe the support team have some other suggestions. Hope it's not "unsupported drives, have a nice day" :-/
So I spent way too long trying to make a bootable CD with the WDIDLE tool on it. Took a few tries due to having 64 bit windows 7 and no floppy disk.
THEN, I could not get WDIDLE to recognize my disk because I have a stupid Gateway with the BIOS setting to change the SATA mode from Onboard to RAID [or in my case, RAID to onboard] greyed out from the factory. So my options at this point are flash BIOS with unpredictable results, or try another machine. No use in potentially destroying a machine for days to troubleshoot a "dead" disk right?
I put the WD20EADS in a different PC as the only disk, booted to CD and ran wdidle3 /d and it ran for approx 1 second, showed the drive model and serial numbers then a message stating that the timer had been disabled. I think this is good, but the program did not return and spit out a "could not read from drive a:" which was probably an issue with the boot CD. So I exited out of the program and powered off the machine, insert that disk in to NAS [powered off] and start it up.
Same issue now. RAIDar shows the drive as normal and fine. Frontview reports the drive as not present and my shares are missing since the volume choked as it has been. So is the issue with these "incompatible drives" related to a setting in the drive that is detected early on and remembered so the NAS will ignore it from that point forward? This seems very strange to me, but I am not familiar with how the RAID controller communicates with the hardware.
Mon May 30 21:49:39 EDT 2011 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.
Mon May 30 21:47:06 EDT 2011 System is up.
Mon May 30 21:47:01 EDT 2011 The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. media backup
I will let it run for another hour to see if anything happens, but it appears nothing has changed. I did discover that this PC has 2 open screwless bays for SATA hard disks. That has made it easy to work with the vendor tools. What are my options now? Should I try using the vendor tools to zero fille one of my brand new disks to see if that improves things? Should I connect them to the other PC to run WDIDLE on those too before I zero fill/try them in the ReadyNAS?
I'm starting to feel like this is not going to end well, but maybe the support team have some other suggestions. Hope it's not "unsupported drives, have a nice day" :-/
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
