NAS540 setting retention, stuck on default password
Freshman Member
A week or 2 ago my NAS540 started showing some strange issues:
- the paired LAN interfaces wouldn't work anymore, had to revert to a single connection
- in the webinterface, moving icons to the 2nd page would work, but it would be gone after login out/in again
- an RSync job in backuplanner stopped running automatically and when started manually produced a '500 internal server error'
So I tried to fix this by factory reset, firmware downgrade and upgrade in the hopes that that would wipe some setting files. I removed the drives before. Back on V5.21(AATB.13), I started adding the drives and shares again, and it appeared to work except that reorganise the icons would still not be persistent.
But on adding the last drive and share I got a new error in the web interface (can not remember which). After a reboot, It seems it is now stuck with the default password. It asks to enter a new password, but will not move beyond that, always and only asking to enter a new password.
Is there anything I can try to recover? I wanted to try the rescuedisk, but the site (http://zyxel.diskstation.eu/Users/Mijzelf/Firmware/) is down at the moment.
All Replies
-
It's now gone from not great to pretty bad. I found the archive with the rescue firmware here:
http://mijzelf.duckdns.org/zyxel/zypkg-repo/fw5/
But now I can't connect over ethernet at all. There is no beeping, not even when holding the power button for many seconds.
I should probably give up?
What would be a reasonable and cheap alternative?
0 -
And now my second NAS520 box is devolving to similar state: after a reboot, the web login page accepts default password 1234, shows the dialog to change the password but then goes back to the default anyway and I can't get to any other settings.
I didn't attempt any firmware updates on this one, just a reboot.
This is not looking good.
0 -
Did you have an extremely long uptime? The problems in your first post could be caused by aging flash memory. But two boxes at the same time?
The flash is only read on boot, and written when you update settings. (Or update firmware). So if your 520 has been up for years, the odds increase that in that years some threshold was exceeded.
Another option could be that the browser changed. There is a lot of javascript and redirections in the login procedure. Don't know how fragile that is. I know that there were often problems after a firmware update, when the (cached) redirections didn't work anymore. In that case clearing the browser's cache solved the problem.
I found the archive with the rescue firmware here:
Meanwhile there is a new mirror at http://zyxel.ddnss.eu/Users/Mijzelf/
0 -
Box A did have a long uptime. I bought it new ~10 years ago and it has been on 24/7 since.
Box B I got second hand about 5 yearrs ago, but it has been turned on only sporadically for backups. So total uptime must be much lower.Box A symptoms do look like a gradual degradation where at some settings started to get lost over time, but Box B worked perfectly fine until now suddenly it doesn't.
Box A seems bricked at this point. I guess I can try looking into a serial connection. But given its age, I think that's may not be worth the trouble anymore.
Box B I still hope to recover (if only to copy the drives). When I enter the default password and it asks for a new one, it then doesn't seem to commit that. It show the rotating clock on the gray background, but after a minute it reloads the login screen without ever confirming the pasword change. I tried on multiple browsers and all have the same behaviour.
When I press and hold the power button, it beeps once, then again, but a third beep never comes.
0 -
When I press and hold the power button, it beeps once, then again, but a third beep never comes.
The first beep is an acknowledge that the button is pressed, and a signal is send to the OS to shutdown. The second beep is an acknowledge that the MCU takes it over and just cuts the power (in case the OS is crashed). There shouldn't be a 3th beep.
If you intended to do a factory reset, you should use the reset button on the back.
Box A seems bricked at this point.
Have you tried without disks? Or have you the possibility to try another power supply? A power supply can wear out, not being able to supply the needed juice anymore.
0 -
I am a special kind of idiot to not find the reset button in the first place.
I did a factory reset on Box B and am now installing the drives from Box A one by one. All are basic volumes, so that should be OK. It is working at the moment, except I can't move icons around on the web interface. Weird, but if that is the only issue I'll live with it.
Box A is very dead. Reset button doesn't do anything it seems.
0 -
Box B is working reasonably well. All shares reestablished and rsync seems to work.
However in 'Control Panel'/System/Power gives me the fields visible below but all overlayed with a gray box and 500 Internal Server Error.
0 -
'Control Panel'/System/Power? I don't have that entry. I do have a 'Control Panel'/Maintenance/Power.
0 -
yes indeed. I was confused by the menu on the left.
I set up a backup job and while it appears that it did run yesterday evening, I can not modify the schedule anymore. Again a 500 error.
0 -
A backup job is part of the BackupPlanner package, right? Did you install it after you swapped disks? Else it might be running the package you installed on Box A, and maybe it's configuration is not perfectly sane.
0
Guru Member
Categories
- All Categories
- 415 Beta Program
- 2.5K Nebula
- 152 Nebula Ideas
- 101 Nebula Status and Incidents
- 5.8K Security
- 296 USG FLEX H Series
- 281 Security Ideas
- 1.5K Switch
- 77 Switch Ideas
- 1.1K Wireless
- 42 Wireless Ideas
- 6.5K Consumer Product
- 254 Service & License
- 396 News and Release
- 85 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.6K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 87 About Community
- 76 Security Highlight
