Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'I don't think so' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
I don't think so
Authored by: Ilgaz on Sep 21, '06 10:51:22AM

Everything suggests a real disk failure, caused by a non-relocated bad block other than journalling or carbon copy cloner.

Another thing: Is Carbon Copy Cloner compatible with OS X Server aka Xserve? There are differences between systems. First, Xserve comes with ACL on; OS X (client) comes with ACL off. (Ref: Bresink help file on Tinkertool System)

Even if Carbon Copy cloner has an evil "bug," you can't blame the package. Does it say "Xserve" in system requirements/compatibility? No. I would specifically look for "XServe" whatever I install to that machine.

As another person said, journalling (and SMART too!) makes people think there could be no sector errors, no corrupt files anymore. Journalling only handles "where" files are, not "content" of them corrupt or not. Lets say your kernel crashed while saving a jpeg and file is incomplete. Next time you reboot, OS X will replay "journal" and fix inconsistencies in volumes file allocation table. It won't magically fix a corrupt jpeg.



[ Reply to This | # ]