Re: DriveReady SeekComplete Error

[mattia <mattia@nixlab.net>]

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