From: Phil Turmel <philip@turmel.org>
To: Roman Mamedov <rm@romanrm.net>,
Carsten Aulbert <Carsten.Aulbert@aei.mpg.de>
Cc: Michael Munger <michael.munger@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Which physical device failed?
Date: Wed, 27 May 2015 09:16:26 -0400 [thread overview]
Message-ID: <5565C3AA.7020809@turmel.org> (raw)
In-Reply-To: <20150527172701.1090e525@natsu>
On 05/27/2015 08:27 AM, Roman Mamedov wrote:
> On Wed, 27 May 2015 14:10:03 +0200
> Carsten Aulbert <Carsten.Aulbert@aei.mpg.de> wrote:
>
>> On 05/27/2015 02:04 PM, Michael Munger wrote:
>>> Or, does the OS have access to serial numbers, etc...?
>>>
>>> I have to guide someone through a drive replacement on the phone, and it
>>> would be great if I could tell them exactly which drive to swap out...
>>
>> If you have direct knowledge, which serial number is where, you could
>> use hdparm -I /dev/sdX or smartctl -a /dev/sdX against the still
>> reachable drives.
>
> If /dev/sdc is still present in the system (even if not responding correctly to
> hdparm or smartctl anymore), you should be able to find its serial number from
> the udev symlink that was registered earlier, by running e.g.:
>
> ls -la /dev/disk/by-id/ | grep sdc$
>
> Serial number is typically the last piece of the ID, after the manufacturer
> name and model number.
>
This is one of the reasons I wrote lsdrv [1], especially after I noticed
that the port sequence it reports is stable for the various ports on
every mobo and sata expansion card I've handled. Per controller, at least.
I save of copy of an lsdrv report for each system I commission so that
there's no ambiguity later.
Phil
[1] https://github.com/pturmel/lsdrv
next prev parent reply other threads:[~2015-05-27 13:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 12:04 Which physical device failed? Michael Munger
2015-05-27 12:10 ` Carsten Aulbert
2015-05-27 12:27 ` Roman Mamedov
2015-05-27 13:16 ` Phil Turmel [this message]
2015-05-27 14:24 ` Michael Munger
2015-05-27 18:16 ` Wilson, Jonathan
2015-05-27 18:38 ` Phil Turmel
2015-05-28 9:03 ` Wilson, Jonathan
2015-05-27 17:48 ` Wols Lists
2015-05-27 18:02 ` Roman Mamedov
2015-05-27 18:19 ` Can Jeuleers
2015-05-27 18:38 ` Wols Lists
2015-05-27 18:41 ` Benjamin ESTRABAUD
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=5565C3AA.7020809@turmel.org \
--to=philip@turmel.org \
--cc=Carsten.Aulbert@aei.mpg.de \
--cc=linux-raid@vger.kernel.org \
--cc=michael.munger@gmail.com \
--cc=rm@romanrm.net \
/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.