DriveReady SeekComplete Error

DISCUSSION mattia 5 participants 10 messages Jun 4, 2004 – Jun 5, 2004

Share & tools

mattia

author

2004-06-04 10:15 UTC #0 lore raw

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

Quoted 26 lines

(don't trim people from the cc list, thanks)
Quoted 8 lines · Rick Jansen
Quoted 5 lines · Jens Axboe
It is, what kernel are you using?
Signature · 1 line
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.
Signature · 7 lines
Jens Axboe

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Jens Axboe

2004-06-04 10:23 UTC #1 lore raw

damnit, don't trim the cc list!

Quoted 25 lines · 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!

Quoted 2 lines

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.

Signature · 1 line

Jens Axboe

Bartlomiej Zolnierkiewicz

2004-06-04 11:41 UTC #2 lore raw

Quoted 28 lines · Jens Axboe

damnit, don't trim the cc list!

Quoted 25 lines · 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!

Quoted 6 lines

Quoted 2 lines
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

Jens Axboe

2004-06-04 11:57 UTC #3 lore raw

Quoted 36 lines · Bartlomiej Zolnierkiewicz

Quoted 28 lines · Jens Axboe

damnit, don't trim the cc list!

Quoted 25 lines · 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!

Quoted 6 lines

Quoted 2 lines
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.

Quoted 7 lines

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?).

Quoted 2 lines

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

Signature · 1 line

Jens Axboe

Bartlomiej Zolnierkiewicz

2004-06-04 12:12 UTC #4 lore raw

Quoted 39 lines · Jens Axboe

Quoted 38 lines · Bartlomiej Zolnierkiewicz

Quoted 28 lines · Jens Axboe

damnit, don't trim the cc list!

Quoted 25 lines · 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!

Quoted 6 lines

Quoted 2 lines
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.

Quoted 8 lines

Quoted 5 lines
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)

Quoted 4 lines

Quoted 2 lines
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

Jens Axboe

2004-06-04 12:17 UTC #5 lore raw

Quoted 65 lines · Bartlomiej Zolnierkiewicz

Quoted 39 lines · Jens Axboe
Quoted 38 lines · Bartlomiej Zolnierkiewicz
Quoted 28 lines · Jens Axboe
damnit, don't trim the cc list!
Quoted 25 lines · 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!
Quoted 6 lines
Quoted 2 lines
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.
Quoted 8 lines
Quoted 5 lines
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:

Review

Quoted 3 lines

(quoted diff) +3 -0

+/* 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.

Review

Quoted 9 lines

Quoted 4 lines
Quoted 2 lines
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()
(quoted diff) +2 -0
+	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?

Signature · 1 line

Jens Axboe

Bartlomiej Zolnierkiewicz

2004-06-04 12:37 UTC #6 lore raw

Quoted 102 lines · Jens Axboe

Quoted 67 lines · Bartlomiej Zolnierkiewicz
Quoted 39 lines · Jens Axboe
Quoted 38 lines · Bartlomiej Zolnierkiewicz
Quoted 28 lines · Jens Axboe
damnit, don't trim the cc list!
Quoted 25 lines · 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!
Quoted 6 lines
Quoted 2 lines
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.
Quoted 8 lines
Quoted 5 lines
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) \
Review
Quoted 1 line
(quoted diff) +1 -0
+	(((id)->cfs_enable_2 & 0x2400) == 0x2400)
Ok, so I didn't miss anything. Was just wondering because of your comment on -mm2.
Review
Quoted 9 lines
Quoted 4 lines
Quoted 2 lines
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()
(quoted diff) +2 -0
+	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;
}

Quoted 3 lines

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.

Quoted 1 line

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

Yep.

Quoted 2 lines

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?

Ed Tomlinson

2004-06-04 21:55 UTC #7 lore raw

In reply to Jens Axboe

Quoted 3 lines · Jens Axboe

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:

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

Eric D. Mudama

2004-06-04 19:56 UTC #8 lore raw

In reply to mattia

Quoted 5 lines

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

Signature · 2 lines

Eric D. Mudama
[email protected]

mattia

author

2004-06-05 13:45 UTC #9 lore raw

Quoted 25 lines · Eric D. Mudama

Quoted 5 lines
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)

Quoted 6 lines

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