Re: DriveReady SeekComplete Error...

[Dhruv Matani <dhruvbird@gmx.net>]

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.