Skip to contentSkip to conversation

Detecting I/O error and Halting System

DISCUSSION zine el abidine Hamid 5 participants 10 messages Mar 27, 2006 – Apr 2, 2006

lore
Share & tools
lore
#0 lore raw

Hi everybody,

I have I/O error which occurs on servers based on a VIA VT82C686 chipset and I have to prevent or stop the error. I spent a lot time for searching solutions to stop the error but I don't found anything, So I want to write a module which will surveil the HDD and stops the system after sending a mail.

I read a lot of documents about kernel and writting modules but I don't know how to start...? Help, please.

I'm not closed to others solutions (like smartd, or writting classical programms)

Best regards.

Zine

PS : this are errors du to VIA chipset; if anyone knows wath appens...?

 Feb 12 04:46:03 porte_de_clignancourt_nds_b kernel:
hda: timeout waiting for DMA
Feb 12 04:46:06 alesia_nds_b ucd-snmp[812]: Connection
from 104.25.3.11
Feb 12 04:46:23 porte_de_clignancourt_nds_b kernel:
ide_dmaproc: chipset supported ide_dma_timeout func
only: 14
Feb 12 04:46:23 porte_de_clignancourt_nds_b kernel:
hda: status timeout: status=0xd0 { Busy }      adapter
disque annonce un status busy du DMA
Feb 12 04:46:23 porte_de_clignancourt_nds_b kernel:
hda: drive not ready for command
Feb 12 04:46:23 porte_de_clignancourt_nds_b
ucd-snmp[813]: Connection from 104.1.3.11
Feb 12 04:46:23 porte_de_clignancourt_nds_b
ucd-snmp[813]: Connection from 104.1.3.11
Feb 12 04:46:23 porte_de_clignancourt_nds_b last
message repeated 3 times
Feb 12 04:46:23 porte_de_clignancourt_nds_b kernel:
ide0: reset: success             
Feb 12 10:22:38 porte_de_clignancourt_nds_b kernel:
hda: timeout waiting for DMA
Feb 12 10:24:46 porte_de_clignancourt_nds_b kernel:
ide_dmaproc: chipset supported ide_dma_timeout func
only: 14
Feb 12 10:24:46 porte_de_clignancourt_nds_b kernel:
hda: status timeout: status=0xd0 { Busy }
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
hda: drive not ready for command
Feb 12 10:24:47 porte_de_clignancourt_nds_b
ucd-snmp[813]: Connection from 104.1.3.11
Feb 12 10:24:47 porte_de_clignancourt_nds_b last
message repeated 4 times
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
ide0: reset timed-out, status=0x80                   
le premier reser de ide0 est en échec
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
hda: status timeout: status=0x80 { Busy }
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
hda: drive not ready for command
Feb 12 10:24:47 porte_de_clignancourt_nds_b
ucd-snmp[813]: Connection from 104.1.3.11
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:

ide0: reset: success

Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:

hda: irq timeout: status=0xd0 { Busy }

Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:

hda: DMA disabled

Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
ide0: reset timed-out, status=0x80
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
hda: status timeout: status=0x80 { Busy }        
nouvel échec de reset
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
hda: drive not ready for command
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:

ide0: reset: success

Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
ide0: reset timed-out, status=0x80
Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
hda: status timeout: status=0x80 { Busy }
Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
hda: drive not ready for command
Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
ide0: reset timed-out, status=0x80
Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
end_request: I/O error, dev 03:02 (hda), sector 102263
Feb 12 13:45:38 porte_de_clignancourt_nds_b syslogd:
/var/log/maillog: Input/output error
Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
end_request: I/O error, dev 03:02 (hda), sector 110720
Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:

end_request: I/O error, dev 03:02 (hda), sector 110728

___________________________________________________________________________
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com

#1 lore raw
Quoted 100 lines · zine el abidine Hamid

Hi everybody,

I have I/O error which occurs on servers based on a VIA VT82C686 chipset and I have to prevent or stop the error. I spent a lot time for searching solutions to stop the error but I don't found anything, So I want to write a module which will surveil the HDD and stops the system after sending a mail.

I read a lot of documents about kernel and writting modules but I don't know how to start...? Help, please.

