Time machine / cannot mount disk image / …
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
1) I've got time machine over time capsule.
2) It worked for two weeks.
3) Until the backup failed with "time machine cannot mount disk image"
4) I've checked the sparsebundle disk image with the apple disk utility. Result:
= Indeed, the disk image is corrupted (incorrect block count).
= But CANNOT be repaired due to 'invalid sibling link'
CONCLUSION: The time machine/ time capsule failed in its core function. To provide backup!
= (So much to: 'because apple produces hardware and software...')
SOLUTIONS ?!:
1) I cannot understand how other people with this problem put up with 'deleting the sparsebundle' as a solution?!
= It's not a solution, you are loosing all the different time-snapshots and you are without backup for a certain time!
2) Using 'disk warrior' (Cost: 100USD which apple most likely is not going to refund me!) does repair the disk image, although with (in my case) hundreds of 'overlapping' thus lost files...
My confidence in the apple time machine solution is completely lost.
QUESTION: Do time machine users with this problem have to buy 'disk warrior' for 100USD or is apple going to revise their beta-release of a backup 'solution'?!
15 replies
Sign in or join Beachball Help to reply.
- 0
graphics-guru ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I encountered the same message once. After power cycling my notebook and the TC incremental backups worked as expected. The TC has worked flawlessly with 3 Macs for the past month or so after.
Not sure that this will help but thought I would share my experience.
- 0
aleimgru ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
This is more an additional testimony, but maybe it will encourage someone (Apple?) to provide a solution if the list of 'corrupted backups' grow.
I have been using time machine / time capsule for over a month now (too short to pretend that a backup system is reliable) and it started to display the 'cannot mount' message yesterday.
Shutting down my MBP and the time capsule had a surprising transient effect: the message changed to: 'time machine failed to backup, the drive is read only'.
After another shutdown, the backup fails with remarkable stability i.e. I get the 'cannot mount drive' message.
It's interesting though to be able to browse the .sparsebundle folder (i.e. the drive image) in terminal.
I am considering turning back to a good old rsync, and agree with panzana's remark, reliability is suposed to be the core function of time machine/capsule.
- 0
Serge88 ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
You're not alone it just happen to me this morning, 'Cannot mount disk image'
It takes 4 days to do a complete backup, I can't believe I have to do it again...
Serge
- 0
resonantvox ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Same issue here... would someone from Apple please let us know what information to provide to troubleshoot this problem?
Thanks.
- 0
David Fry ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I had exactly the same symptoms as the original post and eventually only was able to solve the problem by purchasing Disk Warrior. $100 more than I expected to spend for Time Capsule. Apple needs to fix this.
- 0
D Herrick Design ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I just started to get this message as well and experiencing the same problems in the last week or so. I've been working with Apple products for 22 years and this is by far the worst excuse for easy reliable backup I have ever seen. Not only is it extremely slow, it also slows down any other process I'm involved in while the backup is processing. I can't believe any company would put out a backup device system as worthless as this. The only thing left for me to do is reformat my time capsule. What a waste of my time and money.
Dave
Message was edited by: D Herrick
- 0
steinbacher ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Since yesterday evening I have the same symptoms (only with german messages) with my MacBook and the Time Capsule (1TB). Couriously my MacMini does not have this problem.
The Time Capsule is running now for 1 month. Is this the average lifespan of such a "server grade" HD device from Apple 😟
What is the workaround? This tool you've described does not fully reactivates the Backup? isn't it?
Do we really have to delete the whole Sparsebundle and restart the initial backup every month?
Best, Andreas!
- 0
David Fry ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
after repairing my sparsebundle with Disk Warrior I was able to successfully resume regular backups without deleting any of the previous snapshots. So, I can go back in TM both before and since I repaired the disk. (did not require me to start over)
- 0
resonantvox ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
It's nice to know the sparsbundle can be repaired, but I don't want to spend $100 to repair functionality which should work on the Apple products I have already purchased.
- 0
John K. ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I agree, it completely ***** to have to shell out an extra $100, but Disk Warrior has saved my behind more than once- on my old PB G4 and on my MBP. Honestly, I think it's a utility no one should be without.
- 0
aleimgru ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Maybe the solution is to keep the hardware (i.e. the time capsule itself works fine for the time being) and use another backup software...
I used to make a quick shell script based on rsync to backup my data before the time capsule/machine era.
Anyone has another suggestion of software (freeware?) ?
I think I'd rather have a more reliable backup solution.
- 0
Kyle McG ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Woke up this morning to the same error message. Prior to this, TC was working fine. From the discussion boards, sounds like their may be multiple reasons for this. I called Apple Support and was told that the message appears after Time Machine is interrupted backing up. I'm guessing that I may have closed the computer and put it to sleep last night while it was in the middle of the hourly backup. Won't be doing that again!
For me, I was able to simply go into Airport Utility and rerun the setup for the TC. Then, went into Time Machine and chose the backup disc, entered password, and all was right with the Apple universe. When it started to back up, though, I got the Preparing to Backup message for about 45 minutes, which Support told me is normal as it has to go back and check all the files before finishing the backup. Still, one hour of preparing to back up is faster than 24 hours of redoing the entire back up process.
All's back to normal now. Good luck, All.
- 0
resonantvox ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
That didn't work for me. I then decided to go ahead and blow my whole sparsebundle away, and couldn't because of some write permissions issue. Even on the command line, I couldn't remove the "bands" directory within the sparsebundle.
Eventually, I disconnect, and re-connect to the time capsule, and am able to remove it through the command line in the sparsbundle directory:
rm -rf bands
This removed all the 40 some thousand files and I was able to start the back-up again, anew.
Really, if this is caused by the computer going to sleep, shutting it down prematurely, or what have you, Apple NEEDS to find a way for Time Machine to effectively recover from those situations.
Having to go back to rsync is laughable when part of the reason I purchased a mac was so I could stop being a $NIX hobbyist. I'm TRYING to be less technical at home. I want stuff to just work and it seems like the QA going on at Apple needs better project management or more time to get projects out the door that work from day one.
Message was edited by: resonantvox
- 0
macSEuser ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I may have a solution for some of you. I have a time capsule and my wife's IMac and my macbook pro are both backing up to it. Backed up fine 3/13 to two days ago, then my wife started starting getting an error message. But my Macbook was still backing up fine.
So I checked Apple's support on time capsule and found little of help. Checked time machine topics and found the following:Mac OS X 10.5: Time Machine backups are not visible
Last Modified on: November 08, 2007
Article: 306928
Issue or symptom
In the Mac OS X 10.5 Time Machine "time travel" window, past backups may not appear if your computer name includes certain characters.Products affected
Mac OS X 10.5 Leopard
Time Machine
Solution
Check your computer name in Sharing preferences. Make sure the computer name only includes ASCII characters from following set and is not blank (no matter which Mac OS X language version you are using):0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ
My wife's computer had an apostrophe in it's name. Mine does not.
Of interest, In January, backup failed to a western digital IBook from her Imac after 10 days. I returned it to the store and waited for a time capsule. Her's is backing up fine again. Mine is still fine. I'll let you know if things change, but Apple should have this rule for the name in big print on the Mac setup info! - 0
ManxStef ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I've encountered this a couple of times now, too, and it's hellishly annoying. I'm hoping Apple will make the Time Capsule's backup procedure more robust, because as it stands it's not good enough: most people will end up deleting the sparseimage to get their backups working, which is unacceptable. However, it
is possible to repair without any 3rd party utilities.Here's how to fix it:
Before we start, I *strongly recommend* connecting via gigabit ethernet rather that wirelessly as it'll be much, much faster. Also, you need to know what you're doing, if you're uncomfortable running any of the below procedures you'd be better off getting help from an Apple Genius.
Reboot the Time Capsule (either with Airport Utility, or by pulling the plug), as it always seems to have gone a little weird post-corrupted-sparseimage.
On your Mac(s), turn off Time Machine until you've finished this repair.
Connect to the Time Capsule's Airdisk and find the duff sparseimage. (If you can't do this, you may need to enable Disk Sharing using the Airport Utility first.)
Mount the sparseimage (by double-clicking). If it won't mount, repair it as much as possible using Disk Utility (which will repair it a little, then fail. If you run it again, all subsequent attempts get partway through and crash).
Once it's mounting, open up a Terminal. Type in 'diskutil list' and press return. It should produce something similar to this:
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID
partitionscheme *111.8 Gi disk0
1: EFI 200.0 Mi disk0s1
2: Apple_HFS Stef 111.5 Gi disk0s2
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: Apple
partitionscheme *463.8 Gi disk2
1: Apple
partitionmap 31.5 Ki disk2s1
2: Apple_HFSX Backup of Stef's Laptop 463.8 Gi disk2s2Notice how the Time Capsule is /dev/disk2 and the sparseimage is disk2s2
Right, we want to repair this sparseimage. From the Terminal, run 'fsck_hfs -r /dev/disk2s2' making sure to replace the disk2s2 part with whatever was listed when you typed the above step.
fsck will now run on the sparseimage and should repair it without crashing (unlike Disk Utility). It'll run through and repair, then run another pass to confirm the repair. This will take a good while, in the order of 2-3 hours using gigabit ethernet. If you must use wireless, run it overnight as it'll probably take 6 hours or more.
The output will be similar to this:
** /dev/rdisk2s2
** Checking Journaled HFS Plus volume.
** Detected a case-sensitive catalog.
** Checking Extents Overflow file.
** Checking Catalog file.
** Rebuilding Catalog B-tree.
** Rechecking volume.
** Checking Journaled HFS Plus volume.
** Detected a case-sensitive catalog.
** Checking Extents Overflow file.
** Checking Catalog file.
Incorrect number of thread records
(4, 30440)
Incorrect number of thread records
(4, 30440)
** Checking multi-linked files.
Incorrect number of file hard links
** Checking Catalog hierarchy.
Invalid directory item count
(It should be 40301 instead of 40302)
Missing thread record (id = 3043439)
Invalid directory item count
(It should be 0 instead of 1)
** Checking Extended Attributes file.
Incorrect number of Extended Attributes
(It should be 1797762 instead of 1797752)
Incorrect number of Access Control Lists
(It should be 1793798 instead of 1793788)
** Checking multi-linked directories.
Incorrect number of directory hard links
** Checking volume bitmap.
Volume Bit Map needs minor repair
** Checking volume information.
Invalid volume free block count
(It should be 99681536 instead of 99959337)
Volume Header needs minor repair
(2, 0)
** Repairing volume.
Previous ID in a hard link chain is incorrect (id = 1867367)
(It should be 0 instead of 1968526)
Invalid first link in hard link chain (id = 1296542)
(It should be 1867367 instead of 3043451)
Next ID in a hard link chain is incorrect (id = 1867367)
(It should be 1968526 instead of 0)
Previous ID in a hard link chain is incorrect (id = 1968526)
(It should be 1867367 instead of 2148720)
Next ID in a hard link chain is incorrect (id = 1968526)--- edit, removing hundreds of similar lines ---
Invalid first link in hard link chain (id = 3031389)
(It should be 3041877 instead of 3043456)
Indirect node 3031389 needs link count adjustment
(It should be 1 instead of 2)
** Rechecking volume.
** Checking Journaled HFS Plus volume.
** Detected a case-sensitive catalog.
** Checking Extents Overflow file.
** Checking Catalog file.
** Checking multi-linked files.
** Checking Catalog hierarchy.
** Checking Extended Attributes file.
** Checking multi-linked directories.
** Checking volume bitmap.
** Checking volume information.
** The volume Backup of Stef's Laptop was repaired successfully.You can now turn Time Machine back on on your Mac. Run a backup and it should now work again. Phew.
Hope that helps!