Re: DriveReady SeekComplete Error

Re: DriveReady SeekComplete Error

[mattia]

I have the following error (kernel 2.6.6):

Jun  4 08:05:43 blink kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Jun  4 08:05:43 blink kernel: hdc: Maxtor 6Y160P0, ATA DISK drive
Jun  4 08:05:43 blink kernel: hdd: Maxtor 6Y120L0, ATA DISK drive
Jun  4 08:05:43 blink kernel: ide1 at 0x170-0x177,0x376 on irq 15
Jun  4 08:05:43 blink kernel: hda: max request size: 128KiB
Jun  4 08:05:43 blink kernel: hda: 78177792 sectors (40027 MB) w/1819KiB
Cache, CHS=65535/16/63, UDMA(100)
Jun  4 08:05:43 blink kernel:  hda: hda1 hda2 hda3
Jun  4 08:05:43 blink kernel: hdc: max request size: 1024KiB
Jun  4 08:05:43 blink kernel: hdc: 320173056 sectors (163928 MB)
w/7936KiB Cache, CHS=19929/255/63, UDMA(100)
Jun  4 08:05:43 blink kernel:  hdc: hdc1
Jun  4 08:05:43 blink kernel: hdd: max request size: 128KiB
Jun  4 08:05:43 blink kernel: hdd: 240121728 sectors (122942 MB)
w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
Jun  4 08:05:43 blink kernel:  hdd: hdd1 hdd2 hdd3
Jun  4 08:05:43 blink kernel: hdd: task_no_data_intr: status=0x51 {
DriveReady SeekComplete Error }
Jun  4 08:05:43 blink kernel: hdd: task_no_data_intr: error=0x04 {
DriveStatusError }
Jun  4 08:05:43 blink kernel: hdd: Write Cache FAILED Flushing!


I found somewhere that's something wrong with that maxtor drive.
However, everything works fine.
Bye

> 
> (don't trim people from the cc list, thanks)
> 
> On Fri, Jun 04 2004, Rick Jansen wrote:
> > On Fri, Jun 04, 2004 at 11:59:00AM +0200, Jens Axboe wrote:
> > > 
> > > It is, what kernel are you using?
> > > 
> > > -- 
> > > Jens Axboe
> > 
> > This is 2.6.6.
> 
> The that's a known error, you should not worry about it. It's fixed in
> later kernels.
> 
> -- 
> Jens Axboe
> 
> -
> 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/
> 
> 

-- 

Re: DriveReady SeekComplete Error

[Jens Axboe]

damnit, don't trim the cc list!

On Fri, Jun 04 2004, mattia wrote:
> I have the following error (kernel 2.6.6):
> 
> Jun  4 08:05:43 blink kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> Jun  4 08:05:43 blink kernel: hdc: Maxtor 6Y160P0, ATA DISK drive
> Jun  4 08:05:43 blink kernel: hdd: Maxtor 6Y120L0, ATA DISK drive
> Jun  4 08:05:43 blink kernel: ide1 at 0x170-0x177,0x376 on irq 15
> Jun  4 08:05:43 blink kernel: hda: max request size: 128KiB
> Jun  4 08:05:43 blink kernel: hda: 78177792 sectors (40027 MB) w/1819KiB
> Cache, CHS=65535/16/63, UDMA(100)
> Jun  4 08:05:43 blink kernel:  hda: hda1 hda2 hda3
> Jun  4 08:05:43 blink kernel: hdc: max request size: 1024KiB
> Jun  4 08:05:43 blink kernel: hdc: 320173056 sectors (163928 MB)
> w/7936KiB Cache, CHS=19929/255/63, UDMA(100)
> Jun  4 08:05:43 blink kernel:  hdc: hdc1
> Jun  4 08:05:43 blink kernel: hdd: max request size: 128KiB
> Jun  4 08:05:43 blink kernel: hdd: 240121728 sectors (122942 MB)
> w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
> Jun  4 08:05:43 blink kernel:  hdd: hdd1 hdd2 hdd3
> Jun  4 08:05:43 blink kernel: hdd: task_no_data_intr: status=0x51 {
> DriveReady SeekComplete Error }
> Jun  4 08:05:43 blink kernel: hdd: task_no_data_intr: error=0x04 {
> DriveStatusError }
> Jun  4 08:05:43 blink kernel: hdd: Write Cache FAILED Flushing!
> 
> 
> I found somewhere that's something wrong with that maxtor drive.
> However, everything works fine.

There's nothing wrong with the drive technically, it's just odd (lba48
without FLUSH_CACHE_EXT). It's really a linux ide bug that's fixed in
newer kernels. 2.6.7 will fix your problem.

-- 
Jens Axboe

Re: DriveReady SeekComplete Error

[Bartlomiej Zolnierkiewicz]

On Friday 04 of June 2004 12:22, Jens Axboe wrote:
> damnit, don't trim the cc list!
>
> On Fri, Jun 04 2004, mattia wrote:
> > I have the following error (kernel 2.6.6):
> >
> > Jun  4 08:05:43 blink kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> > Jun  4 08:05:43 blink kernel: hdc: Maxtor 6Y160P0, ATA DISK drive
> > Jun  4 08:05:43 blink kernel: hdd: Maxtor 6Y120L0, ATA DISK drive
> > Jun  4 08:05:43 blink kernel: ide1 at 0x170-0x177,0x376 on irq 15
> > Jun  4 08:05:43 blink kernel: hda: max request size: 128KiB
> > Jun  4 08:05:43 blink kernel: hda: 78177792 sectors (40027 MB) w/1819KiB
> > Cache, CHS=65535/16/63, UDMA(100)
> > Jun  4 08:05:43 blink kernel:  hda: hda1 hda2 hda3
> > Jun  4 08:05:43 blink kernel: hdc: max request size: 1024KiB
> > Jun  4 08:05:43 blink kernel: hdc: 320173056 sectors (163928 MB)
> > w/7936KiB Cache, CHS=19929/255/63, UDMA(100)
> > Jun  4 08:05:43 blink kernel:  hdc: hdc1
> > Jun  4 08:05:43 blink kernel: hdd: max request size: 128KiB
> > Jun  4 08:05:43 blink kernel: hdd: 240121728 sectors (122942 MB)
> > w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
> > Jun  4 08:05:43 blink kernel:  hdd: hdd1 hdd2 hdd3
> > Jun  4 08:05:43 blink kernel: hdd: task_no_data_intr: status=0x51 {
> > DriveReady SeekComplete Error }
> > Jun  4 08:05:43 blink kernel: hdd: task_no_data_intr: error=0x04 {
> > DriveStatusError }
> > Jun  4 08:05:43 blink kernel: hdd: Write Cache FAILED Flushing!
> >
> >
> > I found somewhere that's something wrong with that maxtor drive.
> > However, everything works fine.
>
> There's nothing wrong with the drive technically, it's just odd (lba48
> without FLUSH_CACHE_EXT). It's really a linux ide bug that's fixed in
> newer kernels. 2.6.7 will fix your problem.

Wrong.

Bug is a combination of a very minor firmware quirk
and lack of strict checking in Linux IDE driver.

FLUSH_CACHE_EXT bit is set but it is not supported
(but it is not a problem because LBA48 is not supported also).

It is fixed in 2.6.7-rc1 but your IDE barrier patch has this problem
(just reminding you that it is still not fixed in 2.6.7-rc2-mm2).

Cheers,
Bartlomiej

Re: DriveReady SeekComplete Error

[Jens Axboe]

On Fri, Jun 04 2004, Bartlomiej Zolnierkiewicz wrote:
> On Friday 04 of June 2004 12:22, Jens Axboe wrote:
> > damnit, don't trim the cc list!
> >
> > On Fri, Jun 04 2004, mattia wrote:
> > > I have the following error (kernel 2.6.6):
> > >
> > > Jun  4 08:05:43 blink kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> > > Jun  4 08:05:43 blink kernel: hdc: Maxtor 6Y160P0, ATA DISK drive
> > > Jun  4 08:05:43 blink kernel: hdd: Maxtor 6Y120L0, ATA DISK drive
> > > Jun  4 08:05:43 blink kernel: ide1 at 0x170-0x177,0x376 on irq 15
> > > Jun  4 08:05:43 blink kernel: hda: max request size: 128KiB
> > > Jun  4 08:05:43 blink kernel: hda: 78177792 sectors (40027 MB) w/1819KiB
> > > Cache, CHS=65535/16/63, UDMA(100)
> > > Jun  4 08:05:43 blink kernel:  hda: hda1 hda2 hda3
> > > Jun  4 08:05:43 blink kernel: hdc: max request size: 1024KiB
> > > Jun  4 08:05:43 blink kernel: hdc: 320173056 sectors (163928 MB)
> > > w/7936KiB Cache, CHS=19929/255/63, UDMA(100)
> > > Jun  4 08:05:43 blink kernel:  hdc: hdc1
> > > Jun  4 08:05:43 blink kernel: hdd: max request size: 128KiB
> > > Jun  4 08:05:43 blink kernel: hdd: 240121728 sectors (122942 MB)
> > > w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
> > > Jun  4 08:05:43 blink kernel:  hdd: hdd1 hdd2 hdd3
> > > Jun  4 08:05:43 blink kernel: hdd: task_no_data_intr: status=0x51 {
> > > DriveReady SeekComplete Error }
> > > Jun  4 08:05:43 blink kernel: hdd: task_no_data_intr: error=0x04 {
> > > DriveStatusError }
> > > Jun  4 08:05:43 blink kernel: hdd: Write Cache FAILED Flushing!
> > >
> > >
> > > I found somewhere that's something wrong with that maxtor drive.
> > > However, everything works fine.
> >
> > There's nothing wrong with the drive technically, it's just odd (lba48
> > without FLUSH_CACHE_EXT). It's really a linux ide bug that's fixed in
> > newer kernels. 2.6.7 will fix your problem.
> 
> Wrong.
> 
> Bug is a combination of a very minor firmware quirk
> and lack of strict checking in Linux IDE driver.
> 
> FLUSH_CACHE_EXT bit is set but it is not supported
> (but it is not a problem because LBA48 is not supported also).

Ah my bad, I didn't realize this bit was actually set correctly (you
mean (cfs_enable_2 & 0x2400) == 0x2400 is actually true?).

> It is fixed in 2.6.7-rc1 but your IDE barrier patch has this problem
> (just reminding you that it is still not fixed in 2.6.7-rc2-mm2).

So where's the bug? I don't see it...

-- 
Jens Axboe

Re: DriveReady SeekComplete Error

[Bartlomiej Zolnierkiewicz]

On Friday 04 of June 2004 13:56, Jens Axboe wrote:
> On Fri, Jun 04 2004, Bartlomiej Zolnierkiewicz wrote:
> > On Friday 04 of June 2004 12:22, Jens Axboe wrote:
> > > damnit, don't trim the cc list!
> > >
> > > On Fri, Jun 04 2004, mattia wrote:
> > > > I have the following error (kernel 2.6.6):
> > > >
> > > > Jun  4 08:05:43 blink kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> > > > Jun  4 08:05:43 blink kernel: hdc: Maxtor 6Y160P0, ATA DISK drive
> > > > Jun  4 08:05:43 blink kernel: hdd: Maxtor 6Y120L0, ATA DISK drive
> > > > Jun  4 08:05:43 blink kernel: ide1 at 0x170-0x177,0x376 on irq 15
> > > > Jun  4 08:05:43 blink kernel: hda: max request size: 128KiB
> > > > Jun  4 08:05:43 blink kernel: hda: 78177792 sectors (40027 MB)
> > > > w/1819KiB Cache, CHS=65535/16/63, UDMA(100)
> > > > Jun  4 08:05:43 blink kernel:  hda: hda1 hda2 hda3
> > > > Jun  4 08:05:43 blink kernel: hdc: max request size: 1024KiB
> > > > Jun  4 08:05:43 blink kernel: hdc: 320173056 sectors (163928 MB)
> > > > w/7936KiB Cache, CHS=19929/255/63, UDMA(100)
> > > > Jun  4 08:05:43 blink kernel:  hdc: hdc1
> > > > Jun  4 08:05:43 blink kernel: hdd: max request size: 128KiB
> > > > Jun  4 08:05:43 blink kernel: hdd: 240121728 sectors (122942 MB)
> > > > w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
> > > > Jun  4 08:05:43 blink kernel:  hdd: hdd1 hdd2 hdd3
> > > > Jun  4 08:05:43 blink kernel: hdd: task_no_data_intr: status=0x51 {
> > > > DriveReady SeekComplete Error }
> > > > Jun  4 08:05:43 blink kernel: hdd: task_no_data_intr: error=0x04 {
> > > > DriveStatusError }
> > > > Jun  4 08:05:43 blink kernel: hdd: Write Cache FAILED Flushing!
> > > >
> > > >
> > > > I found somewhere that's something wrong with that maxtor drive.
> > > > However, everything works fine.
> > >
> > > There's nothing wrong with the drive technically, it's just odd (lba48
> > > without FLUSH_CACHE_EXT). It's really a linux ide bug that's fixed in
> > > newer kernels. 2.6.7 will fix your problem.
> >
> > Wrong.
> >
> > Bug is a combination of a very minor firmware quirk
> > and lack of strict checking in Linux IDE driver.
> >
> > FLUSH_CACHE_EXT bit is set but it is not supported
> > (but it is not a problem because LBA48 is not supported also).
>
> Ah my bad, I didn't realize this bit was actually set correctly (you
> mean (cfs_enable_2 & 0x2400) == 0x2400 is actually true?).

Yes but only on unaffected drives. ;-)

0x2000 is FLUSH_CACHE_EXT support
0x0400 is LBA48 support

Affected drives have 0x2000 set incorrectly so we have to check also 0x0400.
(== 0x2400 is needed because & 0x2400 is true if & 0x2000 OR if & 0x0400).

Everything is explained in the patch changelog:

| - many Maxtor disks incorrectly claim CACHE FLUSH EXT command support,
|   fix it by checking both CACHE FLUSH EXT command and LBA48 support
|   (thanks to Eric D. Mudama for help in fixing this)

and in the patch itself:

+/* some Maxtor disks have bit 13 defined incorrectly so check bit 10 too */
+#define ide_id_has_flush_cache_ext(id)	\
+	(((id)->cfs_enable_2 & 0x2400) == 0x2400)

> > It is fixed in 2.6.7-rc1 but your IDE barrier patch has this problem
> > (just reminding you that it is still not fixed in 2.6.7-rc2-mm2).
>
> So where's the bug? I don't see it...

ide_fill_flush_cmd()

+	if (drive->id->cfs_enable_2 & 0x2400)
+		rq->buffer[0] = WIN_FLUSH_CACHE_EXT;

Cheers,
Bartlomiej

Re: DriveReady SeekComplete Error

