On Fri, Sep 24, 2004 at 08:31:28 +1000, James Ponza wrote:
> 1. The BIOS reports the HDD name as: "GDC GD!6 0JB-0 DEA#" wheras it SHOULD be
> something like "WDC WD1600JB-00xxxx". (it is a WD 160Gb drive).
There's a pattern to those errors -- a single bit in each 16-bit half
word is always zero, but it should be a one in some of them. That could
be caused by one or more of:
1. Cable fault. Try a different cable.
2. Fault in the other drive on same cable. Try disconnecting the other
drive.
3 IDE controller fault. Try connecting the drive to the other
channel.
4. Drive fault. If you can get hold of another drive of the same
type, you might be able to swap the controller boards and get some
data off the dead one. No guarantee though; the data may have
already been corrupted. If you try it, make sure the data on the
other drive is backed up before you swap the controller board, just
in case you damage it.
You don't need to boot an O/S to test any of these. If you can get the
BIOS to report the correct drive identity, it's OK.
> incorrectly (and incidentally this is /dev/hdd - it has one partition - using
> the ext2 filesystem, it is connected as the secondary slave, to the SAME
> CHANNEL as my DVD-RW (is this a problem?). I have not yet tested the
Not usually, unless they're both configured as slaves.
> or have I had something hideously bad happen, ie the drive is dying / has
> died?
It might be.
Cheers,
John
--
If a bean counter complains about 9G root drives with only 600M used
introduce it to the underfloor void. Don't worry, the shouting stops
after a while.
-- Geoff Lane
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
