NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
After backup: Destination is read-only?
I'm working on implementing a proper backup procedure as most experts on this forum recommend. But when trying to backup a large amount of data, I keep getting this error message: Backup: Error bac...
Have been looking for a solution for this problem for a long time, but never managed to find the root cause.
In the end, I decided to remove the offending subdirectory that contained a file backup of a Windows system. This solved the problem with the backup procedure.
Have narrowed it down to my "Documents" share that is causing the problem. All the other shares backup without issues. Will try to narrow it down further in the coming period.
If I connect the disk to the PC and look for files and dirs with read-only attribute set, it finds nothing. Strange. The NAS just told me there is a read-only problem.
If I check for dirty bit, it tells me the disk is clean.
If I do a check disk on the drive, it tells me that no problems were found.
If I connect the disk to the PC and look for files and dirs with read-only attribute set, it finds nothing. Strange. The NAS just told me there is a read-only problem.
F:\>dir /A:R /R *.*
De volumenaam van station F is My Disk
Het volumenummer is XXXC-487P
Map van F:\
Het bestand is niet gevonden (= file not found)
If I check for dirty bit, it tells me the disk is clean.
F:\>fsutil dirty query f:
Volume - f: is schoon (= f: is NOT dirty)
If I do a check disk on the drive, it tells me that no problems were found.
We've been having these issues since the original OS6 and it's only on NAS drives were the USB drive is unplugged after backing up.
We have a numbe rof customers who rotate between two or more USB backups and even when you select 'Eject after backup' every few weeks this problem occurs.
Customers with only one drive that is permenantly connected have never had this issue, so it's a bug in the software or hardware.
In most cases, if you mount the drive in a PC and let the OS "repair" it, the drive becomes readable again.
Usually what is happening is that the dirty bit is being set on the drive.
Have been looking for a solution for this problem for a long time, but never managed to find the root cause.
In the end, I decided to remove the offending subdirectory that contained a file backup of a Windows system. This solved the problem with the backup procedure.
Sadly, I wish that was the case for our customers! We've now tried reformatting the backup drives as NTFS and HFS+ but the problem always comes back at some point.
Netgear still have problems using USB external drives and backup, which after nearly 2 years, needs fixing.
The configuration is cumbersome, but I managed to configure backup of volume:data to USB right USB to dir /data.
Plans are for me to build a backup scenario with 2 external drives around that.
I had similar issues trying to back up a shared network drive to another netwrok drive that only I could see. After the initial backup it would ofcourse only update the changes. After a recent update to the newest software for the shared NAS the back up function stopped working.
"destination is read-only or files/folders could not be created. Check if these files or folders meet the destination file system limitation."
The destination is not read only. I unmounted the drives and hooked them up directly to my PC and scanned the file system with that.....blah blah blah. I tried a ton of different things before I finally just renamed the old back up folder and created a new empty one. The next backup then repopulated this new folder and everything works fine. Subsequent back ups have ran fine as well. I don't know if anyone else will find this helpful but it worked for me.
On a side note, I would be curious to hear an explanation for why this problem even occurred. Why would an update cause the system to erroneously identify a file as read only?
The status info stored on the drive includes a "dirty' bit, which usually ends up set if if the disk is not properly dismounted - esp. if a file copy was in progress when that was done.
If it is set (for whatever reason), the volume is mounted read-only by the NAS. On Windows, it results in a scan/repair prompt.
Clearing the dirty bit generally is only done as part of a scan/repair process that ensures the NTFS structures are ok. The NAS doesn't have the ability to do that, so you need to connect the drive to a system that can do it.
Your situation with the backup might have had a different cause of course.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
