Is this HD beyond repair???


hda: WDC WD600AB-22BVA0, ATA DISK drive
hdc: WDC WD600AB-00BVA0, ATA DISK drive
hda: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=7297/255/63, UDMA(66)
hdc: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=116301/16/63, UDMA(66)
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=80390, sector=2
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=80390, sector=2
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=80390, sector=2
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=80390, sector=2
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=80390, sector=2
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=80390, sector=2
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=80390, sector=2
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=80390, sector=2
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=80390, sector=2
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=80390, sector=2
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=80390, sector=2
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=80390, sector=2
hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=80390, sector=2
hdc: DMA disabled
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x01 { AddrMarkNotFound }, LBAsect=80390, sector=2
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=80390, sector=2
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=80390, sector=2

If you have other reasons to believe the drive is trashed (eg, it has been dropped or zapped), then I would draw that conclusion. Otherwise, it's entirely possible that it's a kernel issue or something else.

First:

- Has this drive functioned before with the same configuration?
- Have you checked all cabling in the machine?

If this is a fresh installation of Linux, it might be a kernel issue. I had similar errors on a Maxtor drive with RedHat Roswell public beta. The ext3 filesystem was giving me errors (not nearly as many) on boot, and bootup took quite a long time due to this.

The same drive works fine with ext2 and NTFS (it's dual-boot). I ended up disabling DMA to fix the problem.

If you suspect this might be similar, try passing ide=nodma to your kernel. In lilo, just type:

linux ide=nodma

Assuming your image name is 'linux'.

There are other similar things you might try, but the above is what I have personally seen happen.

Hope some of this is helpful.

<EDIT>
Also, if none of the above is helpful, you might try changing settings in your BIOS, namely turning LBA on and off, even disabling DMA in the BIOS, to see if anything changes.
</EDIT>

Thanks for your reply.

The strange thing is that this faulty HDC: is the same as drive HDA: wich works very well so...

We got the same type of errors (albeit a little different) in a FreeBSD machine and the drive crashed and burned soon after getting them. I'd try to recover the data and get a new HDD.

Hmm, look at this;

hda: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=7297/255/63, UDMA(66)
hdc: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=116301/16/63, UDMA(66)

HDC: is the one with errors. How can I change CHS from HDC: exactly as CHS from HDA: ?

Like I said earlier, try changing some of the BIOS settings around.

CHS == Cylinders, Heads, Sectors

Generally "Auto" should be chosen in the BIOS, but if this doesn't work you may need to set them manually (see the docs that came with the drive, or search the manufacture's website, or see the label on the drive). Note that, since a few years ago, the CHS values are always bogus and not actual... it's an intel legacy thing...

Linux isn't as picky as some other OS's, so LBA is not required, but is recommended anyway.

In any case, my suggestion is to go into your BIOS and set the non-functioning drive to the exact same settings as the functioning drive.

Ok, I forgot to mention that I only have remote access so changing BIOS settings is out of the question... :bawling:

In that case I would contact my provider about it. In either case it's a hardware problem, and if you are leasing a server, your provider should be able to help.

I'd recommend having them change the BIOS settings first and, failing that, replace the drive.

If you actually own the box, you'll need someone with physical access to help you... not much else I can suggest at this point.

Originally posted by Domenico
Hmm, look at this;

hda: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=7297/255/63, UDMA(66)
hdc: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=116301/16/63, UDMA(66)

HDC: is the one with errors. How can I change CHS from HDC: exactly as CHS from HDA: ?

If those are exactly the same drive then I dont know about the linux side but theres definately a hardware misconfiguration there on hdc. Other than that all I can offer is theyre WDC drives which havent got the greatest reliability status around.