NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Admin page unavailable after cancelled backup job & hard reboot, shares are working
Hopefully someone can help me get out of this deadlock. I recently added a rsync backup job to sync the local /media share with an USB drive that was connected via the rear USB socket of the RN...
Did you at any point disconnect or power down the USB drive before the backup job said it was done? I ask because I suspect that it continued after that. But once the USB drive wasn't connected, it began to copy files to the mount point in the OS partion instead of the USB drive that should have been mounted there. That'll fill the OS partition in a hurry.
The message you are seeing is the location where the OS crashed, undoubtedly due to the too-full OS partition. If you are now able to enable SSH after the OS re-install, you need to go in and clear out any files that were copied to the mount point directory.
The fact that your files were copied to media/media is the way the rsync backup jobs are designed. I disagree that's the way it shoud be, but it is. The work-around is that you need to go back into the backup job configuration after it's created and put a single forward slash "/" as the source path.
For future aborts, I recommend you check the log (available inn the backup job menu) to see that it says the job was cancelled. The log is only updated at completion (it doesn't show progress), so that should be a sure way to know it's done.
There are other ways we could have helped you clean out the system, but it's complicated. Since you had a full backup, that's really the road of least resistance in this kind of case.
Sandshark wrote:For future aborts, I recommend you check the log (available inn the backup job menu) to see that it says the job was cancelled. The log is only updated at completion (it doesn't show progress), so that should be a sure way to know it's done.
There are other ways we could have helped you clean out the system, but it's complicated. Since you had a full backup, that's really the road of least resistance in this kind of case.
One last thing and on a sidenote:
What would be the recommended way to restore my backup? NB: It's around 4TB of data on an external USB3 box with NTFS filesystem. I could abuse the "Backup" GUI option (kind of backwards rsync, *sigh*), just a trivial copy-paste in the NAS' file browser (will this also copy hidden/system files - at least they are not shown there?) or probably even by rsyncing in an SSH root shell, e. g. something like:
su rsync -avh /media/USB_HDD_1/home/ /data/home &
to restore the home folders (don't know if activating checksums with -c is really necessary). At least eton had success doing it that way (see his post in https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/How-to-restore-a-nas-with-rsync/td-p/840685, I modified directories to match my RN214). I would somehow need to send the command to the background, since I don't want to keep the SSH console window open for hours. Dragging the files around the network connection with a remote PC would be the very last resort.
Thanks again!
Addendum: Just sending rsync to the background with "&" does not work. The process will stop once the SSH terminal window is closed. Some people had success with nohup, redirecting stdin, stdout and stderr to /dev/nul. This seems quite complicated to me.
Then there is the fraction recommending to install the screen package with
apt-get update apt-get install screen
and then
screen -S rsync rsync -avh /media/USB_HDD_1/home/ /data/home
in your SSH terminal to create a screen named "rsync", start the restore and hit CTRL+a, d to detach the screen. Once the restore is finished, you would run
screen -r rsync
in the SSH terminal to reconnect.
I would probably send stdout and stderr to a file, so there is a way of diagnosing things in case something went wrong:
rsync -avh /media/USB_HDD_1/home/ /data/home >~/rsync.log 2>&1
What do you think? I'm a bit hesitant though to install $STUFF on my RN214 box - if that works at all...
Restore using an rsync backup job will take a lot longer than just using a standard internal to intenal one, which seems to be little more than a cp -a.
Sandshark wrote:Restore using an rsync backup job will take a lot longer than just using a standard internal to intenal one, which seems to be little more than a cp -a.
OK. I have just started a good plain old local copy job from the connected external USB box to a NAS share and forego with any fancy checksums *). Let's hope the data arrives intact and the whole process is not going to take an eternity.
Thanks again!
*) ... for now. I can still rsync -c later, use TotalCommander from the Windows PC, Meld, or mess with hashes later.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
