View Full Version : Structure errors in bootable backup partition

02-24-2007, 01:33 PM
I've been using SuperDuper Smart Backup mode to back up two G4 laptops (60 and 80Gb drives to two each of four equal (ca 94Gb) partitions on a 400Gb firewire OWC external (Oxford IC, Seagate drive). The backup partitions have different names than the source disks.Drives are 50-60% full and have been scanned with applejack from time to time with no errors observed. I've booted each of the SD partitions on the external periodically, but done nothing else with them.

After an unexpected hang or two on the Ibook, I ran the Apple hardware test and found memory errors. Reseating didn't help, so I bought a replacement DIMM and a copy of DriveGenius to screen for disk issues.

Recalling painfully OS9 drive utilities doing more damage than good, I ran the DG verify and repair routines on the Ibook and got 'successful repair' of 'minor volume header' issues. I then ran the same routines on the two Ibook SD partitions. One was clean; the other yielded many tens of lines of 'orphaned inodes' errors, but was also as reported as repaired. I hadn't sought in advance how to find/save the logfile. Scans of all partitions on the external show no bad blocks.

So should I just keep backing up to the 'repaired' partition or erase it and start over?
In the past you've said that when you restore from a bootable external, it should be renamed to the original name of the source drive to avoid issues with aliases. Since I started up from these partitions while they have a different name, are they somehow compromised for doing a restore in the future?



02-24-2007, 01:35 PM
I'd erase the one that had orphaned inodes, but leave the other alone.

02-24-2007, 01:47 PM
Thanks for the amazingly quick reply and the excellent program. Is there a way to avoid whatever happened or should I be running drive hygiene programs on the backup partitions regularly in addition to trial booting from them?

02-24-2007, 02:42 PM
There's nothing about the backup as such that would require that, but at the times where you'd normally check drives (e.g. crashes, etc), I'd check it when you check other things.