I'm not closed to others solutions (like smartd, or writting classical programms)

Best regards.

Zine

PS : this are errors du to VIA chipset; if anyone knows wath appens...?

Feb 12 04:46:03 porte_de_clignancourt_nds_b kernel:
hda: timeout waiting for DMA
Feb 12 04:46:06 alesia_nds_b ucd-snmp[812]: Connection
from 104.25.3.11
Feb 12 04:46:23 porte_de_clignancourt_nds_b kernel:
ide_dmaproc: chipset supported ide_dma_timeout func
only: 14
Feb 12 04:46:23 porte_de_clignancourt_nds_b kernel:
hda: status timeout: status=0xd0 { Busy }      adapter
disque annonce un status busy du DMA
Feb 12 04:46:23 porte_de_clignancourt_nds_b kernel:
hda: drive not ready for command
Feb 12 04:46:23 porte_de_clignancourt_nds_b
ucd-snmp[813]: Connection from 104.1.3.11
Feb 12 04:46:23 porte_de_clignancourt_nds_b
ucd-snmp[813]: Connection from 104.1.3.11
Feb 12 04:46:23 porte_de_clignancourt_nds_b last
message repeated 3 times
Feb 12 04:46:23 porte_de_clignancourt_nds_b kernel:
ide0: reset: success
Feb 12 10:22:38 porte_de_clignancourt_nds_b kernel:
hda: timeout waiting for DMA
Feb 12 10:24:46 porte_de_clignancourt_nds_b kernel:
ide_dmaproc: chipset supported ide_dma_timeout func
only: 14
Feb 12 10:24:46 porte_de_clignancourt_nds_b kernel:
hda: status timeout: status=0xd0 { Busy }
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
hda: drive not ready for command
Feb 12 10:24:47 porte_de_clignancourt_nds_b
ucd-snmp[813]: Connection from 104.1.3.11
Feb 12 10:24:47 porte_de_clignancourt_nds_b last
message repeated 4 times
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
ide0: reset timed-out, status=0x80
le premier reser de ide0 est en échec
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
hda: status timeout: status=0x80 { Busy }
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
hda: drive not ready for command
Feb 12 10:24:47 porte_de_clignancourt_nds_b
ucd-snmp[813]: Connection from 104.1.3.11
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:

ide0: reset: success

Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:

hda: irq timeout: status=0xd0 { Busy }

Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:

hda: DMA disabled

Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
ide0: reset timed-out, status=0x80
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
hda: status timeout: status=0x80 { Busy }
nouvel échec de reset
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
hda: drive not ready for command
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:

ide0: reset: success

Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
ide0: reset timed-out, status=0x80
Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
hda: status timeout: status=0x80 { Busy }
Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
hda: drive not ready for command
Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
ide0: reset timed-out, status=0x80
Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
end_request: I/O error, dev 03:02 (hda), sector 102263
Feb 12 13:45:38 porte_de_clignancourt_nds_b syslogd:
/var/log/maillog: Input/output error
Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
end_request: I/O error, dev 03:02 (hda), sector 110720
Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
Quoted 3 lines

end_request: I/O error, dev 03:02 (hda), sector 110728

Maybe you should just fix the problem rather than attempting to work around it! The problem is that that you system has difficulty communicating with a hard disk. This is caused by either:

(1) Bad hard disk.
(2) Bad cable.
(3) Improper configuration of one or more disks.

Since a reset timed out, it is likely that one of the disks that share the same cable is defective, not necessarily /dev/hda if you have another drive on the same cable. If you have only one drive per cable (or only one drive), it is likely that /dev/hda is (or becomes defective). Note that the disk can fail if it gets too hot.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.15.4 on an i686 machine (5589.42 BogoMips). Warning : 98.36% of all statistics are fiction, book release in April. _


****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to [email protected] - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.

#2 lore raw
In reply to zine el abidine Hamid
Quoted 2 lines · zine el abidine Hamid

hda: status timeout: status=0xd0 { Busy } adapter
disque annonce un status busy du DMA

If I'm reading the translation right then your hard disk decided it was busy and then never came back

