NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Crashing during factory reset
Hi folks -
This is a new problem based on the ReadyNAS Pro Business 6-disk discussed in viewtopic.php?f=65&t=75720
I finally decided it was time to factory reset the whole system. So I did. But when I came back the next day (today) the system had hung -- inaccessible via RAIDar, and with the display reading "Resync C, 10.8%".
I took some hints from viewtopic.php?f=65&t=44745 that Slot 1 is a little bit special, and that a bad disk in that slot might cause this sort of trouble. So I swapped disks 1 and 2, and factory reset again. The process went fine... testing disks... installing FW... awaiting RAIDar... I set it for X-RAID2, started the process, and went to lunch. Came back after lunch, and it was hung: the display said "192.168.168.168", and it was not visible on RAIDar. My understanding is that it should always show up in RAIDar except for quite brief interludes during certain processes. Anyway, nothing happened for 20 minutes or so, so I forced power off.
Per more hints on that same thread, I pulled out all the disks, put disk #6 into the #1 slot, and factory reset again. All progressed fine except that the NAS ignored me when I clicked on Setup in RAIDar. The display said "Awaiting RAIDar...Timer stopped". So I thought perhaps the Pro requires at least two disks in place in order to boot.
Put disk #5 into the #2 slot (so now there are two disks installed). Factory reset again. This time everything proceeded further than it had before. After I clicked setup via RAIDar, it proceeded through Installing and Creating Volume and File system check 100% and finally Booting. One of the two network connections took a DHCP address from my server (the other retaining 192.168.168.168), as seen via RAIDar.
Then the NAS abruptly disappeared from RAIDar. The front panel of the device reads "Resync C, 4.2%" and has been stuck there for over half an hour. Same problem, apparently, as the one I faced when I first came in this morning. So this appears to be a persistent problem.
I am having trouble believing that most or all of my disks have suddenly gone so bad that they can't support a clean installation. They are Seagate Constellation ES 1TB disks, ST31000524NS, listed on the HCL. They have been running happily since December 2010, so it isn't a cohort of lemons. The UPS (that the NAS once was hooked up to over USB, and that coincided with the NAS having problems) is also on the HCL; it's an APC Smart-UPS RM 1500.
A couple of weeks ago, I did a RAM check (from the boot menu) and the RAM checked out OK. None of the hard disks showed any problems via Frontview (before I did the factory reset); I checked each one a couple of weeks ago and they each had 0 ATA errors and no other warning signs that I recognized.
I'm fresh out of options. It sort of seems like something has gotten fried in the solid state hardware, but that's what I always think when I'm stumped. Any better ideas? Any options other than bricking the whole box?
Thanks everybody -
Thom
This is a new problem based on the ReadyNAS Pro Business 6-disk discussed in viewtopic.php?f=65&t=75720
I finally decided it was time to factory reset the whole system. So I did. But when I came back the next day (today) the system had hung -- inaccessible via RAIDar, and with the display reading "Resync C, 10.8%".
I took some hints from viewtopic.php?f=65&t=44745 that Slot 1 is a little bit special, and that a bad disk in that slot might cause this sort of trouble. So I swapped disks 1 and 2, and factory reset again. The process went fine... testing disks... installing FW... awaiting RAIDar... I set it for X-RAID2, started the process, and went to lunch. Came back after lunch, and it was hung: the display said "192.168.168.168", and it was not visible on RAIDar. My understanding is that it should always show up in RAIDar except for quite brief interludes during certain processes. Anyway, nothing happened for 20 minutes or so, so I forced power off.
Per more hints on that same thread, I pulled out all the disks, put disk #6 into the #1 slot, and factory reset again. All progressed fine except that the NAS ignored me when I clicked on Setup in RAIDar. The display said "Awaiting RAIDar...Timer stopped". So I thought perhaps the Pro requires at least two disks in place in order to boot.
Put disk #5 into the #2 slot (so now there are two disks installed). Factory reset again. This time everything proceeded further than it had before. After I clicked setup via RAIDar, it proceeded through Installing and Creating Volume and File system check 100% and finally Booting. One of the two network connections took a DHCP address from my server (the other retaining 192.168.168.168), as seen via RAIDar.
Then the NAS abruptly disappeared from RAIDar. The front panel of the device reads "Resync C, 4.2%" and has been stuck there for over half an hour. Same problem, apparently, as the one I faced when I first came in this morning. So this appears to be a persistent problem.
I am having trouble believing that most or all of my disks have suddenly gone so bad that they can't support a clean installation. They are Seagate Constellation ES 1TB disks, ST31000524NS, listed on the HCL. They have been running happily since December 2010, so it isn't a cohort of lemons. The UPS (that the NAS once was hooked up to over USB, and that coincided with the NAS having problems) is also on the HCL; it's an APC Smart-UPS RM 1500.
A couple of weeks ago, I did a RAM check (from the boot menu) and the RAM checked out OK. None of the hard disks showed any problems via Frontview (before I did the factory reset); I checked each one a couple of weeks ago and they each had 0 ATA errors and no other warning signs that I recognized.
I'm fresh out of options. It sort of seems like something has gotten fried in the solid state hardware, but that's what I always think when I'm stumped. Any better ideas? Any options other than bricking the whole box?
Thanks everybody -
Thom
7 Replies
Replies have been turned off for this discussion
- The pro will boot with only one disk.
I am thinking it is more likely a system failure than the disks, based on your writeup.
Though I would probably run seatools on the original disk 6, and maybe others to confirm that they are all good.
I think I'd also try removing the UPS altogether, just to rule out any possibility that it is providing inadequate power. How old is the UPS? Did you ever replace the battery? - Hrmm. I suspect that you're right. By "system failure" in this context I assume you mean something broken in the low-level hardware that can't be modified by users? Or is there something I can do? Any chance that it's a RAM failure, for example, even though the RAM check from the boot menu told me that it was fine?
I don't think it's a shortage of power -- that same UPS is also supporting two other ReadyNAS boxes (both of which are doing fine), a SonicWALL firewall, and a smart switch. But it could be, conceivably, that the particular plug that this box is plugged into is problematic, so I can test that. First by just plugging into the wall, I think, as you suggest.
The UPS is "new" -- though it is "new" from a refurbisher who installed new batteries. Conceivably they are pathetic batteries, though this refurbisher does a lot of business in the area and focuses a lot on repeat business, so I suspect they aren't in the sell-and-run game.
Thanks much -
Thom - Since all the other devices are happy, it seems unlikely to be the UPS, but it is easy to rule out.
By "system failure" I meant PSU, RAM, a system board component, SATA backplane ... Of course diagnostics aren't 100%, so it could be RAM. But passing the diags does make it seem less likely. - OK, I've started another memory test, just to make sure.
Once it's done, I'll try it off the UPS. BTW, when I was setting up the memory test, I noticed that the LED front panel only seemed to acknowledge the presence of the disk in slot #1 (disk #6), even though disk #5 was also there in slot #2. Not sure I want to read too much into that, as of course it couldn't boot with only one disk either, but maybe a bit more disk scrambling is in order.
Is there an straightforward way to test the PSU? Basic power is getting where it has to go, obviously, but there might be spikes or other misbehavior. I can figure out how to replace that if there's any way I can reasonably attribute these problems to power (as opposed to permanent damage elsewhere that might have occurred because of power issues).
If it isn't the RAM or PSU, though, dare I assume that nothing else is really user-serviceable?
thanks
Thom - Nothing else would be serviceable with my hardware skills...
I can't think of any easy way to isolate it to the PSU, other than replacing it and see. You've already reduced the number of drives, so it doesn't seem likely to be overall power capacity. So it would need to be something more subtle. - In the test above drive number 6 is always there and the NAS failed to setup with just that drive. As Stephen said, the Pro6 will work with just one drive. Try another single drive, if that fails as well, then you have a HW problem. The next step could be reseating the connectors and the RAM - even though your memory tests seems ok.
- Good logic; I'll do that, just in case. Thanks.
thom
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