[Jens Axboe]

On Fri, Jun 04 2004, Bartlomiej Zolnierkiewicz wrote:
> On Friday 04 of June 2004 13:56, Jens Axboe wrote:
> > On Fri, Jun 04 2004, Bartlomiej Zolnierkiewicz wrote:
> > > On Friday 04 of June 2004 12:22, Jens Axboe wrote:
> > > > damnit, don't trim the cc list!
> > > >
> > > > On Fri, Jun 04 2004, mattia wrote:
> > > > > I have the following error (kernel 2.6.6):
> > > > >
> > > > > Jun  4 08:05:43 blink kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> > > > > Jun  4 08:05:43 blink kernel: hdc: Maxtor 6Y160P0, ATA DISK drive
> > > > > Jun  4 08:05:43 blink kernel: hdd: Maxtor 6Y120L0, ATA DISK drive
> > > > > Jun  4 08:05:43 blink kernel: ide1 at 0x170-0x177,0x376 on irq 15
> > > > > Jun  4 08:05:43 blink kernel: hda: max request size: 128KiB
> > > > > Jun  4 08:05:43 blink kernel: hda: 78177792 sectors (40027 MB)
> > > > > w/1819KiB Cache, CHS=65535/16/63, UDMA(100)
> > > > > Jun  4 08:05:43 blink kernel:  hda: hda1 hda2 hda3
> > > > > Jun  4 08:05:43 blink kernel: hdc: max request size: 1024KiB
> > > > > Jun  4 08:05:43 blink kernel: hdc: 320173056 sectors (163928 MB)
> > > > > w/7936KiB Cache, CHS=19929/255/63, UDMA(100)
> > > > > Jun  4 08:05:43 blink kernel:  hdc: hdc1
> > > > > Jun  4 08:05:43 blink kernel: hdd: max request size: 128KiB
> > > > > Jun  4 08:05:43 blink kernel: hdd: 240121728 sectors (122942 MB)
> > > > > w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
> > > > > Jun  4 08:05:43 blink kernel:  hdd: hdd1 hdd2 hdd3
> > > > > Jun  4 08:05:43 blink kernel: hdd: task_no_data_intr: status=0x51 {
> > > > > DriveReady SeekComplete Error }
> > > > > Jun  4 08:05:43 blink kernel: hdd: task_no_data_intr: error=0x04 {
> > > > > DriveStatusError }
> > > > > Jun  4 08:05:43 blink kernel: hdd: Write Cache FAILED Flushing!
> > > > >
> > > > >
> > > > > I found somewhere that's something wrong with that maxtor drive.
> > > > > However, everything works fine.
> > > >
> > > > There's nothing wrong with the drive technically, it's just odd (lba48
> > > > without FLUSH_CACHE_EXT). It's really a linux ide bug that's fixed in
> > > > newer kernels. 2.6.7 will fix your problem.
> > >
> > > Wrong.
> > >
> > > Bug is a combination of a very minor firmware quirk
> > > and lack of strict checking in Linux IDE driver.
> > >
> > > FLUSH_CACHE_EXT bit is set but it is not supported
> > > (but it is not a problem because LBA48 is not supported also).
> >
> > Ah my bad, I didn't realize this bit was actually set correctly (you
> > mean (cfs_enable_2 & 0x2400) == 0x2400 is actually true?).
> 
> Yes but only on unaffected drives. ;-)
> 
> 0x2000 is FLUSH_CACHE_EXT support
> 0x0400 is LBA48 support
> 
> Affected drives have 0x2000 set incorrectly so we have to check also 0x0400.
> (== 0x2400 is needed because & 0x2400 is true if & 0x2000 OR if & 0x0400).
> 
> Everything is explained in the patch changelog:
> 
> | - many Maxtor disks incorrectly claim CACHE FLUSH EXT command support,
> |   fix it by checking both CACHE FLUSH EXT command and LBA48 support
> |   (thanks to Eric D. Mudama for help in fixing this)
> 
> and in the patch itself:
> 
> +/* some Maxtor disks have bit 13 defined incorrectly so check bit 10 too */
> +#define ide_id_has_flush_cache_ext(id)	\
> +	(((id)->cfs_enable_2 & 0x2400) == 0x2400)

Ok, so I didn't miss anything. Was just wondering because of your
comment on -mm2.

> > > It is fixed in 2.6.7-rc1 but your IDE barrier patch has this problem
> > > (just reminding you that it is still not fixed in 2.6.7-rc2-mm2).
> >
> > So where's the bug? I don't see it...
> 
> ide_fill_flush_cmd()
> 
> +	if (drive->id->cfs_enable_2 & 0x2400)
> +		rq->buffer[0] = WIN_FLUSH_CACHE_EXT;

Just checked a fresh copy of 2.6.7-rc2-mm2, and it has it correctly:

static void ide_fill_flush_cmd(ide_drive_t *drive, struct request *rq)
{
        char *buf = rq->cmd;

        /*
         * reuse cdb space for ata command
         */
        memset(buf, 0, sizeof(rq->cmd));

        rq->flags |= REQ_DRIVE_TASK | REQ_STARTED;
        rq->buffer = buf;
        rq->buffer[0] = WIN_FLUSH_CACHE;

        if (ide_id_has_flush_cache_ext(drive->id))
                rq->buffer[0] = WIN_FLUSH_CACHE_EXT;
}

So that's why I didn't follow what you meant, there should be no problem
here. You are reading disk-barrier-ide.patch, barrier-update.patch is
applied on top of that.

So we are back to step 1, why is his drive complaining. I'm guessing it
doesn't have write back caching enabled and aborts the flush on those
grounds - Ed, what is the output of hdparm -i on your booted system?

-- 
Jens Axboe

Re: DriveReady SeekComplete Error

[Bartlomiej Zolnierkiewicz]

On Friday 04 of June 2004 14:17, Jens Axboe wrote:
> On Fri, Jun 04 2004, Bartlomiej Zolnierkiewicz wrote:
> > On Friday 04 of June 2004 13:56, Jens Axboe wrote:
> > > On Fri, Jun 04 2004, Bartlomiej Zolnierkiewicz wrote:
> > > > On Friday 04 of June 2004 12:22, Jens Axboe wrote:
> > > > > damnit, don't trim the cc list!
> > > > >
> > > > > On Fri, Jun 04 2004, mattia wrote:
> > > > > > I have the following error (kernel 2.6.6):
> > > > > >
> > > > > > Jun  4 08:05:43 blink kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> > > > > > Jun  4 08:05:43 blink kernel: hdc: Maxtor 6Y160P0, ATA DISK drive
> > > > > > Jun  4 08:05:43 blink kernel: hdd: Maxtor 6Y120L0, ATA DISK drive
> > > > > > Jun  4 08:05:43 blink kernel: ide1 at 0x170-0x177,0x376 on irq 15
> > > > > > Jun  4 08:05:43 blink kernel: hda: max request size: 128KiB
> > > > > > Jun  4 08:05:43 blink kernel: hda: 78177792 sectors (40027 MB)
> > > > > > w/1819KiB Cache, CHS=65535/16/63, UDMA(100)
> > > > > > Jun  4 08:05:43 blink kernel:  hda: hda1 hda2 hda3
> > > > > > Jun  4 08:05:43 blink kernel: hdc: max request size: 1024KiB
> > > > > > Jun  4 08:05:43 blink kernel: hdc: 320173056 sectors (163928 MB)
> > > > > > w/7936KiB Cache, CHS=19929/255/63, UDMA(100)
> > > > > > Jun  4 08:05:43 blink kernel:  hdc: hdc1
> > > > > > Jun  4 08:05:43 blink kernel: hdd: max request size: 128KiB
> > > > > > Jun  4 08:05:43 blink kernel: hdd: 240121728 sectors (122942 MB)
> > > > > > w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
> > > > > > Jun  4 08:05:43 blink kernel:  hdd: hdd1 hdd2 hdd3
> > > > > > Jun  4 08:05:43 blink kernel: hdd: task_no_data_intr: status=0x51
> > > > > > { DriveReady SeekComplete Error }
> > > > > > Jun  4 08:05:43 blink kernel: hdd: task_no_data_intr: error=0x04
> > > > > > { DriveStatusError }
> > > > > > Jun  4 08:05:43 blink kernel: hdd: Write Cache FAILED Flushing!
> > > > > >
> > > > > >
> > > > > > I found somewhere that's something wrong with that maxtor drive.
> > > > > > However, everything works fine.
> > > > >
> > > > > There's nothing wrong with the drive technically, it's just odd
> > > > > (lba48 without FLUSH_CACHE_EXT). It's really a linux ide bug that's
> > > > > fixed in newer kernels. 2.6.7 will fix your problem.
> > > >
> > > > Wrong.
> > > >
> > > > Bug is a combination of a very minor firmware quirk
> > > > and lack of strict checking in Linux IDE driver.
> > > >
> > > > FLUSH_CACHE_EXT bit is set but it is not supported
> > > > (but it is not a problem because LBA48 is not supported also).
> > >
> > > Ah my bad, I didn't realize this bit was actually set correctly (you
> > > mean (cfs_enable_2 & 0x2400) == 0x2400 is actually true?).
> >
> > Yes but only on unaffected drives. ;-)
> >
> > 0x2000 is FLUSH_CACHE_EXT support
> > 0x0400 is LBA48 support
> >
> > Affected drives have 0x2000 set incorrectly so we have to check also
> > 0x0400. (== 0x2400 is needed because & 0x2400 is true if & 0x2000 OR if &
> > 0x0400).
> >
> > Everything is explained in the patch changelog:
> > | - many Maxtor disks incorrectly claim CACHE FLUSH EXT command support,
> > |   fix it by checking both CACHE FLUSH EXT command and LBA48 support
> > |   (thanks to Eric D. Mudama for help in fixing this)
> >
> > and in the patch itself:
> >
> > +/* some Maxtor disks have bit 13 defined incorrectly so check bit 10 too
> > */ +#define ide_id_has_flush_cache_ext(id)	\
> > +	(((id)->cfs_enable_2 & 0x2400) == 0x2400)
>
> Ok, so I didn't miss anything. Was just wondering because of your
> comment on -mm2.
>
> > > > It is fixed in 2.6.7-rc1 but your IDE barrier patch has this problem
> > > > (just reminding you that it is still not fixed in 2.6.7-rc2-mm2).
> > >
> > > So where's the bug? I don't see it...
> >
> > ide_fill_flush_cmd()
> >
> > +	if (drive->id->cfs_enable_2 & 0x2400)
> > +		rq->buffer[0] = WIN_FLUSH_CACHE_EXT;
>
> Just checked a fresh copy of 2.6.7-rc2-mm2, and it has it correctly:
>
> static void ide_fill_flush_cmd(ide_drive_t *drive, struct request *rq)
> {
>         char *buf = rq->cmd;
>
>         /*
>          * reuse cdb space for ata command
>          */
>         memset(buf, 0, sizeof(rq->cmd));
>
>         rq->flags |= REQ_DRIVE_TASK | REQ_STARTED;
>         rq->buffer = buf;
>         rq->buffer[0] = WIN_FLUSH_CACHE;
>
>         if (ide_id_has_flush_cache_ext(drive->id))
>                 rq->buffer[0] = WIN_FLUSH_CACHE_EXT;
> }
>
> So that's why I didn't follow what you meant, there should be no problem
> here. You are reading disk-barrier-ide.patch, barrier-update.patch is
> applied on top of that.

Hehe, indeed, my bad.

> So we are back to step 1, why is his drive complaining. I'm guessing it

Yep.

> doesn't have write back caching enabled and aborts the flush on those
> grounds - Ed, what is the output of hdparm -i on your booted system?

Re: DriveReady SeekComplete Error

[Ed Tomlinson]

On June 4, 2004 08:17 am, Jens Axboe wrote:
> So we are back to step 1, why is his drive complaining. I'm guessing it
> doesn't have write back caching enabled and aborts the flush on those
> grounds - Ed, what is the output of hdparm -i on your booted system?

On 2.6.7-rc2 its:

Ed

root@bert:/home/knoppix# hdparm -iI /dev/hda

