IDE errors: Bad HD or Kernel problem

larrystorch · 11-02-2003, 12:44 AM

I just started having the following errors on my WD 80gig HD since upgrading to Slackware 9.1 and compiling a custom kernel for it. I've had the drive for about a year and have not had a problem with it till now.

Code:

kernel: hda: write_intr error1: nr_sectors=8, stat=0x51
kernel: hda: write_intr: status=0x51 { DriveReady SeekComplete
kernel: hda: write_intr: error=0x10 { SectorIdNotFound }, LBAsect=78157001, sector=776
kernel: hda: write_intr error1: nr_sectors=8, stat=0x51
kernel: hda: write_intr: status=0x51 { DriveReady SeekComplete
kernel: hda: write_intr: error=0x10 { SectorIdNotFound }, LBAsect=78157001, sector=776
kernel: hda: write_intr error1: nr_sectors=8, stat=0x51
kernel: hda: write_intr: status=0x51 { DriveReady SeekComplete
kernel: hda: write_intr: error=0x10 { SectorIdNotFound }, LBAsect=78157001, sector=776
kernel: hda: write_intr error1: nr_sectors=8, stat=0x51
kernel: hda: write_intr: status=0x51 { DriveReady SeekComplete
kernel: hda: write_intr: error=0x10 { SectorIdNotFound }, LBAsect=78157001, sector=776    
kernel: ide0: reset: success

Is this a sign that the drive is failing or a kernel config problem?
Here is some info to help out:

Code:

hdparm -iI /dev/hdc
/dev/hdc:
 
 Model=WDC WD800JB-00CRA1, FwRev=17.07W17, SerialNo=WD-WMA8E4200547
 Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
 RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=40
 BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=156301488
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4
 DMA modes:  mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
 AdvancedPM=no WriteCache=enabled
 Drive conforms to: device does not report version:  1 2 3 4 5


 xfermode to 69 (UltraDMA mode5)
 multcount    = 16 (on)
 IO_support   =  3 (32-bit w/sync)
 unmaskirq    =  1 (on)
 using_dma    =  1 (on)

These are the settings I have been using for a long time, So I don't think they would be the culprit.

exodist · 11-02-2003, 12:51 AM

I have had this before to, what kernel did you use/what ide options (noteable ones) did you use?

crashmeister · 11-02-2003, 03:26 AM

If you still got warranty on the hdd head over to http://sourceforge.net/projects/va-ctcs/ install it,read the warning and run the hdd test for about a day or two.I had the same warning various times on one hdd about a year ago and also got data corruption but after I changed file systems it worked fine.

larrystorch · 11-02-2003, 12:55 PM

Here's some more info:

ext3 filesystem
Albatron KX-400-8X mobo (VIA KT-400 chipset)

Kernel:

Code:

# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_BLK_DEV_GENERIC is not set
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_BLK_DEV_VIA82CXXX=y
.......
# CONFIG_IDE_CHIPSETS is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_DMA_NONPCI is not set
CONFIG_BLK_DEV_IDE_MODES=y

Looking over this config, it looks like I should try and compile a new kernel and clean up the IDE section abit (lose CMD640, etc)

larrystorch · 11-02-2003, 08:38 PM

This just popped up in my log:

Code:

Nov  2 18:31:47 storchnet kernel: journal_bmap: journal block not found at offset 3084 on ide1(22,2)
Nov  2 18:31:47 storchnet kernel: Aborting journal on device ide1(22,2).
Nov  2 18:31:50 storchnet kernel: ext3_abort called.
Nov  2 18:31:50 storchnet kernel: EXT3-fs abort (device ide1(22,2)): ext3_journal_start: Detected aborted journal
Nov  2 18:31:50 storchnet kernel: Remounting filesystem read-only
Nov  2 18:32:35 storchnet kernel: EXT3-fs error (device ide1(22,2)) in start_transaction: Journal has aborted

So it seems that my ext3 journal is borked. Any idea on how to fix it?.....off to google it

larrystorch · 11-02-2003, 11:42 PM

Ok, a kernel recompile (2.4.22) did nothing as did a fsck for bad blocks.

Is this ext3 related, hard drive or possibly the IDE on the motherboard

TIA guys and gals

larrystorch · 11-03-2003, 08:19 PM

Ok, I think I found a few things that might have been causing the errors, but as far as which exact one, I'll never know.

1. ext3: I'm mounting the partitions as ext2 to avoid the corrupt journal. Trying to figure out how to fix it.
2. I have $CFLAGS and $CXXFLAGS sourced at login. They might have borked up the kernel.
3. ACPI: I did have it working with 2.4.19 and had to dump it when moving to 2.4.21. I re-enabled it for 2.4.22, and it seemed to make my system flaky.

Lessons:
1. Switching to a different journaling filesystem at next hardware upgrade. Ext3 worked good for a few years, but I can't afford to lose my /home partition, too much valuable info. (yes I back up, but one day can really screw me).
2. Compile flags will be exported only when I actually compile a program, not at login.
3 ACPI is nice, but not too stable at this point, hopefully 2.6 will make it more solid.

Thanks for the help guys. Off to search the forums about journaling FS opinions.

taran · 03-09-2004, 09:45 PM

larrystorch, did you ever figure out how to fix the problem? I think I am having the same issue but I don't know how to fix it.

larrystorch · 03-10-2004, 11:47 AM

In the end, the hard drive was on it's last leg. It was a Maxtor that was only 2 years old. I bought a new Western Digital, and was able to copy over my important data before taking a sldgehammer to the Maxtor.

For some reason, I have had 3 Maxtor drives of different sizes and purchased at different times all die prematurely. On the other hand, some of my friends have never had a problem with Maxtor.

If you have another hard drive around, hook it up to the same IDE channel to see if it's kernel or IDE channel giving you problems. I went thru a bunch of kernel, IDE channel and drive combos till I was certain it was hard drive.

Good luck

taran · 03-10-2004, 12:31 PM

Hmm...my hdd is only about 6mo old. Arg...I'll see if I can find another HDD somewhere and test it out.

trade14u · 03-22-2004, 08:57 AM

I'm having the same problem - except my drive is a week old.

taran · 03-23-2004, 03:11 PM

I ended up re-installing RH and haven't had the problem reoccur since (its been about a week and a half). It was a pain but i was tired of pulling my hair out trying to fix it.