NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
fvbackup crashes, stalling further backup, disables graceful shutdown
ReadyNAS 314 with Firmware 6.9.5 Hotfix 1 I have a problem with backup jobs crashing and freezing ReadyNas from time to time. These jobs back up various ReadyNas shares to a portable USB drive. ...
I believe the hightlighed error is linked to the USB drive.
I'd test the USB drive in a PC. You can use vendor tools (seatools or lifeguard) and/or just try to copy files to and from the drive. Personally I'd do the full erase test in addition to the extended non-destructive test.
Thank you for your response. That was my first hunch too. I might have forgotten to note in my original posting that I have been getting this for more than a error, sporadically.
So during a year of troubleshooting, I have tried out the following already, on the USB disk:
(1) As ReadyNAS renders the USB disk readonly, I would connect it to a windows PC and simply clear the code, reconnect it back to ReadyNAS. After that it will work fine for a while.
(2) Completely erase and reformat the USB disk using a Windows PC and then connect it back to ReadyNAS. After that it will work fine for a while.
(3) Replace the USB disk with a brand new one of a different brand. After that it will work fine for a while.
As I get the same symptoms back irrespective of what I do, I tend to think that it is not related to the USB disk.
Moreover, I have been running the same backup's for several years now on the same kind of USB disks. I started getting it only about a year back; after one ReadyNAS OS update. I am not sure which one.
If I may ask what exactly makes you think that the error is related to the USB drive? Is it because of the reference to ufsd?
debumitra wrote:
If I may ask what exactly makes you think that the error is related to the USB drive? Is it because of the reference to ufsd?
Yes. Paragon's driver set is called "Universal File System Drivers", and they use ufsd in a variety of places. https://download.paragon-software.com/doc/Paragon_NTFS-HFS_for_Linux_9.5_User_Manual.pdf
debumitra wrote:
(1) As ReadyNAS renders the USB disk readonly, I would connect it to a windows PC and simply clear the code, reconnect it back to ReadyNAS. After that it will work fine for a while.
This might be a result of an improper ejection (which of course is a given if the NAS crashes with the drive mounted).
debumitra wrote:(2) Completely erase and reformat the USB disk using a Windows PC and then connect it back to ReadyNAS. After that it will work fine for a while.
I would definitely test it then.
I am sorry, but I do not understand the diagnosis.
I have tried a brand new USB drive - I get the same error on that too. Please note, the error doesn't happen frequently; only once in 2-3 months.
Not just that, I have other backup jobs backing up other shares on the same USB disk. Those never fail. How can it be a disk issue if it shows up for only one backup job?
This makes me think that the issue is not with the USB disk per se.
Thanks.
debumitra wrote:
I am sorry, but I do not understand the diagnosis.
To be clear - it's at most a hypothesis that needs to be confirmed. If it were my own disk, I'd begin by running both the long non-destructive test and the full write-zeros/erase disk test using the vendor tools (WD's lifeguard program or Seagate's Seatools).
If you aren't running the maintenance tasks (on the volume settings wheel) regularly, you might also run the disk test for the internal drives there. The scrub task is also a good diagnostic (as it either reads or writes every sector in the data volume). Though I'd hesitate to do a scrub before confirming that I had a solid backup.
debumitra wrote:
Not just that, I have other backup jobs backing up other shares on the same USB disk. Those never fail. How can it be a disk issue if it shows up for only one backup job?
This makes me think that the issue is not with the USB disk per se.
You could be correct - though the error definitely says the paragon drivers are crashing.
I have certainly had USB drives that fail in a particular range of sectors. It is conceivable that the particular share just happens to wind up on a marginal area of the disk. If the share has more churn (files changing) then it might also be the case that the specific share requires more I/O than the others.
FWIW, I have had at least one case where I found that many old files that hadn't changed since the initial backup couldn't be restored when I needed them - the copies failed when I restored from the USB drive. Personally I make sure I have at least two backups - in part to reduce the possibility that the backup hasn't silently failed.
BTW, another strategy here is to connect the drive to a Windows PC and back up the NAS over ethernet. There are free tools out there that can do that on schedule (and I think some might also be able to verify). Then you could see if the problem moves to the PC or stays with the NAS.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
