NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
syklone
Jan 20, 2013Aspirant
ReadyNAS Ultra 4 stuck on "Booting" after log file download
Hi all.
Story is this: I have just completed a 300GB rsync backup and I got an error in the log. The log was too big to display in the web interface so I tried to download the complete logs.
After this my readynas hanged and could not be accessed. It could also not be powered down using the double-click on the power button, so I had to force it by holding the powerbutton down.
After this my readynas won't boot. It goes to the "Booting"-message and just stops there. I can ping the device on it's fixed IP address but I cannot access shares or the web interface. Accessing shares also do not work. SSH login also does not work.
I have backup of the most important data, but I want to get some tips what I can do besides factory defaulting so I am not risking full data loss.
Thanks.
Story is this: I have just completed a 300GB rsync backup and I got an error in the log. The log was too big to display in the web interface so I tried to download the complete logs.
After this my readynas hanged and could not be accessed. It could also not be powered down using the double-click on the power button, so I had to force it by holding the powerbutton down.
After this my readynas won't boot. It goes to the "Booting"-message and just stops there. I can ping the device on it's fixed IP address but I cannot access shares or the web interface. Accessing shares also do not work. SSH login also does not work.
I have backup of the most important data, but I want to get some tips what I can do besides factory defaulting so I am not risking full data loss.
Thanks.
21 Replies
Replies have been turned off for this discussion
- sykloneAspirantHi, just tried entering boot menu and chose "OS reinstall". It went through and then stuck on "Booting" again. The IP didn't change from the old fixed IP address which I think it should after a OS reinstall. Also after letting the NAS sit for 10-15 minutes it stops responding to pings. It did this before OS reinstall also.
- sykloneAspirantHello, I have just seen this exact error in this persons post:
http://www.readynas.com/forum/viewtopic.php?f=64&t=67337
I guess I have to open a support case and let a Netgear technician take a look at it? - sykloneAspirantFiled a support case. Really thankful if it could be looked at.
Case # 20398529 - RabbieAspirantYou can boot to "tech support" then forward the port 23 to WAN ip.
After that PM the WAN ip, i can login and have a check. - chirpaLuminaryForwarding port 23 to WAN is NOT recommended. That allows anyone to connect to your system remotely.
The NAS already has a 'phone home' function to connect to NTGR servers securely, without port forwarding. Support agents are the only ones authorized to connect via this secure mode.
Also giving non-NTGR employees access in this mode will cause support/warranty issues.
Rabbie, you need to check with OOM-9, to get yourself properly represented as a NTGR employee/contractor on the forums here. - sykloneAspirantYes, I too think forwarding telnet to my device would be a security risk.
However I just got a reply in the Netgear service portal asking me to forward port 22, 23 and give them WAN and LAN IP's.
This should not be necessary then? I replied stating just that. My NAS is in tech support mode right now. - mdgm-ntgrNETGEAR Employee RetiredAll they should need from you is the 5-digit ID shown in the Info (far right) column in RAIDar and on the LCD display to connect to your NAS.
You should not need to forward any ports. Port 22 is for SSH which isn't available in tech support mode - JustKJAspirantAll,
Was reading the forums this morning and something made me want to see my log files. Using the Web Interface I click the link for the log files. Nothing happened. I waited for 10-15 minutes and tried to refresh the screen and it would not load the page. After about another 15 minutes, I powered down by holing the power button. After it was off, I turned it back on and it stayed "booting..." for over 30 minutes. I have never seen that before.
Checking the forums again, a recomendation was a cold boot. The only way to do this was pull the plug. I did that left it out for 90 seconds until all drive sounds were gone, and then replugged it and pressed power. It began powering up, did a volume check and again now has been "Booting..." for 30 minutes.
On the front panel all four drive lights are on, the Activity light is blinking fast, and the power button is fading on and off quickly.
It sound similar to what happened to syklonem, any thoughts? - sykloneAspirant
mdgm wrote: All they should need from you is the 5-digit ID shown in the Info (far right) column in RAIDar and on the LCD display to connect to your NAS.
You should not need to forward any ports. Port 22 is for SSH which isn't available in tech support mode
Hm, seems like the tech support on the Netgear service portal still is asking me to forward telnet port to wan. I have now given them my 5 digit code as displayed on the LCD.
I'll wait now for the next reply. If not I guess I have to open up port 23 so they can connect so I can have this resolved. - chirpaLuminaryTell whoever you are speaking with in tech support they might as well escalate the case to the next level. Because whoever is going to be working on your system should know that port forwarding telnet is NOT required.
I just spoke with an L3 there, your five digit ID works fine right now without forwarding, the secure access tunnel is functioning.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!