Quoted 2 lines
Feb 12 04:46:23 porte_de_clignancourt_nds_b kernel:

ide0: reset: success

So the IDE layer tried to reset it

Quoted 2 lines
Feb 12 10:22:38 porte_de_clignancourt_nds_b kernel:

hda: timeout waiting for DMA

Which didnt help

Quoted 2 lines
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:

ide0: reset: success

Still trying

Quoted 5 lines
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:

hda: irq timeout: status=0xd0 { Busy }

Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:

hda: DMA disabled

We gave up on DMA to see if PIO would help

Quoted 11 lines
                              
   
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
ide0: reset timed-out, status=0x80
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
hda: status timeout: status=0x80 { Busy }        
nouvel échec de reset
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:
hda: drive not ready for command
Feb 12 10:24:47 porte_de_clignancourt_nds_b kernel:

ide0: reset: success

And reset..

Quoted 13 lines
Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
hda: status timeout: status=0x80 { Busy }
Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
hda: drive not ready for command
Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
ide0: reset timed-out, status=0x80
Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
end_request: I/O error, dev 03:02 (hda), sector 102263
Feb 12 13:45:38 porte_de_clignancourt_nds_b syslogd:
/var/log/maillog: Input/output error
Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
end_request: I/O error, dev 03:02 (hda), sector 110720
Feb 12 13:45:38 porte_de_clignancourt_nds_b kernel:
Quoted 1 line

end_request: I/O error, dev 03:02 (hda), sector 110728

Eventually we give up.

First thing to check would be the disk and the temperature, then the cabling. In particular make sure the *long* part of the cable is between the drive and the controller.

#3 lore raw

First of all, thank you for your analysis.

I don't think that it's a HDD problem nor a cable problem because the servers are new. We have tried different HDD (seagate, maxtor) but it has not help anyway.
It's perhaps a temperature problem but we make a lot tests in hard condition (high temperature) successfuly...

