NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Disk Failure Detected...
I've recently purchased a ReadyNAS Ultra 6 along with 6 2 Tb Seagate ST2000DL003 disks (which are on the HCL). I've set up the NAS in a dual redundancy X-RAID2 configuration and have starting copyi...
Update:
It has been almost three weeks since I have opened a case. It has been a frustrating experience so far. I have "factory defaulted" the unit once, and a week or so later, I had another disk failure. I think I'm over ten at this point. After the last failure, the "engineers" looked at the unit and said they could find no problems, and nothing in the logs. I gave tech support remote access and booted the unit into some sort of maintenance/debug mode. Oddly enough, they wanted Telnet (port 23) forwarded, and not SSH (22) which I found strange. Perhaps "debug mode" only has hooks for Telnet?
Anyway, I now have a new firmware to try - it appears to be Beta code: 4.2.20-T15. This was the recommendation given to me by engineering. I applied the new firmware about 20 minutes ago, so now it's time to sit and wait.
I will commend Tech Support on their responsiveness; I have had difficulty conveying/re-conveying information to them at times, and so far the answers I have received have not been too helpful, but they have been polite and quick to respond. It feels like they are just walking me through a script for the most part, but we will see how the new firmware performs. The next step is an RMA, which will almost certainly NOT help, but again, it's part of the process for now.
I will keep everyone updated as this evolves.
It has been almost three weeks since I have opened a case. It has been a frustrating experience so far. I have "factory defaulted" the unit once, and a week or so later, I had another disk failure. I think I'm over ten at this point. After the last failure, the "engineers" looked at the unit and said they could find no problems, and nothing in the logs. I gave tech support remote access and booted the unit into some sort of maintenance/debug mode. Oddly enough, they wanted Telnet (port 23) forwarded, and not SSH (22) which I found strange. Perhaps "debug mode" only has hooks for Telnet?
Anyway, I now have a new firmware to try - it appears to be Beta code: 4.2.20-T15. This was the recommendation given to me by engineering. I applied the new firmware about 20 minutes ago, so now it's time to sit and wait.
I will commend Tech Support on their responsiveness; I have had difficulty conveying/re-conveying information to them at times, and so far the answers I have received have not been too helpful, but they have been polite and quick to respond. It feels like they are just walking me through a script for the most part, but we will see how the new firmware performs. The next step is an RMA, which will almost certainly NOT help, but again, it's part of the process for now.
I will keep everyone updated as this evolves.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
