PDA

View Full Version : Unable to eject sparse image on NAS drive


michelh
08-12-2010, 11:33 PM
I am using SuperDuper to backup to a sparse image on a NAS drive. When the backup process does not complete, so I redo the backup.

Sometimes I am unable to eject the sparse image and i get this message: "The volume could be be ejected because it is currently in use." Even when I close all apps and data files, I still can't eject the sparse image and nor the NAS drive. I only have this problem when I use SuperDuper.

I have no problems directly opening the sparse image from the desktop.

The SuperDuper log reads:
| 12:19:39 PM | Info | ......COMMAND => Setting ownership and access modes for '/Volumes/mbhbackup/Macintosh backup NAS.sparseimage'
| 12:19:39 PM | Info | ......COMMAND => Mounting Macintosh backup NAS
| 12:19:40 PM | Info | /dev/disk4 GUID_partition_scheme
| 12:19:40 PM | Info | /dev/disk4s1 EFI
| 12:19:40 PM | Info | /dev/disk4s2 Apple_HFS /Volumes/Macintosh backup NAS 2
| 12:19:40 PM | Info | ......COMMAND => Mounting Macintosh backup NAS
| 12:19:40 PM | Info | Waiting for Macintosh backup NAS to mount.
| 12:19:42 PM | Info | Waiting for Macintosh backup NAS to mount.
| 12:19:44 PM | Info | Waiting for Macintosh backup NAS to mount.
| 12:19:46 PM | Info | Waiting for Macintosh backup NAS to mount.
| 12:19:48 PM | Info | Waiting for Macintosh backup NAS to mount.
| 12:19:48 PM | Error | Failed to mount Macintosh backup NAS

dnanian
08-13-2010, 08:29 AM
From what I can tell, you may have a bunch of bad mount points in /Volumes. Use Finder's "Go To Folder" command to open /Volumes. In there, you'll find one or more folders (not aliases/symlink) with the name of the image. Delete those and empty your trash, then restart your Mac.

The backup "not completing" seems like it's because your network connection is failing, or your NAS is dropping the connection/failing.

As far as "can't eject" goes - this may be because Spotlight is indexing the image, or because an AntiVirus program has active files up there. We certainly don't have active files when we're not running...

michelh
08-18-2010, 11:11 AM
Thanks for your reply. I did as you suggested. Subsequently I used SD to backup the computer to an external HD and to a sparse image on a Synology NAS drive. The backup worked for both, but the sparse image did not unmount with the message that the disk is in use and cannot be ejected. The only way to unmount the sparse image and NAS drive was to restart the Mac.

This unmounting problem only happens when using SD. There are no problems in normal use of files on the NAS drive or in opening the sparse images on the NAS drive. I am not sure if this is only a problem occurring in backing up the computer. I use SD with other volumes without issue but then these are less than 5GB.

The Synology wiki community could not give any suggestions if the NAS drive is at fault. There are threads in the Apple discussion forums highlighting problems with Mac disconnecting external servers but no solutions seemed to have been found and Apple is being blamed.

Could you advise further please? Would using sparse bundles be better?

dnanian
08-18-2010, 12:52 PM
I can only suggest that it's because of what I mentioned above. You might find using lsof (list open files), filtered by the volume name, will help you determine what files are actually active and preventing eject...