Hey there, my server installed an update and spontaneously rebooted while Time Machine was backing up to it. The result seems to be a sparsebundle file that is corrupt. I've tried attaching the disk image with the -nomount parameter and running fsck over it, but to no avail.
One thing that seems odd, however, is that when fsck runs, it says this:
What does "NO WRITE" mean? Does that mean the disk image (from the sparsebundle file) is mounting read-only? Does that mean that fsck will only verify and won't actually repair anything?
fsck *acts* like it's repairing. It says this at one point:
Is fsck not smart enough to know when the disk it's operating on is read-only?
Thanks!
One thing that seems odd, however, is that when fsck runs, it says this:
Code:
/dev/rdisk2s2: fsck_hfs run at Fri Dec 16 08:30:45 2011
/dev/rdisk2s2: ** /dev/rdisk2s2 [COLOR="Blue"](NO WRITE)[/COLOR]
/dev/rdisk2s2: Executing fsck_hfs (version diskdev_cmds-491.6~3).
QUICKCHECK ONLY; FILESYSTEM DIRTYWhat does "NO WRITE" mean? Does that mean the disk image (from the sparsebundle file) is mounting read-only? Does that mean that fsck will only verify and won't actually repair anything?
fsck *acts* like it's repairing. It says this at one point:
Code:
** Checking volume bitmap.
** Checking volume information.
** Repairing volume.
Orphaned file inode (id = 12096855)
Orphaned file inode (id = 12096856)Is fsck not smart enough to know when the disk it's operating on is read-only?
Thanks!