AMITIAE - Tuesday 29 May 2012
Rescue and Repair of an iBook G4 |
|
By Graham K. Rogers
Nonetheless, I do have a drawer full of disks I have acquired (legally) over the years and among the operating system versions and rescue software, there ought to have been something I could use. It also dawned on me that I was going to have to work a bit faster than I was used to as I did not have the power supply. The one in my office (and the one at home) has the later MagSafe connector and was therefore not suitable for the older G4 iBook.
I restarted and tried to eject the disk. As before, there was no Apple logo, but holding down the trackpad did not eject the disk. On all other Macs I have used, pressing the mouse button or the trackpad at startup will eject a disk. I scratched my head for a while, and pressed the eject button a couple of times, but nothing happened. I tried a second restart, but this time pressed the eject button and the disk came out. If one disk could come out, then it might be an idea to try another. I inserted the Disk Warrior one that I keep safe in the room. Another restart and I watched as the Apple logo came up again. All well and good. I know that the Disk Warrior startup is always slow, but this was geological; and then the screen changed. Lots of Unix style text and "We are hanging here" was shown on the screen. I haven't seen that for ages. We had had a good, old-fashioned kernel panic. Good and bad really: there was something in the system that was readable, but we did have problems. I did one more restart to eject the disk. This time, the Apple logo appeared, but not the spinning gear-wheel. I tried Single User mode again and this time, I was able to access the system and effect a repair using the command fsck -fy. As the process ran, I was not surprised to see that there were problems, nor the problems that were indicated: the hierarchical structure. It had lost the plot. Unlike the earliest versions of OS X, the file system check makes the repair and then runs again, reporting at the end that the disk "appears to be OK" -- praise indeed. With the repair done, I restarted as normal and the process was as it should be, right up to the login screen. I did not have the password, so carried it down to my colleague's office as it was and put it on her desk. After she had blinked once or twice, I made a strong suggestion that any data needed should be rescued as I was not willing to give any guarantees about the disk itself, even though SMART (Self-Monitoring, Analysis and Reporting Technology) reports all is well.
Graham K. Rogers teaches at the Faculty of Engineering, Mahidol University in Thailand. He wrote in the Bangkok Post, Database supplement on IT subjects. For the last seven years of Database he wrote a column on Apple and Macs. |
|
For further information, e-mail to