#Hard Disk Crash
Don,
Well, after 9 months I finally had my first HD crash. I had a power glitch
(luckily, very rare) while writing to my CLtd HD. The glitch was fast enough so
that my Amiga did not lose its mind, but my disk drive sat there and clucked to
itself for a while with the LED flashing for about 5 minutes and then settled
down. I was then able to read and write to the HD with no problems. To be sure
I had not corrupted the system, I rebooted. I was promptly informed my HD was
no longer a DOS disk.
As an experiment I decided to try Diskdoctor (I know, I know, but I was
curious). We had a similar problem with our PAL Sr. drive at work and were told
by BYTE by BYTE to use Diskdoctor to ressurect it. If you haven't tried it, it
renames your HD Lazarus. Nice touch. With our PAL it worked great. When I tried
it on my CLtd, it didn't work quite so well. It read all 600 and something
tracks and then started replacing files. It came with 7 files it listed as
corrupted and ask if I wanted to delete them. I did. All seem to be OK reading
the drive, however when I tried to write to it, Amy said the drive was not
validated. When I did an info from CLI, it said the drive was validating. I
then rebooted and the drive spent about 5 mins during the s-s and then gave me
a system requestor saying "Error validating disk Key 13532 – bad extension"
When I clicked "cancel" another one came up and told the "disk structure
corrupt. Use diskdoctor" After this, I could read the HD but still not write to
it. Info says it is validating. However after waiting overnight, it was still
validating. I repeated using diskdoctor and got exactly the same results.
Of course I can't use Dave Haynie's Disksalvage without another 24 meg HD. Out
of curiousity I still would like to see if I can recover the drive without
reformatting. Any ideas on how to get the drive to validate?
Anyone else have any ideas?
Later, Greg