One thinks that the problem comes from the VIA chipset VT82c686 (it's also the opinion of Dick Johnson (linux-os) whom advised me to try UDMA33 instead of UDMA66).

How can I determine the problem?

I want to add that the HDD seems to be disconnected (the BIOS can't find any drive for boot) after a simple reset. We must switch off the servers to get them work again.
However, it takes a long time (4 mounths and more) before the HDD fell down. I want to work around by write a module which will supervise the HDD. I know how to write a module (I used the lkmpg guide
(http://www.tldp.org/LDP/lkmpg/) but how can I shutdown Linux from inside a module...?

best regards.

Zine.

Quoted 82 lines · --- Alan Cox
Quoted 1 line · zine el abidine Hamid

hda: status timeout: status=0xd0 { Busy }

adapter

Quoted 1 line

disque annonce un status busy du DMA

If I'm reading the translation right then your hard disk decided
it was busy and then never came back

Quoted 1 line
Feb 12 04:46:23 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

ide0: reset: success

So the IDE layer tried to reset it

Quoted 1 line
Feb 12 10:22:38 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

hda: timeout waiting for DMA

Which didnt help

Quoted 1 line
Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

ide0: reset: success

Still trying

Quoted 1 line
Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 4 lines

hda: irq timeout: status=0xd0 { Busy }

Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

hda: DMA disabled

We gave up on DMA to see if PIO would help

Quoted 3 lines
                              
   
Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 2 lines

ide0: reset timed-out, status=0x80

Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 3 lines

hda: status timeout: status=0x80 { Busy } nouvel échec de reset

Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 2 lines

hda: drive not ready for command

Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

ide0: reset: success

And reset..

Quoted 1 line
Feb 12 13:45:38 porte_de_clignancourt_nds_b

kernel:

Quoted 2 lines

hda: status timeout: status=0x80 { Busy }

Feb 12 13:45:38 porte_de_clignancourt_nds_b

kernel:

Quoted 2 lines

hda: drive not ready for command

Feb 12 13:45:38 porte_de_clignancourt_nds_b

kernel:

Quoted 2 lines

ide0: reset timed-out, status=0x80

Feb 12 13:45:38 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

end_request: I/O error, dev 03:02 (hda), sector

102263

Quoted 1 line
Feb 12 13:45:38 porte_de_clignancourt_nds_b

syslogd:

Quoted 2 lines

/var/log/maillog: Input/output error

Feb 12 13:45:38 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

end_request: I/O error, dev 03:02 (hda), sector

110720

Quoted 1 line
Feb 12 13:45:38 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

end_request: I/O error, dev 03:02 (hda), sector

110728

Quoted 10 lines

Eventually we give up.

First thing to check would be the disk and the temperature, then the
cabling. In particular make sure the *long* part of the cable is between
the drive and the controller.

___________________________________________________________________________
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com

#4 lore raw
Quoted 2 lines · zine el abidine Hamid

I don't think that it's a HDD problem nor a cable problem because the servers are new. We have tried

New. Thats another word for "untested" I believe 8)

Quoted 1 line

How can I determine the problem?

I would consult the hardware vendor

Quoted 4 lines

I want to add that the HDD seems to be disconnected (the BIOS can't find any drive for boot) after a simple reset. We must switch off the servers to get them work again.

Thats strongly indicating a hardware problem.

Quoted 2 lines

(http://www.tldp.org/LDP/lkmpg/) but how can I shutdown Linux from inside a module...?

See the softdog driver for an example.

#5 lore raw
Quoted 1 line · Alan Cox

See the softdog driver for an example.

The usermode agent (watchdog(8) can, btw monitor the availableness of a file, no need to write a module. MAybe this feature was added after somebody took that code over from you? :)

watchdog.conf(5) says:

# file = <filename> Set file name for file mode. This option can be
# given as often as you like to check several files.

Bernd

#6 lore raw

watchdog isn't helpfull because some parts of the drives (some directories, and some command) seems to be accessible and most aren't. But I think that the files that seems to be readable are on the cache.

Quoted 16 lines · --- Bernd Eckenfels
Quoted 1 line · Alan Cox

See the softdog driver for an example.

The usermode agent (watchdog(8) can, btw monitor the availableness of a
file, no need to write a module. MAybe this feature was added after somebody
took that code over from you? :)

watchdog.conf(5) says:

# file = <filename> Set file name for file mode.
This option can be
# given as often as you like to check
several files.

Quoted 9 lines

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

___________________________________________________________________________
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com

#7 lore raw
In reply to Alan Cox

Hi Dick,

Excuses me for the silence.

Can you tell me why the drive stops to respond? Where the problem starts? As I tell before, we tried different drives and that has not help us.

Friday, The constructor comes to a meeting in our offices and they affirm that their materials is ok.

Have you read some articles that pointed out failures on the South Bridge VIA VT82c686 or other's chipset off the VIA PN133 architecture?
(http://www.via.com.tw/en/products/chipsets/legacy/pn133/)

If it can help, this are the description :

00:00.0 Host bridge: VIA Technologies, Inc. VT8605 [ProSavage PM133] (rev 01)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8605 [PM133 AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40
)
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 1a)
00:07.3 USB Controller: VIA Technologies, Inc. USB (rev 1a)
00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio
Controller (rev 50)
00:10.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
01:00.0 VGA compatible controller: S3 Inc. ProSavage PM133 (rev 02) [root@Porte_de_Clignancourt_nds_b root]# lspci -n 00:00.0 Class 0600: 1106:0605 (rev 01) 00:01.0 Class 0604: 1106:8605
00:07.0 Class 0601: 1106:0686 (rev 40) 00:07.1 Class 0101: 1106:0571 (rev 06) 00:07.2 Class 0c03: 1106:3038 (rev 1a) 00:07.3 Class 0c03: 1106:3038 (rev 1a) 00:07.4 Class 0680: 1106:3057 (rev 40) 00:07.5 Class 0401: 1106:3058 (rev 50) 00:10.0 Class 0200: 8086:1229 (rev 08) 01:00.0 Class 0300: 5333:8a25 (rev 02)

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 8
model name : Pentium III (Coppermine)
stepping : 10
cpu MHz : 998.393
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8
sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 1992.29

Quoted 16 lines · --- Alan Cox
Quoted 2 lines · zine el abidine Hamid

I don't think that it's a HDD problem nor a cable problem because the servers are new. We have tried

New. Thats another word for "untested" I believe 8)

Quoted 1 line

How can I determine the problem?

I would consult the hardware vendor

Quoted 1 line

I want to add that the HDD seems to be

disconnected

Quoted 2 lines

(the BIOS can't find any drive for boot) after a simple reset. We must switch off the servers to

get

Quoted 10 lines
Quoted 1 line

them work again.

Thats strongly indicating a hardware problem.

Quoted 2 lines

(http://www.tldp.org/LDP/lkmpg/) but how can I shutdown Linux from inside a module...?

See the softdog driver for an example.

___________________________________________________________________________
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com

#8 lore raw
In reply to zine el abidine Hamid
Quoted 28 lines · zine el abidine Hamid

First of all, thank you for your analysis.

I don't think that it's a HDD problem nor a cable problem because the servers are new. We have tried different HDD (seagate, maxtor) but it has not help anyway.
It's perhaps a temperature problem but we make a lot tests in hard condition (high temperature) successfuly...

One thinks that the problem comes from the VIA chipset VT82c686 (it's also the opinion of Dick Johnson (linux-os) whom advised me to try UDMA33 instead of UDMA66).

How can I determine the problem?

I want to add that the HDD seems to be disconnected (the BIOS can't find any drive for boot) after a simple reset. We must switch off the servers to get them work again.
However, it takes a long time (4 mounths and more) before the HDD fell down. I want to work around by write a module which will supervise the HDD. I know how to write a module (I used the lkmpg guide
(http://www.tldp.org/LDP/lkmpg/) but how can I shutdown Linux from inside a module...?

Quoted 3 lines

best regards.

Zine.

I take it that you are aware of a drive monitoring utility called smartd? By querying the drive after a new powerup, you may be able to extract usefull information about its health.

Quoted 113 lines
Quoted 112 lines · --- Alan Cox

On Llu, 2006-03-27 at 16:55 +0200, zine el abidine

Quoted 1 line · Hamid

hda: status timeout: status=0xd0 { Busy }

adapter

Quoted 1 line

disque annonce un status busy du DMA

If I'm reading the translation right then your hard disk decided
it was busy and then never came back

Quoted 1 line
Feb 12 04:46:23 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

ide0: reset: success

So the IDE layer tried to reset it

Quoted 1 line
Feb 12 10:22:38 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

hda: timeout waiting for DMA

Which didnt help

Quoted 1 line
Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

ide0: reset: success

Still trying

Quoted 1 line
Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 4 lines

hda: irq timeout: status=0xd0 { Busy }

Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

hda: DMA disabled

We gave up on DMA to see if PIO would help

Quoted 1 line
Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 2 lines

ide0: reset timed-out, status=0x80

Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 3 lines

hda: status timeout: status=0x80 { Busy } nouvel échec de reset

Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 2 lines

hda: drive not ready for command

Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

ide0: reset: success

And reset..

Quoted 1 line
Feb 12 13:45:38 porte_de_clignancourt_nds_b

kernel:

Quoted 2 lines

hda: status timeout: status=0x80 { Busy }

Feb 12 13:45:38 porte_de_clignancourt_nds_b

kernel:

Quoted 2 lines

hda: drive not ready for command

Feb 12 13:45:38 porte_de_clignancourt_nds_b

kernel:

Quoted 2 lines

ide0: reset timed-out, status=0x80

Feb 12 13:45:38 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

end_request: I/O error, dev 03:02 (hda), sector

102263

Quoted 1 line
Feb 12 13:45:38 porte_de_clignancourt_nds_b

syslogd:

Quoted 2 lines

/var/log/maillog: Input/output error

Feb 12 13:45:38 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

end_request: I/O error, dev 03:02 (hda), sector

110720

Quoted 1 line
Feb 12 13:45:38 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

end_request: I/O error, dev 03:02 (hda), sector

110728

Eventually we give up.

First thing to check would be the disk and the temperature, then the
cabling. In particular make sure the *long* part of the cable is between
the drive and the controller.

Signature · 7 lines
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules.  I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
#9 lore raw

I know about smartd, but the HDD are ok. When the
problem happen's, we have to switch off/on the servers and then go on without any errors; The servers work's after that like nothing happen's...

Quoted 152 lines · --- Gene Heskett
Quoted 7 lines · zine el abidine Hamid

First of all, thank you for your analysis.

I don't think that it's a HDD problem nor a cable problem because the servers are new. We have tried different HDD (seagate, maxtor) but it has not help anyway.
It's perhaps a temperature problem but we make a

lot

Quoted 4 lines

tests in hard condition (high temperature) successfuly...

One thinks that the problem comes from the VIA

chipset

Quoted 17 lines

VT82c686 (it's also the opinion of Dick Johnson (linux-os) whom advised me to try UDMA33 instead of UDMA66).

How can I determine the problem?

I want to add that the HDD seems to be disconnected (the BIOS can't find any drive for boot) after a simple reset. We must switch off the servers to get them work again.
However, it takes a long time (4 mounths and more) before the HDD fell down. I want to work around by write a module which will supervise the HDD. I know how to write a module (I used the lkmpg guide
(http://www.tldp.org/LDP/lkmpg/) but how can I shutdown Linux from inside a module...?

Quoted 3 lines

best regards.

Zine.

I take it that you are aware of a drive monitoring utility called
smartd? By querying the drive after a new powerup, you may be able to
extract usefull information about its health.

Quoted 2 lines
Quoted 1 line · --- Alan Cox

On Llu, 2006-03-27 at 16:55 +0200, zine el

abidine

Quoted 9 lines
Quoted 9 lines
Quoted 1 line · Hamid

hda: status timeout: status=0xd0 { Busy }

adapter

Quoted 1 line

disque annonce un status busy du DMA

If I'm reading the translation right then your

hard

Quoted 97 lines
Quoted 97 lines

disk decided
it was busy and then never came back

Quoted 1 line
Feb 12 04:46:23 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

ide0: reset: success

So the IDE layer tried to reset it

Quoted 1 line
Feb 12 10:22:38 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

hda: timeout waiting for DMA

Which didnt help

Quoted 1 line
Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

ide0: reset: success

Still trying

Quoted 1 line
Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 4 lines

hda: irq timeout: status=0xd0 { Busy }

Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

hda: DMA disabled

We gave up on DMA to see if PIO would help

Quoted 1 line
Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 2 lines

ide0: reset timed-out, status=0x80

Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 3 lines

hda: status timeout: status=0x80 { Busy } nouvel échec de reset

Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 2 lines

hda: drive not ready for command

Feb 12 10:24:47 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

ide0: reset: success

And reset..

Quoted 1 line
Feb 12 13:45:38 porte_de_clignancourt_nds_b

kernel:

Quoted 2 lines

hda: status timeout: status=0x80 { Busy }

Feb 12 13:45:38 porte_de_clignancourt_nds_b

kernel:

Quoted 2 lines

hda: drive not ready for command

Feb 12 13:45:38 porte_de_clignancourt_nds_b

kernel:

Quoted 2 lines

ide0: reset timed-out, status=0x80

Feb 12 13:45:38 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

end_request: I/O error, dev 03:02 (hda), sector

102263

Quoted 1 line
Feb 12 13:45:38 porte_de_clignancourt_nds_b

syslogd:

Quoted 2 lines

/var/log/maillog: Input/output error

Feb 12 13:45:38 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

end_request: I/O error, dev 03:02 (hda), sector

110720

Quoted 1 line
Feb 12 13:45:38 porte_de_clignancourt_nds_b

kernel:

Quoted 1 line

end_request: I/O error, dev 03:02 (hda), sector

110728

Eventually we give up.

Quoted 27 lines
Quoted 3 lines
Quoted 3 lines

First thing to check would be the disk and the
temperature, then the
cabling. In particular make sure the *long* part

of

Quoted 2 lines
Quoted 2 lines

the cable is between
the drive and the controller.

Signature · 18 lines
Cheers, Gene
People having trouble with vz bouncing email to me
should add the word
'online' between the 'verizon', and the dot which
bypasses vz's
stupid bounce rules.  I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note,
additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights
reserved.
-
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/

___________________________________________________________________________
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com