PDA

View Full Version : Time Machine volume on NAS won't mount



snark
2nd April 2010, 01:10 PM
I have been using Time Machine to back up my MBP over wireless to a share on my NAS. As of today, I'm unable to back up, or enter Time Machine - either over wireless or wired ethernet.

My set up is a follows:
1. I have set up a share on my Lacie Ethernet Disk mini , which I mount using smb://ip_address/sharename. I can successfully mount this using either smp or afp.

2. On the share, I have set up a sparse disk image called computername_ethernetmacaddress.sparsebundle. I can see this using Disk Utility.

3. Inside the disk image is a volume called Tardis, which is the Time Machine (obviously). I am having problems mounting this.

I've tried to repair the disk, but Disk Utility reports that it is unable to repair the disk. I've included some logs below.

2010-04-02 13:16:14 +1100: Verify and Repair volume “disk1s2”
2010-04-02 13:16:14 +1100: Starting repair tool:
2010-04-02 13:16:14 +1100: Checking Journaled HFS Plus volume.
2010-04-02 13:16:14 +1100: Checking extents overflow file.
2010-04-02 13:16:15 +1100: Checking catalog file.
2010-04-02 13:16:37 +1100: Incorrect block count for file live.2.shadowIndexGroups
2010-04-02 13:16:37 +1100: (It should be 18 instead of 0)
2010-04-02 13:16:37 +1100: Incorrect block count for file live.3.indexArrays
2010-04-02 13:16:37 +1100: (It should be 2048 instead of 0)
2010-04-02 13:16:37 +1100: Incorrect block count for file live.3.indexCompactDirectory
2010-04-02 13:16:37 +1100: (It should be 2 instead of 0)
2010-04-02 13:17:59 +1100: Overlapped node allocation
2010-04-02 13:17:59 +1100: Rebuilding catalog B-tree.
2010-04-02 13:22:13 +1100: Invalid node structure
2010-04-02 13:22:45 +1100: Invalid node structure
2010-04-02 13:22:45 +1100: Invalid node structure
2010-04-02 13:22:46 +1100: The volume Tardis could not be repaired.
2010-04-02 13:23:02 +1100: Stopped by user
2010-04-02 13:23:02 +1100: Volume repair complete.
2010-04-02 13:23:02 +1100: Updating boot support partitions for the volume as required.
2010-04-02 13:23:02 +1100: Repair tool completed:
2010-04-02 13:23:02 +1100:

Is there any hope of recovering this volume? If I copy the sparse image to another physical disk (it's about 145 GB), would it be usable? ie. would I be able to re-point Time Machine to it?

<edit> copying disk image to a spare USB HD now - Finder says "only" 10 hours to go :frustrating:

snark
2nd April 2010, 07:17 PM
A ray of hope maybe. After copying the sparse image to a USB drive, it looks like I can access all the files that have been backed up for the past 6 months. They are showing up under the file path:
backup.backupdb\<computername>\yyyy-mm-dd-hhmmss\<osxvolumename>\..

Now, if I tell Time Machine to start using this drive as the new TM destination, will I be able to merge all the existing backups into the "new" Time Machine?

Brains
3rd April 2010, 09:49 AM
Your chances are slim bordering on nil because of the overly-complex way in which it stores files and references them by hardlinks -- when the directory goes, the archive essentially becomes useless. The fact you were doing it over wireless compounds the problem. If you've upgraded to 10.6.3, you're quite likely a victim of the change in checksum protocol.

I've said it here many many times -- Time Machine is not compatible with a generic NAS or other network storage unless it is a Time Capsule or another Mac.

snark
3rd April 2010, 10:09 AM
If you've upgraded to 10.6.3, you're quite likely a victim of the change in checksum protocol.


Hmmm, possibly, although I've done at least two backups since upgrading to 10.6.3. What exactly is the "change in checksum protocol"?

I'm quite optimistic that I'm going to be able to recover all my old backups. The problem appears to be mounting the disk image inside the sparse bundle. Now that I've got the sparse bundle copied onto a USB disk, I am able to mount the disk image, which I was not able to do when it was on the NAS. And now that it's mounted, I'm doing a block level copy (using Disk Utility > Restore) to copy the disk image (not the sparse bundle) onto a new
disk.
ETA is 8 hours, so we'll find out in due course.

If my way of using Time Machine is not supported (although it can't be THAT different to how Time Capsule works), then I suppose I ought to look at getting a Time Capsule - I love being able to backup over wireless.
Do you know if the disk spins down when not in use?

snark
4th April 2010, 01:07 PM
Dang, this is really frustrating !!

I've block copied my old Time Machine volume onto a USB disk, and I'm able to browse all my backups (back to September '09), using the Time Machine UI, but I can't perform any new backups to the disk - Time Machine is complaining that the disk is "read only".

I've tried Disk Utility > First Aid > Repair Disk, and it bombs out, saying it can't repair it. One of the errors is:
Rebuilding catalog B-tree
Invalid node structure

...which sounds pretty bad. But then the disk mounts - but in a crippled state, apparently.

Are there any other tools I could use the fix the volume? Quite clearly, all the data is there - it just appears that something else is corrupt, and preventing the disk from behaving properly.