From: Harri Olin <harri.olin@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: ata device numbers
Date: Sat, 9 Oct 2010 21:58:08 +0300 [thread overview]
Message-ID: <4CB0BB40.1090104@gmail.com> (raw)
In-Reply-To: <20101009200110.3e00a14c@lxorguk.ukuu.org.uk>
Alan Cox wrote:
>> ata13: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>> ata13.00: ATA-7: WDC WD7500AYYS-01RCA0, 30.04G30, max UDMA/133
>> ata13.00: 1465149168 sectors, multi 0: LBA48 NCQ (depth 31/32)
>> ata13.00: configured for UDMA/133
>> scsi 12:0:0:0: Direct-Access ATA WDC WD7500AYYS-0 30.0 PQ: 0
>> ANSI: 5
>> sd 12:0:0:0: [sdm] 1465149168 512-byte logical blocks: (750 GB/698 GiB)
>> sd 12:0:0:0: Attached scsi generic sg12 type 0
>> sd 12:0:0:0: [sdm] Write Protect is off
>> sd 12:0:0:0: [sdm] Mode Sense: 00 3a 00 00
>> sd 12:0:0:0: [sdm] Write cache: enabled, read cache: enabled, doesn't
>> support DPO or FUA
>> sdm: sdm1
>> sd 12:0:0:0: [sdm] Attached SCSI disk
>
> So /dev/sdm
>
Sorry, I mistyped. Error was on ata23, not on ata13, as seen at the end
of dmesg. And I'm more interested on some kind of reliable way to make
the translation - is there anything on /sys where ata device number
could be checked?
I suppose ata23 could still be sd22 ..
ata23 scanning messages appear around halfway of dmesg, line 710:
...
ata15: SATA link down (SStatus 0 SControl 300)
usb 1-1: new high speed USB device using ehci_hcd and address 2
usb 1-1: configuration #1 chosen from 1 choice
ata23: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata23.00: ATA-7: WDC WD7500AYYS-01RCA0, 30.04G30, max UDMA/133
ata23.00: 1465149168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata23.00: configured for UDMA/133
usb 1-5: new high speed USB device using ehci_hcd and address 3
usb 1-5: configuration #1 chosen from 1 choice
input: Peppercon AG Multidevice as /class/input/input2
...
and sd22 scan somewhere around line 971:
...
scsi 22:0:0:0: Direct-Access ATA WDC WD7500AYYS-0 30.0 PQ: 0
ANSI: 5
sd 22:0:0:0: [sdt] 1465149168 512-byte logical blocks: (750 GB/698 GiB)
sd 22:0:0:0: [sdt] Write Protect is off
sd 22:0:0:0: [sdt] Mode Sense: 00 3a 00 00
sd 22:0:0:0: [sdt] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 22:0:0:0: Attached scsi generic sg19 type 0
sdt:
sd 21:0:0:0: [sds] Write Protect is off
sd 21:0:0:0: [sds] Mode Sense: 00 3a 00 00
sd 21:0:0:0: [sds] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sds: sdt1
sd 22:0:0:0: [sdt] Attached SCSI disk
unknown partition table
sd 21:0:0:0: [sds] Attached SCSI disk
...
Care to tell which line is for what drive? :)
(hint: sds contains what partitions?)
I thought of inserting USB stick in the middle of scanning just to throw
the numbering off.. just to make things a little more interesting :)
--
Harri.
next prev parent reply other threads:[~2010-10-09 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 17:08 ata device numbers Harri Olin
2010-10-09 19:01 ` Alan Cox
2010-10-09 18:58 ` Harri Olin [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-11-13 0:38 Paul Klapperich
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=4CB0BB40.1090104@gmail.com \
--to=harri.olin@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.