From: John Robinson <john.robinson@anonymous.org.uk>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Possible HDD error, how do I find which HDD it is?
Date: Sat, 19 Feb 2011 17:25:33 +0000 [thread overview]
Message-ID: <4D5FFD0D.4030202@anonymous.org.uk> (raw)
In-Reply-To: <4D5FF386.6070003@turmel.org>
On 19/02/2011 16:44, Phil Turmel wrote:
> On 02/19/2011 10:37 AM, John Robinson wrote:
>> On 19/02/2011 11:52, Mathias Burén wrote:
>> [...]
>>> What I wonder is, how do I know what device is ata3? I do have 4
>>> devices of that model (WD20EARS). I've tried searching in /sys but
>>> there's nothing of value there (or I've missed it). If dmesg only
>>> showed the S/N...
>>> I posted the smartctl --all output of all devices here in case someone
>>> has time to take a look:
>>> http://stuff.dyndns.org/logs/smart-sd[a,b,c,d,e,f,g].log
>>
>> Try using Phil Turmel's excellent lsdrv script; I've attached the version I use on EL5, but I hacked it about to work on such an old distro so I wouldn't swear it will work on more recent distros; Phil's original that does work on more recent distros can be found in the list archives around 6 November last year in the thread "Determining which spindle is out of order".
>
> I've attached the latest version. It falls back to smartctl if it can't find the sginfo utility. It should work on both old and new sysfs layouts.
It still lists nothing on EL5. My SCSI hosts appear in /sys/devices/ as
follows:
/sys/devices/pci0000:00/0000:00:1f.2/host7/scsi_host:host7
/sys/devices/pci0000:00/0000:00:1f.2/host6/scsi_host:host6
/sys/devices/pci0000:00/0000:00:1f.2/host5/scsi_host:host5
/sys/devices/pci0000:00/0000:00:1f.2/host4/scsi_host:host4
/sys/devices/pci0000:00/0000:00:1f.2/host3/scsi_host:host3
/sys/devices/pci0000:00/0000:00:1f.2/host2/scsi_host:host2
/sys/devices/pci0000:00/0000:00:1e.0/0000:05:01.1/host9/scsi_host:host9
/sys/devices/pci0000:00/0000:00:1e.0/0000:05:01.0/host8/scsi_host:host8
/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/host1/scsi_host:host1
/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/host0/scsi_host:host0
So I changed the find regex as follows:
find /sys/devices/ -regex '.+/scsi_host\(:block\|:host[0-9]+\)?'
though I'd be interested to know why the simpler:
find /sys/devices/ -name 'scsi_host*'
isn't sufficient?
Cheers,
John.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-19 17:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 11:52 Possible HDD error, how do I find which HDD it is? Mathias Burén
2011-02-19 14:09 ` Simon McNair
2011-02-19 15:37 ` John Robinson
2011-02-19 16:44 ` Phil Turmel
2011-02-19 17:25 ` John Robinson [this message]
[not found] ` <4D5FFCEC.9040207@anonymous.org.uk>
2011-02-19 18:02 ` Phil Turmel
2011-02-19 18:18 ` John Robinson
2011-02-19 20:09 ` Mathias Burén
2011-02-19 22:22 ` Phil Turmel
2011-02-19 22:30 ` Mathias Burén
2011-02-19 22:40 ` Phil Turmel
2011-02-19 23:26 ` Mathias Burén
2011-02-20 3:11 ` John Robinson
2011-02-20 3:44 ` Mathias Burén
2011-02-20 9:52 ` Simon Mcnair
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=4D5FFD0D.4030202@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=linux-raid@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