Quite some months ago I raised some questions, got some answers and
continued working silently until my problem was solved. While digging
the archives for yet another IDE problem today I realized I did
not send any message to you guys nor to the list afterwards.
Just in case someone is interested or cares still:
1) Sorry for not sending a "problem solved" mail when it was solved
2) My box is running smoothly again. It was neither a kernel issue
nor a hardware problem with the disks. Different kernel versions
did behave differently, but the cause of it all seems to be a broken
CPU (or broken jumper settings).
Installing a new CPU made all problems go away. And the box is
rock solid with or without IDE-DMA turned on.
Regards
Florian
P.S: A little block quoted below in case someone wants to remember what
this was about:
On 16 Sep 2002 15:46:35 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Mon, 2002-09-16 at 15:26, Florian Hinzmann wrote:
> >
> > On 16-Sep-2002 Alan Cox wrote:
> > > On Mon, 2002-09-16 at 12:17, Florian Hinzmann wrote:
> > >> kernel: hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
> > >> kernel: hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=97567071, high=5, lo
> > >> kernel: hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
> > >
> > > Which is the drive reporting a physical media error
> >
> > Which seems to exist only while using the named combinations of DMA access
> > and kernel versions. While using i.e. 2.4.19 without DMA I can access the same data,
> > dd the whole disk to /dev/null or run badblock checks without finding
> > any physical media errors.
> >
> > 2.4.19 should complain, too, if there is a physical error indeed, right?
>
> The "sectoridnotfound" return is from the drive. That makes it very hard
> to believe it isnt a physical error
>
-- Florian Hinzmann private: f.hinzmann@hamburg.de Debian: fh@debian.org PGP Key / ID: 1024D/B4071A65 Fingerprint : F9AB 00C1 3E3A 8125 DD3F DF1C DF79 A374 B407 1A65 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/