Is this a hardware or software problem, or could it be either?
Jul 26 23:51:59 asdf kernel: hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
Jul 26 23:51:59 asdf kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=8545004, sector=62608
Jul 26 23:51:59 asdf kernel: end_request: I/O error, dev 03:05
(hda), sector 62608
Just got it opening up a mail folder. Drive made a bit of noise
and then PINE had to be killed.
2 root@asdf:~# hdparm -i /dev/hda
/dev/hda:
Model=IBM-DTLA-307030, FwRev=TX4OA50C, SerialNo=YKDYKGF1437
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40
BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=60036480
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4 udma5
No mucking around with hdparm on this box, using stock RHL7.1
i586 UP kernel.
----------------------------------------------------------------------
Mike A. Harris - Linux advocate - Open Source advocate
Opinions and viewpoints expressed are solely my own.
----------------------------------------------------------------------
Definition: MCSE - Microsoft Certified Solitaire Expert
I don't know my drives that well, but it looks like a drive problem to me.
> Is this a hardware or software problem, or could it be either?
>
> Jul 26 23:51:59 asdf kernel: hda: dma_intr: status=0x51
> { DriveReady SeekComplete Error }
I believe that his means the drive failed to seek to the desired sector,
it was either miscalibrated, or the sector was bad.
> Jul 26 23:51:59 asdf kernel: hda: dma_intr: error=0x40
> { UncorrectableError }, LBAsect=8545004, sector=62608
> Jul 26 23:51:59 asdf kernel: end_request: I/O error, dev 03:05
> (hda), sector 62608
I believe that this means that even with the on disk ECC the data from
the sector was not recoverable.
-Kip
Mike A. Harris wrote:
> Is this a hardware or software problem, or could it be either?
>
> Jul 26 23:51:59 asdf kernel: hda: dma_intr: status=0x51
> { DriveReady SeekComplete Error }
> Jul 26 23:51:59 asdf kernel: hda: dma_intr: error=0x40
> { UncorrectableError }, LBAsect=8545004, sector=62608
> Jul 26 23:51:59 asdf kernel: end_request: I/O error, dev 03:05
> (hda), sector 62608
>
> Just got it opening up a mail folder. Drive made a bit of noise
> and then PINE had to be killed.
It's most likely a bad block on the hard drive. A less likely (IMO)
possibility is that at one point in time, the drive was powered down
while it was in the middle of flushing that pine folder from its cache
onto the disk.
> 2 root@asdf:~# hdparm -i /dev/hda
>
> /dev/hda:
>
> Model=IBM-DTLA-307030, FwRev=TX4OA50C, SerialNo=YKDYKGF1437
Hmmm, 30GB IBM 75GXP -- from what I've seen in the StorageReview.com
discussion boards, the 75GXP line as a whole seems a bit too
unreliable...
Your next step should be to run IBM's Drive Fitness Test in quick mode.
(If you don't already have DFT, or if you have a version older than the
current v2.10, download the disk image from
<http://service.boulder.ibm.com/storage/hddtech/dft-v210img.bin> and use
dd to copy it to a 1.44MB floppy disk.)
What's probably going to happen next is that the quick test will finish
*real* fast, with a message saying that the disk can be repaired by
using DFT's Erase Disk function, and just in case you don't want to do
that, the next screen (if you choose not to erase, IIRC, and you'll
definitely want to choose not to erase for the moment if you haven't
backed things up at this point) will have various pieces of information
needed to get an RMA for warranty replacement. (Should you decide to
immediately go that route, write down the information from the Technical
Result Code screen, go to http://www.storage.ibm.com/warranty, click on
"check warranty status..." and go from there.)
If you want to try to get some more life out of your current drive,
Erase Disk in DFT (after backups, of course). If your drive has too many
remapped bad sectors, Erase Disk will fail and you'll have no recourse
but to RMA the drive. Otherwise, the result will be a blank drive with
all the bad sectors remapped (in theory, at least) and, in DFT's eyes
(and probably IBM's eyes) the drive will not be defective until more
bad sectors appear.
You could theoretically start using the drive again at this point, but
IMO it would be more prudent to partition the drive as a single FAT32
partition or a bunch of FAT16/32 partitions, then run SpinRite (if you
don't have this, it costs $90 from <http://grc.com/>) in level 5 mode,
from a boot floppy with the Win95, 98, or ME version of MS-DOS. This
will thoroughly scrub the disk and remap more bad sectors for you. Note
that IME SpinRite seems to remap some bad blocks even when its logs and
on-screen displays show that it thinks the disk was in perfect
condition. Also, I think SpinRite will probably back down to level 4 on
its own, but that's OK.
(I guess SpinRite's level 5 is kind of like a closed-source "badblocks
-n" with data recovery features, for FAT filesystems only. I'm not aware
of any truly equivalent open-source programs.)
Then, if you can live with the ugliness and performance loss, try using
ext2 on several loopback files (e.g., one for /, one for /usr, etc.) on
one or more FAT filesystems, or use UMSDOS. This way you'll be able to
go straight to SpinRite the next time you get bad blocks (level 3 if
you're trying to fix the disk quickly and get back to work, level 4 or 5
if you're running SpinRite as periodic maintenance to remap marginal
blocks before they become clearly bad). Yes, this is hideously ugly,
but it has prevented data loss on an IBM TravelStar of mine. (I should
note that I've only tried loopback files, not UMSDOS, in this scenario,
but I don't see any reason why UMSDOS wouldn't work. In fact, I imagine
that UMSDOS would work better than loopback files with SpinRite's
"DynaStat" feature, but I haven't needed that yet.)
One interesting thing to do is to run "smartctl -a /dev/hdX" (from the
latest ucsc-smartsuite beta <http://csl.cse.ucsc.edu/smart.shtml>) and
observe the "Remapped Sector" and "Remapped Event" counts (that is, the
raw numbers in the rightmost column of output) over time. In particular,
look at the difference before and after a SpinRite level 5 run.
I hope this helps.
-Barry K. Nathan <[email protected]>
"Mike A. Harris" wrote:
>
> Is this a hardware or software problem, or could it be either?
>
> Jul 26 23:51:59 asdf kernel: hda: dma_intr: status=0x51
> { DriveReady SeekComplete Error }
> Jul 26 23:51:59 asdf kernel: hda: dma_intr: error=0x40
> { UncorrectableError }, LBAsect=8545004, sector=62608
> Jul 26 23:51:59 asdf kernel: end_request: I/O error, dev 03:05
> (hda), sector 62608
>
> Just got it opening up a mail folder. Drive made a bit of noise
> and then PINE had to be killed.
>
> 2 root@asdf:~# hdparm -i /dev/hda
>
> /dev/hda:
>
> Model=IBM-DTLA-307030, FwRev=TX4OA50C, SerialNo=YKDYKGF1437
Ah, one of these excellent Hungarian DTLA drives? :) AFAIK, the entire batch
was broken, although there are people who insist that there was no single
working hard drive leaving that factory! I personally have seen 7 out of 7
failing...
Take it back to where you bought it and demand a replacement for something
NOT bearing "MADE IN HUNGARY" sign.
cheers,
Milek
--
mailto:[email protected] | "Man in the Moon and other weird things" -
http://wfmh.org.pl/~thorgal/ | see it at http://wfmh.org.pl/~thorgal/Moon/
Fight for the good cause: http://www.laubzega.com/dvd/
> Is this a hardware or software problem, or could it be either?
>
> Jul 26 23:51:59 asdf kernel: hda: dma_intr: status=0x51
> { DriveReady SeekComplete Error }
> Jul 26 23:51:59 asdf kernel: hda: dma_intr: error=0x40
> { UncorrectableError }, LBAsect=8545004, sector=62608
> Jul 26 23:51:59 asdf kernel: end_request: I/O error, dev 03:05
> (hda), sector 62608
The uncorrectable error came from the drive itself. The sector number is in
range so I suspect its a real disk error.
Alan
> > Model=IBM-DTLA-307030, FwRev=TX4OA50C, SerialNo=YKDYKGF1437
>
> Ah, one of these excellent Hungarian DTLA drives? :) AFAIK, the entire batch
> was broken, although there are people who insist that there was no single
> working hard drive leaving that factory! I personally have seen 7 out of 7
> failing...
I have a large collection of these drives and none of them are problematic,
while the maxtors seem a little less reliable
> Take it back to where you bought it and demand a replacement for something
> NOT bearing "MADE IN HUNGARY" sign.
Of course the writer of this is Polish and the drives are Hungarian ..
Alan
do you know if the ones made in thailand have the same problem ?
On Fri, 27 Jul 2001, Miloslaw Smyk wrote:
> "Mike A. Harris" wrote:
> >
> > Is this a hardware or software problem, or could it be either?
> >
> > Jul 26 23:51:59 asdf kernel: hda: dma_intr: status=0x51
> > { DriveReady SeekComplete Error }
> > Jul 26 23:51:59 asdf kernel: hda: dma_intr: error=0x40
> > { UncorrectableError }, LBAsect=8545004, sector=62608
> > Jul 26 23:51:59 asdf kernel: end_request: I/O error, dev 03:05
> > (hda), sector 62608
> >
> > Just got it opening up a mail folder. Drive made a bit of noise
> > and then PINE had to be killed.
> >
> > 2 root@asdf:~# hdparm -i /dev/hda
> >
> > /dev/hda:
> >
> > Model=IBM-DTLA-307030, FwRev=TX4OA50C, SerialNo=YKDYKGF1437
>
> Ah, one of these excellent Hungarian DTLA drives? :) AFAIK, the entire batch
> was broken, although there are people who insist that there was no single
> working hard drive leaving that factory! I personally have seen 7 out of 7
> failing...
>
> Take it back to where you bought it and demand a replacement for something
> NOT bearing "MADE IN HUNGARY" sign.
>
> cheers,
> Milek
> --
> mailto:[email protected] | "Man in the Moon and other weird things" -
> http://wfmh.org.pl/~thorgal/ | see it at http://wfmh.org.pl/~thorgal/Moon/
> Fight for the good cause: http://www.laubzega.com/dvd/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Alan Cox wrote:
>
> > > Model=IBM-DTLA-307030, FwRev=TX4OA50C, SerialNo=YKDYKGF1437
> >
> > Ah, one of these excellent Hungarian DTLA drives? :) AFAIK, the entire batch
> > was broken, although there are people who insist that there was no single
> > working hard drive leaving that factory! I personally have seen 7 out of 7
> > failing...
>
> I have a large collection of these drives and none of them are problematic,
> while the maxtors seem a little less reliable
>
> > Take it back to where you bought it and demand a replacement for something
> > NOT bearing "MADE IN HUNGARY" sign.
>
> Of course the writer of this is Polish and the drives are Hungarian ..
>
But he is right. Practically all the "Made in Hungary" ones develop bad
sectors after a few months. The "Made in Phillipinnes" ones do not.
Strangely, I am Hong Kong and almost all the GXP75s we got here were
made in Hungary - go figure! They were so bad the dealers finally
wouldn't stock them. If your experience has been different, think
yourself lucky.
Regards,
Steve
>>>>> "Steve" == Steve Underwood <[email protected]> writes:
Steve> But he is right. Practically all the "Made in Hungary" ones
Steve> develop bad sectors after a few months. The "Made in
Steve> Phillipinnes" ones do not. Strangely, I am Hong Kong and
Steve> almost all the GXP75s we got here were made in Hungary - go
Steve> figure! They were so bad the dealers finally wouldn't stock
Steve> them. If your experience has been different, think yourself
Steve> lucky.
I have an IBM drive made in Hungary. It get `fiery hot'! I kept
moving it until I had it in a place with good thermal contact to the
case. Then these drive errors went away. At first I had a Linux
install on that drive. Later it crashed, I fixed it, deleted the OS
on my HDA that I was no longer using and moved Linux there. Now I
only keep MP3s, tmp, and swap (a 2nd one) on the IBM drive.
Sometimes when I close the case, I still get errors. So it may be a
case of overheating. You could try to change the position of the drive
to see if it fixes things. Mine was made in Hungary. And in case (ha ha)
I am talking crap,
[bpringle@localhost bpringle]$ dmesg | grep ^hdd:
hdd: IBM-DTTA-351010, ATA DISK drive
hdd: 19807200 sectors (10141 MB) w/466KiB Cache, CHS=19650/16/63, UDMA(33)
Model=IBM-DTTA-351010, FwRev=T56OA73A, SerialNo=WF0WFFD7387
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=34
BuffType=3(DualPortCache), BuffSize=466kB, MaxMultSect=16, MultSect=off
DblWordIO=no, maxPIO=2(fast), DMA=yes, maxDMA=2(fast)
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=19807200
WARNING 3293136 ORPHANED SECTORS :: KERNEL REPORTING ERROR
tDMA={min:120,rec:120}, DMA modes: sword0 sword1 sword2 mword0 mword1 mword2
IORDY=on/off, tPIO={min:240,w/IORDY:120}, PIO modes: mode3 mode4
UDMA modes: mode0 mode1 *mode2
Drive Supports : ATA/ATAPI-4 T13 1153D revision 17 : ATA-1 ATA-2 ATA-3 ATA-4
fwiw,
Bill Pringlemeir.