/dev/hda:

 Model=WDC AC26400R, FwRev=15.01J15, SerialNo=WD-WM6271600165
 Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
 RawCHS=13328/15/63, TrkSize=57600, SectSize=600, ECCbytes=40
 BuffType=DualPortCache, BuffSize=512kB, MaxMultSect=16, MultSect=16
 CurCHS=13328/15/63, CurSects=12594960, LBA=yes, LBAsects=12594960
 IORDY=on/off, tPIO={min:160,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
 AdvancedPM=no WriteCache=enabled
 Drive conforms to: device does not report version:  1 2 3 4

 * signifies the current active mode


ATA device, with non-removable media
        Model Number:       WDC AC26400R
        Serial Number:      WD-WM6271600165
        Firmware Revision:  15.01J15
Standards:
        Supported: 4 3 2 1
        Likely used: 4
Configuration:
        Logical         max     current
        cylinders       13328   13328
        heads           15      15
        sectors/track   63      63
        --
        bytes/track: 57600      bytes/sector: 600
        CHS current addressable sectors:   12594960
        LBA    user addressable sectors:   12594960
        device size with M = 1024*1024:        6149 MBytes
        device size with M = 1000*1000:        6448 MBytes (6 GB)
Capabilities:
        LBA, IORDY(can be disabled)
        Buffer size: 512.0kB    bytes avail on r/w long: 40     Queue depth: 1
        Standby timer values: spec'd by Standard, no device specific minimum
        R/W multiple sector transfer: Max = 16  Current = 16
        DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
             Cycle time: no flow control=160ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
           *    READ BUFFER cmd
           *    WRITE BUFFER cmd
           *    Look-ahead
           *    Write cache
           *    Power Management feature set
           *    SMART feature set

Re: DriveReady SeekComplete Error

[Eric D. Mudama]

>Jun  4 08:05:43 blink kernel: hdd: task_no_data_intr: status=0x51 {
>DriveReady SeekComplete Error }
>Jun  4 08:05:43 blink kernel: hdd: task_no_data_intr: error=0x04 {
>DriveStatusError }
>Jun  4 08:05:43 blink kernel: hdd: Write Cache FAILED Flushing!

That is a known issue in older driver versions that should be resolved
now.  It only affects our latest generation of drives that are <=
120GB, it will not affect the larger drives (>= 160GB), and it won't
affect any drives of the next product generation because I fixed the
root cause in the drive as well as helping identify a driver
workaround/fix.

error=0x04 is an "abort" and not a critical error

The original note had error=0x40, which is an Uncorrectable ECC
error... that is bad, and you should probably RMA the drive.

You can also try to see if you can "fix" it by writing to that LBA
(obviously backup your data first) and see if the error goes
away... if that is the case, the ECC could have been due to a write
splice at power failure or some other transient event (extreme shock
or heat or something)

If there are a lot of ECC errors (you have them in about 2 places)
which could be a sign of bad things in progress, just RMA the drive.

--eric


-- 
Eric D. Mudama
edmudama@mail.bounceswoosh.org

Re: DriveReady SeekComplete Error

[mattia]

Eric D. Mudama wrote:

>> Jun  4 08:05:43 blink kernel: hdd: task_no_data_intr: status=0x51 {
>> DriveReady SeekComplete Error }
>> Jun  4 08:05:43 blink kernel: hdd: task_no_data_intr: error=0x04 {
>> DriveStatusError }
>> Jun  4 08:05:43 blink kernel: hdd: Write Cache FAILED Flushing!
>
>
> That is a known issue in older driver versions that should be resolved
> now.  It only affects our latest generation of drives that are <=
> 120GB, it will not affect the larger drives (>= 160GB), and it won't
> affect any drives of the next product generation because I fixed the
> root cause in the drive as well as helping identify a driver
> workaround/fix.
>
> error=0x04 is an "abort" and not a critical error
>
> The original note had error=0x40, which is an Uncorrectable ECC
> error... that is bad, and you should probably RMA the drive.
>
> You can also try to see if you can "fix" it by writing to that LBA
> (obviously backup your data first) and see if the error goes
> away... if that is the case, the ECC could have been due to a write
> splice at power failure or some other transient event (extreme shock
> or heat or something)
>
> If there are a lot of ECC errors (you have them in about 2 places)
> which could be a sign of bad things in progress, just RMA the drive.
>
> --eric
>
>
I use that drive normally, smartctl does not report errors.
That error was not displayed before: I don't remember, but maybe with 
the 2.6.5 kernel (is that possible?) - now i run the 2.6.6

Bye

RE: DriveReady SeekComplete Error...

[Piszcz, Justin Michael]

Hrmm, does anyone else have that same drive or chipset you use, do they
also experience the problem?

What is the exact model of the drive and what chipset do you use?

cd /proc/ide/hda ; cat model

lspci -vvv # as root

-----Original Message-----
From: Dwayne Rightler [mailto:drightler@technicalogic.com] 
Sent: Tuesday, July 13, 2004 11:58 AM
To: Piszcz, Justin Michael; linux-kernel@vger.kernel.org
Cc: Dhruv Matani
Subject: Re: DriveReady SeekComplete Error...

The CONFIG_IDEDISK_MULTI_MODE setting makes no difference as seen below:

demigod:~# uname -a
Linux demigod 2.6.7-kexec #2 Tue Jul 13 08:31:56 CDT 2004 i686 GNU/Linux

demigod:~# zgrep CONFIG_IDEDISK_MULTI_MODE /proc/config.gz
CONFIG_IDEDISK_MULTI_MODE=y

demigod:~# dmesg | grep ^hda
hda: SAMSUNG SV2044D, ATA DISK drive
hda: max request size: 128KiB
hda: 39862368 sectors (20409 MB) w/472KiB Cache, CHS=39546/16/63
hda: DMA disabled
hda: dma_timer_expiry: dma status == 0x61
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete
DataRequest }
hda: dma_timer_expiry: dma status == 0x61
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete
DataRequest }
hda: dma_timer_expiry: dma status == 0x61
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete
DataRequest }
hda: DMA disabled

##########################################

demigod:~# uname -a
Linux demigod 2.6.7-kexec #1 Mon Jul 5 11:30:36 CDT 2004 i686 GNU/Linux

demigod:~# zgrep CONFIG_IDEDISK_MULTI_MODE /proc/config.gz
# CONFIG_IDEDISK_MULTI_MODE is not set

demigod:~# dmesg | grep ^hda
hda: SAMSUNG SV2044D, ATA DISK drive
hda: max request size: 128KiB
hda: 39862368 sectors (20409 MB) w/472KiB Cache, CHS=39546/16/63
hda: DMA disabled
hda: dma_timer_expiry: dma status == 0x61
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete
DataRequest }
hda: dma_timer_expiry: dma status == 0x61
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete
DataRequest }
hda: DMA disabled
hda: dma_timer_expiry: dma status == 0x41
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete
DataRequest }
hda: dma_timer_expiry: dma status == 0x61
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete
DataRequest }
----- Original Message ----- 
From: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
To: "Dwayne Rightler" <drightler@technicalogic.com>;
<linux-kernel@vger.kernel.org>
Cc: "Dhruv Matani" <dhruvbird@gmx.net>
Sent: Tuesday, July 13, 2004 7:44 AM
Subject: RE: DriveReady SeekComplete Error...


> <*>     Include IDE/ATA-2 DISK support
> [*]       Use multi-mode by default
>
> Have you tried recompiling the kernel and checking off the second
option
> show above?
>
> CONFIG_IDEDISK_MULTI_MODE
> If you get this error, try to say Y here:
> hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
> hda: set_multmode: error=0x04 { DriveStatusError }
> If in doubt, say N.
>
>
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Dwayne
Rightler
> Sent: Tuesday, July 13, 2004 8:33 AM
> To: linux-kernel@vger.kernel.org
> Cc: Dhruv Matani
> Subject: Re: DriveReady SeekComplete Error...
>
> I have a similar problem with a Samsung hard drive. Model SV2044D.
The
> output of 'hdparm -i' below indicates it supports several multiword
and
> ultra DMA modes but if i run the drive in anything other than PIO mode
> it
> gets DMA timeouts and SeekComplete Errors.  This has been on every
> kernel I
> can recall in the 2.4 and 2.6 series.
>
> demigod:~# hdparm -i /dev/hda
>
> /dev/hda:
>
>  Model=SAMSUNG SV2044D, FwRev=MM200-53, SerialNo=0228J1FN905733
>  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
>  RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
>  BuffType=DualPortCache, BuffSize=472kB, MaxMultSect=16, MultSect=16
>  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39862368
>  IORDY=yes, 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
>  AdvancedPM=no WriteCache=enabled
>  Drive conforms to: ATA/ATAPI-4 T13 1153D revision 17:  1 2 3 4
>
>  * signifies the current active mode
>
>
>
> ----- Original Message ----- 
> From: "Dhruv Matani" <dhruvbird@gmx.net>
> To: <linux-kernel@vger.kernel.org>
> Sent: Tuesday, July 13, 2004 7:30 AM
> Subject: DriveReady SeekComplete Error...
>
>
> > Hi,
> > I've been getting this error for my brand new (2 months old) Samsung
> > HDD. The model Number is: SV0411N, and it is a 40GB disk. I'm using
> the
> > kernel version 2.4.20-8 provided by RedHat. When I used
RH-7.2(before
> > upgrading to RH-9), the same HDD worked fine. Also, when I
> re-installed
> > RH-7.2, it worked fine?
> >
> > Any suggestions?
> >
> > Please cc me the reply, sine I'm not subscribed.
> > Thanks ;-)
> >
> > -- 
> >         -Dhruv Matani.
> > http://www.geocities.com/dhruvbird/
> >
> > As a rule, man is a fool. When it's hot, he wants it cold.
> > When it's cold he wants it hot. He always wants what is not.
> > -Anon.
> >
> >
> > -
> > 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/
> >
>
> -
> 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/
> -
> 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/
>

Re: DriveReady SeekComplete Error...

[Dwayne Rightler]

[-- Attachment #1: Type: text/plain, Size: 7297 bytes --]

demigod:/proc/ide/hda# cat model
SAMSUNG SV2044D


lspci -vvv output is attached.  /dev/hda is attached to the VIA chipset.  I
have another hard drive /dev/hdb and a cdrom drive /dev/hdc connected to
that chipset as well and they can do DMA transfers.

The Promise controller has 2 hard drives hooked to it which can also do DMA
transfers.

Thanks,
Dwayne
----- Original Message ----- 
From: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
To: "Dwayne Rightler" <drightler@technicalogic.com>;
<linux-kernel@vger.kernel.org>
Cc: "Dhruv Matani" <dhruvbird@gmx.net>
Sent: Tuesday, July 13, 2004 12:23 PM
Subject: RE: DriveReady SeekComplete Error...


> Hrmm, does anyone else have that same drive or chipset you use, do they
> also experience the problem?
>
> What is the exact model of the drive and what chipset do you use?
>
> cd /proc/ide/hda ; cat model
>
> lspci -vvv # as root
>
> -----Original Message-----
> From: Dwayne Rightler [mailto:drightler@technicalogic.com]
> Sent: Tuesday, July 13, 2004 11:58 AM
> To: Piszcz, Justin Michael; linux-kernel@vger.kernel.org
> Cc: Dhruv Matani
> Subject: Re: DriveReady SeekComplete Error...
>
> The CONFIG_IDEDISK_MULTI_MODE setting makes no difference as seen below:
>
> demigod:~# uname -a
> Linux demigod 2.6.7-kexec #2 Tue Jul 13 08:31:56 CDT 2004 i686 GNU/Linux
>
> demigod:~# zgrep CONFIG_IDEDISK_MULTI_MODE /proc/config.gz
> CONFIG_IDEDISK_MULTI_MODE=y
>
> demigod:~# dmesg | grep ^hda
> hda: SAMSUNG SV2044D, ATA DISK drive
> hda: max request size: 128KiB
> hda: 39862368 sectors (20409 MB) w/472KiB Cache, CHS=39546/16/63
> hda: DMA disabled
> hda: dma_timer_expiry: dma status == 0x61
> hda: DMA timeout error
> hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> DataRequest }
> hda: dma_timer_expiry: dma status == 0x61
> hda: DMA timeout error
> hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> DataRequest }
> hda: dma_timer_expiry: dma status == 0x61
> hda: DMA timeout error
> hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> DataRequest }
> hda: DMA disabled
>
> ##########################################
>
> demigod:~# uname -a
> Linux demigod 2.6.7-kexec #1 Mon Jul 5 11:30:36 CDT 2004 i686 GNU/Linux
>
> demigod:~# zgrep CONFIG_IDEDISK_MULTI_MODE /proc/config.gz
> # CONFIG_IDEDISK_MULTI_MODE is not set
>
> demigod:~# dmesg | grep ^hda
> hda: SAMSUNG SV2044D, ATA DISK drive
> hda: max request size: 128KiB
> hda: 39862368 sectors (20409 MB) w/472KiB Cache, CHS=39546/16/63
> hda: DMA disabled
> hda: dma_timer_expiry: dma status == 0x61
> hda: DMA timeout error
> hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> DataRequest }
> hda: dma_timer_expiry: dma status == 0x61
> hda: DMA timeout error
> hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> DataRequest }
> hda: DMA disabled
> hda: dma_timer_expiry: dma status == 0x41
> hda: DMA timeout error
> hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> DataRequest }
> hda: dma_timer_expiry: dma status == 0x61
> hda: DMA timeout error
> hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> DataRequest }
> ----- Original Message ----- 
> From: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
> To: "Dwayne Rightler" <drightler@technicalogic.com>;
> <linux-kernel@vger.kernel.org>
> Cc: "Dhruv Matani" <dhruvbird@gmx.net>
> Sent: Tuesday, July 13, 2004 7:44 AM
> Subject: RE: DriveReady SeekComplete Error...
>
>
> > <*>     Include IDE/ATA-2 DISK support
> > [*]       Use multi-mode by default
> >
> > Have you tried recompiling the kernel and checking off the second
> option
> > show above?
> >
> > CONFIG_IDEDISK_MULTI_MODE
> > If you get this error, try to say Y here:
> > hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
> > hda: set_multmode: error=0x04 { DriveStatusError }
> > If in doubt, say N.
> >
> >
> > -----Original Message-----
> > From: linux-kernel-owner@vger.kernel.org
> > [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Dwayne
> Rightler
> > Sent: Tuesday, July 13, 2004 8:33 AM
> > To: linux-kernel@vger.kernel.org
> > Cc: Dhruv Matani
> > Subject: Re: DriveReady SeekComplete Error...
> >
> > I have a similar problem with a Samsung hard drive. Model SV2044D.
> The
> > output of 'hdparm -i' below indicates it supports several multiword
> and
> > ultra DMA modes but if i run the drive in anything other than PIO mode
> > it
> > gets DMA timeouts and SeekComplete Errors.  This has been on every
> > kernel I
> > can recall in the 2.4 and 2.6 series.
> >
> > demigod:~# hdparm -i /dev/hda
> >
> > /dev/hda:
> >
> >  Model=SAMSUNG SV2044D, FwRev=MM200-53, SerialNo=0228J1FN905733
> >  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> >  RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
> >  BuffType=DualPortCache, BuffSize=472kB, MaxMultSect=16, MultSect=16
> >  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39862368
> >  IORDY=yes, 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
> >  AdvancedPM=no WriteCache=enabled
> >  Drive conforms to: ATA/ATAPI-4 T13 1153D revision 17:  1 2 3 4
> >
> >  * signifies the current active mode
> >
> >
> >
> > ----- Original Message ----- 
> > From: "Dhruv Matani" <dhruvbird@gmx.net>
> > To: <linux-kernel@vger.kernel.org>
> > Sent: Tuesday, July 13, 2004 7:30 AM
> > Subject: DriveReady SeekComplete Error...
> >
> >
> > > Hi,
> > > I've been getting this error for my brand new (2 months old) Samsung
> > > HDD. The model Number is: SV0411N, and it is a 40GB disk. I'm using
> > the
> > > kernel version 2.4.20-8 provided by RedHat. When I used
> RH-7.2(before
> > > upgrading to RH-9), the same HDD worked fine. Also, when I
> > re-installed
> > > RH-7.2, it worked fine?
> > >
> > > Any suggestions?
> > >
> > > Please cc me the reply, sine I'm not subscribed.
> > > Thanks ;-)
> > >
> > > -- 
> > >         -Dhruv Matani.
> > > http://www.geocities.com/dhruvbird/
> > >
> > > As a rule, man is a fool. When it's hot, he wants it cold.
> > > When it's cold he wants it hot. He always wants what is not.
> > > -Anon.
> > >
> > >
> > > -
> > > 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/
> > >
> >
> > -
> > 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/
> > -
> > 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/
> >
>
> -
> 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/
>

