From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kay Sievers <kay.sievers@vrfy.org>
Date: Thu, 22 Dec 2005 04:35:27 +0000
Subject: Re: /dev/disk/by-id incomplete and unhelpful for SATA drives
Message-Id: <20051222043527.GA13175@vrfy.org>
List-Id: <linux-hotplug.vger.kernel.org>
References: <doc5jl$acv$1@sea.gmane.org>
In-Reply-To: <doc5jl$acv$1@sea.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-hotplug@vger.kernel.org

On Wed, Dec 21, 2005 at 09:57:52PM +0000, Chris Paulson-Ellis wrote:
> Kay Sievers wrote:
> >On Wed, Dec 21, 2005 at 06:05:17PM +0000, Chris Paulson-Ellis wrote:
> >
> >>[snip]
> >>http://bugs.gentoo.org/show_bug.cgi?id9582
> >>
> >>I'm currently running udev-078 on vanilla 2.6.15-rc6
> >>[snip]
> >
> >Maxtor has a long history of doing broken serial numbers, they even
> >shipped disks with serials like: "M0000000000000000000". Regarding
> >this, the first suspect here is the disk itself.
> 
> I'm not suprised. I've also found Maxtor to be a manafacturer of poor 
> quality drives. I hope Seagate know what they're buying! This doesn't 
> explain why one of the drives is missing altogether from by-id, while 
> the other drive of the same model is present, albeit with a duff name.

Sure, both disks have the same "serial number", which will create the
same links, so the last one wins and replaces the links of the other
disk.

> >Are the examples with the sata/pata in the bug:
> >  /dev/disk
> >  |-- by-id
> >  |   |-- ata-Maxtor_4D080H4_D41S8XWE -> ../../hde
> >
> >
> >  /dev/disk
> >  |-- by-id
> >  |   |-- scsi-0ATA_Maxtor_6Y160M0_Linux_ATA-SCSI_simulator -> ../../sdb
> >
> >from the same disk model in a different box, or is it a different disk
> >model?
> 
> Different models (PATA/SATA). The drive models shown in the first part 
> of the by-id name are correct.

Ok.

> >What does:
> >  scsi_id -g -p0x80 -x -s /block/sda
> >  scsi_id -g -p0x83 -x -s /block/sda
> >print?
> 
> It looks like you're on to something (though I don't understand what); 
> The first command reveals the correct serial number...

These are the pages requested from the disk which contain all the
product information. It's defined by the SCSI standard.

> # scsi_id -g -p0x80 -x -s /block/sda
> ID_VENDOR=ATA
> ID_MODEL=Maxtor_6Y160M0
> ID_REVISION=YAR5
> ID_SERIAL=SATA_Maxtor_6Y160M0_Y4DCTR3E
> ID_TYPE=disk
> ID_BUS=scsi
> # scsi_id -g -p0x83 -x -s /block/sda
> ID_VENDOR=ATA
> ID_MODEL=Maxtor_6Y160M0
> ID_REVISION=YAR5
> ID_SERIAL
TA_Maxtor_6Y160M0_Linux_ATA-SCSI_simulator
> ID_TYPE=disk
> ID_BUS=scsi
> 
> 
> >Any chance to check the failing disk on an interface in pata mode, so
> >you get a hd* entry instead?
> 
> I thought the SATA as PATA driver had been replaced by libata? It may be 
> hard to change them anyway as they are in a pre-existing RAID array 
> which may not appreciate the change of naming! I'll give it a go if the 
> above is not sufficient.

No, the page 0x80 is fine, I hope. Try if putting:
  vendor="ATA",options=-p 0x80
in:
  /etc/scsi_id.config
helps.

Kay


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel