1 |
Matthias Langer wrote: |
2 |
|
3 |
> Hemmann, Volker Armin wrote: |
4 |
> |
5 |
>> On Saturday 08 October 2005 04:15, Matthias Langer wrote: |
6 |
>> |
7 |
>> |
8 |
>>> I just bought myself a new harddrive. While everything seems to work |
9 |
>>> fine so far, I recognized these messages from dmesg: |
10 |
>>> |
11 |
>>> hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } |
12 |
>>> hdd: dma_intr: error=0x84 { DriveStatusError BadCRC } |
13 |
>>> |
14 |
>>> I'm using vanilla-sources-2.6.12.5. |
15 |
>>> |
16 |
>>> Here are some other parts from dmesg, which are included to describe |
17 |
>>> the |
18 |
>>> relevant hardware in detail: |
19 |
>>> |
20 |
>>> SiI680: IDE controller at PCI slot 0000:00:09.0 |
21 |
>>> .... |
22 |
>>> SiI680: chipset revision 1 |
23 |
>>> SiI680: BASE CLOCK == 133 |
24 |
>>> SiI680: 100% native mode on irq 10 |
25 |
>>> ide0: MMIO-DMA , BIOS settings: hda:pio, hdb:pio |
26 |
>>> ide1: MMIO-DMA , BIOS settings: hdc:pio, hdd:pio |
27 |
>>> ... |
28 |
>>> Probing IDE interface ide1... |
29 |
>>> hdc: _NEC DVD_RW ND-3540A, ATAPI CD/DVD-ROM drive |
30 |
>>> hdd: Maxtor 6L250R0, ATA DISK drive |
31 |
>>> hdd: max request size: 64KiB |
32 |
>>> hdd: 490234752 sectors (251000 MB) w/16384KiB Cache, CHS=30515/255/63, |
33 |
>>> UDMA(133) |
34 |
>>> hdd: cache flushes supported |
35 |
>>> |
36 |
>>> Finally, this is what i get from hdparm -i /dev/hdd: |
37 |
>>> |
38 |
>>> Model=Maxtor 6L250R0, FwRev=BAH41G10, SerialNo=L59CY5SH |
39 |
>>> Config={ Fixed } |
40 |
>>> RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57 |
41 |
>>> BuffType=DualPortCache, BuffSize=16384kB, MaxMultSect=16, MultSect=16 |
42 |
>>> CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455 |
43 |
>>> IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} |
44 |
>>> PIO modes: pio0 pio1 pio2 pio3 pio4 |
45 |
>>> DMA modes: mdma0 mdma1 mdma2 |
46 |
>>> UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 udma6 |
47 |
>>> AdvancedPM=yes: disabled (255) WriteCache=enabled |
48 |
>>> Drive conforms to: (null): |
49 |
>>> |
50 |
>>> Maybe someone can give me a hint what might be wrong with my |
51 |
>>> configuration. |
52 |
>>> |
53 |
>> |
54 |
>> |
55 |
>> first off all, you should never mix ata and atapi devices (harddisks |
56 |
>> and opticals) on one channel. That is known for making problems. |
57 |
>> |
58 |
>> Your error message could be have two origins: your cable is defective |
59 |
>> or not properly seated (easy to check), or your harddisk is on its |
60 |
>> way to the great vendor in the sky. |
61 |
>> Get a different cable. Connect the drive with this new cable. ONLY |
62 |
>> connect the drive, not the burner. Does the error still occurs? Bring |
63 |
>> back the harddisk, where you bought it. |
64 |
>> |
65 |
>> |
66 |
> Well, I tried to connect the drive to another cable with success. |
67 |
> However, with this cable, which seemed to be an older one, the drive |
68 |
> was restricted to UDMA(33). |
69 |
> |
70 |
> My theory about these messages now is the following: |
71 |
> The HD I'm talking about is not directly connected to the ide-cable, |
72 |
> but via a rather old 'HD-Box'. Thus I have: |
73 |
> |
74 |
> Controller->Modern IDE-Cable->HD-Box->Old IDE-Cable->HD. |
75 |
> |
76 |
> I think that the 'Old IDE-Cable' part is causing the troubles. However |
77 |
> I can't verify that without rearranging a bulk of ide-drives. |
78 |
> I'll buy myself a new box and tell you about the results. |
79 |
|
80 |
Well, it was as I expected. After switching to an UDMA(133) compatible |
81 |
mobile rack the error messages are gone. |
82 |
|
83 |
> |
84 |
> Thanks for your hints, Matthias |
85 |
|
86 |
|
87 |
-- |
88 |
gentoo-user@g.o mailing list |