I have the following message from the second hard drive. It worked fine with rh9 and fc2t2. But I'm getting getting cache write problems with fc2 with both 2.6.5 and 2.6.6 kernels. Anything change???
May 16 18:06:22 www kernel: hdb: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } May 16 18:06:22 www kernel: hdb: task_no_data_intr: error=0x04 { DriveStatusError } May 16 18:06:22 www kernel: hdb: Write Cache FAILED Flushing! May 16 18:06:22 www kernel: hdb: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } May 16 18:06:22 www kernel: hdb: task_no_data_intr: error=0x04 { DriveStatusError } May 16 18:06:22 www kernel: hdb: Write Cache FAILED Flushing! May 16 18:06:22 www kernel: hdb: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } May 16 18:06:22 www kernel: hdb: task_no_data_intr: error=0x04 { DriveStatusError } May 16 18:06:22 www kernel: hdb: Write Cache FAILED Flushing! May 16 18:06:22 www kernel: hdb: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } May 16 18:06:22 www kernel: hdb: task_no_data_intr: error=0x04 { DriveStatusError } May 16 18:06:22 www kernel: hdb: Write Cache FAILED Flushing! May 16 18:06:22 www kernel: hdb: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } May 16 18:06:22 www kernel: hdb: task_no_data_intr: error=0x04 { DriveStatusError } May 16 18:06:22 www kernel: hdb: Write Cache FAILED Flushing! May 16 18:06:22 www kernel: EXT3 FS on hda3, internal journal
The drive is working fine....
On Sun, May 23, 2004 at 01:18:31AM -0400, Dwaine Garden wrote:
I have the following message from the second hard drive. It worked fine with rh9 and fc2t2. But I'm getting getting cache write problems with fc2 with both 2.6.5 and 2.6.6 kernels. Anything change???
If its a Maxtor then certain maxtors trigger this and its basically harmless. Should be fixed upstream now
Alan Cox wrote:
On Sun, May 23, 2004 at 01:18:31AM -0400, Dwaine Garden wrote:
I have the following message from the second hard drive. It worked fine with rh9 and fc2t2. But I'm getting getting cache write problems with fc2 with both 2.6.5 and 2.6.6 kernels. Anything change???
If its a Maxtor then certain maxtors trigger this and its basically harmless. Should be fixed upstream now
It is a maxtor drive. What in the maxtor drive is causing the problem that other drives do not have? Different cache timings?
Thanks Alan....
On Sun, May 23, 2004 at 09:46:56AM -0400, Dwaine Garden wrote:
It is a maxtor drive. What in the maxtor drive is causing the problem that other drives do not have? Different cache timings?
Certain maxtor drives report that they support LBA48 cache flush, but also report they don't support LBA48 (large disk). In that situation Linux tried to issue an LBA48 cache flush and the drive rejected it. It is fixed upstream