> If software than provoke your disks to think they have bad blocks, your
> disks a certainly broken. [There may be another error somewhere in linux,
> but theres at least one error in the hw.]
Agree, but still no reason to lock solid. That IS a bug.
>
Hi!
> > > Sep 21 23:55:44 fs1 kernel: hdb: timeout waiting for DMA
> > > Sep 21 23:55:44 fs1 kernel: hdb: irq timeout: status=0xd0 { Busy }
> > > Sep 21 23:55:44 fs1 kernel: hda: DMA disabled
>
> Perhaps some timeouts are not set correctly or the specs include some errors, but
> it is very stran
On Fri, Sep 22, 2000 at 12:03:30PM -0700, Andre Hedrick wrote:
> On Fri, 22 Sep 2000, Andries Brouwer wrote:
>
> > Here 1.4 MB is wasted on hdb because the BIOS has invented
> > this 1229/255/63 translation. The disk access methods on
> > hdb and hdc is the same.
>
> Yes, and soon CHS will go aw
On Fri, 22 Sep 2000, Andre Hedrick wrote:
> On Fri, 22 Sep 2000, Andries Brouwer wrote:
>
> > Here 1.4 MB is wasted on hdb because the BIOS has invented
> > this 1229/255/63 translation. The disk access methods on
> > hdb and hdc is the same.
>
> Yes, and soon CHS will go away completely with 4
>
> > Do you have stuff logged about trying to access out of range blocks ?
Putting primary to secondary slave (two UDMA devices on the same
bus) fixed the lockup.
The second drive was ginging errors in some cases, and sometimes it
didn't. Was the reason I couldn't reproduce the unrecoverable e
On Fri, 22 Sep 2000, Andries Brouwer wrote:
> Here 1.4 MB is wasted on hdb because the BIOS has invented
> this 1229/255/63 translation. The disk access methods on
> hdb and hdc is the same.
Yes, and soon CHS will go away completely with 48-bit LBA or if you CHS
these large drives. I considered
On Fri, 22 Sep 2000, Andries Brouwer wrote:
> On Fri, Sep 22, 2000 at 02:34:16PM +0200, Igmar Palsenberg wrote:
>
> > It could be that it is choking on the fact that one drives is LBA, one
> > drive isn't. Drives are identical, but dmesg gives different CHS for each
> > of them..
>
> A FAQ. See
On Fri, Sep 22, 2000 at 02:34:16PM +0200, Igmar Palsenberg wrote:
> It could be that it is choking on the fact that one drives is LBA, one
> drive isn't. Drives are identical, but dmesg gives different CHS for each
> of them..
A FAQ. See
http://www.win.tue.nl/~aeb/linux/Large-Disk-14.htm
> Do you have stuff logged about trying to access out of range blocks ?
No. It start to bark about the DMA mode and then dies.
Igmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://w
> This is the following problem
>
> hda: Maxtor 71626 AP, 1554MB w/128kB Cache, CHS=789/64/63, DMA
> hdb: Maxtor 91021U2, 9641MB w/512kB Cache, CHS=1229/255/63, (U)DMA
> hdc: Maxtor 91021U2, 9641MB w/512kB Cache, CHS=19590/16/63, (U)DMA
I'll put both UDMA drives on ide1 and kick it's ass again.
On Fri, 22 Sep 2000, Carsten Lang wrote:
> i don't think that we can blame the disks!
> I have 3 different drives, which produce this error after 24 hrs under heavy load.
This one chokes after about 10 mins. Total meltdown. Drives are brandnew,
so I doubt the failure.
If I md5sum the files aft
On Fri, 22 Sep 2000, Alan Cox wrote:
> > This machine is running 2.2.17aa2 (I needed LFS), and I'm able to lock it
> > hard. This is what was in the logs :
> >
> > Sep 21 23:55:38 fs1 kernel: hdc: dma_intr: status=0x51 { DriveReady
> > SeekComplete Error }
>
> A disk seek failed
>
> > Sep 21 2
> > Uncorrectable error is the drive.
>
> i don't think that we can blame the disks!
Uncorrectable error is the drive. Its not something the kernel can directly
get wrong nor is it timing. It is possible it occurred because the kernel asked
for something silly.
Do you have stuff logged about t
Why don't you try my patches ontop and thin see what happens.
Then you are claiming heavy loads.
Go grab the smart-suite off of source-forge and see if you crapped out the
drives.
On Fri, 22 Sep 2000, Carsten Lang wrote:
> Hi Alan,
>
> > Uncorrectable error is the drive.
> >
>
> i don't t
Hi Alan,
> Uncorrectable error is the drive.
>
i don't think that we can blame the disks!
I have 3 different drives, which produce this error after 24 hrs under heavy load.
I'm very sure, that the whole IDE-stuff is broken under heavy load conditions, but i
can't find out, what happens exac
Hi,
This machine is running 2.2.17aa2 (I needed LFS), and I'm able to lock it
hard. This is what was in the logs :
Sep 21 23:55:38 fs1 kernel: hdc: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 21 23:55:38 fs1 kernel: hdc: dma_intr: error=0x40 { UncorrectableError
}, LBAsect=16373
16 matches
Mail list logo
