Comments on: Fix Time Machine Sparsebundle Network Backup Errors

By: Ryan

Ryan — Sat, 21 Jan 2012 02:24:44 +0000

Got me up and running again. Thanks!

By: Garth

Garth — Thu, 12 Jan 2012 19:54:36 +0000

Desmond – it looks like the volume is not being mounted with read/write permissions – check to make sure you entered all the commands exactly.

By: Olivier Roux

Olivier Roux — Thu, 05 Jan 2012 23:44:29 +0000

With a mix of your post and this one http://krypted.com/mac-os-x/mass-deploying-time-machine/, I managed to get my Time Capsule backup back on tracks.
Thanks a lot and thank the web!

By: Desmond Foulger

Desmond Foulger — Wed, 04 Jan 2012 20:45:41 +0000

Thanks for this informative article. I am part way through but I get the following message in Terminal. How should I now proceed please? Happy New Year BTW from New Zealand

sh-3.2# fsck_hfs -drfy /dev/disk7s2
Unable to open block device /dev/disk7s2: Permission deniedjournal_replay(/dev/disk7s2) returned 13
** /dev/rdisk7s2 (NO WRITE)
Using cacheBlockSize=32K cacheTotalBlock=49152 cacheSize=1572864K.
Executing fsck_hfs (version diskdev_cmds-540.1~34).
Non-empty journal: start = 136646656, end = 136941568
Journal need to be replayed but volume is read-only
** Checking Journaled HFS Plus volume.
** Detected a case-sensitive volume.
The volume name is iMac TimeMachine Backup
** Checking extents overflow file.
** Checking catalog file.
** The volume iMac TimeMachine Backup was found corrupt and needs to be repaired.
volume type is pure HFS+
primary MDB is at block 0 0×00
alternate MDB is at block 0 0×00
primary VHB is at block 2 0×02
alternate VHB is at block 3906357278 0xe8d6481e
sector size = 512 0×200
VolumeObject flags = 0×07
total sectors for volume = 3906357280 0xe8d64820
total sectors for embedded volume = 0 0×00

By: juan

juan — Mon, 12 Dec 2011 09:54:17 +0000

Thaks Garth.
I solved the problem, but I think my volume is dead because the sfck says:
** The volume Copias de Time Machine could not be verified completely.
volume check failed with error 7
volume type is pure HFS+
primary MDB is at block 0 0×00
alternate MDB is at block 0 0×00
primary VHB is at block 2 0×02
alternate VHB is at block 1952828350 0x7465cbbe
sector size = 512 0×200
VolumeObject flags = 0×07
total sectors for volume = 1952828352 0x7465cbc0
total sectors for embedded volume = 0 0×00

By: Garth

Garth — Sat, 10 Dec 2011 01:04:31 +0000

Teejay – is this disk connected normally via USB to an Airport Extreme? I have another post (similar but different) for repairs in that case.

By: Garth

Garth — Sat, 10 Dec 2011 01:03:26 +0000

Juan – the (NO WRITE) message means (I think) that you did not copy the initial mounting message correctly – you need to mount the drive via the command line not by double clicking it.

By: juan

juan — Thu, 08 Dec 2011 00:56:42 +0000

Hi, and thanks for this post.

I have a problem:
after run the fsck_hfs -drfy /dev/disk2s2 comand the terminal says:
iMac:~ root# fsck_hfs -drfy /dev/disk2s2
Unable to open block device /dev/disk2s2: Permission deniedjournal_replay(/dev/disk2s2) returned 13
** /dev/rdisk2s2 (NO WRITE)
Using cacheBlockSize=32K cacheTotalBlock=16384 cacheSize=524288K.
Executing fsck_hfs (version diskdev_cmds-540.1~25).
Journal is empty
** Checking Journaled HFS Plus volume.
** Detected a case-sensitive volume.
The volume name is Copias de Time Machine
** Checking extents overflow file.
** Checking catalog file.
** The volume Copias de Time Machine was found corrupt and needs to be repaired.
volume type is pure HFS+
primary MDB is at block 0 0×00
alternate MDB is at block 0 0×00
primary VHB is at block 2 0×02
alternate VHB is at block 1952828350 0x7465cbbe
sector size = 512 0×200
VolumeObject flags = 0×07
total sectors for volume = 1952828352 0x7465cbc0
total sectors for embedded volume = 0 0×00
iMac:~ root#

Do you have any idea to recover my TM volume or all is lost?
Thanks a lot from Spain.
Juan

By: Teejay87

Teejay87 — Wed, 30 Nov 2011 22:30:03 +0000

Unfortunately, this din’t word for me.

After running 2 times the fsck, i got a “could not be repaired” message.
Further fsck had no luck.

Got to scratch my backup, again…. MyBook World with Lion, this happens every 2 weeks…
No solutions from Western Digital.

Just burnt 200 €.

By: Phil Ryan

Phil Ryan — Mon, 31 Oct 2011 21:48:33 +0000

Garth, great effort putting this together. I’ve just gone through your procedure successfully on a Lion Macbook Pro, against a Time Machine backup on a QNAP-410 NAS. I had recently had a similar problem on my wife’s Snow Leopard machine, then in the middle of starting a new TM backup, that machine crashed and so we had no backup to recover from.

It might be worth making it clearer that the two things that should be done to the ~.plist file within the sparsebundle will likely need to be done in almost all cases (as I read the instructions above, it looked like they were only related to the sparsebundle-being-locked case).