NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN 104 won't run backup & locks up after 6.4.1 update
I updated my ReadyNAS 104 from firmware 6.2.4 to 6.4.1 and a scheduled backup job could no longer run. The destination was a Seagate Go-Flex drive with USB 3.0 connected to the front USB port on the ...
dsnpevl wrote:
This leads me to believe that there is a problem in the backup procedure to USB that in some obscure cases (like e.g. a very deep dir structure with extremely long file names) will switch on the "read-only" flag on the USB drive.
That sounds like a reasonable hypothesis. There is of course a 260 character limit to the qualified filename size, and that can get in the way when copying over the network.
It does sound like a bug in the paragon software in the NAS though. If you can reproduce this (short of a full windows backup) you might want to PM skywalker.
StephenB wrote:
dsnpevl wrote:This leads me to believe that there is a problem in the backup procedure to USB that in some obscure cases (like e.g. a very deep dir structure with extremely long file names) will switch on the "read-only" flag on the USB drive.
That sounds like a reasonable hypothesis. There is of course a 260 character limit to the qualified filename size, and that can get in the way when copying over the network.
It does sound like a bug in the paragon software in the NAS though. If you can reproduce this (short of a full windows backup) you might want to PM skywalker.
Unfortuneatly, I no longer have that specific backup any more, so I cannot reproduce it. After spending several days trying to find the root cause, without success, I decided that the backup was not that important to keep and removed it from the NAS. That stopped the read-only message from occuring during backup to USB. I did document my findings in this thread: https://community.netgear.com/t5/Backing-up-to-your-ReadyNAS/After-backup-Destination-is-read-only/td-p/960340 . Hope this helps.
dsnpevl wrote ():If I remove a couple of files, the backup suddenly succeeds. But it doesn't matter which files are removed, as long as the total number of characters of all the filenames stays below 2112.
So I decided to keep all the files but reduce the number of characters in some filenames, so the total drops below the 2112 threshold.
Just adding 1 character to reach this threshold is the trigger point for the error "Destination is read-only" to occur. So 2112 produces the error, for 2111 characters the backup works.Didn't exceed the 260 filename size limit. But did anyone ever encounter a problem with the total characters of all the file names in a directory that centered around the 2111 / 2112 limit? That seemed to trigger the read-only bit to be set back in Jan 2015.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
