Hard Disk Failure

[MeanyOwl]

Hello again, people.  A more complex issue has arisen this time.  The computer experiencing the difficulty is a Comaq Presario CQ62, running KDE PCLinuxOS.  The issue is that upon boot, it does not register the hard drive existing.  Upon attempts to boot with LiveCD, and reformat, the hard drive for the computer is not listed.  Any attempts to access it are redirected to another drive.

My issue is quite close to this issue: http://www.pclinuxos.com/forum/index.php/topic,81444.0.html

But upon following some of it's advice, I found this error message in Konsole instead:
fsck from util-linux-ng 2.18
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext2: Invalid argument while trying to open /dev/sda

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

I followed the advice of accessing the hard disk, and trying to apply more pressure to it's connection cable to restore proper connectivity, but the issue has not been resolved.  Advice?

[AS]

Hello again, people.  A more complex issue has arisen this time.  The computer experiencing the difficulty is a Comaq Presario CQ62, running KDE PCLinuxOS.  The issue is that upon boot, it does not register the hard drive existing.  Upon attempts to boot with LiveCD, and reformat, the hard drive for the computer is not listed.  Any attempts to access it are redirected to another drive.

Is the disk visible from BIOS ?

My issue is quite close to this issue: http://www.pclinuxos.com/forum/index.php/topic,81444.0.html

But upon following some of it's advice, I found this error message in Konsole instead:
fsck from util-linux-ng 2.18
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext2: Invalid argument while trying to open /dev/sda

/dev/sda refer to the whole disk, you may want to check each single partitions, thus using fsck -f /dev/sdaN, where N is the number of the partition ...

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

that's normal if you tried to check /dev/sda, see above.

I followed the advice of accessing the hard disk, and trying to apply more pressure to it's connection cable to restore proper connectivity, but the issue has not been resolved.  Advice?

1) check BIOS
2) most HP/COMPAQ computers provide SMART checking from BIOS (may be it's called "hard disk test" ...)
3) possibly check both ends of the cables
4) after the disk is recognized from BIOS, look at the partition table, using fdisk -l from LiveCD

AS

[T6]

also would be good to verify in bios that if ahci option is available for that hard disk, turn it off

[MeanyOwl]

Is the disk visible from BIOS ?

No, it does not appear to be.

/dev/sda refer to the whole disk, you may want to check each single partitions, thus using fsck -f /dev/sdaN, where N is the number of the partition ...

Produces this:
 fsck -n -v /dev/sda1
fsck from util-linux-ng 2.18
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext2: No such file or directory while trying to open /dev/sda1
Possibly non-existent device?

1) check BIOS
2) most HP/COMPAQ computers provide SMART checking from BIOS (may be it's called "hard disk test" ...)
3) possibly check both ends of the cables
4) after the disk is recognized from BIOS, look at the partition table, using fdisk -l from LiveCD

AS

Attempting to initiate the Hard Disk Test causes the BIOS to lock up...didn't know that was possible, actually.  The other end of the cord seems to go into a part of the computer I cannot access, but there is a bit of metal with a plastic flap on top of it near where it turns inward.  I can't seem to find anything wrong with that....

also would be good to verify in bios that if ahci option is available for that hard disk, turn it off

I'm afraid I'm unfamiliar with that.  Could you clarify?

[AS]

Unless I'm missing something .... you drive look like dead.  

The AHCI vs. Legacy option, is a BIOS setting that provide support for older OSes that do not support directly SATA, this can be relevant only at OS level... if you don't see the drive at BIOS level ... this setting doesn't matter.

The lockup at "Hard disk test" ... could be a due to some difficult to recognize the hard drive ...

Afraid, there is not a single hint that your hard disk is alive ...

AS

[Old-Polack]

MeanyOwl:

Expanding on what as just posted, something has failed at the hardware level, and the choices are hard drive, cable, motherboard controller or controller connector socket. You need to determine which is the culprit. Turn the computer off. Try each or the below in turn, followed by an attempt to boot the installed system.

1. Unplug and replug both ends of the data cable connecting the hard drive to the motherboard, several times, to assure a good connection.

2. Unplug and replug the power cable at the hard drive connection; as above.

3. Unplug the power connector and replug using a different power connector.

4. Try connecting to a different socket on the motherboard.

5. Try a different data cable on both the present MB socket, and a different one.

6. Connect a different hard drive to the currently used MB socket, using the present cable, then a new/known good one.

I'm assuming the motherboard controller itself is still good, as you report other drives still being recognized. Through process of elimination you will determine which is the failed hardware item.

[T6]

yes, if not present in bios and you can't change cables(verify cables), the drive sounds dead to me

time to replace it

[andy]

+1, BIOS must see it first. T-shooting connections/cables first as mentioned above, then if possible, try another drive on the end of the same cables where the current problem drive lives.  You can try to listen for it to spin up upon boot as well. If it spins up, then maybe the data cable is the culprit and the power cable is good.
Andy