[-- Attachment #2: lspci-output.gz --]
[-- Type: application/x-gzip, Size: 1821 bytes --]

Re: DriveReady SeekComplete Error...

[Dhruv Matani]

[-- Attachment #1: Type: text/plain, Size: 8219 bytes --]

On Thu, 2004-07-15 at 01:40, Dwayne Rightler wrote:
> demigod:/proc/ide/hda# cat model
> SAMSUNG SV2044D

I have: SAMSUNG SV0411N

> 
> 
> lspci -vvv output is attached.  /dev/hda is attached to the VIA chipset.  I
> have another hard drive /dev/hdb and a cdrom drive /dev/hdc connected to
> that chipset as well and they can do DMA transfers.
> 
> The Promise controller has 2 hard drives hooked to it which can also do DMA
> transfers.

I have attached my configuration too. The HDD is connected to the
primary master cable, and I have 2 cd-roms (One cd-writer connected to
Secondary slave), and the cd-reader connected to the secondary master
cable.

> 
> Thanks,
> Dwayne
> ----- Original Message ----- 
> From: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
> To: "Dwayne Rightler" <drightler@technicalogic.com>;
> <linux-kernel@vger.kernel.org>
> Cc: "Dhruv Matani" <dhruvbird@gmx.net>
> Sent: Tuesday, July 13, 2004 12:23 PM
> Subject: RE: DriveReady SeekComplete Error...
> 
> 
> > Hrmm, does anyone else have that same drive or chipset you use, do they
> > also experience the problem?
> >
> > What is the exact model of the drive and what chipset do you use?
> >
> > cd /proc/ide/hda ; cat model
> >
> > lspci -vvv # as root
> >
> > -----Original Message-----
> > From: Dwayne Rightler [mailto:drightler@technicalogic.com]
> > Sent: Tuesday, July 13, 2004 11:58 AM
> > To: Piszcz, Justin Michael; linux-kernel@vger.kernel.org
> > Cc: Dhruv Matani
> > Subject: Re: DriveReady SeekComplete Error...
> >
> > The CONFIG_IDEDISK_MULTI_MODE setting makes no difference as seen below:
> >
> > demigod:~# uname -a
> > Linux demigod 2.6.7-kexec #2 Tue Jul 13 08:31:56 CDT 2004 i686 GNU/Linux
> >
> > demigod:~# zgrep CONFIG_IDEDISK_MULTI_MODE /proc/config.gz
> > CONFIG_IDEDISK_MULTI_MODE=y
> >
> > demigod:~# dmesg | grep ^hda
> > hda: SAMSUNG SV2044D, ATA DISK drive
> > hda: max request size: 128KiB
> > hda: 39862368 sectors (20409 MB) w/472KiB Cache, CHS=39546/16/63
> > hda: DMA disabled
> > hda: dma_timer_expiry: dma status == 0x61
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > hda: dma_timer_expiry: dma status == 0x61
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > hda: dma_timer_expiry: dma status == 0x61
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > hda: DMA disabled
> >
> > ##########################################
> >
> > demigod:~# uname -a
> > Linux demigod 2.6.7-kexec #1 Mon Jul 5 11:30:36 CDT 2004 i686 GNU/Linux
> >
> > demigod:~# zgrep CONFIG_IDEDISK_MULTI_MODE /proc/config.gz
> > # CONFIG_IDEDISK_MULTI_MODE is not set
> >
> > demigod:~# dmesg | grep ^hda
> > hda: SAMSUNG SV2044D, ATA DISK drive
> > hda: max request size: 128KiB
> > hda: 39862368 sectors (20409 MB) w/472KiB Cache, CHS=39546/16/63
> > hda: DMA disabled
> > hda: dma_timer_expiry: dma status == 0x61
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > hda: dma_timer_expiry: dma status == 0x61
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > hda: DMA disabled
> > hda: dma_timer_expiry: dma status == 0x41
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > hda: dma_timer_expiry: dma status == 0x61
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > ----- Original Message ----- 
> > From: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
> > To: "Dwayne Rightler" <drightler@technicalogic.com>;
> > <linux-kernel@vger.kernel.org>
> > Cc: "Dhruv Matani" <dhruvbird@gmx.net>
> > Sent: Tuesday, July 13, 2004 7:44 AM
> > Subject: RE: DriveReady SeekComplete Error...
> >
> >
> > > <*>     Include IDE/ATA-2 DISK support
> > > [*]       Use multi-mode by default
> > >
> > > Have you tried recompiling the kernel and checking off the second
> > option
> > > show above?
> > >
> > > CONFIG_IDEDISK_MULTI_MODE
> > > If you get this error, try to say Y here:
> > > hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
> > > hda: set_multmode: error=0x04 { DriveStatusError }
> > > If in doubt, say N.
> > >
> > >
> > > -----Original Message-----
> > > From: linux-kernel-owner@vger.kernel.org
> > > [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Dwayne
> > Rightler
> > > Sent: Tuesday, July 13, 2004 8:33 AM
> > > To: linux-kernel@vger.kernel.org
> > > Cc: Dhruv Matani
> > > Subject: Re: DriveReady SeekComplete Error...
> > >
> > > I have a similar problem with a Samsung hard drive. Model SV2044D.
> > The
> > > output of 'hdparm -i' below indicates it supports several multiword
> > and
> > > ultra DMA modes but if i run the drive in anything other than PIO mode
> > > it
> > > gets DMA timeouts and SeekComplete Errors.  This has been on every
> > > kernel I
> > > can recall in the 2.4 and 2.6 series.
> > >
> > > demigod:~# hdparm -i /dev/hda
> > >
> > > /dev/hda:
> > >
> > >  Model=SAMSUNG SV2044D, FwRev=MM200-53, SerialNo=0228J1FN905733
> > >  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> > >  RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
> > >  BuffType=DualPortCache, BuffSize=472kB, MaxMultSect=16, MultSect=16
> > >  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39862368
> > >  IORDY=yes, 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
> > >  AdvancedPM=no WriteCache=enabled
> > >  Drive conforms to: ATA/ATAPI-4 T13 1153D revision 17:  1 2 3 4
> > >
> > >  * signifies the current active mode
> > >
> > >
> > >
> > > ----- Original Message ----- 
> > > From: "Dhruv Matani" <dhruvbird@gmx.net>
> > > To: <linux-kernel@vger.kernel.org>
> > > Sent: Tuesday, July 13, 2004 7:30 AM
> > > Subject: DriveReady SeekComplete Error...
> > >
> > >
> > > > Hi,
> > > > I've been getting this error for my brand new (2 months old) Samsung
> > > > HDD. The model Number is: SV0411N, and it is a 40GB disk. I'm using
> > > the
> > > > kernel version 2.4.20-8 provided by RedHat. When I used
> > RH-7.2(before
> > > > upgrading to RH-9), the same HDD worked fine. Also, when I
> > > re-installed
> > > > RH-7.2, it worked fine?
> > > >
> > > > Any suggestions?
> > > >
> > > > Please cc me the reply, sine I'm not subscribed.
> > > > Thanks ;-)
> > > >
> > > > -- 
> > > >         -Dhruv Matani.
> > > > http://www.geocities.com/dhruvbird/
> > > >
> > > > As a rule, man is a fool. When it's hot, he wants it cold.
> > > > When it's cold he wants it hot. He always wants what is not.
> > > > -Anon.
> > > >
> > > >
> > > > -
> > > > 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/
> > > >
> > >
> > > -
> > > 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/
> > > -
> > > 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/
> > >
> >
> > -
> > 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/
> >
-- 
        -Dhruv Matani.
http://www.geocities.com/dhruvbird/

As a rule, man is a fool. When it's hot, he wants it cold. 
When it's cold he wants it hot. He always wants what is not.
	-Anon.


[-- Attachment #2: lspci_output.gz --]
[-- Type: application/x-gzip, Size: 1151 bytes --]

Re: DriveReady SeekComplete Error...

[Dhruv Matani]

Hi,
        I think I've gotten to the bottom of the matter. It turns out
that from
2.4.0, Kernel keeps DMA enabled by default, while previous versions had
it disabled by default. And Samsung Hard Disks have some whacky
non-standard interface, which is not supported, so every time the kernel
tried to do the DMA hand-shaking dance with the HDD, it got confused,
and reset the HDD. However, DMA data transfers were working at a slower
speed. So, I decided to disable DMA by re-compiling the kernel with the
Default DMA switch disable.. And viola, all the DMA errors vanished,
however data transfer became significantly slower, and every time the
ext3 journal was commited to the disk, XMMS would hang! This was
amazing, so currently I am running a kernel with DMA disabled by
default, but as soon as RedHat takes over, it enables DMA! So no kernel
errors and I also get the speed benefit!

Hope this works!

Anyone know why this works! (If at all?)

-Dhruv.


On Thu, 2004-07-15 at 01:40, Dwayne Rightler wrote:
> demigod:/proc/ide/hda# cat model
> SAMSUNG SV2044D
> 
> 
> lspci -vvv output is attached.  /dev/hda is attached to the VIA chipset.  I
> have another hard drive /dev/hdb and a cdrom drive /dev/hdc connected to
> that chipset as well and they can do DMA transfers.
> 
> The Promise controller has 2 hard drives hooked to it which can also do DMA
> transfers.
> 
> Thanks,
> Dwayne
> ----- Original Message ----- 
> From: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
> To: "Dwayne Rightler" <drightler@technicalogic.com>;
> <linux-kernel@vger.kernel.org>
> Cc: "Dhruv Matani" <dhruvbird@gmx.net>
> Sent: Tuesday, July 13, 2004 12:23 PM
> Subject: RE: DriveReady SeekComplete Error...
> 
> 
> > Hrmm, does anyone else have that same drive or chipset you use, do they
> > also experience the problem?
> >
> > What is the exact model of the drive and what chipset do you use?
> >
> > cd /proc/ide/hda ; cat model
> >
> > lspci -vvv # as root
> >
> > -----Original Message-----
> > From: Dwayne Rightler [mailto:drightler@technicalogic.com]
> > Sent: Tuesday, July 13, 2004 11:58 AM
> > To: Piszcz, Justin Michael; linux-kernel@vger.kernel.org
> > Cc: Dhruv Matani
> > Subject: Re: DriveReady SeekComplete Error...
> >
> > The CONFIG_IDEDISK_MULTI_MODE setting makes no difference as seen below:
> >
> > demigod:~# uname -a
> > Linux demigod 2.6.7-kexec #2 Tue Jul 13 08:31:56 CDT 2004 i686 GNU/Linux
> >
> > demigod:~# zgrep CONFIG_IDEDISK_MULTI_MODE /proc/config.gz
> > CONFIG_IDEDISK_MULTI_MODE=y
> >
> > demigod:~# dmesg | grep ^hda
> > hda: SAMSUNG SV2044D, ATA DISK drive
> > hda: max request size: 128KiB
> > hda: 39862368 sectors (20409 MB) w/472KiB Cache, CHS=39546/16/63
> > hda: DMA disabled
> > hda: dma_timer_expiry: dma status == 0x61
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > hda: dma_timer_expiry: dma status == 0x61
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > hda: dma_timer_expiry: dma status == 0x61
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > hda: DMA disabled
> >
> > ##########################################
> >
> > demigod:~# uname -a
> > Linux demigod 2.6.7-kexec #1 Mon Jul 5 11:30:36 CDT 2004 i686 GNU/Linux
> >
> > demigod:~# zgrep CONFIG_IDEDISK_MULTI_MODE /proc/config.gz
> > # CONFIG_IDEDISK_MULTI_MODE is not set
> >
> > demigod:~# dmesg | grep ^hda
> > hda: SAMSUNG SV2044D, ATA DISK drive
> > hda: max request size: 128KiB
> > hda: 39862368 sectors (20409 MB) w/472KiB Cache, CHS=39546/16/63
> > hda: DMA disabled
> > hda: dma_timer_expiry: dma status == 0x61
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > hda: dma_timer_expiry: dma status == 0x61
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > hda: DMA disabled
> > hda: dma_timer_expiry: dma status == 0x41
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > hda: dma_timer_expiry: dma status == 0x61
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > ----- Original Message ----- 
> > From: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
> > To: "Dwayne Rightler" <drightler@technicalogic.com>;
> > <linux-kernel@vger.kernel.org>
> > Cc: "Dhruv Matani" <dhruvbird@gmx.net>
> > Sent: Tuesday, July 13, 2004 7:44 AM
> > Subject: RE: DriveReady SeekComplete Error...
> >
> >
> > > <*>     Include IDE/ATA-2 DISK support
> > > [*]       Use multi-mode by default
> > >
> > > Have you tried recompiling the kernel and checking off the second
> > option
> > > show above?
> > >
> > > CONFIG_IDEDISK_MULTI_MODE
> > > If you get this error, try to say Y here:
> > > hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
> > > hda: set_multmode: error=0x04 { DriveStatusError }
> > > If in doubt, say N.
> > >
> > >
> > > -----Original Message-----
> > > From: linux-kernel-owner@vger.kernel.org
> > > [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Dwayne
> > Rightler
> > > Sent: Tuesday, July 13, 2004 8:33 AM
> > > To: linux-kernel@vger.kernel.org
> > > Cc: Dhruv Matani
> > > Subject: Re: DriveReady SeekComplete Error...
> > >
> > > I have a similar problem with a Samsung hard drive. Model SV2044D.
> > The
> > > output of 'hdparm -i' below indicates it supports several multiword
> > and
> > > ultra DMA modes but if i run the drive in anything other than PIO mode
> > > it
> > > gets DMA timeouts and SeekComplete Errors.  This has been on every
> > > kernel I
> > > can recall in the 2.4 and 2.6 series.
> > >
> > > demigod:~# hdparm -i /dev/hda
> > >
> > > /dev/hda:
> > >
> > >  Model=SAMSUNG SV2044D, FwRev=MM200-53, SerialNo=0228J1FN905733
> > >  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> > >  RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
> > >  BuffType=DualPortCache, BuffSize=472kB, MaxMultSect=16, MultSect=16
> > >  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39862368
> > >  IORDY=yes, 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
> > >  AdvancedPM=no WriteCache=enabled
> > >  Drive conforms to: ATA/ATAPI-4 T13 1153D revision 17:  1 2 3 4
> > >
> > >  * signifies the current active mode
> > >
> > >
> > >
> > > ----- Original Message ----- 
> > > From: "Dhruv Matani" <dhruvbird@gmx.net>
> > > To: <linux-kernel@vger.kernel.org>
> > > Sent: Tuesday, July 13, 2004 7:30 AM
> > > Subject: DriveReady SeekComplete Error...
> > >
> > >
> > > > Hi,
> > > > I've been getting this error for my brand new (2 months old) Samsung
> > > > HDD. The model Number is: SV0411N, and it is a 40GB disk. I'm using
> > > the
> > > > kernel version 2.4.20-8 provided by RedHat. When I used
> > RH-7.2(before
> > > > upgrading to RH-9), the same HDD worked fine. Also, when I
> > > re-installed
> > > > RH-7.2, it worked fine?
> > > >
> > > > Any suggestions?
> > > >
> > > > Please cc me the reply, sine I'm not subscribed.
> > > > Thanks ;-)
> > > >
> > > > -- 
> > > >         -Dhruv Matani.
> > > > http://www.geocities.com/dhruvbird/
> > > >
> > > > As a rule, man is a fool. When it's hot, he wants it cold.
> > > > When it's cold he wants it hot. He always wants what is not.
> > > > -Anon.
> > > >
> > > >
> > > > -

-- 
	-Dhruv Matani.
http://www.geocities.com/dhruvbird/

template<typename Signature>
  class CustomSignature : public Signature
{ };

Re: DriveReady SeekComplete Error...

[Dwayne Rightler]

demigod:/usr/src/linux-2.6.7-kexec# zgrep CONFIG_IDEDMA_PCI_AUTO
/proc/config.gz
# CONFIG_IDEDMA_PCI_AUTO is not set

I have DMA disabled by default in my kernel already and still have the
problem with the Samsung drive.

----- Original Message ----- 
From: "Dhruv Matani" <dhruvbird@gmx.net>
To: "Dwayne Rightler" <drightler@technicalogic.com>
Cc: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>;
<linux-kernel@vger.kernel.org>
Sent: Monday, July 26, 2004 9:32 AM
Subject: Re: DriveReady SeekComplete Error...


> Hi,
>         I think I've gotten to the bottom of the matter. It turns out
> that from
> 2.4.0, Kernel keeps DMA enabled by default, while previous versions had
> it disabled by default. And Samsung Hard Disks have some whacky
> non-standard interface, which is not supported, so every time the kernel
> tried to do the DMA hand-shaking dance with the HDD, it got confused,
> and reset the HDD. However, DMA data transfers were working at a slower
> speed. So, I decided to disable DMA by re-compiling the kernel with the
> Default DMA switch disable.. And viola, all the DMA errors vanished,
> however data transfer became significantly slower, and every time the
> ext3 journal was commited to the disk, XMMS would hang! This was
> amazing, so currently I am running a kernel with DMA disabled by
> default, but as soon as RedHat takes over, it enables DMA! So no kernel
> errors and I also get the speed benefit!
>
> Hope this works!
>
> Anyone know why this works! (If at all?)
>
> -Dhruv.
>
>
> On Thu, 2004-07-15 at 01:40, Dwayne Rightler wrote:
> > demigod:/proc/ide/hda# cat model
> > SAMSUNG SV2044D
> >
> >
> > lspci -vvv output is attached.  /dev/hda is attached to the VIA chipset.
I
> > have another hard drive /dev/hdb and a cdrom drive /dev/hdc connected to
> > that chipset as well and they can do DMA transfers.
> >
> > The Promise controller has 2 hard drives hooked to it which can also do
DMA
> > transfers.
> >
> > Thanks,
> > Dwayne
> > ----- Original Message ----- 
> > From: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
> > To: "Dwayne Rightler" <drightler@technicalogic.com>;
> > <linux-kernel@vger.kernel.org>
> > Cc: "Dhruv Matani" <dhruvbird@gmx.net>
> > Sent: Tuesday, July 13, 2004 12:23 PM
> > Subject: RE: DriveReady SeekComplete Error...
> >
> >
> > > Hrmm, does anyone else have that same drive or chipset you use, do
they
> > > also experience the problem?
> > >
> > > What is the exact model of the drive and what chipset do you use?
> > >
> > > cd /proc/ide/hda ; cat model
> > >
> > > lspci -vvv # as root
> > >
> > > -----Original Message-----
> > > From: Dwayne Rightler [mailto:drightler@technicalogic.com]
> > > Sent: Tuesday, July 13, 2004 11:58 AM
> > > To: Piszcz, Justin Michael; linux-kernel@vger.kernel.org
> > > Cc: Dhruv Matani
> > > Subject: Re: DriveReady SeekComplete Error...
> > >
> > > The CONFIG_IDEDISK_MULTI_MODE setting makes no difference as seen
below:
> > >
> > > demigod:~# uname -a
> > > Linux demigod 2.6.7-kexec #2 Tue Jul 13 08:31:56 CDT 2004 i686
GNU/Linux
> > >
> > > demigod:~# zgrep CONFIG_IDEDISK_MULTI_MODE /proc/config.gz
> > > CONFIG_IDEDISK_MULTI_MODE=y
> > >
> > > demigod:~# dmesg | grep ^hda
> > > hda: SAMSUNG SV2044D, ATA DISK drive
> > > hda: max request size: 128KiB
> > > hda: 39862368 sectors (20409 MB) w/472KiB Cache, CHS=39546/16/63
> > > hda: DMA disabled
> > > hda: dma_timer_expiry: dma status == 0x61
> > > hda: DMA timeout error
> > > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > > DataRequest }
> > > hda: dma_timer_expiry: dma status == 0x61
> > > hda: DMA timeout error
> > > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > > DataRequest }
> > > hda: dma_timer_expiry: dma status == 0x61
> > > hda: DMA timeout error
> > > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > > DataRequest }
> > > hda: DMA disabled
> > >
> > > ##########################################
> > >
> > > demigod:~# uname -a
> > > Linux demigod 2.6.7-kexec #1 Mon Jul 5 11:30:36 CDT 2004 i686
GNU/Linux
> > >
> > > demigod:~# zgrep CONFIG_IDEDISK_MULTI_MODE /proc/config.gz
> > > # CONFIG_IDEDISK_MULTI_MODE is not set
> > >
> > > demigod:~# dmesg | grep ^hda
> > > hda: SAMSUNG SV2044D, ATA DISK drive
> > > hda: max request size: 128KiB
> > > hda: 39862368 sectors (20409 MB) w/472KiB Cache, CHS=39546/16/63
> > > hda: DMA disabled
> > > hda: dma_timer_expiry: dma status == 0x61
> > > hda: DMA timeout error
> > > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > > DataRequest }
> > > hda: dma_timer_expiry: dma status == 0x61
> > > hda: DMA timeout error
> > > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > > DataRequest }
> > > hda: DMA disabled
> > > hda: dma_timer_expiry: dma status == 0x41
> > > hda: DMA timeout error
> > > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > > DataRequest }
> > > hda: dma_timer_expiry: dma status == 0x61
> > > hda: DMA timeout error
> > > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > > DataRequest }
> > > ----- Original Message ----- 
> > > From: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
> > > To: "Dwayne Rightler" <drightler@technicalogic.com>;
> > > <linux-kernel@vger.kernel.org>
> > > Cc: "Dhruv Matani" <dhruvbird@gmx.net>
> > > Sent: Tuesday, July 13, 2004 7:44 AM
> > > Subject: RE: DriveReady SeekComplete Error...
> > >
> > >
> > > > <*>     Include IDE/ATA-2 DISK support
> > > > [*]       Use multi-mode by default
> > > >
> > > > Have you tried recompiling the kernel and checking off the second
> > > option
> > > > show above?
> > > >
> > > > CONFIG_IDEDISK_MULTI_MODE
> > > > If you get this error, try to say Y here:
> > > > hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
> > > > hda: set_multmode: error=0x04 { DriveStatusError }
> > > > If in doubt, say N.
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: linux-kernel-owner@vger.kernel.org
> > > > [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Dwayne
> > > Rightler
> > > > Sent: Tuesday, July 13, 2004 8:33 AM
> > > > To: linux-kernel@vger.kernel.org
> > > > Cc: Dhruv Matani
> > > > Subject: Re: DriveReady SeekComplete Error...
> > > >
> > > > I have a similar problem with a Samsung hard drive. Model SV2044D.
> > > The
> > > > output of 'hdparm -i' below indicates it supports several multiword
> > > and
> > > > ultra DMA modes but if i run the drive in anything other than PIO
mode
> > > > it
> > > > gets DMA timeouts and SeekComplete Errors.  This has been on every
> > > > kernel I
> > > > can recall in the 2.4 and 2.6 series.
> > > >
> > > > demigod:~# hdparm -i /dev/hda
> > > >
> > > > /dev/hda:
> > > >
> > > >  Model=SAMSUNG SV2044D, FwRev=MM200-53, SerialNo=0228J1FN905733
> > > >  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> > > >  RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
> > > >  BuffType=DualPortCache, BuffSize=472kB, MaxMultSect=16, MultSect=16
> > > >  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39862368
> > > >  IORDY=yes, 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
> > > >  AdvancedPM=no WriteCache=enabled
> > > >  Drive conforms to: ATA/ATAPI-4 T13 1153D revision 17:  1 2 3 4
> > > >
> > > >  * signifies the current active mode
> > > >
> > > >
> > > >
> > > > ----- Original Message ----- 
> > > > From: "Dhruv Matani" <dhruvbird@gmx.net>
> > > > To: <linux-kernel@vger.kernel.org>
> > > > Sent: Tuesday, July 13, 2004 7:30 AM
> > > > Subject: DriveReady SeekComplete Error...
> > > >
> > > >
> > > > > Hi,
> > > > > I've been getting this error for my brand new (2 months old)
Samsung
> > > > > HDD. The model Number is: SV0411N, and it is a 40GB disk. I'm
using
> > > > the
> > > > > kernel version 2.4.20-8 provided by RedHat. When I used
> > > RH-7.2(before
> > > > > upgrading to RH-9), the same HDD worked fine. Also, when I
> > > > re-installed
> > > > > RH-7.2, it worked fine?
> > > > >
> > > > > Any suggestions?
> > > > >
> > > > > Please cc me the reply, sine I'm not subscribed.
> > > > > Thanks ;-)
> > > > >
> > > > > -- 
> > > > >         -Dhruv Matani.
> > > > > http://www.geocities.com/dhruvbird/
> > > > >
> > > > > As a rule, man is a fool. When it's hot, he wants it cold.
> > > > > When it's cold he wants it hot. He always wants what is not.
> > > > > -Anon.
> > > > >
> > > > >
> > > > > -
>
> -- 
> -Dhruv Matani.
> http://www.geocities.com/dhruvbird/
>
> template<typename Signature>
>   class CustomSignature : public Signature
> { };
>
>
> -
> 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/
>

