Portál AbcLinuxu, 11. května 2025 04:56

Dotaz: dma_intr: error=0x84 { DriveStatusError BadCRC }

Johny z Podoli avatar 2.1.2006 23:39 Johny z Podoli | skóre: 26 | blog: rocfdebian
dma_intr: error=0x84 { DriveStatusError BadCRC }
Přečteno: 210×
Odpovědět | Admin
Ahoj, instaluji "novy" server (firewall + fileserver) jedná se o obyč bastl komp, AMD 700Mhz, 1GB ram, disk IBM 160GB.

disk jede v UDMA-66 ... nesetkali jste se s něčím podobným taky?
NET: Registered protocol family 17
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
Můj web o táborech: Letní dětské tábory, Hudební tábor , Můj nový blog na Nul.cz
Nástroje: Začni sledovat (0) ?Zašle upozornění na váš email při vložení nového komentáře.

Odpovědi

Johny z Podoli avatar 3.1.2006 00:10 Johny z Podoli | skóre: 26 | blog: rocfdebian
Rozbalit Rozbalit vše Re: dma_intr: error=0x84 { DriveStatusError BadCRC }
Odpovědět | | Sbalit | Link | Blokovat | Admin
info o disku...
/dev/hda:

 Model=HDT722516DLAT80, FwRev=V43OA70A, SerialNo=VD271BTCC5722C
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=51
 BuffType=DualPortCache, BuffSize=7674kB, MaxMultSect=16, MultSect=off
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
 IORDY=on/off, tPIO={min:240,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 udma5 udma6
 AdvancedPM=yes: disabled (255) WriteCache=enabled
 Drive conforms to: Reserved:

 * signifies the current active mode

Můj web o táborech: Letní dětské tábory, Hudební tábor , Můj nový blog na Nul.cz
3.1.2006 00:12 Zdeněk Burda | skóre: 61 | blog: Zdendův blog | Praha
Rozbalit Rozbalit vše Re: dma_intr: error=0x84 { DriveStatusError BadCRC }
Mrkni se ještěna smartctl -a /dev/hda a taky zkus jiný kabel.
-- Nezdar není hanbou, hanbou je strach z pokusu.
Johny z Podoli avatar 3.1.2006 00:16 Johny z Podoli | skóre: 26 | blog: rocfdebian
Rozbalit Rozbalit vše Re: dma_intr: error=0x84 { DriveStatusError BadCRC }
nevím, co v tom mám hledat... jedná se o uplně nový disk.
dream:~# smartctl -a /dev/hda
smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model:     HDT722516DLAT80
Serial Number:    VD271BTCC5722C
Firmware Version: V43OA70A
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   7
ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 1
Local Time is:    Tue Jan  3 00:15:47 2006 CET
SMART support is: Available - device has SMART capability.
SMART support is: Disabled

SMART Disabled. Use option -s with argument 'on' to enable it.
jdu zkusit ten kabel.
Můj web o táborech: Letní dětské tábory, Hudební tábor , Můj nový blog na Nul.cz
Johny z Podoli avatar 3.1.2006 00:19 Johny z Podoli | skóre: 26 | blog: rocfdebian
Rozbalit Rozbalit vše Re: dma_intr: error=0x84 { DriveStatusError BadCRC }
Uz jsem si precetl ze je treba smart zapnout... takze tedy:

smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: HDT722516DLAT80 Serial Number: VD271BTCC5722C Firmware Version: V43OA70A Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 7 ATA Standard is: ATA/ATAPI-7 T13 1532D revision 1 Local Time is: Tue Jan 3 00:18:12 2006 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: (3385) seconds. Offline data collection capabilities: (0x5b) 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. 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. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 57) 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 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0 3 Spin_Up_Time 0x0007 122 122 024 Pre-fail Always - 319 (Average 254) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 23 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 100 100 020 Pre-fail Offline - 0 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 2851 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 23 192 Power-Off_Retract_Count 0x0032 100 100 050 Old_age Always - 142 193 Load_Cycle_Count 0x0012 100 100 050 Old_age Always - 142 194 Temperature_Celsius 0x0002 166 166 000 Old_age Always - 33 (Lifetime Min/Max 22/43) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 91 (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=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 91 occurred at disk power-on lifetime: 2851 hours (118 days + 19 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 7e 32 99 e0 Error: ICRC, ABRT at LBA = 0x0099327e = 10039934 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 35 00 40 3f 2b 99 e0 00 01:02:01.100 WRITE DMA EXT 35 00 50 e7 2a 99 e0 00 01:02:01.100 WRITE DMA EXT 35 00 08 d7 2a 99 e0 00 01:02:01.100 WRITE DMA EXT 35 00 08 97 c6 00 e0 00 01:02:01.100 WRITE DMA EXT 35 00 c8 cf c5 00 e0 00 01:02:01.100 WRITE DMA EXT Error 90 occurred at disk power-on lifetime: 2851 hours (118 days + 19 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 1e 06 38 e5 Error: ICRC, ABRT at LBA = 0x0538061e = 87557662 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 35 00 10 0f 06 38 e0 00 00:51:58.200 WRITE DMA EXT 35 00 10 ef 05 38 e0 00 00:51:58.200 WRITE DMA EXT 35 00 08 cf 05 38 e0 00 00:51:58.200 WRITE DMA EXT 35 00 08 b7 05 38 e0 00 00:51:58.200 WRITE DMA EXT 35 00 08 9f 05 38 e0 00 00:51:58.200 WRITE DMA EXT Error 89 occurred at disk power-on lifetime: 2851 hours (118 days + 19 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 d6 0d 99 e0 Error: ICRC, ABRT at LBA = 0x00990dd6 = 10030550 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 35 00 00 d7 05 99 e0 00 00:51:24.700 WRITE DMA EXT 35 00 18 bf 00 99 e0 00 00:51:24.700 WRITE DMA EXT 35 00 50 67 00 99 e0 00 00:51:24.700 WRITE DMA EXT 35 00 08 57 00 99 e0 00 00:51:24.700 WRITE DMA EXT 35 00 08 a7 b7 00 e0 00 00:51:24.700 WRITE DMA EXT Error 88 occurred at disk power-on lifetime: 2851 hours (118 days + 19 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 36 d2 39 e5 Error: ICRC, ABRT at LBA = 0x0539d236 = 87675446 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 35 00 60 d7 d1 39 e0 00 00:51:23.700 WRITE DMA EXT 35 00 38 b7 c1 8d e0 00 00:51:23.700 WRITE DMA EXT 35 00 18 6f f4 9f e0 00 00:51:23.700 WRITE DMA EXT 25 00 08 3f 01 3b e0 00 00:51:23.500 READ DMA EXT 25 00 08 77 00 39 e0 00 00:51:23.500 READ DMA EXT Error 87 occurred at disk power-on lifetime: 2851 hours (118 days + 19 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 16 8d 00 e0 Error: ICRC, ABRT at LBA = 0x00008d16 = 36118 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 35 00 50 c7 8c 00 e0 00 00:46:14.900 WRITE DMA EXT 35 00 c8 3f e3 9f e0 00 00:46:14.900 WRITE DMA EXT 35 00 48 27 e2 9f e0 00 00:46:14.900 WRITE DMA EXT 35 00 60 bf e1 9f e0 00 00:46:14.900 WRITE DMA EXT 35 00 08 bf 8c 00 e0 00 00:46:14.900 WRITE DMA EXT SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] Warning! SMART Selective Self-Test Log Structure error: invalid SMART checksum. SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.

Můj web o táborech: Letní dětské tábory, Hudební tábor , Můj nový blog na Nul.cz
Johny z Podoli avatar 3.1.2006 00:12 Johny z Podoli | skóre: 26 | blog: rocfdebian
Rozbalit Rozbalit vše Re: dma_intr: error=0x84 { DriveStatusError BadCRC }
Odpovědět | | Sbalit | Link | Blokovat | Admin
jeste snad tohle....
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03)
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22)
0000:00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10)
0000:00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10)
0000:00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10)
0000:00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)
0000:00:08.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 34)
0000:00:09.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 30)
0000:00:11.0 VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 01)
0000:00:13.0 Unknown mass storage controller: Triones Technologies, Inc. HPT366/368/370/370A/372 (rev 03)
Můj web o táborech: Letní dětské tábory, Hudební tábor , Můj nový blog na Nul.cz
3.1.2006 00:29 Ritchie | skóre: 27 | blog: Ritchie's | Berlin
Rozbalit Rozbalit vše Re: dma_intr: error=0x84 { DriveStatusError BadCRC }
Odpovědět | | Sbalit | Link | Blokovat | Admin
Setkali a vyřešili reklamací.
Johny z Podoli avatar 3.1.2006 00:39 Johny z Podoli | skóre: 26 | blog: rocfdebian
Rozbalit Rozbalit vše Re: dma_intr: error=0x84 { DriveStatusError BadCRC }
pokud se nepletu, tak se jedná o jiný problém, navíc tento disk v jiném PC funguje naprosto korektně.

