From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: /dev/disk/by-id incomplete and unhelpful for SATA drives
Date: Wed, 21 Dec 2005 18:55:18 +0000 [thread overview]
Message-ID: <20051221185518.GA9100@vrfy.org> (raw)
In-Reply-To: <doc5jl$acv$1@sea.gmane.org>
On Wed, Dec 21, 2005 at 06:05:17PM +0000, Chris Paulson-Ellis wrote:
> I have a couple of problems with udev /dev/disk/by-id (missing entries
> and entries with unhelpful names) which is described in this gentoo bug...
>
> http://bugs.gentoo.org/show_bug.cgi?id\x109582
>
> I'm currently running udev-078 on vanilla 2.6.15-rc6. I carefully
> uninstalled all of hotplug, coldplug & udev and then re-installed udev
> just to make sure I've got a cleanly installed udev environment.
>
> Can anyone help?
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.
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?
What does:
scsi_id -g -p0x80 -x -s /block/sda
scsi_id -g -p0x83 -x -s /block/sda
print?
Any chance to check the failing disk on an interface in pata mode, so
you get a hd* entry instead?
Thanks,
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_id\x16865&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
next prev parent reply other threads:[~2005-12-21 18:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 18:05 /dev/disk/by-id incomplete and unhelpful for SATA drives Chris Paulson-Ellis
2005-12-21 18:55 ` Kay Sievers [this message]
2005-12-21 21:57 ` Chris Paulson-Ellis
2005-12-22 4:35 ` Kay Sievers
2005-12-22 11:24 ` Chris Paulson-Ellis
2005-12-22 18:35 ` Bill Nottingham
2005-12-22 21:08 ` David Liontooth
2005-12-22 22:48 ` Chris Paulson-Ellis
2005-12-23 0:12 ` Chris Paulson-Ellis
2006-01-06 1:36 ` patman
2006-01-06 2:57 ` Douglas Gilbert
2006-01-06 12:39 ` [PATCH] " Douglas Gilbert
2006-01-06 13:34 ` Chris Paulson-Ellis
2006-01-06 18:58 ` Patrick Mansfield
2006-01-06 19:46 ` Patrick Mansfield
2006-01-06 23:44 ` Douglas Gilbert
2006-03-06 20:08 ` Jeff Garzik
2006-03-07 17:05 ` Douglas Gilbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051221185518.GA9100@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).