NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Power LED Blinking, Web Admin not accessible.
hi all,
I wonder if anyone came across problem with RN102 boot to a locked condition where the power LED would blink continuously, while all other LED are off except ACT is on.
I have this problem following upgrade a secondary disk in JBOD config to a higher capacity.
Basically this is what happened. I first unmount the disk and ghost it to a new bigger capacity disk using Ghost 11.0 in DOS.
Everything went absolutely well. I mounted the new disk to RN 102. and power up RN, it worked. View from the web admin page I was able to verify the content and capacity expanded.
Note this is still with JBOD configuration. I was able to view and play content from the primary and secondary disk. This is with OS 6.2.2. Seems it is able to detect extra space in the new disk and expand the partition automatically.
Having pleased with this achievement. I decided to use another drive instead since I had bought another disk for backup purpose.
So i re-ghost the old disk to this 'another' new disk.
Having repeat all the steps as first what I did. This time, RN 102 would boot up but then stalled with power LED blinking and ACT LED on continuously.
I was not able to access web admin page now. Thus, I unmount this 'another' disk and mount back with the old disk.
This time now, it still stall with power LED blinking and ACT LED on continuously.
I also tried to mount with first new disk, it also the same with blinking power LED.
I tried also to use boot menu to OS re-install, however still the same result.
The data of both disk still can be accessed from network. Using file explorer, I was able to view and play the content.
However, web admin page still cannot be accessed.
Later, I check all the disk with HDDscan, soon I found that the last 'another' disk installed, has bad sector from the SMART attribute # 196.
I suspect because of this, once I plugged the bad 'disk', OS 6.2.2 lock the system into service mode and cease to operate as normal.
Now I still can view the data from network, but USB disk plugged in won't be shown in the file explorer as it normally would.
When power on RN102 now, it would boot like normally it does, first power LED blinking, then, stop blinking, on for few seconds, then ACT LED on, then power LED blinking again continuously.
I hope this is really an OS 6 locking mechanism and I would be able to unlock it so that I would not have to copy all the files and setup all over again..
I wonder if anyone came across problem with RN102 boot to a locked condition where the power LED would blink continuously, while all other LED are off except ACT is on.
I have this problem following upgrade a secondary disk in JBOD config to a higher capacity.
Basically this is what happened. I first unmount the disk and ghost it to a new bigger capacity disk using Ghost 11.0 in DOS.
Everything went absolutely well. I mounted the new disk to RN 102. and power up RN, it worked. View from the web admin page I was able to verify the content and capacity expanded.
Note this is still with JBOD configuration. I was able to view and play content from the primary and secondary disk. This is with OS 6.2.2. Seems it is able to detect extra space in the new disk and expand the partition automatically.
Having pleased with this achievement. I decided to use another drive instead since I had bought another disk for backup purpose.
So i re-ghost the old disk to this 'another' new disk.
Having repeat all the steps as first what I did. This time, RN 102 would boot up but then stalled with power LED blinking and ACT LED on continuously.
I was not able to access web admin page now. Thus, I unmount this 'another' disk and mount back with the old disk.
This time now, it still stall with power LED blinking and ACT LED on continuously.
I also tried to mount with first new disk, it also the same with blinking power LED.
I tried also to use boot menu to OS re-install, however still the same result.
The data of both disk still can be accessed from network. Using file explorer, I was able to view and play the content.
However, web admin page still cannot be accessed.
Later, I check all the disk with HDDscan, soon I found that the last 'another' disk installed, has bad sector from the SMART attribute # 196.
I suspect because of this, once I plugged the bad 'disk', OS 6.2.2 lock the system into service mode and cease to operate as normal.
Now I still can view the data from network, but USB disk plugged in won't be shown in the file explorer as it normally would.
When power on RN102 now, it would boot like normally it does, first power LED blinking, then, stop blinking, on for few seconds, then ACT LED on, then power LED blinking again continuously.
I hope this is really an OS 6 locking mechanism and I would be able to unlock it so that I would not have to copy all the files and setup all over again..
19 Replies
Replies have been turned off for this discussion
- Managed to salvage all data. Found only transmission config files corrupted. Suspect transmission app corruption is the culprit which held up the boot process. Any idea if I can do something like deleting transmission in root/etc/int.d/ to workaround that boot problem?
- What version of the Transmission app was installed?
I would suggest using the new version of the app 3.00.8.
You could try removing the app. We use systemd to start services in OS6 - Already removed fvapp-transmissionr6.service from lib/systems/system it still won't boot properly. Anyway I can force os reinstall beside boot menu? Tried few times boot menu os reinstall unable to fix .
- Any clues as to what is preventing boot up in the journal?
Has the ownership of files been recursively set to guest? - I think it actually boot up succesfully, otherwise i can't access all files through both AFP and SMB share.
It is only accessible via admin account with correct password.
Only web admin page is not available and power LED blinking, other application seems to be running fine. - Some users have tried resetting ownership of files on the OS partition to root. Personally I would recommend backing up your data, doing a factory default (wipes all data, settings, everything) and restoring your data from backup.
- Seems this "power LED blinking and no web admin page but SMB/AFP is working" is commonly encountered among Readynas OS 6 user.
What is the common root cause of this problem?
Is because file ownership? I don't think it is the case for me since, I didn't meddle with ownership before having this problem.
I'm looking for a more intrusive way to perform OS reinstall since it appear to do nothing as of now.
By resetting ownership of all files in root partition will help?
Another behavior I observe is, if I didn't plug-in the secondary drive, SMB/AFP sharing dissapear from network, even though primary drive also have multiple shared folders.
# systemctl status apache2
# systemctl status readynasd
# journalctl -a | grep apache2 | tail -n 20
# journalctl -a | grep readynasd | tail -n 20
# ls -la /etc- conection refused.
do I need to set the unit to "Tech support" from boot menu?
NAS@NAS102:~$ ssh 192.168.1.100
ssh: connect to host 192.168.1.100 port 22: Connection refused
NAS@NAS102:~$ ssh admin@192.168.1.100
ssh: connect to host 192.168.1.100 port 22: Connection refused
in /etc/default/services set SSH=1 ? - Seeing you have a backup, I think it would be simplest to do a factory default (wipes all data, settings, everything) and restore your data from backup.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