Johny
Můj web o táborech: Letní dětské tábory, Hudební tábor , Můj nový blog na Nul.cz
3.1.2006 00:49 Ritchie | skóre: 27 | blog: Ritchie's | Berlin
Rozbalit Rozbalit vše Re: dma_intr: error=0x84 { DriveStatusError BadCRC }
Chyba může být v řadiči, kabelu, disku. Chipset KT133 měl prý problémy s DMA přenosy. Vyskytuje se chyba deterministicky nebo náhodně?
Johny z Podoli avatar 3.1.2006 00:52 Johny z Podoli | skóre: 26 | blog: rocfdebian
Rozbalit Rozbalit vše Re: dma_intr: error=0x84 { DriveStatusError BadCRC }
Pravda je, že obecně tento komp už měl jednou s 80GB seagatem problém - nechtěl vubec naběhnout a hlásil samou chybu. Pak se to "samo" vyřešilo.

Jinak používám už třetí zcela novej 80žil. kabel. Chyba se vyskytuje výhradně při větším množství přístupů na disk, specialně třeba při tarování a podobně.

Johny
Můj web o táborech: Letní dětské tábory, Hudební tábor , Můj nový blog na Nul.cz
3.1.2006 03:09 Thunder.m | skóre: 35 | blog: e17
Rozbalit Rozbalit vše Re: dma_intr: error=0x84 { DriveStatusError BadCRC }
S tím přesně ty staré desky s KT133 měly problémy, zkus update biosu, nebo jádra, jestli máš nějaké starší než 2.6.14
Johny z Podoli avatar 3.1.2006 14:09 Johny z Podoli | skóre: 26 | blog: rocfdebian
Rozbalit Rozbalit vše Re: dma_intr: error=0x84 { DriveStatusError BadCRC }
mám 2.6.8, kernel 2.6.14 to řeší?
Můj web o táborech: Letní dětské tábory, Hudební tábor , Můj nový blog na Nul.cz
3.1.2006 14:18 David Jež | skóre: 42 | blog: -djz | Brno
Rozbalit Rozbalit vše Re: dma_intr: error=0x84 { DriveStatusError BadCRC }
Spíše než magii zkus standardní postup pro tyto případy: Povolit nebo zakázat CONFIG_IDEDISK_MULTI_MODE, CONFIG_IDEDMA_IVB a zkontroluj jestli máš také podporu pro svůj řadič.
-djz
"Yield to temptation; it may not pass your way again." -- R. A. Heinlein

Založit nové vláknoNahoru

Tiskni Sdílej: Linkuj Jaggni to Vybrali.sme.sk Google Del.icio.us Facebook

ISSN 1214-1267, (c) 1999-2007 Stickfish s.r.o.