Backup Error : Destination cannot be mounted on the system. ReadyNas 102
I had an issue with the backup jobs not working. I checked both backup drives. I run seperate backup jobs on each drive. They are Toshiba 2Tb 2.5" HDD's. One needed repairing, so I connected it to my computer and allowed Windows to repair it. I then reconnected it to the Nas (Bottom rear USB). As far as I can tell one backup was completed, then I received the message above.
The drives are using their original NTFS formatting. I have read that it is best to use a particular file system. I do not want to use a system that I cannot read directly from any computer. I want to be able to use these backup drives as portable drives for when I am away from home.
When I reconnected this drive I set the options to disconnect after the backup job is complete. Prior to this, that option was not set.
Re: Backup Error : Destination cannot be mounted on the system. ReadyNas 102
If the filesystem isn't unmounted safely then it can lead to the filesystem being marked dirty and going read-only.
Connecting it up to your PC and repairing it can be a good way to go.
If that doesn't resolve it (i.e. problem comes back quickly despite safely unmounting the USB disk) then you could try formatting the disk again and seeing if things work better with a clean filesystem.
If that still doesn't resolve it perhaps check the USB disk using vendor tools. If the disk is failing that could explain the problem too.
Re: Backup Error : Destination cannot be mounted on the system. ReadyNas 102
"If the filesystem isn't unmounted safely then it can lead to the filesystem being marked dirty and going read-only."
So is this the Nas causing this problem? Interesting since I have 3 major issues with this Nas now.
I cannot turn it off nicely. I keep pushing the button and nothing happens except the LED flashes for a while. I had to pull the plug. The admin page was not loading the details. Just showing a progress indicator for 10 mins until pulling the plug. Speaking of which, I plugged in the 2nd USB HDD last night. It worked perfectly on my notebook. I setup a backup job and started a backup. If I had not pulled the Nas plug it would still be going, well over 12 hrs later. How long does it take to do a backup on less than 400Gb of data? I have deleted both backup jobs.
"Connecting it up to your PC and repairing it can be a good way to go."
Is there another way? I am not aware of one.
"If that doesn't resolve it (i.e. problem comes back quickly despite safely unmounting the USB disk) then you could try formatting the disk again and seeing if things work better with a clean filesystem."
These disks were both new last August. The only thing they have been used for is Nas backup disks and as the Nas keeps failing these, not very many. If there is a problem with the format then it was caused by the Nas. We had a lengthy power failure a while ago. The relevant log details:
Thu Jan 7 2016 17:12:27: System: ReadyNASOS service or process was restarted. Thu Jan 7 2016 16:40:21: System: UPS UPS () battery is low. System will shut down soon. Thu Jan 7 2016 16:21:53: System: UPS UPS () is on battery power. Thu Jan 7 2016 13:47:42: Backup: Saved backup job Backup1.
As the UPS did its job properly as far as I can tell, this power failure did not seem to cause any problems. There was a successful backup completed the next day as well.
The Nas has finally shut down so I pulled both USB drives. The one re the thread title did not show any errors. Windows did a full scan. The other drive had errors which were fixed.
I plan on copying the entire contents of the Nas to another external HDD for safety if I can. The 3rd issue is with very slow access. I have already spent more time on these problems than I think this Nas is worth. I am considering getting another Nas. Not Netgear of course.
Re: Backup Error : Destination cannot be mounted on the system. ReadyNas 102
"If the filesystem isn't unmounted safely that would typically be caused by user error."
I I unplugged the Nas, granted. But if the Nas has been trying to do a simple backup for over 12hrs, the admin page is flakey, keeps restarting and when it starts won't give any info except for a busy icon. When it refuses to turn off by the usual methods outlined in the manual (a situation that has existed since I first got it) you have got to accept that there is no other option if one wishes to get somewhere.
On the other hand :
Mon Jan 11 2016 12:22:29 : System: External storage 'TOSHIBA_MQ01UBB200' might not have been safely ejected after last use. This device will be read-only. Plug it into its native operating system and repair it before it will be writeable. Mon Jan 11 2016 12:19:24 : System: External storage device connected.
Cannot blame the user for that one.
This all tells me that there is some serious problems here and I am getting nowhere and as I said I have already spent over my allocation of reasonable time to sort this problem out. A sensible person recognises that there is a point where you should cut your loses and go elsewhere.
I have yet to see any indication that you know anything about the problem. This is not a dig at you, just a comment that there are too many problems to deal with in this manner.
"Repairing the disk using your PC is the way to go."
Quote from my last post
""Connecting it up to your PC and repairing it can be a good way to go."
Is there another way? I am not aware of one."
However I have to say that this is not the way to go. Look at this from my position.
I connect the USB HDD. I try to do a backup. It doesn't work. I remove the USB HDD and repair it.
Repeat previous step.
The way to go is to have the Nas do automatic backups without having to do the USB HDD 2 step constantly.
"Which services and apps are you running?" SMB, AFP, ReadyDLNA, Rscync, UPnP, HTTP and HTTPS. "No Application Is Running"
I I unplugged the Nas, granted. But if the Nas has been trying to do a simple backup for over 12hrs, the admin page is flakey, keeps restarting and when it starts won't give any info except for a busy icon. When it refuses to turn off by the usual methods outlined in the manual (a situation that has existed since I first got it) you have got to accept that there is no other option if one wishes to get somewhere.
Then you have to accept the consequences of doing that. Unsafely unmounting it the filesystem may makr itself as dirty as a precaution.
USB Backups may take quite some time and USB does use a lot of resources. Particularly on a cost effective device such as the 100 series you can find that low priority things like the admin page may not be accessible whilst the device is under high load. So it's possible that the backup was progressing well and you just needed to be more patient.
Mon Jan 11 2016 12:22:29 : System: External storage 'TOSHIBA_MQ01UBB200' might not have been safely ejected after last use. This device will be read-only. Plug it into its native operating system and repair it before it will be writeable. Mon Jan 11 2016 12:19:24 : System: External storage device connected.
Cannot blame the user for that one.
Safely ejecting the disk is something that should be done. If it is not done for whatever reason then there are consequences and we alert you about that.
This all tells me that there is some serious problems here and I am getting nowhere and as I said I have already spent over my allocation of reasonable time to sort this problem out. A sensible person recognises that there is a point where you should cut your loses and go elsewhere.
Well you'be provided some information on the problem you are experiencing, but more details would be required to know what's going on.
Gnewendlo wrote:
I have yet to see any indication that you know anything about the problem. This is not a dig at you, just a comment that there are too many problems to deal with in this manner.
The advice on the community, certainly at first when responding to a thread tends to be general in nature. Every system is different and to get down into diagnosing a problem in greater detail we would need things such as logs (see the Sending Logs link in my sig). Preferably download the logs ASAP so that the relevant entries are hopefully near the end of the relevant log files. Some logs are timestamped so mentioning the time of events can be helpful too.
Gnewendlo wrote:
I connect the USB HDD. I try to do a backup. It doesn't work. I remove the USB HDD and repair it.
Repeat previous step.
The way to go is to have the Nas do automatic backups without having to do the USB HDD 2 step constantly.
"Which services and apps are you running?" SMB, AFP, ReadyDLNA, Rscync, UPnP, HTTP and HTTPS. "No Application Is Running"
"Which firmware are you running?" 6.4.2-T59
I agree that backups should work and that you shouldn't need to verify the USB disk constantly, but to diagnose why you are having problems would require more information than you had provided.
Furthermore you started this thread only yesterday. If you had opened a support case for a problem like this it would not have been resolved yet. Some problems can be resolved simply by providing general advice. Others may require more information as to what is going on.
Re: Backup Error : Destination cannot be mounted on the system. ReadyNas 102
According to the smallnetbuilder review (back in 2013):
Backup to a directly connected USB-2 NTFS formatted drive should run at about 9 MB/s - so it ought to take about 10 hours to back up 310 GB.
A directly connected USB-3 drive should run at about 25 MB/s - so it ought to take about 4 hours.
However, that does assume that the NAS is not doing other things, and if you are still struggling with 6.4.x performance issues you might well be seeing much slower speeds.
Also, it is best to use a USB drive that is not powered from the USB port itself.
Re: Backup Error : Destination cannot be mounted on the system. ReadyNas 102
Last night I connected one of my older 3.5" 1Tb USB drives to the Nas, after checking it for errors. At 11:30 pm a backup job was created and started straight away. It is still "In Progress" at 8:25 am. 9 hours.
I will wait and see what happens.
It appears that the Nas has taken an aversion to the 2.5" disks for some unknown reason.
From 16/09/2012 to 17/12/2012 there were 37 backup jobs successfully completed in sequence with the only failure being caused by the USB drive being disconnected at the scheduled time. This drive was reconnected and the backups continued normally.
On the 20/12/2012 the System Firmware was upgraded to 6.4.1.
And the next log entries from then are:
Sun Dec 20 2015 11:45:29 System: External storage 'TOSHIBA_MQ01UBB200' might not have been safely ejected after last use. This device will be read-only. Plug it into its native operating system and repair it before it will be writeable. Sun Dec 20 2015 11:45:18 System: External storage device connected. Sun Dec 20 2015 11:45:01 System: External storage 'TOSHIBA_MQ01UBB200' might not have been safely ejected after last use. This device will be read-only. Plug it into its native operating system and repair it before it will be writeable. Sun Dec 20 2015 11:43:44 System: External storage device connected.
There is however this entry:
Sat Dec 19 2015 0:05:14 Backup: Error backup job Backup2: destination is read-only or files/folders could not be created, please check if these files/folders meet the destination filesystem limitation.
This was the day before the OS upgrade. At this point I was not aware of any problems with the Nas and so did not touch it.
Re: Backup Error : Destination cannot be mounted on the system. ReadyNas 102
"Copying over gigabit ethernet is faster than copying to a directly attached USB 3 drive."
So Nas --- Ethernet (Gig) --- Notebook --- USB HDD is faster than Nas --- USB HDD? The same HDD.
"Can you access it from web ui? Is it read-only?"
Yes to both this morning.
Last night I connected one of my older 1Gig 3.5" USB3 drives to the Nas and set up a backup job starting at 11:30pm. It started normally. It is still going, 10.5 hrs later.
Re: Backup Error : Destination cannot be mounted on the system. ReadyNas 102
The backup finished after 19 hrs. I ran another about an hour later. Assuming the previous one was a full backup I wanted to see how long a incremental one would take.
It failed.
"Tue Jan 12 2016 19:33:53 Backup: Error backup job Backup2: destination cannot be mounted on the system".
The backup finished after 19 hrs. I ran another about an hour later. Assuming the previous one was a full backup I wanted to see how long a incremental one would take.
It failed.
"Tue Jan 12 2016 19:33:53 Backup: Error backup job Backup2: destination cannot be mounted on the system".
Just wanting to confirm: Is this re-running the same backup job that had just finished? Also, the USB drive had remained connected to the RN102 throughout the process?
Yes, but only recently. This has been discussed in this thread.
Where? I can't find any reference to that in this thread.
"Destination cannot be mounted on the system" is the exact error that will occur if you try to start a backup job to a USB drive that has been ejected.
Re: Backup Error : Destination cannot be mounted on the system. ReadyNas 102
Ok.
What is "Auto eject device when the job is done" used for? I read that it was to turn off the disk when not in use, post backup, which is why I selected it. Was this wrong?
I cannot find any reference to it in the Instruction manual I have. (OS 6.2)
How do I eject the USB drives safely.
I have disconnected/reconnected one of the drives. I deselected "Auto eject device when the job is done". I ran backup which worked normally and only took a few minutes.
Re: Backup Error : Destination cannot be mounted on the system. ReadyNas 102
The eject function is to prepare the disk from removal when you are going to physically unplug the drive from the system -- like Windows' "Safely Remove" function.
