From: Tim Small <tim@buttersideup.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Daniel Pittman <daniel@rimspace.net>,
linux-raid@vger.kernel.org,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: mapping ataXX.YY to a /dev/sdX
Date: Thu, 08 Jul 2010 11:05:48 +0100 [thread overview]
Message-ID: <4C35A2FC.5080402@buttersideup.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1007071749320.23489@uplift.swm.pp.se>
Mikael Abrahamsson wrote:
> On Wed, 7 Jul 2010, Daniel Pittman wrote:
>
>> No. OTOH, the poor sysadmins version of the "disk identification
>> light" is:
>>
>> sudo dd if=/dev/sdFAIL of=/dev/null
>>
>> ...plus a pair of eyes. FWIW.
>
> Yeah, if the drive is failed or if I know what drive to access I have
> no problem identifying it (I can access the working array and see what
> drive slots blink and which don't, or try to access the failed drive).
> But I have right now no way to identify the drive on "ata14.00". I can
> from dmesg deduce that it's most likely /dev/sdj (by observing the
> order of things being identified), but I don't know for sure it seems.
>
Whilst SCSI drives have the ability to blink the activity light, I don't
think SATA drives have this (BICBW). Are these links any use to you:
root@ermintrude:~# ls
'/sys/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block'
sda
?
Could you access all the other drives, and thus eliminate them from your
enquiries? Bit naff, but better than nothing...
Tim.
next parent reply other threads:[~2010-07-08 10:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.1.10.1007070810540.23489@uplift.swm.pp.se>
[not found] ` <87wrt7ijp3.fsf@rimspace.net>
[not found] ` <alpine.DEB.1.10.1007071749320.23489@uplift.swm.pp.se>
2010-07-08 10:05 ` Tim Small [this message]
2010-07-08 10:26 ` mapping ataXX.YY to a /dev/sdX Mikael Abrahamsson
[not found] ` <20100708104422.GA32564@cthulhu.home.robinhill.me.uk>
2010-07-08 11:05 ` Mikael Abrahamsson
[not found] ` <20100708232631.014a5ade@atak.bl.pg.gda.pl>
2010-07-08 21:53 ` Mikael Abrahamsson
2010-07-10 4:42 ` Brad Campbell
2010-07-10 7:05 ` Rudy Zijlstra
2010-07-10 11:45 ` Anssi Hannula
2010-07-10 19:23 ` Jeff Garzik
2010-07-10 23:49 ` Rudy Zijlstra
2010-07-11 19:01 ` Jérôme Poulin
[not found] ` <AANLkTiluwfd9LTH7Tb0J9N3NBvp1FbZdoJYUYj1g8BJz@mail.gmail.com>
2010-07-14 19:05 ` Jim Paris
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=4C35A2FC.5080402@buttersideup.com \
--to=tim@buttersideup.com \
--cc=daniel@rimspace.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=swmike@swm.pp.se \
/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