TiBook 667 HD - Gone? HELP!

[zargon]

Hi All,

got this wonderful TiBook 667mhz - and just the other day - I put it to sleep... and when it woke up.. the desktop image was there but there was NO MOUSE - so I control+command+PowerKey and did a restart.. got the folder/face flashing icon in the middle of the screen. I was able to start up with a 80gig Maxtor drive that has 10.3 on it but the TiBook HD seems to have fallen to a deep, deep Sleep.

Is there a way to shake it up and bring it to conciouness just one more time - so I can suck my important info off of it before I say good-Nite forever - Or do you think it is already too late?

I have tried booting from TT4Pro 4.0.3/4 and also DiscWarrior - :-(((((
No word from the mother drive? :-((((

having said all that ... it did the same thing a week or so ago.. but I was stupid... and did not do the proper back up... so I thought 'what the heck, I'll let it rest a while and maybe it will start up again... just like the old daze.'

Help me Oh-Bee-Whaan! You are my Only HOPE!!!

 

[Arden]

I've gotten that, too. It often happens when my computer crashes while running OS 9. What I've found to work is using Disk Utility on the Panther install CD to repair the disk, then rebooting back into whichever OS I want to use (and avoiding a crash ^_^).

Which OS were you running when this happened? Do you have another Firewire-equipped Mac that you can access, perhaps a friend's? If so, you may be able to use the PB in target disk mode (hold T when you start up) and rescue the data. Then you can wipe the hard drive and restore from your Maxtor.

 

[Viro]

I don't know about this problem, but it sounds like the hard drive has died. If you can boot up the OS X install disc, try running some diagnostics and in particular, try to check the SMART status. That should tell you how the drive is doing.

 

[Arden]

It can seem like the hard drive has died when it actually hasn't. I don't know the actual mechanics of it, but I suspect that sometimes a critical file doesn't get properly written because the computer didn't shut down correctly, and the firmware doesn't recognize the hard drive as bootable. I usually have to mess with it in Disk Utility or Techtool Pro to bring it back to life.