OldGuy said:
Working on it and it froze solid.
Booted and says can't find OS.
BIOS says C: Drive is NONE. CD shows up.
So the fairly new HHD has died completely?
Yikes!
And Acronis Drive Monitor said it was in great shape. SMART was all OK
and very few errors.
So ... what next?
Recovery Suggestions please or ...
(don't rattle on about backups since all pertinent data is backed up
multiple places.)
If the hard drive was a refurb, this would not surprise me.
The usual procedure would be to test the drive in another computer.
If it is SATA, you can easily cable it up to your desktop (for 2.5" drives).
If it happened to be a 44 pin IDE, you'd need a 44 pin to 40 pin
adapter, to connect to a ribbon cable interface on your desktop.
The reason for connecting it directly to the computer, is so you
can pop into the BIOS and see if it registers as (NONE) there as well.
As that's a very quick test for a dead drive. If it says (NONE) in the
BIOS, I don't know of any effective thing you can do from the OS
to change that.
Testing it in the desktop, eliminates the laptop as the source
of the problem. If testing points at the laptop, pull the battery
from the laptop and leave it over night with no power source. Just
in case it is "micro latchup" in the Southbridge.
Another quick note about SATA - there is no means in the interface
to assert RESET. If you ever find a SATA drive has "gone nuts", as
has happened to me a couple times, this can be solved by completely
powering down the computer. Then powering up again. Power cycling
resets a SATA drive, whereas pushing the reset button on the front
of the computer, does nothing. The thing is, back in the IDE
(ribbon cable) era, there was a separate reset signal on the cable.
And that guarantees, that pressing reset on the front of the computer,
restores sanity to the hard drive. Whereas, the data cable on SATA,
has no such mechanism. If the drive goes insane, the only option
is to remove all power. This observation hadn't occurred to me,
until my first incident involving drive insanity. It would not
have occurred to me there was no reset signal on the cable. (And
if there was an in-band signalling scheme intended on SATA, such
as a coding violation trick, it didn't work.)
So don't condemn the drive just yet - if it was temporary insanity,
a power cycle will fix it. If it happens too much, replace the drive.
I've only had two insanity incidents here, and haven't replaced any
drives due to the low frequency of occurrence (one drive has 14,000
hours on it) .
Paul