Error Creating Backup Disk Image

enter a title. You can not post a blank message. Please type your message and try again. tommca Level 1 (0 points) Q:

Backup Disk Image Could Not Be Created Error Null

Time Machine won't back up onto Time Capsule I upgraded to the backup disk image could not be created error 1 Mountain Lion last week, and Time Machine won't back up to my Time Capsule. When it fails, the backup disk image could not be created error 22 I get the message:Time Machine couldn't complete the backup to "Tom's Time Capsule".The backup disk image "/Volumes/Data/TomsMac.sparsebundle" could not be created (error 60)I sometimes get the same message,

Creating A Backup Disk For Windows 8

but with "error 17"I also get the following error message popup (even though the disk is the one in my Time Capsule):The disk you inserted was not readable by this computer.The popup offers three choices: Initialize, Ignore, Eject. My local Apple Store Genius concluded that the problem must be with the Time Capsule, so I

Creating A Backup Disk For Windows 7

bought a new one. That didn't fix the problem.Time Machine Buddy messages:Starting manual backupAttempting to mount network destination URL: afp://Tom%20McAuliffe@Toms-Time-Capsule.local/DataMounted network destination at mount point: /Volumes/Data using URL: afp://Tom%20McAuliffe@Toms-Time-Capsule.local/DataCreating disk image /Volumes/Data/TomsMac.sparsebundleError 60 creating backup disk imageFailed to create disk image /Volumes/Data/TomsMac.sparsebundle, status: 60Backup failed with error: 20Failed to eject volume /Volumes/Data (FSVolumeRefNum: -108; status: -47; dissenting pid: 0)I did Repair Disk Permissions and Verify Disk and everything's OK.I erased the Time Capsule using AirPort Utility and did a hard reset on the Time Capsule.I did a re-install of Mountain Lion and that didn't fix anything.My MacBook Pro is accessing the Time Capsule wirelessly, as it always has.Help! Posted on Aug 5, 2012 9:59 AM I have this question too Close Q: Time Machine won't back up onto Time Capsule All replies Helpful answers Page 1 Next by Linc Davis, Linc Davis Aug 5, 2012 11:32 AM in response to tommca Level 10 (208,005 points) Applications Aug 5, 2012 11:32 AM in response to t

Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the creating a backup of a disk master boot record workings and policies of this site About Us Learn more about Stack

Time Machine Backup Failed Not Enough Space

Overflow the company Business Learn more about hiring developers or posting ads with us Ask Different Questions Tags time machine backup failed there isn't enough space Users Badges Unanswered Ask Question _ Ask Different is a question and answer site for power users of Apple hardware and software. Join them; it only takes a minute: Sign https://discussions.apple.com/thread/4179594?tstart=0 up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Time Machine fails backup to a time capsule's attached hard disk up vote 4 down vote favorite 1 I've been backing up my Lion OSX system using Time Machine to an second, external drive connected to http://apple.stackexchange.com/questions/27251/time-machine-fails-backup-to-a-time-capsules-attached-hard-disk a time capsule. It has worked but stopped working. The menu says "Faied" and the time machine prefs says: "The backup disk image “/Volumes/WD1-1/monster.sparsebundle” could not be created (error 22)" As far as I can tell the external hard disk is just fine. One really weird thing is that the external drive is called "WD1". However the Volume in the error message is specified as /Volumes/WD1-1. In fact in shall I see this: monster:~ pitosalas$ mount /dev/disk0s2 on / (hfs, local, journaled) devfs on /dev (devfs, local, nobrowse) /dev/disk1s2 on /Volumes/MonsterHD (hfs, local, journaled) map -hosts on /net (autofs, nosuid, automounted, nobrowse) map auto_home on /home (autofs, automounted, nobrowse) afp_0TSQUm1ubQ4400mmYF0Pyetl-1.2d000003 on /Volumes/WD1 (afpfs, nodev, nosuid, mounted by pitosalas) afp_0TSQUm1ubQ4400mmYF0Pyetl-1.2d00005c on /Volumes/WD1-1 (afpfs, nobrowse) and monster:~ pitosalas$ ls /Volumes/ BootHD MonsterHD WD1 WD1-1 (notice that MonsterHD and BootHD are both internal drives of the OSX box called monster) What is that second Volume WD1-1? It has different characteristics in $ mount listing none of which are meaningful to me. Could that be related to the problem? osx time-machine time-capsule share|i

