Cannot startup from nor initialize hard drive
I have an iMac that I keep around for running older graphics and web building software that I cannot afford to replace, and to run a Classic application occasionally. It worked fine until a few weeks ago.
Hardware:
17" G5 iMac (iSight) 1.9 GHZ (2005)
1.5 GB RAM
10.4.11 (prior to attempt to erase drive, see below)
It froze while viewing and copying multimedia (Quicktime) files (it was running OS X). After attempts to restart, recover, repair, etc., I eventually erased the drive, or so I thought, using Disk Utility (via Firewire Disk Mode and my Macbook Pro). Then I tried to reinstall from the backup, minus unneeded document files. I was unsuccessful, though I didn't note the alert message (I think it was the same as those I'm getting now, copied below). I am just now getting back to attempting the reinstall again. First, I used Disk Utility (from Macbook Pro; iMac in FW disk mode again) to verify and repair the iMac. I get these results:
Checking file system
Error: This disk needs to be repaired. Click Repair Disk.
Disk Utility stopped repairing “disk1s2”
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.
But Disk Utility will not reformat the disk. Neither will Drive Genius III.
Carbon Copy Cloner states that 52 GB are in use on the iMac, though no files are visible in finder.
Since CCC says there are files on the drive, I attempted to boot from the iMac's hard drive:
I get the grey screen with a flashing ? for over a minute
Then it finds the internal HD; that is, I see the grey screen with the apple logo and spinning wheel. This lasts until I turn off the power (ten minutes or so; blue screen never appears).
If I boot from an external backup clone (selected via option key at startup):
grey screen for a normal time (very short; much less than a minute)
then the blue screen and login window
I select user and log in
the desktop never appears; ten minutes later, still nothing
To me, this suggests a problem other than (or as well as) a bad hard drive.
Any suggestions would be most welcome.
Many thanks, as always
Leonard