View Full Version : Failed to Mount Image (hdiutil: operation not supported)

11-17-2009, 11:38 PM
Running 2.6.2 on 10.6.1, attempting to backup all files to a sparse bundle on a NAS volume that has wide open read/write permissions. In SD I'm getting "Failed to Mount Daniel_Macbook_Image." The log shows the following:

| 10:28:14 PM | Info | SuperDuper!, 2.6.2 (87), path: /Applications/SuperDuper!.app, Mac OS 10.6.1 build 10B504 (i386)
| 10:28:14 PM | Info | Started on Tue, Nov 17, 2009 at 10:28 PM
| 10:28:14 PM | Info | Source Volume: Macintosh HD, mount: /, device: /dev/disk0s2, media: TOSHIBA MK2553GSX, interconnect: Internal SATA, file system: "Journaled HFS+", OS: 10.6.1 (10B504), capacity: 249.72 GB, used: 182.49 GB, directories: 209601, files: 714320, ejectable: NO, ACLs: Enabled
| 10:28:14 PM | Info | Target Image: /Volumes/Volume_1/Daniel/Image/Daniel_MacBook_Image.sparsebundle, name: Daniel_MacBook_Image
| 10:28:14 PM | Info | Copy Mode : Smart Update
| 10:28:14 PM | Info | Copy Script : Backup - all files.dset
| 10:28:14 PM | Info | Transcript : BuildTranscript.plist
| 10:28:15 PM | Info | PHASE: 1. Prepare to Copy Files
| 10:28:15 PM | Info | ...ACTION: Preparing Macintosh HD
| 10:28:15 PM | Info | ......COMMAND => Verifying the integrity of volinfo.database
| 10:28:15 PM | Info | volinfo.database OK
| 10:28:15 PM | Info | ......COMMAND => Enabling permissions on Macintosh HD
| 10:28:15 PM | Info | Refreshing Disk Arbitration ...
| 10:28:15 PM | Info | ......COMMAND => Verifying that permissions are enabled for Macintosh HD
| 10:28:15 PM | Info | Permissions on '/' are enabled.
| 10:28:15 PM | Info | ...ACTION: Mounting Daniel_MacBook_Image
| 10:28:15 PM | Info | ......COMMAND => Preparing Daniel_MacBook_Image
| 10:29:05 PM | Info | hdiutil: create failed - Operation not supported
| 10:29:05 PM | Error | ****FAILED****: result=256 errno=22 (Unknown error: 0)

Can someone give me the full hdiutil command for this so I can run it in a terminal session to get more error data? I think if I do that it will tell me more information about why the create failed.

BTW I've tried the same operation with an external USB drive and it got past the creating image stage.

Kind regards,


11-17-2009, 11:40 PM
I bet it doesn't work with Disk Utility either... try using a sparse image instead. Many NAS devices don't seem to support sparse bundles.

11-17-2009, 11:57 PM
A thread from 2006 helped me: http://www.shirt-pocket.com/forums/showthread.php?t=1797

I created the sparse bundle on an external USB drive using Disk Utility. I then copied that over to the NAS and was able to then select that image in SuperDuper.

What are the differences between a sparse image and a sparse bundle? My goal is to just have a bootable copy of my entire hard drive. I'd like it to mirror my hard drive so deleted files are also deleted in the image. A sparse bundle does this, no?

Thanks for your quick reply. Hopefully this thread will help when people search for this error in the future.


11-18-2009, 12:01 AM
They both do that... but an image/bundle is not directly bootable. If you want a bootable backup, you need to write directly to a properly set up FireWire or USB (Intel-only) drive.

11-18-2009, 12:10 AM
Yes, but I can expand/image this sparse bundle to a USB drive and boot from it, right?

11-18-2009, 12:23 AM
Yes... but why not just back up to the USB drive in the first place?

11-18-2009, 01:12 AM
A few reasons I suppose:

-I'm backing up a laptop and I don't want to tether a USB drive to it every night.
-SuperDuper is also backing up my wife's laptop to the NAS. With USB I would have to wait for mine to finish and backup hers or buy a second USB drive.
-The NAS I'm using is RAID1 so I'm getting instant protection against hard disk failure.
-I use the 1TB USB drive as an off-site backup of the NAS. Every month I copy NAS to USB drive and drop it off at the office.

11-18-2009, 08:53 AM
Up to you, flashkube. My general recommendation is that network backups are great as secondary backups, or you can use them as primaries as long as your recognize that they're inherently less reliable, and much less convenient when it comes time to restore.