United States Australia United Kingdom Japan Newsletters Forums Resource Library Tech Pro Free Trial Membership Membership My Profile People Subscriptions My stuff Preferences Send a message Log Out TechRepublic Search GO Topics: CXO Cloud Big Data Security http://www.techrepublic.com/blog/windows-and-office/fix-the-0x80780119-error-when-creating-a-system-image-in-windows-7-and-8/ Innovation Software Data Centers Networking Startups Tech & Work All Topics Sections: Photos Videos http://www.mactalk.com.au/19/96115-time-machine-error-17-45-a.html All Writers Newsletters Forums Resource Library Tech Pro Free Trial Editions: US United States Australia United Kingdom Japan Membership Membership My Profile People Subscriptions My stuff Preferences Send a message Log Out Microsoft Fix the 0x80780119 error when creating a System Image in Windows 7 and 8 There is not enough disk space to create the volume backup disk shadow copy of the storage location (0x80780119). Here is how to fix that. By Greg Shultz | in Windows and Office, August 9, 2013, 8:54 AM PST RSS Comments Facebook Linkedin Twitter More Email Print Reddit Delicious Digg Pinterest Stumbleupon Google Plus I have recently heard from a number of readers who have had difficulties running the System Image tool built into Windows 7 and Windows 8. These readers have been backup disk image encountering the error message shown in Figure A. Because of the length of the error message and the specific number given, the error message is commonly referred to as "There is not enough disk space to create the volume shadow copy of the storage location (0x80780119)." This article is also available as a TechRepublic Screenshot Gallery. Figure A This System Image error message is terribly confusing. As you can see, the full error message is very confusing and more often than not, the shortened version is interpreted as meaning that there is not enough free space on the destination drive. However, in actuality it indicates a problem with the source drive. After investigating the problem in detail, I have discovered that there are two common causes for the problem - one cause in Windows 7 and a different cause in Windows 8. I have also discovered that there are two separate solutions that will ultimately allow you to successfully create a system image. In this edition of the Windows Desktop Report, I will walk you through the steps I used to decipher the problem. Then, I'll examine each of these solutions and show you how to implement them. Breaking down the error message Let's begin with the details revealed in the er

Lost Password Forum Apple Stuff Apple General Time machine error 17 and 45 Results 1 to 7 of 7 Thread: Time machine error 17 and 45 LinkBack LinkBack URL About LinkBacks Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 26th December 2010,06:15 AM #1 KAIM Join Date Dec 2010 Posts 1 Time machine error 17 and 45 I am using an external hard disc - Seagate goFlex Home connected to Wifi Router. The first time machine setup worked fine and I got to backup my Mac probook just fine. After a month I got error messages saying backup failed. now I try to create a new backup by 1. selecting backup disc NONE and then 2 creating new backup -selecting the backup device and time machine tries to "make disc space available" - this is taking about 2 minutes. Then I get an error message: Time machine could not complete the backup. The backup disk image"/Volumes/GoFlexHome Public-1/KM's MacBook Pro.sparsebundle" could not be created (error 45). The error is displayed as error 17 as well. I have no problem accessing the network drive at all thanks Kai Reply With Quote 26th December 2010,08:23 AM #2 snark Join Date Apr 2005 Location Melbonia Posts 2,192 In my experience, backing up using Time Machine to a disk connected to your wireless router works perfectly well - until it doesn't. I had the same thing happen to me when I used a NAS drive. Unless you are using a Time Capsule, you really are better off connecting the disk directly to your machine. Live life with Blue Sun Reply With Quote 26th December 2010,06:15 PM #3 Brains Still stuck in 1984 Join Date Mar 2005 Location Inside your head Posts 6,557 Seconded. Because Time Machine uses a dual-ended checksum protocol, it is only compatible with a directly-connected USB/FW/SATA drive, a networked Time Caps