My ReadyNAS Pro Business became unresponsive for the first time in years. It was not showing under SHARED on my Mac this morning. When I tried to ping it, I got nothing. RAIDar did not detect it, so I decided to go to my LAN room to see what was going on. The power was on, but when I pressed the power button, the LED screen did not react. I decided to shut it off by holding down the front panel power button, and it did shut down this way. After I powered it back up, it came back on and I am now able to access it. I can now ping it, RAIDar sees it, and I can access shares on it. I downloaded all logs, but I’m not sure what I should be looking for. One thing I could correlate to this is that yesterday I had an unexplained crash of my Cisco 871. The ReadNAS is plugged into one of the switch ports on the Cisco 871, so when the Cisco 871 rebooted, the ReadyNAS lost the link and then re-acquired it. I wonder if this loss of the network connection could have caused the ReadyNAS to become unresponsive or if this is just a coincidence. The ReadyNAS is running 4.2.21, to which I upgraded from 4.2.20 on June 24, 2012.

Well the NAS does not request a new DHCP address before the lease is up, and if the Cisco switch crashed, then the ARP table in the switch is erased. The ARP table wont build itself up before you reboot the devices attached to the switch.I'm not sure why it didn't respond to the power button though

There’s no DHCP - it’s configured for a static IP. ARP table would get rebuilt when I tried to ping it (if not earlier because there are plenty of services running on this ReadyNAS - NTP being one of them), which would have caused traffic resulting in the ARP table rebuilt.

Well then I'm not sure. Unless the Cisco sent a surge that bunked your NAS when it crashed.

The ARP theory doesn't explain the LCD screen not responding, so I don't think that is the cause.As usual you should look at disk health for each drive, and perhaps also look to see if the OS partition is getting full.If the NAS is on the same power circuit as the switch, it is possible that a common power glitch affected both of them. Are you using a UPS? As Slasky points out, a surge could also come in through the ethernet cable, though I'd think that would require a pretty extreme event (nearby lightening strike for instance).

I didn't say it's common :P but it is a fault source, albeit a rare one. It could be a software malfunction as well, and as Stephen suggest, check the OS partition. It's not certain that the two events are connected, but in my experience it's rare for two events like this not to be connected.

ReadyNAS Pro unresponsive on 4.2.21 - first time in years.

20 Replies

Replies have been turned off for this discussion

Slasky
Aspirant
Jul 05, 2012
Well the NAS does not request a new DHCP address before the lease is up, and if the Cisco switch crashed, then the ARP table in the switch is erased. The ARP table wont build itself up before you reboot the devices attached to the switch.

I'm not sure why it didn't respond to the power button though
sirozha
Aspirant
Jul 05, 2012
There’s no DHCP - it’s configured for a static IP.

ARP table would get rebuilt when I tried to ping it (if not earlier because there are plenty of services running on this ReadyNAS - NTP being one of them), which would have caused traffic resulting in the ARP table rebuilt.
Slasky
Aspirant
Jul 05, 2012
Well then I'm not sure. Unless the Cisco sent a surge that bunked your NAS when it crashed.
StephenB
Guru - Experienced User
Jul 05, 2012
The ARP theory doesn't explain the LCD screen not responding, so I don't think that is the cause.

As usual you should look at disk health for each drive, and perhaps also look to see if the OS partition is getting full.

If the NAS is on the same power circuit as the switch, it is possible that a common power glitch affected both of them. Are you using a UPS?

As Slasky points out, a surge could also come in through the ethernet cable, though I'd think that would require a pretty extreme event (nearby lightening strike for instance).
Slasky
Aspirant
Jul 05, 2012
I didn't say it's common :P but it is a fault source, albeit a rare one.

It could be a software malfunction as well, and as Stephen suggest, check the OS partition.

It's not certain that the two events are connected, but in my experience it's rare for two events like this not to be connected.
StephenB
Guru - Experienced User
Jul 05, 2012
It does seem likely that there is a connection.
sirozha
Aspirant
Jul 05, 2012
How do I check if the partition getting full? What size is full? What should I do if it is getting full? Both the NAS and the Cisco 871 are plugged in to the same UPS. There’s no event logged in the log that shows on the Web GUI since I upgraded the firmware to 4.2.21 two weeks ago.
Slasky
Aspirant
Jul 05, 2012
There should be some info if you download all the logs. Otherwise you'd have to SSH into your device, but thats some more hassle
sirozha
Aspirant
Jul 05, 2012
Slasky wrote:
There should be some info if you download all the logs. Otherwise you'd have to SSH into your device, but thats some more hassle

I’d much rather SSH. Which partition should be I looking for? Should I issue the “df” command? What size is “too full”?
Slasky
Aspirant
Jul 05, 2012
Not sure about the command, but iirc the OS partition is on about 2GB. So anywhere near that would be full :P