/dev/hdl not showing up with 2.6.8-rc2-mm1

I have an x86 setup with a large(9) number of ide hard drives. With 2.6.8-rc2, all of them show up (as a,b,d,e,f,g,h,i,j,k, and l), but on 2.6.8-rc2-mm1, the last one (hdl) does not show up, even though it's a slave on the same controller as hdk. Everything about the config is identical between the two. Is there some default limit or other restriction in the current mm kernels that's preventing that drive from showing up? I haven't tried any other recent mm kernels, so I don't know when this was introduced.

-Tupshin

Well, I found the source of the problem. Dmesg gives a "ignoring undecoded slave" message, which is coming from the fix-ide-probe-double-detection patch.

Both /dev/hdk and /dev/hdl are the same model of hard drive, and unfortunately, they both report that they are Model M0000000000000000000, which triggers the double detection removal.

Does anybody have a suggestion (besides maintaining my own kernel without this patch)? Is the serial number settable? Is there a boot param I can use?

Also, what is in /proc/ide/hd?/identity besides serial number. The two drives have very similar identity files, but they are slightly different. Could that additional info be used to check for duplicates?

-Tupshin

---snippet from dmesg---
PDC20276: IDE controller at PCI slot 0000:00:0c.0
ACPI: PCI interrupt 0000:00:0c.0[A] -> GSI 19 (level, low) -> IRQ 19
PDC20276: chipset revision 1
PDC20276: 100% native mode on irq 19
ide4: BM-DMA at 0xdc00-0xdc07, BIOS settings: hdi:pio, hdj:pio
ide5: BM-DMA at 0xdc08-0xdc0f, BIOS settings: hdk:pio, hdl:pio
hdi: SAMSUNG SV8004H, ATA DISK drive
hdj: Maxtor 6Y250P0, ATA DISK drive
ide4 at 0xec00-0xec07,0xe802 on irq 19
hdk: Maxtor 4R120L0, ATA DISK drive
hdl: Maxtor 4R120L0, ATA DISK drive
ide-probe: ignoring undecoded slave
ide5 at 0xe400-0xe407,0xe002 on irq 19

Ah, thanks for working that out.

Did you know that Cc: stands for "copy culprit"?

I need the real model and serial number information not "MOOO" to debug this kind of thing

Two disks are not permitted to have the same serial number. If you can give me the full ident data I'll take a detailed look - could be I'm not comparing enough bytes if its only different on the last digit.

Alan

Sure they are.

But the combination of MODEL::SERIALNO is guaranteed to be unique.

Mark Lord
(hdparm keeper & the original "Linux IDE Guy")

Thats what the code is intended to check. I'm assuming I've screwed up the logic a little somewhere. Once I've got the ident info it should be blindingly obvious

I originally thought that the problem might be not enough bytes being checked, but now I'm concerned that Maxtor has some problem with not having a proper serial number recorded for some drives. hdparm -i also show M0000000000000000000 for both of these drives. Below is the output of hdparm -i for the two drives, and below that, the output of catting /dev/ide/hdk and hdl.

Doing a google search on "M0000000000000000000" shows that there have a been a handful of reports of maxtor drives showing this as the serial number, but I don't see any explanation of why.

-Tupshin

hdparm -i /dev/hdl

/dev/hdl:

Model=Maxtor 4R120L0, FwRev=RAMB1TU0, SerialNo=M0000000000000000000 Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57 BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=240121728 IORDY=on/off, 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 udma5 *udma6
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: (null):

* signifies the current active mode

rescue:/home/tupshin# hdparm -i /dev/hdk

/dev/hdk:

Model=Maxtor 4R120L0, FwRev=RAMB1TU0, SerialNo=M0000000000000000000 Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57 BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=240121728 IORDY=on/off, 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 udma5 *udma6
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: (null):

* signifies the current active mode

cat /proc/ide/hdl/identify
0040 3fff c837 0010 0000 0000 003f 0000 0000 0000 4d30 3030 3030 3030 3030 3030 3030 3030 3030 3030 0003 1000 0039 5241 4d42 3154 5530 4d61 7874 6f72 2034 5231 3230 4c30 2020 2020 2020 2020 2020 2020 2020 2020 2020 2020 2020 2020 2020 8010 0000 2f00 4000 0200 0000 0007 3fff 0010 003f fc10 00fb 0110 f780 0e4f 0000 0007 0003 0078 0078 0078 0078 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00fe 001e 7c6b 7b09 4003 7c68 3a01 4003 407f 0000 0000 0000 fffe 6b00 c0c0 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 8aa5

cat /proc/ide/hdk/identify
0040 3fff c837 0010 0000 0000 003f 0000 0000 0000 4d30 3030 3030 3030 3030 3030 3030 3030 3030 3030 0003 1000 0039 5241 4d42 3154 5530 4d61 7874 6f72 2034 5231 3230 4c30 2020 2020 2020 2020 2020 2020 2020 2020 2020 2020 2020 2020 2020 8010 0000 2f00 4000 0200 0000 0007 3fff 0010 003f fc10 00fb 0110 f780 0e4f 0000 0007 0003 0078 0078 0078 0078 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00fe 001e 7c6b 7b09 4003 7c68 3a01 4003 407f 0000 0000 0000 fffe 603b c0c0 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 5aa5

Thanks. Well thats easy to special case. Wonder what kind of a cow the Maxtor was having that day 8)

M00 indeed

Alan

that's a big field... if maxtor manages to ship 10^18 disks we're not going to have room on the surface of the earth for them all... ;)

-------------------------------------------------------------------------- Joel Jaeggli  	       Unix Consulting 	       [email protected] GPG Key Fingerprint:     5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2

The SN# is garbage in the ID block, I don't know why this is occurring with our drives. I am going to forward this note to our program lead for that product to see if he's aware of the issue. Unfortunately, if the utility zone configuration is corrupt, I am not sure anything can be done in the field to fix it... the drives might require an RMA. =/

--eric