From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phil Turmel Subject: Re: Which physical device failed? Date: Wed, 27 May 2015 09:16:26 -0400 Message-ID: <5565C3AA.7020809@turmel.org> References: <5565B2BB.5090701@gmail.com> <5565B41B.8040104@aei.mpg.de> <20150527172701.1090e525@natsu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20150527172701.1090e525@natsu> Sender: linux-raid-owner@vger.kernel.org To: Roman Mamedov , Carsten Aulbert Cc: Michael Munger , linux-raid@vger.kernel.org List-Id: linux-raid.ids On 05/27/2015 08:27 AM, Roman Mamedov wrote: > On Wed, 27 May 2015 14:10:03 +0200 > Carsten Aulbert 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