I've got an old ReadyNas Duo that has stopped responding. The only way to restart it is by unplugging the power cord. After reboot, it does the quota check procedure, and goes up to 6% of the volume resync and then it hangs.
Question: Should I remove one of the disks and reboot again? Reinstall the OS?
Any help would be greatly appreciated.
----
This is the information that I captured after the last reboot:
I believe that is a good plan, and you should do it with Drive 2. The high pending sector count, raw read errors, and other errors suggest Drive 1 is failing. Assuming that works, backup your data, then replace Drive 1 with a suitable (not Green) drive. And be prepared to replace drive 2 before long as well. It does not have nearly as many load cycles as the other (likely because of the newer firmware version), but it does already have some pending sectors.
OK, I removed disk 1. Trying to backup the share but it is not even starting the backup as there is some sort of problem with the connection (backup log message below)
rsync is enabled on my unit. What should be my next step here? I am reluctant to reinstall the OS as I don't have a backup of this data (I know, shame on me). Thx!
---
Backup Status: Fail: Failure during copy.
Failed to run rsync, return rc 10 'rsync' command returns rc=10
rsync: failed to connect to 192.168.1.78 (192.168.1.78): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(125) [Receiver=3.1.2]
Forgot to mention that when creating the backup job, it did require a port number (I put 6000 as I didn't find any reference that a specific port number should be used). I wonder if that is my problem.
The standard port for rsync is 873. Unless the rsync server to which you are sending the data uses a non-standard port, that's the one you need to use.
Thx for the info. I should have made a simple search for "Standard rsync port". Duh! Anyway. Will let the bakcup to the USB drive finish and retry using rsync to my other ReadyNas duo.
Do you think I should insert the new HDD (not arrived yet) as is or try to reinstall the OS first?
USB Drive backup completed but... Going back to the log, it says there were errors. I tried to download the full system log and the zip file is corrupted.
Just waiting for the new disks (bought the red ones as per recommendation) to arrive and start the replacement process.
Make sure the rsync backup job is set to incremental, and then try running it again. It should complete quickly (only trying to copy files that weren't transfered the first time).
Got the new disk (WD Red) as recommended. Replaced disk 1, resync went fine. Status is healthy on both SMART+ reports on the bottom).
But...
Ran backup on USB drive and it gave me a bunch of "cp: cannot stat Input/output error". Any ideas as to why the backup is still failing? Any workarounds?
How is the USB drive formatted? How big is the USB drive? A duo V1 can't handle a USB drive bigger than 2 TB.
If it is a format windows supports, try putting the USB drive into a Windows PC. It likely will offer to "repair" the file system - if it does that, let it.
FWIW, USB backup on a duo v1 is extremely slow. You will get faster speeds if you connect the drive to a PC and back up over a wired Network. If you do it that way, you can use something like FreeFileSync or Teracopy, you don't need to use the built-in backup.
It is important to mention that the USB drive is there to back up the NAS data which came from old laptops that are now in computer heaven. I am doing current back-up on the cloud.
----
How is the USB drive formatted? EXT3
How big is the USB drive? 2TB (it is 1.8GB occupied)
A duo V1 can't handle a USB drive bigger than 2 TB.
If it is a format windows supports, try putting the USB drive into a Windows PC. It likely will offer to "repair" the file system - if it does that, let it.
From what I've seen on a different thread, I would need to install drivers for my Windows PC to be able to read/write on the EXT3 formatted drive. Having said that, I tend to believe that the repair would be required on the NAS disk and not on the USB drive. Am I wrong?
FWIW, USB backup on a duo v1 is extremely slow. I painfully noticed that.
From what I've seen on a different thread, I would need to install drivers for my Windows PC to be able to read/write on the EXT3 formatted drive.
OSX and Windows are quite forgiving on USB drive ejection. Linux isn't, so if the drive is pulled without being ejected (or even if the system is forcibly shut down with the drive mounted), the system tends to mount the drive as read-only.
Since it is ext formatted, Windows can't fix that.
I tend to believe that the repair would be required on the NAS disk and not on the USB drive. Am I wrong?
Usually it's the USB. The details in the log might be useful in sorting it out, you can also try resetting the file permissions for each share in the "advanced" tab of the share settings. If you click on the icon for any supported protocol on the share list, you'll see the advanced tab on the right.
FWIW, USB backup on a duo v1 is extremely slow. I painfully noticed that.
If you aren't far along, perhaps reformat the disk as NTFS (assuming you use windows), and start the backup again over the network (using freefilesync or teracopy). It should be 3-5x faster (about 3x if you use 100 mbit ethernet). That should also give you quicker information on the problem files if it were to fail. Teracopy can verify too, I don't know if freefilesync has that feature.