Re: DriveReady SeekComplete Error...

[Dhruv Matani]

Hi everyone!
	Great news!
First of all I would like to say that there was something seriously
wrong with the kernel 2.4.20-8.

1. DMA was screwed up for Samsung disks at least.
2. When I disabled, DMA, I regularly go hda: lost interrupt errors.
3. My ATX power supply did not switch off the computer automatically.

However, on using the vanilla 2.4.20 kernel, all the above errors have
vanished, and also XMMS does not skip any more! I am using DMA by
enabling use DMA by default while building the kernel without any
errors!

I suspect that the timing considerations for these hdds was wrong
somewhere, and in the older kernel version, it was right. Please see if
this helps.

Regards,
-Dhruv.




On Thu, 2004-07-15 at 01:40, Dwayne Rightler wrote:
> demigod:/proc/ide/hda# cat model
> SAMSUNG SV2044D
> 
> 
> lspci -vvv output is attached.  /dev/hda is attached to the VIA chipset.  I
> have another hard drive /dev/hdb and a cdrom drive /dev/hdc connected to
> that chipset as well and they can do DMA transfers.
> 
> The Promise controller has 2 hard drives hooked to it which can also do DMA
> transfers.
> 
> Thanks,
> Dwayne
> ----- Original Message ----- 
> From: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
> To: "Dwayne Rightler" <drightler@technicalogic.com>;
> <linux-kernel@vger.kernel.org>
> Cc: "Dhruv Matani" <dhruvbird@gmx.net>
> Sent: Tuesday, July 13, 2004 12:23 PM
> Subject: RE: DriveReady SeekComplete Error...
> 
> 
> > Hrmm, does anyone else have that same drive or chipset you use, do they
> > also experience the problem?
> >
> > What is the exact model of the drive and what chipset do you use?
> >
> > cd /proc/ide/hda ; cat model
> >
> > lspci -vvv # as root
> >
> > -----Original Message-----
> > From: Dwayne Rightler [mailto:drightler@technicalogic.com]
> > Sent: Tuesday, July 13, 2004 11:58 AM
> > To: Piszcz, Justin Michael; linux-kernel@vger.kernel.org
> > Cc: Dhruv Matani
> > Subject: Re: DriveReady SeekComplete Error...
> >
> > The CONFIG_IDEDISK_MULTI_MODE setting makes no difference as seen below:
> >
> > demigod:~# uname -a
> > Linux demigod 2.6.7-kexec #2 Tue Jul 13 08:31:56 CDT 2004 i686 GNU/Linux
> >
> > demigod:~# zgrep CONFIG_IDEDISK_MULTI_MODE /proc/config.gz
> > CONFIG_IDEDISK_MULTI_MODE=y
> >
> > demigod:~# dmesg | grep ^hda
> > hda: SAMSUNG SV2044D, ATA DISK drive
> > hda: max request size: 128KiB
> > hda: 39862368 sectors (20409 MB) w/472KiB Cache, CHS=39546/16/63
> > hda: DMA disabled
> > hda: dma_timer_expiry: dma status == 0x61
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > hda: dma_timer_expiry: dma status == 0x61
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > hda: dma_timer_expiry: dma status == 0x61
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > hda: DMA disabled
> >
> > ##########################################
> >
> > demigod:~# uname -a
> > Linux demigod 2.6.7-kexec #1 Mon Jul 5 11:30:36 CDT 2004 i686 GNU/Linux
> >
> > demigod:~# zgrep CONFIG_IDEDISK_MULTI_MODE /proc/config.gz
> > # CONFIG_IDEDISK_MULTI_MODE is not set
> >
> > demigod:~# dmesg | grep ^hda
> > hda: SAMSUNG SV2044D, ATA DISK drive
> > hda: max request size: 128KiB
> > hda: 39862368 sectors (20409 MB) w/472KiB Cache, CHS=39546/16/63
> > hda: DMA disabled
> > hda: dma_timer_expiry: dma status == 0x61
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > hda: dma_timer_expiry: dma status == 0x61
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > hda: DMA disabled
> > hda: dma_timer_expiry: dma status == 0x41
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > hda: dma_timer_expiry: dma status == 0x61
> > hda: DMA timeout error
> > hda: dma timeout error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
> > ----- Original Message ----- 
> > From: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
> > To: "Dwayne Rightler" <drightler@technicalogic.com>;
> > <linux-kernel@vger.kernel.org>
> > Cc: "Dhruv Matani" <dhruvbird@gmx.net>
> > Sent: Tuesday, July 13, 2004 7:44 AM
> > Subject: RE: DriveReady SeekComplete Error...
> >
> >
> > > <*>     Include IDE/ATA-2 DISK support
> > > [*]       Use multi-mode by default
> > >
> > > Have you tried recompiling the kernel and checking off the second
> > option
> > > show above?
> > >
> > > CONFIG_IDEDISK_MULTI_MODE
> > > If you get this error, try to say Y here:
> > > hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
> > > hda: set_multmode: error=0x04 { DriveStatusError }
> > > If in doubt, say N.
> > >
> > >
> > > -----Original Message-----
> > > From: linux-kernel-owner@vger.kernel.org
> > > [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Dwayne
> > Rightler
> > > Sent: Tuesday, July 13, 2004 8:33 AM
> > > To: linux-kernel@vger.kernel.org
> > > Cc: Dhruv Matani
> > > Subject: Re: DriveReady SeekComplete Error...
> > >
> > > I have a similar problem with a Samsung hard drive. Model SV2044D.
> > The
> > > output of 'hdparm -i' below indicates it supports several multiword
> > and
> > > ultra DMA modes but if i run the drive in anything other than PIO mode
> > > it
> > > gets DMA timeouts and SeekComplete Errors.  This has been on every
> > > kernel I
> > > can recall in the 2.4 and 2.6 series.
> > >
> > > demigod:~# hdparm -i /dev/hda
> > >
> > > /dev/hda:
> > >
> > >  Model=SAMSUNG SV2044D, FwRev=MM200-53, SerialNo=0228J1FN905733
> > >  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> > >  RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
> > >  BuffType=DualPortCache, BuffSize=472kB, MaxMultSect=16, MultSect=16
> > >  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39862368
> > >  IORDY=yes, 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
> > >  AdvancedPM=no WriteCache=enabled
> > >  Drive conforms to: ATA/ATAPI-4 T13 1153D revision 17:  1 2 3 4
> > >
> > >  * signifies the current active mode
> > >
> > >
> > >
> > > ----- Original Message ----- 
> > > From: "Dhruv Matani" <dhruvbird@gmx.net>
> > > To: <linux-kernel@vger.kernel.org>
> > > Sent: Tuesday, July 13, 2004 7:30 AM
> > > Subject: DriveReady SeekComplete Error...
> > >
> > >
> > > > Hi,
> > > > I've been getting this error for my brand new (2 months old) Samsung
> > > > HDD. The model Number is: SV0411N, and it is a 40GB disk. I'm using
> > > the
> > > > kernel version 2.4.20-8 provided by RedHat. When I used
> > RH-7.2(before
> > > > upgrading to RH-9), the same HDD worked fine. Also, when I
> > > re-installed
> > > > RH-7.2, it worked fine?
> > > >
> > > > Any suggestions?
> > > >
> > > > Please cc me the reply, sine I'm not subscribed.
> > > > Thanks ;-)
> > > >
> > > > -- 
> > > >         -Dhruv Matani.
> > > > http://www.geocities.com/dhruvbird/
> > > >
> > > > As a rule, man is a fool. When it's hot, he wants it cold.
> > > > When it's cold he wants it hot. He always wants what is not.
> > > > -Anon.

