Hi All, Every summer I have disk problems on our SOHO server (probably because of the excess heat and lack of fans on some external drives).
I have one disk now that reports in Disk Utility when "repaired" > Verify and Repair volume “Hatken” > Verifying volume when it is mounted with write access. > Checking Journaled HFS Plus volume. > Checking extents overflow file. > Checking catalog file. > Incorrect number of thread records > Invalid leaf record count > (It should be 1600539 instead of 1600538) > Checking multi-linked files. > Checking catalog hierarchy. > Checking extended attributes file. > Checking volume bitmap. > Volume bitmap needs minor repair for under-allocation > Checking volume information. > The volume Hatken was found corrupt and needs to be repaired. > Volume repair complete.Updating boot support partitions for the volume as > required.Error: Disk Utility can’t repair this disk. Back up as many of your > files as possible, reformat the disk, and restore your backed-up files. or similar (see below). I could not use Disk Utility to do a block copy of this disk (for some reason it would stop and hang the app or machine part way through). This was during the hot period and the disk could have been overheating during the operation However, I have used Carbon Copy Cloner to copy the disk onto another disk without problem. I assume this means CCC is just copying what it thinks is correct and the resulting disk may be missing data, files, etc. I have a Time Machine backup of this disk but unfortunately it is a week or so out of date. My question is how shall I combine these two (CCC clone of bad disk and Time Machine backup of disk a few days old) to get the best recovery? It's tempting to just use the CCC cloned disk - it looks ok ;-) Is there anyway to compare or "merge" the two? To find the bad files and fix them from the Time Machine backup or to find the changes made after the Time Machine backup and include them from the cloned disk etc. Thanks in advance for any suggestions. Cheers, Ashley. -- Further Repair Disk outputs: > Verify and Repair volume “Hatken” > Verifying volume when it is mounted with write access. > Checking Journaled HFS Plus volume. > Checking extents overflow file. > Checking catalog file. > Incorrect number of thread records > Invalid leaf record count > (It should be 1600541 instead of 1600540) > Checking multi-linked files. > Checking catalog hierarchy. > Invalid directory item count > (It should be 59 instead of 60) > Checking extended attributes file. > Checking volume bitmap. > Volume bitmap needs minor repair for orphaned blocks > Checking volume information. > The volume Hatken was found corrupt and needs to be repaired. > Volume repair complete.Updating boot support partitions for the volume as > required.Error: Disk Utility can’t repair this disk. Back up as many of your > files as possible, reformat the disk, and restore your backed-up files. > Verify and Repair volume “Hatken” > Verifying volume when it is mounted with write access. > Checking Journaled HFS Plus volume. > Checking extents overflow file. > Checking catalog file. > Incorrect number of thread records > Invalid leaf record count > (It should be 1600603 instead of 1600602) > Checking multi-linked files. > Checking catalog hierarchy. > Checking extended attributes file. > Checking volume bitmap. > Volume bitmap needs minor repair for orphaned blocks > Checking volume information. > The volume Hatken was found corrupt and needs to be repaired. > Volume repair complete.Updating boot support partitions for the volume as > required.Error: Disk Utility can’t repair this disk. Back up as many of your > files as possible, reformat the disk, and restore your backed-up files. > _______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
