Skip to contentSkip to conversation

DriveReady SeekComplete Error...

DISCUSSION Dhruv Matani 3 participants 6 messages Jul 13, 2004 1 message not in the archive

lore
Share & tools
lore

Dhruv Matani

author
#0 lore raw

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 ;-)

Signature · 6 lines
        -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.
#1 lore raw

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" <[email protected]>
To: <[email protected]>
Sent: Tuesday, July 13, 2004 7:30 AM
Subject: DriveReady SeekComplete Error...

Quoted 27 lines

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 ;-)

Signature · 5 lines
        -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.
(quoted diff) +0 -2
-Anon.
 
 
-

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/

A message that is not in the archive (sent off-list or not yet received): [email protected]

author
#3 lore raw
Quoted 30 lines · Evaldo Gardenali

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

Quoted 8 lines

~ 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?

Quoted 32 lines

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

Signature · 6 lines
        -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.
author
#4 lore raw
In reply to a message not in the archive

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

Quoted 70 lines · Evaldo Gardenali

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

Signature · 6 lines
        -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.
author
#5 lore raw
In reply to a message not in the archive

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.

Quoted 70 lines · Evaldo Gardenali

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

Signature · 6 lines
        -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.
#6 lore raw

Hi,

Quoted 4 lines · 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

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

Quoted 2 lines

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

Quoted 5 lines

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.

Quoted 4 lines

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