-- 
        -Dhruv Matani.
http://www.geocities.com/dhruvbird/

The price of freedom is responsibility, but it's a bargain, because
freedom is priceless. ~ Hugh Downs

RE: DriveReady SeekComplete Error...

[Piszcz, Justin Michael]

<*>     Include IDE/ATA-2 DISK support  
[*]       Use multi-mode by default

Have you tried recompiling the kernel and checking off the second option
show above?

CONFIG_IDEDISK_MULTI_MODE
If you get this error, try to say Y here:
hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
hda: set_multmode: error=0x04 { DriveStatusError }
If in doubt, say N.


-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Dwayne Rightler
Sent: Tuesday, July 13, 2004 8:33 AM
To: linux-kernel@vger.kernel.org
Cc: Dhruv Matani
Subject: Re: DriveReady SeekComplete Error...

I have a similar problem with a Samsung hard drive. Model SV2044D.  The
output of 'hdparm -i' below indicates it supports several multiword and
ultra DMA modes but if i run the drive in anything other than PIO mode
it
gets DMA timeouts and SeekComplete Errors.  This has been on every
kernel I
can recall in the 2.4 and 2.6 series.

demigod:~# hdparm -i /dev/hda

/dev/hda:

 Model=SAMSUNG SV2044D, FwRev=MM200-53, SerialNo=0228J1FN905733
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
 RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
 BuffType=DualPortCache, BuffSize=472kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39862368
 IORDY=yes, 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
 AdvancedPM=no WriteCache=enabled
 Drive conforms to: ATA/ATAPI-4 T13 1153D revision 17:  1 2 3 4

 * signifies the current active mode



----- Original Message ----- 
From: "Dhruv Matani" <dhruvbird@gmx.net>
To: <linux-kernel@vger.kernel.org>
Sent: Tuesday, July 13, 2004 7:30 AM
Subject: DriveReady SeekComplete Error...


> Hi,
> I've been getting this error for my brand new (2 months old) Samsung
> HDD. The model Number is: SV0411N, and it is a 40GB disk. I'm using
the
> kernel version 2.4.20-8 provided by RedHat. When I used RH-7.2(before
> upgrading to RH-9), the same HDD worked fine. Also, when I
re-installed
> RH-7.2, it worked fine?
>
> Any suggestions?
>
> Please cc me the reply, sine I'm not subscribed.
> Thanks ;-)
>
> -- 
>         -Dhruv Matani.
> http://www.geocities.com/dhruvbird/
>
> As a rule, man is a fool. When it's hot, he wants it cold.
> When it's cold he wants it hot. He always wants what is not.
> -Anon.
>
>
> -
> 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/
>

-
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/

Re: DriveReady SeekComplete Error...

[Dwayne Rightler]

The CONFIG_IDEDISK_MULTI_MODE setting makes no difference as seen below:

demigod:~# uname -a
Linux demigod 2.6.7-kexec #2 Tue Jul 13 08:31:56 CDT 2004 i686 GNU/Linux

demigod:~# zgrep CONFIG_IDEDISK_MULTI_MODE /proc/config.gz
CONFIG_IDEDISK_MULTI_MODE=y

demigod:~# dmesg | grep ^hda
hda: SAMSUNG SV2044D, ATA DISK drive
hda: max request size: 128KiB
hda: 39862368 sectors (20409 MB) w/472KiB Cache, CHS=39546/16/63
hda: DMA disabled
hda: dma_timer_expiry: dma status == 0x61
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
hda: dma_timer_expiry: dma status == 0x61
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
hda: dma_timer_expiry: dma status == 0x61
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
hda: DMA disabled

##########################################

demigod:~# uname -a
Linux demigod 2.6.7-kexec #1 Mon Jul 5 11:30:36 CDT 2004 i686 GNU/Linux

demigod:~# zgrep CONFIG_IDEDISK_MULTI_MODE /proc/config.gz
# CONFIG_IDEDISK_MULTI_MODE is not set

demigod:~# dmesg | grep ^hda
hda: SAMSUNG SV2044D, ATA DISK drive
hda: max request size: 128KiB
hda: 39862368 sectors (20409 MB) w/472KiB Cache, CHS=39546/16/63
hda: DMA disabled
hda: dma_timer_expiry: dma status == 0x61
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
hda: dma_timer_expiry: dma status == 0x61
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
hda: DMA disabled
hda: dma_timer_expiry: dma status == 0x41
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
hda: dma_timer_expiry: dma status == 0x61
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
----- Original Message ----- 
From: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
To: "Dwayne Rightler" <drightler@technicalogic.com>;
<linux-kernel@vger.kernel.org>
Cc: "Dhruv Matani" <dhruvbird@gmx.net>
Sent: Tuesday, July 13, 2004 7:44 AM
Subject: RE: DriveReady SeekComplete Error...


> <*>     Include IDE/ATA-2 DISK support
> [*]       Use multi-mode by default
>
> Have you tried recompiling the kernel and checking off the second option
> show above?
>
> CONFIG_IDEDISK_MULTI_MODE
> If you get this error, try to say Y here:
> hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
> hda: set_multmode: error=0x04 { DriveStatusError }
> If in doubt, say N.
>
>
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Dwayne Rightler
> Sent: Tuesday, July 13, 2004 8:33 AM
> To: linux-kernel@vger.kernel.org
> Cc: Dhruv Matani
> Subject: Re: DriveReady SeekComplete Error...
>
> I have a similar problem with a Samsung hard drive. Model SV2044D.  The
> output of 'hdparm -i' below indicates it supports several multiword and
> ultra DMA modes but if i run the drive in anything other than PIO mode
> it
> gets DMA timeouts and SeekComplete Errors.  This has been on every
> kernel I
> can recall in the 2.4 and 2.6 series.
>
> demigod:~# hdparm -i /dev/hda
>
> /dev/hda:
>
>  Model=SAMSUNG SV2044D, FwRev=MM200-53, SerialNo=0228J1FN905733
>  Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
>  RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
>  BuffType=DualPortCache, BuffSize=472kB, MaxMultSect=16, MultSect=16
>  CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39862368
>  IORDY=yes, 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
>  AdvancedPM=no WriteCache=enabled
>  Drive conforms to: ATA/ATAPI-4 T13 1153D revision 17:  1 2 3 4
>
>  * signifies the current active mode
>
>
>
> ----- Original Message ----- 
> From: "Dhruv Matani" <dhruvbird@gmx.net>
> To: <linux-kernel@vger.kernel.org>
> Sent: Tuesday, July 13, 2004 7:30 AM
> Subject: DriveReady SeekComplete Error...
>
>
> > Hi,
> > I've been getting this error for my brand new (2 months old) Samsung
> > HDD. The model Number is: SV0411N, and it is a 40GB disk. I'm using
> the
> > kernel version 2.4.20-8 provided by RedHat. When I used RH-7.2(before
> > upgrading to RH-9), the same HDD worked fine. Also, when I
> re-installed
> > RH-7.2, it worked fine?
> >
> > Any suggestions?
> >
> > Please cc me the reply, sine I'm not subscribed.
> > Thanks ;-)
> >
> > -- 
> >         -Dhruv Matani.
> > http://www.geocities.com/dhruvbird/
> >
> > As a rule, man is a fool. When it's hot, he wants it cold.
> > When it's cold he wants it hot. He always wants what is not.
> > -Anon.
> >
> >
> > -
> > 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/
> >
>
> -
> 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/
> -
> 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/
>

DriveReady SeekComplete Error...

[Dhruv Matani]

Hi,
	I've been getting this error for my brand new (2 months old) Samsung
HDD. The model Number is: SV0411N, and it is a 40GB disk. I'm using the
kernel version 2.4.20-8 provided by RedHat. When I used RH-7.2(before
upgrading to RH-9), the same HDD worked fine. Also, when I re-installed
RH-7.2, it worked fine?

Any suggestions?

Please cc me the reply, sine I'm not subscribed.
Thanks ;-)

-- 
        -Dhruv Matani.
http://www.geocities.com/dhruvbird/

As a rule, man is a fool. When it's hot, he wants it cold. 
When it's cold he wants it hot. He always wants what is not.
	-Anon.

Re: DriveReady SeekComplete Error...

[Dwayne Rightler]

I have a similar problem with a Samsung hard drive. Model SV2044D.  The
output of 'hdparm -i' below indicates it supports several multiword and
ultra DMA modes but if i run the drive in anything other than PIO mode it
gets DMA timeouts and SeekComplete Errors.  This has been on every kernel I
can recall in the 2.4 and 2.6 series.

demigod:~# hdparm -i /dev/hda

/dev/hda:

 Model=SAMSUNG SV2044D, FwRev=MM200-53, SerialNo=0228J1FN905733
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
 RawCHS=16383/16/63, TrkSize=34902, SectSize=554, ECCbytes=4
 BuffType=DualPortCache, BuffSize=472kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39862368
 IORDY=yes, 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
 AdvancedPM=no WriteCache=enabled
 Drive conforms to: ATA/ATAPI-4 T13 1153D revision 17:  1 2 3 4

 * signifies the current active mode



----- Original Message ----- 
From: "Dhruv Matani" <dhruvbird@gmx.net>
To: <linux-kernel@vger.kernel.org>
Sent: Tuesday, July 13, 2004 7:30 AM
Subject: DriveReady SeekComplete Error...


> Hi,
> I've been getting this error for my brand new (2 months old) Samsung
> HDD. The model Number is: SV0411N, and it is a 40GB disk. I'm using the
> kernel version 2.4.20-8 provided by RedHat. When I used RH-7.2(before
> upgrading to RH-9), the same HDD worked fine. Also, when I re-installed
> RH-7.2, it worked fine?
>
> Any suggestions?
>
> Please cc me the reply, sine I'm not subscribed.
> Thanks ;-)
>
> -- 
>         -Dhruv Matani.
> http://www.geocities.com/dhruvbird/
>
> As a rule, man is a fool. When it's hot, he wants it cold.
> When it's cold he wants it hot. He always wants what is not.
> -Anon.
>
>
> -
> 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/
>

Re: DriveReady SeekComplete Error...

[Dhruv Matani]

On Tue, 2004-07-13 at 17:55, Evaldo Gardenali wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Dhruv Matani wrote:
> | Hi,
> | 	I've been getting this error for my brand new (2 months old) Samsung
> | HDD. The model Number is: SV0411N, and it is a 40GB disk. I'm using the
> | kernel version 2.4.20-8 provided by RedHat. When I used RH-7.2(before
> | upgrading to RH-9), the same HDD worked fine. Also, when I re-installed
> | RH-7.2, it worked fine?
> |
> | Any suggestions?
> |
> | Please cc me the reply, sine I'm not subscribed.
> | Thanks ;-)
> |
> 
> Hi there!
> on your kernel config, make sure you enable this:
> 
> 
> ~  lqqqqqqqqqqqqqqqqqqqqqqq Use multi-mode by default
> qqqqqqqqqqqqqqqqqqqqqqqk
> ~  x CONFIG_IDEDISK_MULTI_MODE:
> ~    x
> ~  x
> ~    x
> ~  x If you get this error, try to say Y here:
> ~    x
> ~  x
> ~    x
> ~  x hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
> ~    x
> ~  x hda: set_multmode: error=0x04 { DriveStatusError }
> ~    x
> ~  x
> ~    x
> ~  x If in doubt, say N.

I don't think this will apply here, because the error that aI get
associated with the error is: 

Jul 12 00:19:52 localhost kernel: Freeing unused kernel memory: 92k
freed
Jul 12 00:19:52 localhost kernel: hda: dma_intr: status=0x51 {
DriveReady SeekComplete Error }
Jul 12 00:19:52 localhost kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Jul 12 00:19:52 localhost kernel: hda: dma_intr: status=0x51 {
DriveReady SeekComplete Error }
Jul 12 00:19:52 localhost kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Jul 12 00:19:52 localhost kernel: hda: dma_intr: status=0x51 {
DriveReady SeekComplete Error }
Jul 12 00:19:52 localhost kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Jul 12 00:19:52 localhost kernel: hda: dma_intr: status=0x51 {
DriveReady SeekComplete Error }
Jul 12 00:19:52 localhost kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Jul 12 00:19:52 localhost kernel: ide0: reset: success
Jul 12 00:19:52 localhost kernel: hda: dma_intr: status=0x51 {
DriveReady SeekComplete Error }
Jul 12 00:19:52 localhost kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Jul 12 00:19:52 localhost kernel: hda: dma_intr: status=0x51 {
DriveReady SeekComplete Error }
Jul 12 00:19:52 localhost kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Jul 12 00:19:52 localhost kernel: hda: dma_intr: status=0x51 {
DriveReady SeekComplete Error }
Jul 12 00:19:52 localhost kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Jul 12 00:19:52 localhost kernel: hda: dma_intr: status=0x51 {
DriveReady SeekComplete Error }
Jul 12 00:19:52 localhost kernel: hda: dma_intr: error=0x84 {
DriveStatusError BadCRC }
Jul 12 00:19:52 localhost kernel: ide0: reset: success
Jul 12 00:19:52 localhost kernel: Real Time Clock Driver v1.10e

