NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Readynas Ultra 6 freezes (case: 18799893)
About a week ago I bought a ReadyNas Ultra 6. I set it up, upgraded it to the latest available RAIDiator firmware 4.2.20 and installed 6 x 2TB Hitachi HUA722020ALA330 drives (from the compatibility list).
I already have 3 Readynas NV+ units all on the same network (DHCP) and I've always been very happy with their performance. This new one however is giving me some headaches.
After a couple of days, while the device was still basically empty, I woke up one morning and found the ReadyNas to be frozen. The blue power-on button was on, but the device was completely unresponsive. It wasn't available on the network anymore, RAIDar didn't detect it when scanning, I couldn't get to Frontview using the IP address that had been assigned to it, and I had to restart it by pressing the front power button until it rebooted. It worked fine for about a week so I thought this might have been a one-off occurrence and this morning I woke up to the same exact thing: the device is powered, blue light is on, but it doesn't respond, nothing happens if I press the power button (the led display doesn't come up). Only thing I can do is reboot by keeping front button pressed.
I don't think it's a temperature issue, as far as I can tell: the server wasn't really being used/accessed at the time, and I don't get any warnings or other symptoms, I just find the ReadyNAS still on but frozen/unaccessible.
After I force a reboot, I can access it just fine but there's nothing in the logs indicating that there was a problem and the device boots cleanly, without doing a filesystem check or any other indication that the Readynas is aware that it was not shutdown properly. I can't see anything in the logs, nothing immediately evident in the 'health' section of Frontview.
Any ideas/suggestions? This is my 4th ReadyNas (I have three NV+ on the same network) and this is the only one that has ever exhibited this problem. Should I look into returning it (I've had it for about a week now so it's clearly still under warranty)?
Also, if I return it, can I remove the drives from the current unit and stick them into a replacement unit as they are and preserve the data or would they have to be re-formatted/reconfigured?
Thanks in advance for any advice you can give.
I already have 3 Readynas NV+ units all on the same network (DHCP) and I've always been very happy with their performance. This new one however is giving me some headaches.
After a couple of days, while the device was still basically empty, I woke up one morning and found the ReadyNas to be frozen. The blue power-on button was on, but the device was completely unresponsive. It wasn't available on the network anymore, RAIDar didn't detect it when scanning, I couldn't get to Frontview using the IP address that had been assigned to it, and I had to restart it by pressing the front power button until it rebooted. It worked fine for about a week so I thought this might have been a one-off occurrence and this morning I woke up to the same exact thing: the device is powered, blue light is on, but it doesn't respond, nothing happens if I press the power button (the led display doesn't come up). Only thing I can do is reboot by keeping front button pressed.
I don't think it's a temperature issue, as far as I can tell: the server wasn't really being used/accessed at the time, and I don't get any warnings or other symptoms, I just find the ReadyNAS still on but frozen/unaccessible.
After I force a reboot, I can access it just fine but there's nothing in the logs indicating that there was a problem and the device boots cleanly, without doing a filesystem check or any other indication that the Readynas is aware that it was not shutdown properly. I can't see anything in the logs, nothing immediately evident in the 'health' section of Frontview.
Any ideas/suggestions? This is my 4th ReadyNas (I have three NV+ on the same network) and this is the only one that has ever exhibited this problem. Should I look into returning it (I've had it for about a week now so it's clearly still under warranty)?
Also, if I return it, can I remove the drives from the current unit and stick them into a replacement unit as they are and preserve the data or would they have to be re-formatted/reconfigured?
Thanks in advance for any advice you can give.
6 Replies
Replies have been turned off for this discussion
- First, the array should be able to be removed intact (with the unit powered off normally), installed intact with each drive in the same respective bay (ie: drive that was in bay 1 in old unit inserted in bay 1 of the new unit) and booted.
Since this is a sporadic problem you may not know for a while if you have fixed it or not. If you have a PC that you can leave on 24/7 for 10-14 days, I would do a direct connection and see if the problem comes back up. There is a possibility, however, that a disk problem is causing the problem.
Since you have had the unit for less than 90 days, you may want to take advantage of the free telephone support and call technical support to open a case. When you have the case number, edit your previous post and append the case number to the end of the subject line. - Readynas support suggested it could be a firmware corruption issue and to redownload and install the Raidiator image. I did that (in the meantime 4.2.21 was released, so I upgraded to that) and I haven't had the device freeze up since then (it's been 6 days). I don't know if I'm out of the woods (the previous 2 crashes occurred after 2 and 7 days of uptime, respectively) but we'll see. Incidentally, is there a quick/easy to see the uptime of a Readynas device? I feel like this should be an option in Frontview or Raidar but if so I've missed it.
- While there is not specific "uptime" sat as far as I know either, but every time you boot the NAS, there should be an entry in the log (Status -> logs). It will basically say "System is up" and of course is logged with date and time. From this you can calculate the days/hours of uptime.
- For those comfortable with SSH, the "uptime" command can be used. However SSH is not for everybody as if you misuse SSH support can be denied. Obviously doing things like checking the uptime would be fine.
- have had the same problem since 2 days
the nas seems to enter in deep sleep mode and never wake up...
WTF with this hardware?
its only backup device and he is capable of freezing?
never view anything like this with my synology nas.....
oh yeah, the firmware dont report correct cpu temperature (always 50°c), and now it freeze randomly...
perhaps firmware corruption? oh yeah? we dont touch it and it corrupts itself?
6 month and problem occurs?
6 years with synology nas and never had anything...
starting to ask myself if netgear nas arent developped with foots..... - harmakhis you should open your own thread and contact support (please post your case number) so they can review your logs zip file (Status > Logs > Download all Logs) to help determine the cause of the problem. Your problem may have a different cause to the other user's.
Apparently the temperature is recorded as 50 degrees as temperatures below this level cannot be recorded accurately. So the temperature of the CPU would be at or below 50 degrees.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
