[gentoo-user-fr] DMA timeout error

Le
Arnaud
bonjour,

j'ai un problme avec un serveur sous gentoo
dans les logs j'ai un DMA timeout error pour mon 2e disque dur, le
problme est alatoire il peut arriv aprs 2-3 jours ou 1 2 =
semaines.
je ne sais pas d'o peut venir le problme, j'ai test le disque =
dur
avec fsck, il n'a pas trouv de problme. j'ai pass galement =
la
disquette du constructeur, pareil rien trouv. le problme c'est que =
je
suis oblig de rebooter la machine a fais perdre galement le =
DMA au
2 autres disque dur.
et hdparm n'arrive pas le ractiver.

d'avance merci

kernel : 2610-gentoo-r4

Feb 7 03:12:21 [kernel] hdb: dma_timer_expiry: dma status == 0x61
Feb 7 03:12:31 [kernel] hdb: DMA timeout error
Feb 7 03:12:31 [kernel] hdb: task_in_intr: status=0x51 { DriveReady =

SeekComplete Error }
- Last output repeated 3 times -
Feb 7 03:12:31 [kernel] ide0: reset: success
Feb 7 03:12:51 [kernel] hdb: dma_timer_expiry: dma status == 0x41
Feb 7 03:13:01 [kernel] hdb: DMA timeout error
Feb 7 03:13:21 [kernel] hdb: dma_timer_expiry: dma status == 0x41
Feb 7 03:13:31 [kernel] hdb: DMA timeout error
Feb 7 03:13:31 [kernel] hdb: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Feb 7 03:13:51 [kernel] hdb: dma_timer_expiry: dma status == 0x41
Feb 7 03:14:01 [kernel] hdb: DMA timeout error



Arnaud=


--
gentoo-user-fr@gentoo.org mailing list
Vos réponses
Trier par : date / pertinence
Michel Paquet
Le #7166011
Bonjour Arnaud

T'a vérifier dans le bios le paramêtre de mise en veille des disques durs??
Mise à part de ca, ca pourrais peut-être aussi l'allimentation qui est
devenu inssufisante ou instable (power supp défectueux)

Michel Paquet
Québec, CA


Arnaud a écrit :

bonjour,

j'ai un problème avec un serveur sous gentoo
dans les logs j'ai un DMA timeout error pour mon 2e disque dur, le
problème est aléatoire il peut arrivé après 2-3 jours ou 1à 2
semaines. je ne sais pas d'où peut venir le problème, j'ai testé le
disque dur avec fsck, il n'a pas trouvé de problème. j'ai passé
également la disquette du constructeur, pareil rien trouvé. le
problème c'est que je suis obligé de rebooter la machine ça fais
perdre également le DMA au 2 autres disque dur.
et hdparm n'arrive pas le réactiver.

d'avance merci

kernel : 2610-gentoo-r4

Feb 7 03:12:21 [kernel] hdb: dma_timer_expiry: dma status == 0x61
Feb 7 03:12:31 [kernel] hdb: DMA timeout error
Feb 7 03:12:31 [kernel] hdb: task_in_intr: status=0x51 { DriveReady
SeekComplete Error }
- Last output repeated 3 times -
Feb 7 03:12:31 [kernel] ide0: reset: success
Feb 7 03:12:51 [kernel] hdb: dma_timer_expiry: dma status == 0x41
Feb 7 03:13:01 [kernel] hdb: DMA timeout error
Feb 7 03:13:21 [kernel] hdb: dma_timer_expiry: dma status == 0x41
Feb 7 03:13:31 [kernel] hdb: DMA timeout error
Feb 7 03:13:31 [kernel] hdb: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Feb 7 03:13:51 [kernel] hdb: dma_timer_expiry: dma status == 0x41
Feb 7 03:14:01 [kernel] hdb: DMA timeout error



Arnaud

--
mailing list






--
mailing list
Arnaud
Le #7165961
--Apple-Mail-3-772439607
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=ISO-8859-1;
format=flowed

Le 8 févr. 05, à 03:31, Michel Paquet a écrit :

Bonjour Arnaud

T'a vérifier dans le bios le paramêtre de mise en veille des disques
durs??
Mise à part de ca, ca pourrais peut-être aussi l'allimentation qui est
devenu inssufisante ou instable (power supp défectueux)

Michel Paquet
Québec, CA



Bonjour,
merci Michel pour ta réponse, je viens de changer l'alimentation je
vais voir si ça marche mieux comme ça.

j'ai également installé smartctl, je pense que mon disque dur est
quand même malade mais si quelqu'un peut me donner son avis.

d'avance merci.
--
Arnaud