And not set_multimode.

I read somewhere, that some time interval has been changed to 20ms /
50ms, and 100ms was the previous one, and Samsung HDDs have been konking
off after that. What's this?

> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> 
> tqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(100%)qqu
> 
> ~  x                                < Exit >
> ~    x
> 
> mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> 
> iD8DBQFA89Ss5121Y+8pAbIRAio8AJ4sJ1ekYRSwVEoGBE90QIITqQyg0wCfXFaE
> npdo42iFQ0Le8Fzq7sXjGUg=
> =4aFw
> -----END PGP SIGNATURE-----
-- 
        -Dhruv Matani.
http://www.geocities.com/dhruvbird/

As a rule, man is a fool. When it's hot, he wants it cold. 
When it's cold he wants it hot. He always wants what is not.
	-Anon.

Re: DriveReady SeekComplete Error...

[Dhruv Matani]

BTW, the multi-mode setting is already enabled. I made sure while
re-compiling the kernel, and double-checked right now.

On Tue, 2004-07-13 at 17:55, Evaldo Gardenali wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Dhruv Matani wrote:
> | Hi,
> | 	I've been getting this error for my brand new (2 months old) Samsung
> | HDD. The model Number is: SV0411N, and it is a 40GB disk. I'm using the
> | kernel version 2.4.20-8 provided by RedHat. When I used RH-7.2(before
> | upgrading to RH-9), the same HDD worked fine. Also, when I re-installed
> | RH-7.2, it worked fine?
> |
> | Any suggestions?
> |
> | Please cc me the reply, sine I'm not subscribed.
> | Thanks ;-)
> |
> 
> Hi there!
> on your kernel config, make sure you enable this:
> 
> 
> ~  lqqqqqqqqqqqqqqqqqqqqqqq Use multi-mode by default
> qqqqqqqqqqqqqqqqqqqqqqqk
> ~  x CONFIG_IDEDISK_MULTI_MODE:
> ~    x
> ~  x
> ~    x
> ~  x If you get this error, try to say Y here:
> ~    x
> ~  x
> ~    x
> ~  x hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
> ~    x
> ~  x hda: set_multmode: error=0x04 { DriveStatusError }
> ~    x
> ~  x
> ~    x
> ~  x If in doubt, say N.
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> 
> tqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(100%)qqu
> 
> ~  x                                < Exit >
> ~    x
> 
> mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> 
> iD8DBQFA89Ss5121Y+8pAbIRAio8AJ4sJ1ekYRSwVEoGBE90QIITqQyg0wCfXFaE
> npdo42iFQ0Le8Fzq7sXjGUg=
> =4aFw
> -----END PGP SIGNATURE-----
-- 
        -Dhruv Matani.
http://www.geocities.com/dhruvbird/

As a rule, man is a fool. When it's hot, he wants it cold. 
When it's cold he wants it hot. He always wants what is not.
	-Anon.

Re: DriveReady SeekComplete Error...

[Dhruv Matani]

One more thing I forgot to mention is that if I use that hard 80-pin
cable, then I do not get such errors at boot time, but get them when
some service is loading, and if I use the cheaper more flexible
cable(with possibly lesser number of cables), then I get these errors
while the kernel is loading as well as when some service is loading.
That service is smartd.

Again, only in 2.4.20-8, in the previous version(the default that came
with RedHat-7.2), there is no such problem. Also, I use a re-compiled
version of the 2.4.20-8 kernel, whereas the default RedHat provided one
for 7.2, but the errors persist even for the default RedHat-9 kernel
2.4.20-8, so I suspect that it's a kernel thing.

One more thing! In RedHat-9 with 2.4.20-8, sometimes, the number of
processes just increases like mad! and the whole system becomes
unstable. Then I get errors like I/O error, and hda can not be read
from, and a whole list of blocks.



On Tue, 2004-07-13 at 17:55, Evaldo Gardenali wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Dhruv Matani wrote:
> | Hi,
> | 	I've been getting this error for my brand new (2 months old) Samsung
> | HDD. The model Number is: SV0411N, and it is a 40GB disk. I'm using the
> | kernel version 2.4.20-8 provided by RedHat. When I used RH-7.2(before
> | upgrading to RH-9), the same HDD worked fine. Also, when I re-installed
> | RH-7.2, it worked fine?
> |
> | Any suggestions?
> |
> | Please cc me the reply, sine I'm not subscribed.
> | Thanks ;-)
> |
> 
> Hi there!
> on your kernel config, make sure you enable this:
> 
> 
> ~  lqqqqqqqqqqqqqqqqqqqqqqq Use multi-mode by default
> qqqqqqqqqqqqqqqqqqqqqqqk
> ~  x CONFIG_IDEDISK_MULTI_MODE:
> ~    x
> ~  x
> ~    x
> ~  x If you get this error, try to say Y here:
> ~    x
> ~  x
> ~    x
> ~  x hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
> ~    x
> ~  x hda: set_multmode: error=0x04 { DriveStatusError }
> ~    x
> ~  x
> ~    x
> ~  x If in doubt, say N.
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> ~  x
> ~    x
> 
> tqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq(100%)qqu
> 
> ~  x                                < Exit >
> ~    x
> 
> mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> 
> iD8DBQFA89Ss5121Y+8pAbIRAio8AJ4sJ1ekYRSwVEoGBE90QIITqQyg0wCfXFaE
> npdo42iFQ0Le8Fzq7sXjGUg=
> =4aFw
> -----END PGP SIGNATURE-----
-- 
        -Dhruv Matani.
http://www.geocities.com/dhruvbird/

As a rule, man is a fool. When it's hot, he wants it cold. 
When it's cold he wants it hot. He always wants what is not.
	-Anon.

Re: DriveReady SeekComplete Error...

[Bartlomiej Zolnierkiewicz]

Hi,

On Tuesday 13 of July 2004 16:47, Dhruv Matani wrote:
> One more thing I forgot to mention is that if I use that hard 80-pin
> cable, then I do not get such errors at boot time, but get them when
> some service is loading, and if I use the cheaper more flexible
> cable(with possibly lesser number of cables), then I get these errors

You get "BadCRC" errors.  They usually indicate bad cabling.

> while the kernel is loading as well as when some service is loading.
> That service is smartd.

Are you sure it is _exactly_ the same error?

If it is "task_no_data_intr" one then it is harmless
(means that command is not supported by a drive).

You may also want to check http://smartmontools.sf.net

> Again, only in 2.4.20-8, in the previous version(the default that came
> with RedHat-7.2), there is no such problem. Also, I use a re-compiled
> version of the 2.4.20-8 kernel, whereas the default RedHat provided one
> for 7.2, but the errors persist even for the default RedHat-9 kernel
> 2.4.20-8, so I suspect that it's a kernel thing.

RedHat has its own bugtracking system for their kernels.

Please check if you can reproduce the problem with the current
vanilla kernel from kernel.org.

> One more thing! In RedHat-9 with 2.4.20-8, sometimes, the number of
> processes just increases like mad! and the whole system becomes
> unstable. Then I get errors like I/O error, and hda can not be read
> from, and a whole list of blocks.

AFAICS the current kernel for RH9 is kernel-2.4.20-31.9 and you should
be using it instead of > 1 year old 2.4.20-8 version.

Bartlomiej

DriveReady SeekComplete Error

[Rick Jansen]

Hi,

Is this drive fubar? It's installed brand-new, and after only three days
of operating it's giving me these errors from time to time.

May 30 07:08:18 web3 kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
May 30 07:08:18 web3 kernel: hda: dma_intr: error=0x40 {
UncorrectableError }, LBAsect=227270012, sector=227270007
May 30 07:08:18 web3 kernel: end_request: I/O error, dev hda, sector
227270007

I could find some other people on the net with these problems, but none
of them happened with brandnew drives. 

What can I do?

Rick Jansen

-- 
Looking for books? Try http://www.megabooksearch.com
The Linux on 64-Bit platforms Wiki: http://www.linux64.net
PGP Public Key: http://www.rockingstone.nl/rick/pubkey.asc

Re: DriveReady SeekComplete Error

[Daniel Egger]

[-- Attachment #1: Type: text/plain, Size: 373 bytes --]

On 04.06.2004, at 09:54, Rick Jansen wrote:

> Is this drive fubar? It's installed brand-new, and after only three 
> days
> of operating it's giving me these errors from time to time.

Seems so, try getting the SMART utils and have a look at the
output of smartctl -a <device>.

However I fail to see why this l-k related and as such offtopic
here.

Servus,
       Daniel

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 478 bytes --]

Re: DriveReady SeekComplete Error

[John Bradford]

Quote from Daniel Egger <de@axiros.com>:
> Seems so, try getting the SMART utils and have a look at the
> output of smartctl -a <device>.
> 
> However I fail to see why this l-k related and as such offtopic
> here.

1. I see no particular evidence to suggest that the drive is necessarily faulty.
2. It is on topic because it may well be a coding error in the kernel.

John.

Re: DriveReady SeekComplete Error

[John Bradford]

Quote from Rick Jansen <rick@rockingstone.nl>:
> May 30 07:08:18 web3 kernel: hda: dma_intr: status=0x51 { DriveReady
> SeekComplete Error }
> May 30 07:08:18 web3 kernel: hda: dma_intr: error=0x40 {
> UncorrectableError }, LBAsect=227270012, sector=227270007
> May 30 07:08:18 web3 kernel: end_request: I/O error, dev hda, sector
> 227270007
> 
> I could find some other people on the net with these problems, but none
> of them happened with brandnew drives. 
> 
> What can I do?

Please post more information.  First, what size is the disk?

The LBAsect number suggests an access around 108 Gb.  If the disk is smaller
than this, then it would appear that a request was made for a non-existant
sector.

Is the LBAsect number the same in each error?  What is the machine doing
when the errors occur?

John.

Re: DriveReady SeekComplete Error

[Rick Jansen]

On Fri, Jun 04, 2004 at 10:43:02AM +0100, John Bradford wrote:
> Please post more information.  First, what size is the disk?
> 
> The LBAsect number suggests an access around 108 Gb.  If the disk is smaller
> than this, then it would appear that a request was made for a non-existant
> sector.
> 
> Is the LBAsect number the same in each error?  What is the machine doing
> when the errors occur?
> 
> John.

Here's some more information about the disk from the boot log.
I also found some StatusErrors in there.

May 10 11:14:07 web3 kernel: hda: Maxtor 6Y120P0, ATA DISK drive
May 10 11:14:07 web3 kernel: hda: max request size: 128KiB
May 10 11:14:07 web3 kernel: hda: 240121728 sectors (122942 MB)
w/7936KiB Cache, CHS=65535/16/63, UDMA(133)
May 10 11:14:07 web3 kernel:  hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
May 10 11:14:07 web3 kernel: hda: task_no_data_intr: status=0x51 {
DriveReady SeekComplete Error }
May 10 11:14:07 web3 kernel: hda: task_no_data_intr: error=0x04 {
DriveStatusError }
May 10 11:14:07 web3 kernel: hda: Write Cache FAILED Flushing!

Thats a different error then what it gives me occasionaly. Googling this
error lead me to believe this is a bug in the ide driver, that my disk
doesnt support some flush command.

After parsing the log with simple script, these sectors seem to give the
errors:

227270012
227270483
236708724
237757036
237757472
238018530
238020393
238279554
238804853
239066426
239328347
239590823
240116567
240121662
58619113
58619120
58619127
58619447
58619448
58619519
58620045
58620048
58620331

I've tried to reproduce these errors by rsyncing the whole filesystem,
executing various find / commands, but nothing triggered them. The
machine is primarily a web server, so my guess is they happen when
apache tries to do something to the disk. 

The output from smartctl -a seems a bit large to include in this email.

Rick Jansen

-- 
Looking for books? Try http://www.megabooksearch.com
The Linux on 64-Bit platforms Wiki: http://www.linux64.net
PGP Public Key: http://www.rockingstone.nl/rick/pubkey.asc

Re: DriveReady SeekComplete Error

[Jens Axboe]

On Fri, Jun 04 2004, Rick Jansen wrote:
> On Fri, Jun 04, 2004 at 10:43:02AM +0100, John Bradford wrote:
> > Please post more information.  First, what size is the disk?
> > 
> > The LBAsect number suggests an access around 108 Gb.  If the disk is smaller
> > than this, then it would appear that a request was made for a non-existant
> > sector.
> > 
> > Is the LBAsect number the same in each error?  What is the machine doing
> > when the errors occur?
> > 
> > John.
> 
> Here's some more information about the disk from the boot log.
> I also found some StatusErrors in there.
> 
> May 10 11:14:07 web3 kernel: hda: Maxtor 6Y120P0, ATA DISK drive
> May 10 11:14:07 web3 kernel: hda: max request size: 128KiB
> May 10 11:14:07 web3 kernel: hda: 240121728 sectors (122942 MB)
> w/7936KiB Cache, CHS=65535/16/63, UDMA(133)
> May 10 11:14:07 web3 kernel:  hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
> May 10 11:14:07 web3 kernel: hda: task_no_data_intr: status=0x51 {
> DriveReady SeekComplete Error }
> May 10 11:14:07 web3 kernel: hda: task_no_data_intr: error=0x04 {
> DriveStatusError }
> May 10 11:14:07 web3 kernel: hda: Write Cache FAILED Flushing!
> 
> Thats a different error then what it gives me occasionaly. Googling this
> error lead me to believe this is a bug in the ide driver, that my disk
> doesnt support some flush command.

It is, what kernel are you using?

-- 
Jens Axboe

Re: DriveReady SeekComplete Error

[Rick Jansen]

On Fri, Jun 04, 2004 at 11:59:00AM +0200, Jens Axboe wrote:
> 
> It is, what kernel are you using?
> 
> -- 
> Jens Axboe

This is 2.6.6.

Rick Jansen

-- 
Looking for books? Try http://www.megabooksearch.com
The Linux on 64-Bit platforms Wiki: http://www.linux64.net
PGP Public Key: http://www.rockingstone.nl/rick/pubkey.asc

