NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
StephenB
May 09, 2013Guru - Experienced User
OS 6.0.5 "device is offline"
I updated my RN102 from 6.0.4 to 6.0.5 about 7 hours ago, and am still seeing the "device is offline" when I access the web page, and the blinking blue light on the panel.
After a while I get "Connection lost" with "do not reboot the device" and "call netgear technical support".
I can access the volumes over CIFS, ssh access is fine, and there is nothing intensive happening per top.
Anyone else seeing that?
btw, one clue might be the following stuff in error.log:
After a while I get "Connection lost" with "do not reboot the device" and "call netgear technical support".
I can access the volumes over CIFS, ssh access is fine, and there is nothing intensive happening per top.
Anyone else seeing that?
btw, one clue might be the following stuff in error.log:
[Thu May 09 13:24:45 2013] [error] [client 10.0.0.22] Error connecting to readynasd -2, referer: https://rn102/admin/
[Thu May 09 13:24:45 2013] [error] [client 10.0.0.22] 25721:dbbroker.cgi.c:513 , referer: https://rn102/admin/
[Thu May 09 13:24:45 2013] [error] [client 10.0.0.22] Connection fail., referer: https://rn102/admin/
[Thu May 09 13:24:45 2013] [error] [client 10.0.0.22] Premature end of script headers: dbbroker.cgi, referer: https://rn102/admin/
21 Replies
Replies have been turned off for this discussion
- super_poussinVirtuosoSaw that also
- StephenBGuru - Experienced UserIt resolved! system reboot started at 6:18:09, the ReadNASOS background service finally started at 13:45.
Though now it is asking me to register again - which fails, since it is already registered. - roystudiosAspirantAny idea why it took so long to restart? Mine is in the same state - I don't mind waiting as long as I know what it is waiting for - any log indication of what it was waiting for/triggered the restart?
- StephenBGuru - Experienced User
There was no indication in the system log as to what it was doing during the reboot.roystudios wrote: Any idea why it took so long to restart? Mine is in the same state - I don't mind waiting as long as I know what it is waiting for - any log indication of what it was waiting for/triggered the restart?
When it did finish, I noticed that clicking on the network tab didn't work (it didn't display the ethernet interface, and eventually timed out). So look for that when it is done.
Netgear went into my unit to take a look, but I don't know what they found (I suspect they aren't done analyzing the logs). They did fix the network tab problem, and possibly some other stuff I didn't notice. - roystudiosAspirantThanks. Mine came alive again after 8 hours but the disk light '3' is now mysteriously off although it is still reporting the correct Tb across the 4 x 3Tb disks. But time machine isn't working now, nor any AFP shares attached either through bonjour or afp://x.x.x.x . Will try a reboot and fiddle tomorrow (although a reboot didn't fix the disk3 led not working) hmm - not brimming with confidence at the moment. Will report back
R - roystudiosAspirantOK - AFP was 'on' but I had to switch it off and on again to get it working again (Avahi/Bonjour still not announcing the NAS though). Time Machine still no seeing the disk to connect to, plus ReadyDLNA was enabled (I had disabled it) and it was eating over 50% CPU. Looks like we will have to reset some personal defaults after installing this update.
Tkx
R - hungerApprenticeI'm seeing the same problem on my 312. Started the update about an hour and a half ago. Blinking blue light. Network interface does not respond to pings or anything else. I'll check it in the morning.
- hungerApprenticeBlinking stopped, but still non-responsive.
- evan2NETGEAR ExpertHi Hunger,
Could you send me logs? I need to check, thanks!
if you can not open UI, could you try to do OS-Reinstall. - hungerApprenticeThanks, Evan.
I ended up calling support that morning. The tech had me power down the unit and power it back up. Afterward, it seemed fine except for two problems:
1) The list of users was empty and attempts to add myself resulted in an error message although I could add others, and
2) I could not check the box to enable Replicate as attempts to do so resulted in an error message regarding a bad port number. What is strange is that the device did show up on replicate.readynas.com even though the check box was not checked.
The tech tried to download the logs but was unable to do so.
The tech asked me do an OS reinstall, which I did later on that day. After it came back up I tried to access it via my browser and I was presented with a basic authentication dialog (A username and password are being requested by https://xxx.xxx.xxx. The site says: "ReadyNAS Admin"). I was unable to login via the UI as it did not recognize the login and password. I have no access to the shares either as it does not recognized my login and password. In addition, it does not show up in RAIDar. What is really bizarre is that I can access it using ReadyCLOUD but I am unable to launch the Admin Page UI from there due to the login/password problem. It is merrily sending emails to me complaining about not being able to talk to my UPS.
It dawned on me that if I can access it via ReadyCLOUD for which I use the same login ID but a different password then perhaps doing the OS reinstall somehow changed the password on the ReadyNAS from the one I used when I configured it originally when I launched Setup from RAIDar to the ReadyCLOUD password instead. Sure enough, using the ReadyCLOUD password lets me access the Admin Page and also the shares.
It is acting very strangely. I cannot enable Replicate as it won't even allow me to click the check box. It can't communicate with the UPS. When I tried to download the log files, after several minutes, the following appeared in the browser:
<xs:nml xmlns:xs="http://www.netgear.com/protocol/transaction/NMLSchema-0.9" src="browser" dst="nas" locale="en-us">
<xs:transaction ref-id="" type="0">
<xs:response ref-id="opid" status="failure">
<xs:error>
<xs:error-code>
<![CDATA[ 12008010002 ]]>
</xs:error-code>
<xs:error-cause>
<![CDATA[ Can't create zipped log ]]>
</xs:error-cause>
<xs:error-details>
<![CDATA[ Error in dlowload log ]]>
</xs:error-details>
</xs:error>
</xs:response>
</xs:transaction>
</xs:nml>
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!