--Apple-Mail-3-772439607
Content-Transfer-Encoding: 7bit
Content-Type: application/octet-stream;
x-unix-mode00;
name="smartctl.log"
Content-Disposition: attachment;
filename=smartctl.log

smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION == Device Model: Maxtor 5T060H6
Serial Number: T6HHMNPC
Firmware Version: TAH71DP0
User Capacity: 61,492,838,400 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 6
ATA Standard is: ATA/ATAPI-6 T13 1410D revision 0
Local Time is: Wed Feb 9 06:54:46 2005 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION == SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 30) seconds.
Offline data collection
capabilities: (0x1b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 37) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000a 253 252 000 Old_age Always - 7
3 Spin_Up_Time 0x0027 175 175 063 Pre-fail Always - 17936
4 Start_Stop_Count 0x0032 253 253 000 Old_age Always - 557
5 Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail Always - 1
6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail Offline - 0
7 Seek_Error_Rate 0x000a 253 252 000 Old_age Always - 0
8 Seek_Time_Performance 0x0027 252 244 187 Pre-fail Always - 48327
9 Power_On_Minutes 0x0032 239 239 000 Old_age Always - 492h+37m
10 Spin_Retry_Count 0x002b 236 233 223 Pre-fail Always - 17
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 252 252 000 Old_age Always - 537
196 Reallocated_Event_Count 0x0008 253 253 000 Old_age Offline - 0
197 Current_Pending_Sector 0x0008 253 253 000 Old_age Offline - 0
198 Offline_Uncorrectable 0x0008 253 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0008 199 198 000 Old_age Offline - 1
200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always - 0
201 Soft_Read_Error_Rate 0x000a 253 237 000 Old_age Always - 9
202 TA_Increase_Count 0x000a 253 252 000 Old_age Always - 0
203 Run_Out_Cancel 0x000b 253 252 180 Pre-fail Always - 2
204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age Always - 0
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age Always - 0
207 Spin_High_Current 0x002a 242 242 000 Old_age Always - 11
208 Spin_Buzz 0x002a 249 247 000 Old_age Always - 4
209 Offline_Seek_Performnce 0x0024 253 253 000 Old_age Offline - 0
96 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
97 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
98 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
99 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
100 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0
101 Unknown_Attribute 0x0004 253 253 000 Old_age Offline - 0

SMART Error Log Version: 1
Warning: ATA error count 498 inconsistent with error log pointer 5

ATA Error Count: 498 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DDÚys, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 498 occurred at disk power-on lifetime: 4529 hours (188 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 b0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 b0 00 00:07:53.952 DEVICE RESET

Error 497 occurred at disk power-on lifetime: 4529 hours (188 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 b0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 b0 00 00:07:53.488 DEVICE RESET

Error 496 occurred at disk power-on lifetime: 4529 hours (188 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 b0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 b0 00 23d+20:11:43.568 DEVICE RESET
ca 00 08 3f 00 00 f0 08 23d+20:10:00.384 WRITE DMA
ca 00 08 9f 10 00 f0 08 23d+20:10:00.384 WRITE DMA
ca 00 08 9f 10 00 f0 08 23d+20:10:00.384 WRITE DMA
ca 00 08 9f 10 00 f0 08 23d+20:10:00.384 WRITE DMA

Error 495 occurred at disk power-on lifetime: 4529 hours (188 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 b0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 b0 00 23d+20:11:23.600 DEVICE RESET
ca 00 08 3f 00 00 f0 08 23d+20:10:00.384 WRITE DMA
ca 00 08 9f 10 00 f0 08 23d+20:10:00.384 WRITE DMA
ca 00 08 9f 10 00 f0 08 23d+20:10:00.384 WRITE DMA
ca 00 08 9f 10 00 f0 08 23d+20:10:00.384 WRITE DMA

Error 494 occurred at disk power-on lifetime: 4529 hours (188 days + 17 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 01 01 00 00 b0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 01 01 00 00 b0 00 23d+20:11:14.448 DEVICE RESET
ca 00 08 3f 00 00 f0 08 23d+20:10:00.384 WRITE DMA
ca 00 08 9f 10 00 f0 08 23d+20:10:00.384 WRITE DMA
ca 00 08 9f 10 00 f0 08 23d+20:10:00.384 WRITE DMA
ca 00 08 9f 10 00 f0 08 23d+20:10:00.384 WRITE DMA

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]


Device does not support Selective Self Tests/Logging


--Apple-Mail-3-772439607
Content-Type: text/plain; charset=us-ascii

--
mailing list
--Apple-Mail-3-772439607--
Publicité
Poster une réponse
Anonyme