Re: DriveReady SeekComplete Error

[Jens Axboe]

(don't trim people from the cc list, thanks)

On Fri, Jun 04 2004, Rick Jansen wrote:
> On Fri, Jun 04, 2004 at 11:59:00AM +0200, Jens Axboe wrote:
> > 
> > It is, what kernel are you using?
> > 
> > -- 
> > Jens Axboe
> 
> This is 2.6.6.

The that's a known error, you should not worry about it. It's fixed in
later kernels.

-- 
Jens Axboe

Re: DriveReady SeekComplete Error

[Andy Hawkins]

Hi,

In article <20040604100813.GP1946@suse.de>,
           Jens Axboe<axboe@suse.de> wrote:
> The that's a known error, you should not worry about it. It's fixed in
> later kernels.

I'm seeing this error too, and also frequent crashes (total lock ups) of the
machine (every day or two at the moment). Could the two be related?

I haven't got round to doing any diagnostics yet, but there's nothing
obvious in the logs. I was going to dismantle the machine and check
connections etc. first.

Andy

Re: DriveReady SeekComplete Error

[Daniel Egger]

[-- Attachment #1: Type: text/plain, Size: 436 bytes --]

On 04.06.2004, at 11:54, Rick Jansen wrote:

> The output from smartctl -a seems a bit large to include in this email.

This is usually also a bad sign, escpecially if the size is caused
by the Error Log Structure areas.

Please send the info of smartctl -v <device>. This should give a
good indication of whether this is a kernel or a drive problem
because it will show some of the internal status of the drive.

Servus,
       Daniel

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 478 bytes --]

Re: DriveReady SeekComplete Error

[Rick Jansen]

[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]

On Fri, Jun 04, 2004 at 03:41:27PM +0200, Daniel Egger wrote:
> This is usually also a bad sign, escpecially if the size is caused
> by the Error Log Structure areas.
> 
> Please send the info of smartctl -v <device>. This should give a
> good indication of whether this is a kernel or a drive problem
> because it will show some of the internal status of the drive.
> 
> Servus,
>       Daniel

I don't think -v is the option you mean:

smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=======> INVALID ARGUMENT TO -v: /dev/hda <======= 
=======> VALID ARGUMENTS ARE:
	help
	9,halfminutes
	9,minutes
	9,seconds
	9,temp
	192,emergencyretractcyclect
	193,loadunload
	194,10xCelsius
	194,unknown
	198,offlinescanuncsectorct
	200,writeerrorcount
	201,detectedtacount
	220,temp
	N,raw8
	N,raw16
	N,raw48
<=======

Use smartctl -h to get a usage summary


-- 
Looking for books? Try http://www.megabooksearch.com
The Linux on 64-Bit platforms Wiki: http://www.linux64.net
PGP Public Key: http://www.rockingstone.nl/rick/pubkey.asc

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: DriveReady SeekComplete Error

[John Bradford]

> I don't think -v is the option you mean:

Send all the data.

John.

Re: DriveReady SeekComplete Error

[Rick Jansen]

[-- Attachment #1: Type: text/plain, Size: 9696 bytes --]

On Fri, Jun 04, 2004 at 03:05:20PM +0100, John Bradford wrote:
> Send all the data.
> 
> John.

smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model:     Maxtor 6Y120P0
Serial Number:    Y43XXY5E
Firmware Version: YAR41BW0
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 0
Local Time is:    Fri Jun  4 16:16:57 2004 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x80)	Offline data collection activity was
					never started.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 118)	The previous self-test completed having
					the read element of the test failed.
Total time to complete Offline 
data collection: 		 ( 182) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					No General Purpose Logging support.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  60) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  3 Spin_Up_Time            0x0027   252   252   063    Pre-fail  Always       -       1249
  4 Start_Stop_Count        0x0032   253   253   000    Old_age   Always       -       6
  5 Reallocated_Sector_Ct   0x0033   252   252   063    Pre-fail  Always       -       15
  6 Read_Channel_Margin     0x0001   253   253   100    Pre-fail  Offline      -       0
  7 Seek_Error_Rate         0x000a   253   252   000    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0027   249   244   187    Pre-fail  Always       -       41816
  9 Power_On_Minutes        0x0032   251   251   000    Old_age   Always       -       908h+44m
 10 Spin_Retry_Count        0x002b   252   252   157    Pre-fail  Always       -       0
 11 Calibration_Retry_Count 0x002b   252   252   223    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   253   253   000    Old_age   Always       -       8
192 Power-Off_Retract_Count 0x0032   253   253   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   253   253   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0032   253   253   000    Old_age   Always       -       38
195 Hardware_ECC_Recovered  0x000a   253   252   000    Old_age   Always       -       1632
196 Reallocated_Event_Count 0x0008   253   253   000    Old_age   Offline      -       0
197 Current_Pending_Sector  0x0008   252   252   000    Old_age   Offline      -       13
198 Offline_Uncorrectable   0x0008   252   252   000    Old_age   Offline      -       1
199 UDMA_CRC_Error_Count    0x0008   199   199   000    Old_age   Offline      -       0
200 Multi_Zone_Error_Rate   0x000a   253   252   000    Old_age   Always       -       0
201 Soft_Read_Error_Rate    0x000a   253   252   000    Old_age   Always       -       5
202 TA_Increase_Count       0x000a   253   252   000    Old_age   Always       -       0
203 Run_Out_Cancel          0x000b   253   252   180    Pre-fail  Always       -       0
204 Shock_Count_Write_Opern 0x000a   253   252   000    Old_age   Always       -       0
205 Shock_Rate_Write_Opern  0x000a   253   252   000    Old_age   Always       -       0
207 Spin_High_Current       0x002a   252   252   000    Old_age   Always       -       0
208 Spin_Buzz               0x002a   252   252   000    Old_age   Always       -       0
209 Offline_Seek_Performnce 0x0024   195   195   000    Old_age   Offline      -       0
 99 Unknown_Attribute       0x0004   253   253   000    Old_age   Offline      -       0
100 Unknown_Attribute       0x0004   253   253   000    Old_age   Offline      -       0
101 Unknown_Attribute       0x0004   253   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 440 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Timestamp = decimal seconds since the previous disk power-on.
Note: timestamp "wraps" after 2^32 msec = 49.710 days.

Error 440 occurred at disk power-on lifetime: 843 hours
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 03 77 dd 8b ed  Error: UNC 3 sectors at LBA = 0x0d8bdd77 = 227270007

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
  -- -- -- -- -- -- -- --   ---------  --------------------
  c8 00 08 77 dd 8b ed 08 2045545.712  READ DMA
  ca 00 08 e8 a1 3c e0 08 2045545.680  WRITE DMA
  ca 00 08 37 41 54 e2 08 2045545.680  WRITE DMA
  ca 00 08 d0 ca 95 e0 08 2045545.680  WRITE DMA
  ca 00 70 78 a1 3c e0 08 2045545.680  WRITE DMA

Error 439 occurred at disk power-on lifetime: 843 hours
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 03 77 dd 8b ed  Error: UNC 3 sectors at LBA = 0x0d8bdd77 = 227270007

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
  -- -- -- -- -- -- -- --   ---------  --------------------
  c8 00 08 77 dd 8b ed 08 2045544.688  READ DMA
  c8 00 40 ff 0b c7 e2 08 2045544.656  READ DMA
  c8 00 08 4f df 8b ed 08 2045543.632  READ DMA
  ca 00 08 17 0f a8 e2 08 2045543.584  WRITE DMA
  ca 00 08 ef ba 97 e2 08 2045543.584  WRITE DMA

Error 438 occurred at disk power-on lifetime: 843 hours
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 04 4f df 8b ed  Error: UNC 4 sectors at LBA = 0x0d8bdf4f = 227270479

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
  -- -- -- -- -- -- -- --   ---------  --------------------
  c8 00 08 4f df 8b ed 08 2045543.632  READ DMA
  ca 00 08 17 0f a8 e2 08 2045543.584  WRITE DMA
  ca 00 08 ef ba 97 e2 08 2045543.584  WRITE DMA
  ca 00 10 d7 ba 97 e2 08 2045543.584  WRITE DMA
  ca 00 10 8f ba 97 e2 08 2045543.584  WRITE DMA

Error 437 occurred at disk power-on lifetime: 843 hours
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 04 4f df 8b ed  Error: UNC 4 sectors at LBA = 0x0d8bdf4f = 227270479

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
  -- -- -- -- -- -- -- --   ---------  --------------------
  c8 00 08 4f df 8b ed 08 2045542.560  READ DMA
  c8 00 08 8f 0b c7 e2 08 2045542.560  READ DMA
  c8 00 50 af 0b c7 e2 08 2045542.560  READ DMA
  c8 00 10 9f 0b c7 e2 08 2045542.560  READ DMA
  c8 00 08 97 0b c7 e2 08 2045542.560  READ DMA

Error 436 occurred at disk power-on lifetime: 843 hours
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 03 77 dd 8b ed  Error: UNC 3 sectors at LBA = 0x0d8bdd77 = 227270007

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
  -- -- -- -- -- -- -- --   ---------  --------------------
  c8 00 08 77 dd 8b ed 08 2043137.264  READ DMA
  c8 00 18 f7 36 7c e3 08 2043137.248  READ DMA
  c8 00 10 3f 0f 7c e3 08 2043137.248  READ DMA
  c8 00 10 57 d5 7b e3 08 2043137.248  READ DMA
  c8 00 08 37 c7 7b e3 08 2043137.232  READ DMA

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       60%       839         0x0d8bdd7c
# 2  Short offline       Completed: read failure       60%       816         0x0d8bdd7c
# 3  Short offline       Completed: read failure       60%       805         0x0d8bdd7c

-- 
Looking for books? Try http://www.megabooksearch.com
The Linux on 64-Bit platforms Wiki: http://www.linux64.net
PGP Public Key: http://www.rockingstone.nl/rick/pubkey.asc

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: DriveReady SeekComplete Error

[Bruce Allen]

Hi Rick,

> smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen
> Home page is http://smartmontools.sourceforge.net/

Some comments below.

> Device Model:     Maxtor 6Y120P0
> Serial Number:    Y43XXY5E
> Firmware Version: YAR41BW0
> Device is:        In smartctl database [for details use: -P show]
> ATA Version is:   7

You can use selective self-tests on this drive.  You'll need smartmontools
version 5.31 or greater.  This will help you pin down the bad LBAs
quickly.

> Self-test execution status:      ( 118)	The previous self-test completed having
> 					the read element of the test failed.

You have some unreadable disk sectors.

> 					Selective Self-test supported.

This is a very useful disk feature!

>   5 Reallocated_Sector_Ct   0x0033   252   252   063    Pre-fail  Always       -       15

Your disk has already reallocated 15 bad sectors.

> 197 Current_Pending_Sector  0x0008   252   252   000    Old_age   Offline      -       13
> 198 Offline_Uncorrectable   0x0008   252   252   000    Old_age   Offline      -       1

There are 13 unreadable disk sectors that the OS has tried to access, and
one additional unreadable disk sector found in an off-line scan.

> Error 440 occurred at disk power-on lifetime: 843 hours
>   When the command that caused the error occurred, the device was in an unknown state.
> 
>   After command completion occurred, registers were:
>   ER ST SC SN CL CH DH
>   -- -- -- -- -- -- --
>   40 51 03 77 dd 8b ed  Error: UNC 3 sectors at LBA = 0x0d8bdd77 = 227270007

This is a typical read that failed at LBA 227270007.

> SMART Self-test log structure revision number 1
> Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
> # 1  Short offline       Completed: read failure       60%       839         0x0d8bdd7c
> # 2  Short offline       Completed: read failure       60%       816         0x0d8bdd7c
> # 3  Short offline       Completed: read failure       60%       805         0x0d8bdd7c

See http://smartmontools.sourceforge.net/BadBlockHowTo.txt for info on how
to locate and force reallocation of the bad sectors.  When you are done
you should be able to run a long self-test (-t long) with no errors found.
You can use selective self-tests (-t select,M-N) to help locate the bad
sectors.

Bruce

Re: DriveReady SeekComplete Error

[Daniel Egger]

[-- Attachment #1: Type: text/plain, Size: 304 bytes --]

On 04.06.2004, at 15:53, Rick Jansen wrote:

> I don't think -v is the option you mean:

> smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen
> Home page is http://smartmontools.sourceforge.net/

DOH! Works for version 2.1 and will list all attributes
as well as their values.

Servus,
       Daniel

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 478 bytes --]

Re: DriveReady SeekComplete Error

[John Bradford]

Please don't trim the CC list.

Quote from Rick Jansen <rick@rockingstone.nl>:
> On Fri, Jun 04, 2004 at 10:43:02AM +0100, John Bradford wrote:
> > Please post more information.  First, what size is the disk?
> > 
> > The LBAsect number suggests an access around 108 Gb.  If the disk is smaller
> > than this, then it would appear that a request was made for a non-existant
> > sector.
> > 
> > Is the LBAsect number the same in each error?  What is the machine doing
> > when the errors occur?
> > 
> > John.
> 
> Here's some more information about the disk from the boot log.
> I also found some StatusErrors in there.
> 
> May 10 11:14:07 web3 kernel: hda: Maxtor 6Y120P0, ATA DISK drive
> May 10 11:14:07 web3 kernel: hda: max request size: 128KiB
> May 10 11:14:07 web3 kernel: hda: 240121728 sectors (122942 MB)
> w/7936KiB Cache, CHS=65535/16/63, UDMA(133)
> May 10 11:14:07 web3 kernel:  hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
> May 10 11:14:07 web3 kernel: hda: task_no_data_intr: status=0x51 {
> DriveReady SeekComplete Error }
> May 10 11:14:07 web3 kernel: hda: task_no_data_intr: error=0x04 {
> DriveStatusError }
> May 10 11:14:07 web3 kernel: hda: Write Cache FAILED Flushing!
> 
> Thats a different error then what it gives me occasionaly. Googling this
> error lead me to believe this is a bug in the ide driver, that my disk
> doesnt support some flush command.
> 
> After parsing the log with simple script, these sectors seem to give the
> errors:
> 
> 227270012
> 227270483
> 236708724
> 237757036
> 237757472
> 238018530
> 238020393
> 238279554
> 238804853
> 239066426
> 239328347
> 239590823
> 240116567
> 240121662
> 58619113
> 58619120
> 58619127
> 58619447
> 58619448
> 58619519
> 58620045
> 58620048
> 58620331

The lower ones are definitely within the capacity of the drive.  I suspect
it _may_ genuinuely be faulty after all.

Back up your data.

If practical, try overwriting the whole disk, with something like:

dd if=/dev/zero of=/dev/hda

and see if it makes the errors go away.

John.