NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadNAS PRO 6 stuck at "Booting" after requesting download of logs
I have an ReadyNAS pro 6 which I noticed had failed complete a "pull backup" from a primary ReadyNAS Pro 6 because the file system of the backup unit became full.
The primary ReadyNAS Pro 6 is currently operating properly and has no issues, the unit in question is an rsync backup of the primary but does not delete files during rsync (the data is relatively static and accidental deletion is a significant concern). Thus, eventually the backup volume fills up completely and I perform a rsync with delete after verifying that nothing has been lost since the last backup.
I checked the status of the disks via the web interface and all was good, weekly raid scrubbing was on as was a weekly file system integrity check. The last backup which had occurred was off of the visible log window so I requested a download of the logs. At this point the backup NAS became non-responsive, both the web admin interface and access to files (via http, there are no mounted shares on this unit).
Previously when the backup NAS file system has filled I have performed a "full backup" which deletes everything on the NAS and then rsync's everything from the primary NAS.
Having read many of the logs it appears that netgear support logs into the machine and then cleans some things up and it is back to normal. In this case, the machine cannot be put onto a network which is accessable which will limit the options of support.
What are the options for things which I can do myself?
This is a backup "mirror" of the primary NAS, if there is a path which maintains all of my backup jobs but looses the data on the backup that would be workable (I would backup the data to an alternate location from the primary NAS prior getting too aggressive with the backup NAS.)
I believe that the backup ReadyNAS is running 4.2.2x (The original firmware provided with the box), it is factory loaded with 6 - 2Tbyte drives. I will confirm the firmware version tomorrow.
Thank you very much for any recommendations on getting this backup of my primary ReadyNAS back up and running.
mdgm wrote:
It sounds like you may have a large log file or perhaps even a full 4GB root partition.
For these kinds of issues there is per incident support available, but remote access to your NAS would be required.
If ssh is already installed on the NAS, you could access the OS partition yourself and likely find the file and truncate it. However once the OS partition is full, you won't be able to install the add-on to enable ssh.
So your other (painful) option is to do a factory reset on the NAS (which destroys settings and data), rebuild it, and restore the data from the primary NAS.
26 Replies
Replies have been turned off for this discussion
Note that I do see the "Check FS" message on the front panel which completes quickly and then goes on to the "booting" message
Did you discover which firmware is on the unit?
It sounds like you may have a large log file or perhaps even a full 4GB root partition.
For these kinds of issues there is per incident support available, but remote access to your NAS would be required.
mdgm wrote:
It sounds like you may have a large log file or perhaps even a full 4GB root partition.
For these kinds of issues there is per incident support available, but remote access to your NAS would be required.
If ssh is already installed on the NAS, you could access the OS partition yourself and likely find the file and truncate it. However once the OS partition is full, you won't be able to install the add-on to enable ssh.
So your other (painful) option is to do a factory reset on the NAS (which destroys settings and data), rebuild it, and restore the data from the primary NAS.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
