Possible HDD error, how do I find which HDD it is?

Possible HDD error, how do I find which HDD it is?

am 19.02.2011 12:52:37 von mathias.buren

Hi, apologies in advance for the long email due to the log below. This
is the second time I've run a consistency check on the RAID (6 HDDs,
RAID5) that this error has occured. If you look on the ata3 entries in
the log below:

dmesg:

ata1: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76100 irq 40
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-8: Corsair CSSD-F60GB2, 1.1, max UDMA/133
ata1.00: 117231408 sectors, multi 1: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133

ata2: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76180 irq 40
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
ata2.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata2.00: configured for UDMA/133

ata3: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76200 irq 40
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: ATA-8: WDC WD20EARS-00MVWB0, 50.0AB50, max UDMA/133
ata3.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata3.00: configured for UDMA/133
ata3.00: exception Emask 0x0 SAct 0x800801 SErr 0x0 action 0x6 frozen
ata3.00: failed command: READ FPDMA QUEUED
ata3.00: cmd 60/b0:00:50:31:7b/02:00:8b:00:00/40 tag 0 ncq 352256 in
ata3.00: status: { DRDY }
ata3.00: failed command: READ FPDMA QUEUED
ata3.00: cmd 60/00:58:50:29:7b/04:00:8b:00:00/40 tag 11 ncq 524288 in
ata3.00: status: { DRDY }
ata3.00: failed command: READ FPDMA QUEUED
ata3.00: cmd 60/00:b8:50:2d:7b/04:00:8b:00:00/40 tag 23 ncq 524288 in
ata3.00: status: { DRDY }
ata3: hard resetting link
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: configured for UDMA/133
ata3.00: device reported invalid CHS sector 0
ata3.00: device reported invalid CHS sector 0
ata3.00: device reported invalid CHS sector 0
ata3: EH complete

ata4: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76280 irq 40
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: ATA-8: WDC WD20EARS-00MVWB0, 50.0AB50, max UDMA/133
ata4.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata4.00: configured for UDMA/133

ata5: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76300 irq 40
ata5: SATA link down (SStatus 0 SControl 300)

ata6: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76380 irq 40
ata6: SATA link down (SStatus 0 SControl 300)

ata7: SATA max UDMA/133 mmio m1048576@0xfeb00000 port 0xfeb22000 irq 19
ata7: SATA link down (SStatus 0 SControl 300)

ata8: SATA max UDMA/133 mmio m1048576@0xfeb00000 port 0xfeb24000 irq 19
ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata8.00: ATA-8: SAMSUNG HD204UI, 1AQ10003, max UDMA/133
ata8.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata8.00: configured for UDMA/133

ata9: SATA max UDMA/133 mmio m1048576@0xfeb00000 port 0xfeb26000 irq 19
ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata9.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
ata9.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata9.00: configured for UDMA/133

ata10: SATA max UDMA/133 mmio m1048576@0xfeb00000 port 0xfeb28000 irq 19
ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.00: ATA-8: SAMSUNG HD204UI, 1AQ10003, max UDMA/133
ata10.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata10.00: configured for UDMA/133

hdparm -I /dev/sdc:

ATA device, with non-removable media
Model Number: WDC WD20EARS-00MVWB0
Serial Number: WD-WMAZ20152590
Firmware Revision: 50.0AB50

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

Thanks,
// Mathias
--
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

Re: Possible HDD error, how do I find which HDD it is?

am 19.02.2011 15:09:33 von Simon McNair

does this help:
http://www.linux-archive.org/centos/316405-how-map-ata-numbe rs-dev-sd-n=
umbers.html

?
Simon

On 19/02/2011 11:52, Mathias Burén wrote:
> Hi, apologies in advance for the long email due to the log below. Thi=
s
> is the second time I've run a consistency check on the RAID (6 HDDs,
> RAID5) that this error has occured. If you look on the ata3 entries i=
n
> the log below:
>
> dmesg:
>
> ata1: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76100 irq 40
> ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata1.00: ATA-8: Corsair CSSD-F60GB2, 1.1, max UDMA/133
> ata1.00: 117231408 sectors, multi 1: LBA48 NCQ (depth 31/32)
> ata1.00: configured for UDMA/133
>
> ata2: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76180 irq 40
> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata2.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
> ata2.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata2.00: configured for UDMA/133
>
> ata3: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76200 irq 40
> ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.00: ATA-8: WDC WD20EARS-00MVWB0, 50.0AB50, max UDMA/133
> ata3.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata3.00: configured for UDMA/133
> ata3.00: exception Emask 0x0 SAct 0x800801 SErr 0x0 action 0x6 frozen
> ata3.00: failed command: READ FPDMA QUEUED
> ata3.00: cmd 60/b0:00:50:31:7b/02:00:8b:00:00/40 tag 0 ncq 352256 in
> ata3.00: status: { DRDY }
> ata3.00: failed command: READ FPDMA QUEUED
> ata3.00: cmd 60/00:58:50:29:7b/04:00:8b:00:00/40 tag 11 ncq 524288 in
> ata3.00: status: { DRDY }
> ata3.00: failed command: READ FPDMA QUEUED
> ata3.00: cmd 60/00:b8:50:2d:7b/04:00:8b:00:00/40 tag 23 ncq 524288 in
> ata3.00: status: { DRDY }
> ata3: hard resetting link
> ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.00: configured for UDMA/133
> ata3.00: device reported invalid CHS sector 0
> ata3.00: device reported invalid CHS sector 0
> ata3.00: device reported invalid CHS sector 0
> ata3: EH complete
>
> ata4: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76280 irq 40
> ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata4.00: ATA-8: WDC WD20EARS-00MVWB0, 50.0AB50, max UDMA/133
> ata4.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata4.00: configured for UDMA/133
>
> ata5: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76300 irq 40
> ata5: SATA link down (SStatus 0 SControl 300)
>
> ata6: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76380 irq 40
> ata6: SATA link down (SStatus 0 SControl 300)
>
> ata7: SATA max UDMA/133 mmio m1048576@0xfeb00000 port 0xfeb22000 irq =
19
> ata7: SATA link down (SStatus 0 SControl 300)
>
> ata8: SATA max UDMA/133 mmio m1048576@0xfeb00000 port 0xfeb24000 irq =
19
> ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata8.00: ATA-8: SAMSUNG HD204UI, 1AQ10003, max UDMA/133
> ata8.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata8.00: configured for UDMA/133
>
> ata9: SATA max UDMA/133 mmio m1048576@0xfeb00000 port 0xfeb26000 irq =
19
> ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata9.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
> ata9.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata9.00: configured for UDMA/133
>
> ata10: SATA max UDMA/133 mmio m1048576@0xfeb00000 port 0xfeb28000 irq=
19
> ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata10.00: ATA-8: SAMSUNG HD204UI, 1AQ10003, max UDMA/133
> ata10.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata10.00: configured for UDMA/133
>
> hdparm -I /dev/sdc:
>
> ATA device, with non-removable media
> Model Number: WDC WD20EARS-00MVWB0
> Serial Number: WD-WMAZ20152590
> Firmware Revision: 50.0AB50
>
> 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 someon=
e
> has time to take a look:
> http://stuff.dyndns.org/logs/smart-sd[a,b,c,d,e,f,g].log
>
> Thanks,
> // Mathias
> --
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Possible HDD error, how do I find which HDD it is?

am 19.02.2011 16:37:58 von John Robinson

This is a multi-part message in MIME format.
--------------000804080606090107090105
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

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".

Cheers,

John.


--------------000804080606090107090105
Content-Type: text/plain;
name="lsdrv"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="lsdrv"

IyEgL2Jpbi9iYXNoCiMKIyBFeGFtaW5lIHNwZWNpZmljIHN5c3RlbSBob3N0 IGRldmljZXMg
dG8gaWRlbnRpZnkgdGhlIGRyaXZlcyBhdHRhY2hlZAojCgpmdW5jdGlvbiBk ZXNjcmliZV9j
b250cm9sbGVyICgpIHsKCWxvY2FsIGRldmljZSBkcml2ZXIgbW9kcHJlZml4 IHNlcmlhbCBz
bG90bmFtZQoJZHJpdmVyPSJgcmVhZGxpbmsgLWYgXCIkMS9kcml2ZXJcImAi Cglkcml2ZXI9
ImBiYXNlbmFtZSAkZHJpdmVyYCIKCW1vZHByZWZpeD0iYGN1dCAtZDogLWYx IDxcIiQxL21v
ZGFsaWFzXCJgIgoJZWNobyAiQ29udHJvbGxlciBkZXZpY2UgQCAkezEjIy9z eXMvZGV2aWNl
cy99IFskZHJpdmVyXSIKCWlmIFtbICIkbW9kcHJlZml4IiA9PSAicGNpIiBd XSA7IHRoZW4K
CQlzbG90bmFtZT0iYGJhc2VuYW1lIFwiJDFcImAiCgkJZWNobyAiICBgbHNw Y2kgLXMgJHNs
b3RuYW1lIHxjdXQgLWRcICAtZjItYCIKCQlyZXR1cm4KCWZpCglpZiBbWyAi JG1vZHByZWZp
eCIgPT0gInVzYiIgXV0gOyB0aGVuCgkJaWYgW1sgLWYgIiQxL2J1c251bSIg XV0gOyB0aGVu
CgkJCWRldmljZT0iYGNhdCBcIiQxL2J1c251bVwiYDpgY2F0IFwiJDEvZGV2 bnVtXCJgIgoJ
CQlzZXJpYWw9ImBjYXQgXCIkMS9zZXJpYWxcImAiCgkJZWxzZQoJCQlkZXZp Y2U9ImBjYXQg
XCIkMS8uLi9idXNudW1cImA6YGNhdCBcIiQxLy4uL2Rldm51bVwiYCIKCQkJ c2VyaWFsPSJg
Y2F0IFwiJDEvLi4vc2VyaWFsXCJgIgoJCWZpCgkJZWNobyAiICBgbHN1c2Ig LXMgJGRldmlj
ZWAge1NOOiAkc2VyaWFsfSIKCQlyZXR1cm4KCWZpCgllY2hvIC1lICIgIGBj YXQgXCIkMS9t
b2RhbGlhc1wiYCIKfQoKZnVuY3Rpb24gZGVzY3JpYmVfZGV2aWNlICgpIHsK CWxvY2FsIGVt
cHR5PTEKCXdoaWxlIHJlYWQgZGV2aWNlIDsgZG8KCQllbXB0eT0wCgkJaWYg W1sgIiRkZXZp
Y2UiID1+IF4oLispL2Jsb2NrWy86XSguKykkIF1dIDsgdGhlbgoJCQl0YXJn PSIke0JBU0hf
UkVNQVRDSFsxXX0iCgkJCWJkZXY9IiR7QkFTSF9SRU1BVENIWzJdfSIKCQkJ dm5kPSIkKDwg
JHRhcmcvdmVuZG9yKSIKCQkJbWRsPSIkKDwgJHRhcmcvbW9kZWwpIgoJCQlz bj0iYHNnaW5m
byAtcyAvZGV2LyRiZGV2IDI+L2Rldi9udWxsIHwgXAoJCQkJc2VkIC1ybiAt ZSBcIi9TZXJp
YWwgTnVtYmVyL3tzJV4uKycgKiguKykgKicuKlxcXCQlXFxcXDElO3A7cX1c ImAiICY+L2Rl
di9udWxsCgkJCWlmIFtbIC1uICIkc24iIF1dIDsgdGhlbgoJCQkJZWNobyAt ZSAiICAgICQx
OiBgZWNobyAvZGV2LyRiZGV2ICR2bmQgJG1kbCB7U046ICRzbn1gIgoJCQll bHNlCgkJCQll
Y2hvIC1lICIgICAgJDE6IGBlY2hvIC9kZXYvJGJkZXYgJHZuZCAkbWRsYCIK CQkJZmkKCQll
bHNlCgkJCWVjaG8gLWUgIiAgICAkMTogVW5rbm93biAkZGV2aWNlIgoJCWZp Cglkb25lCglb
WyAkZW1wdHkgLWVxIDEgXV0gJiYgZWNobyAtZSAiICAgICQxOiBbRW1wdHld Igp9CgpmdW5j
dGlvbiBjaGVja19ob3N0ICgpIHsKCWxvY2FsIGZvdW5kPTAKCWxvY2FsIHBD b250cm9sbGVy
PQoJd2hpbGUgcmVhZCBzaG9zdCA7IGRvCgkJaG9zdD1gZGlybmFtZSAiJHNo b3N0ImAKCQlj
b250cm9sbGVyPWBkaXJuYW1lICIkaG9zdCJgCgkJYmhvc3Q9YGJhc2VuYW1l ICIkaG9zdCJg
CgkJaWYgW1sgIiRjb250cm9sbGVyIiAhPSAiJHBDb250cm9sbGVyIiBdXSA7 IHRoZW4KCQkJ
cENvbnRyb2xsZXI9IiRjb250cm9sbGVyIgoJCQlkZXNjcmliZV9jb250cm9s bGVyICIkY29u
dHJvbGxlciIKCQlmaQoJCWZpbmQgJGhvc3QgLXJlZ2V4ICcuKy90YXJnZXRb MC05Ol0rL1sw
LTk6XSsvYmxvY2tbOi9dW14vXSsnIHxkZXNjcmliZV9kZXZpY2UgIiRiaG9z dCIKCWRvbmUK
fQoKZmluZCAvc3lzL2RldmljZXMvIC1uYW1lICdzY3NpX2hvc3QqJyB8Y2hl Y2tfaG9zdAoK

--------------000804080606090107090105--
--
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

Re: Possible HDD error, how do I find which HDD it is?

am 19.02.2011 17:44:54 von Phil Turmel

This is a multi-part message in MIME format.
--------------060402090109010208070203
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

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.

Phil


--------------060402090109010208070203
Content-Type: text/plain;
name="lsdrv"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="lsdrv"

IyEgL2Jpbi9iYXNoCiMKIyBFeGFtaW5lIHNwZWNpZmljIHN5c3RlbSBob3N0 IGRldmljZXMg
dG8gaWRlbnRpZnkgdGhlIGRyaXZlcyBhdHRhY2hlZAojCgpmdW5jdGlvbiBk ZXNjcmliZV9j
b250cm9sbGVyICgpIHsKCWxvY2FsIGRldmljZSBkcml2ZXIgbW9kcHJlZml4 IHNlcmlhbCBz
bG90bmFtZQoJZHJpdmVyPSJgcmVhZGxpbmsgLWYgXCIkMS9kcml2ZXJcImAi Cglkcml2ZXI9
ImBiYXNlbmFtZSAkZHJpdmVyYCIKCW1vZHByZWZpeD0iYGN1dCAtZDogLWYx IDxcIiQxL21v
ZGFsaWFzXCJgIgoJZWNobyAiQ29udHJvbGxlciBkZXZpY2UgQCAkezEjIy9z eXMvZGV2aWNl
cy99IFskZHJpdmVyXSIKCWlmIFtbICIkbW9kcHJlZml4IiA9PSAicGNpIiBd XSA7IHRoZW4K
CQlzbG90bmFtZT0iYGJhc2VuYW1lIFwiJDFcImAiCgkJZWNobyAiICBgbHNw Y2kgLXMgJHNs
b3RuYW1lIHxjdXQgLWRcICAtZjItYCIKCQlyZXR1cm4KCWZpCglpZiBbWyAi JG1vZHByZWZp
eCIgPT0gInVzYiIgXV0gOyB0aGVuCgkJaWYgW1sgLWYgIiQxL2J1c251bSIg XV0gOyB0aGVu
CgkJCWRldmljZT0iYGNhdCBcIiQxL2J1c251bVwiYDpgY2F0IFwiJDEvZGV2 bnVtXCJgIgoJ
CQlzZXJpYWw9ImBjYXQgXCIkMS9zZXJpYWxcImAiCgkJZWxzZQoJCQlkZXZp Y2U9ImBjYXQg
XCIkMS8uLi9idXNudW1cImA6YGNhdCBcIiQxLy4uL2Rldm51bVwiYCIKCQkJ c2VyaWFsPSJg
Y2F0IFwiJDEvLi4vc2VyaWFsXCJgIgoJCWZpCgkJZWNobyAiICBgbHN1c2Ig LXMgJGRldmlj
ZWAge1NOOiAkc2VyaWFsfSIKCQlyZXR1cm4KCWZpCgllY2hvIC1lICIgIGBj YXQgXCIkMS9t
b2RhbGlhc1wiYCIKfQoKZnVuY3Rpb24gZGVzY3JpYmVfZGV2aWNlICgpIHsK CWxvY2FsIGVt
cHR5PTEKCXdoaWxlIHJlYWQgZGV2aWNlIDsgZG8KCQllbXB0eT0wCgkJaWYg W1sgIiRkZXZp
Y2UiID1+IF4oLispL2Jsb2NrWy86XSguKykkIF1dIDsgdGhlbgoJCQl0YXJn PSIke0JBU0hf
UkVNQVRDSFsxXX0iCgkJCWJkZXY9IiR7QkFTSF9SRU1BVENIWzJdfSIKCQkJ dm5kPSIkKDwg
JHRhcmcvdmVuZG9yKSIKCQkJbWRsPSIkKDwgJHRhcmcvbW9kZWwpIgoJCQlz bj0iYHNnaW5m
byAtcyAvZGV2LyRiZGV2IDI+L2Rldi9udWxsIHwgXAoJCQkJc2VkIC1ybiAt ZSBcIi9TZXJp
YWwgTnVtYmVyL3tzJV4uKycgKiguKykgKicuKlxcXCQlXFxcXDElO3A7cX1c ImAiICY+L2Rl
di9udWxsCgkJCWlmIFtbIC1uICIkc24iIF1dIDsgdGhlbgoJCQkJZWNobyAt ZSAiICAgICQx
OiBgZWNobyAvZGV2LyRiZGV2ICR2bmQgJG1kbCB7U046ICRzbn1gIgoJCQll bHNlCgkJCQlz
bj0iYHNtYXJ0Y3RsIC1pIC9kZXYvJGJkZXYgMj4vZGV2L251bGwgfCBcCgkJ CQkJc2VkIC1y
biAtZSBcIi9TZXJpYWwgTnVtYmVyOi97cyVeLis6ICooLispICouKlwkJVxc XFwxJTtwO3F9
XCJgIiAmPi9kZXYvbnVsbAoJCQkJaWYgW1sgLW4gIiRzbiIgXV0gOyB0aGVu CgkJCQkJZWNo
byAtZSAiICAgICQxOiBgZWNobyAvZGV2LyRiZGV2ICR2bmQgJG1kbCB7U046 ICRzbn1gIgoJ
CQkJZWxzZQoJCQkJCWVjaG8gLWUgIiAgICAkMTogYGVjaG8gL2Rldi8kYmRl diAkdm5kICRt
ZGxgIgoJCQkJZmkKCQkJZmkKCQllbHNlCgkJCWVjaG8gLWUgIiAgICAkMTog VW5rbm93biAk
ZGV2aWNlIgoJCWZpCglkb25lCglbWyAkZW1wdHkgLWVxIDEgXV0gJiYgZWNo byAtZSAiICAg
ICQxOiBbRW1wdHldIgp9CgpmdW5jdGlvbiBjaGVja19ob3N0ICgpIHsKCWxv Y2FsIGZvdW5k
PTAKCWxvY2FsIHBDb250cm9sbGVyPQoJd2hpbGUgcmVhZCBzaG9zdCA7IGRv CgkJaG9zdD1g
ZGlybmFtZSAiJHNob3N0ImAKCQljb250cm9sbGVyPWBkaXJuYW1lICIkaG9z dCJgCgkJYmhv
c3Q9YGJhc2VuYW1lICIkaG9zdCJgCgkJaWYgW1sgIiRjb250cm9sbGVyIiAh PSAiJHBDb250
cm9sbGVyIiBdXSA7IHRoZW4KCQkJcENvbnRyb2xsZXI9IiRjb250cm9sbGVy IgoJCQlkZXNj
cmliZV9jb250cm9sbGVyICIkY29udHJvbGxlciIKCQlmaQoJCWZpbmQgJGhv c3QgLXJlZ2V4
ICcuKy90YXJnZXRbMC05Ol0rL1swLTk6XSsvYmxvY2tbOi9dW14vXSsnIHxk ZXNjcmliZV9k
ZXZpY2UgIiRiaG9zdCIKCWRvbmUKfQoKZmluZCAvc3lzL2RldmljZXMvIC1y ZWdleCAnLisv
c2NzaV9ob3N0XCg6YmxvY2tcKT8nIHxjaGVja19ob3N0Cg==
--------------060402090109010208070203--
--
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

Re: Possible HDD error, how do I find which HDD it is?

am 19.02.2011 18:25:33 von John Robinson

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 some=
one
>>> 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 ve=
rsion 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 origin=
al that does work on more recent distros can be found in the list archi=
ves around 6 November last year in the thread "Determining which spindl=
e is out of order".
>
> I've attached the latest version. It falls back to smartctl if it ca=
n'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=
=20
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" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Possible HDD error, how do I find which HDD it is?

am 19.02.2011 19:02:09 von Phil Turmel

(whoops, dropped the list. Sorry about the dupe, John)

On 02/19/2011 12:25 PM, John Robinson wrote:
[trim /]
> 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?

It probably is fine, and does work on all my machines close at hand. I did a fair amount of rework after the last public discussion, and I try to be conservative with wildcard matches. I'll use it for a while, and see if it bites.

Phil
--
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

Re: Possible HDD error, how do I find which HDD it is?

am 19.02.2011 19:18:57 von John Robinson

On 19/02/2011 18:02, Phil Turmel wrote:
> (whoops, dropped the list. Sorry about the dupe, John)

It was me who dropped the list in the first place, but I just resent to
the list without mentioning it :-)

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

Re: Possible HDD error, how do I find which HDD it is?

am 19.02.2011 21:09:43 von mathias.buren

On 19 February 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 some=
one
>>> 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 ve=
rsion 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 origin=
al that does work on more recent distros can be found in the list archi=
ves around 6 November last year in the thread "Determining which spindl=
e 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.
>
> Phil
>
>

Hi,

The script works for me:


$ sudo ./lsdrv.sh
Password:
Controller device @ pci0000:00/0000:00:0b.0 [ahci]
SATA controller: nVidia Corporation MCP79 AHCI Controller (rev b1)
host0: /dev/sda ATA Corsair CSSD-F60 {SN: 10326505580009990027}
host1: /dev/sdb ATA WDC WD20EARS-00M {SN: WD-WCAZA1022443}
host2: /dev/sdc ATA WDC WD20EARS-00M {SN: WD-WMAZ20152590}
host3: /dev/sdd ATA WDC WD20EARS-00M {SN: WD-WMAZ20188479}
host4: [Empty]
host5: [Empty]
Controller device @ pci0000:00/0000:00:16.0/0000:05:00.0 [sata_mv]
SCSI storage controller: HighPoint Technologies, Inc. RocketRAID
230x 4 Port SATA-II Controller (rev 02)
host6: [Empty]
host7: /dev/sde ATA SAMSUNG HD204UI {SN: S2HGJ1RZ800964 }
host8: /dev/sdf ATA WDC WD20EARS-00M {SN: WD-WCAZA1000331}
host9: /dev/sdg ATA SAMSUNG HD204UI {SN: S2HGJ1RZ800850 }

So ata3 is the same as host3 then? How come no errors are logged on the=
drive:


ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail
Always - 0
3 Spin_Up_Time 0x0027 163 162 021 Pre-fail
Always - 6808
4 Start_Stop_Count 0x0032 100 100 000 Old_age
Always - 53
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail
Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age
Always - 0
9 Power_On_Hours 0x0032 093 093 000 Old_age
Always - 5169
10 Spin_Retry_Count 0x0032 100 253 000 Old_age
Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age
Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age
Always - 48
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age
Always - 30
193 Load_Cycle_Count 0x0032 172 172 000 Old_age
Always - 85965
194 Temperature_Celsius 0x0022 120 102 000 Old_age
Always - 30
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age
Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age
Always - 0
198 Offline_Uncorrectable 0x0030 200 200 000 Old_age
Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age
Always - 0
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age
Offline - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 4761 =
-
# 2 Short offline Completed without error 00% 2285 =
-
# 3 Extended offline Completed without error 00% 1514 =
-

Cheers,
// Mathias
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Possible HDD error, how do I find which HDD it is?

am 19.02.2011 23:22:22 von Phil Turmel

This is a multi-part message in MIME format.
--------------030202080503000407010608
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On 02/19/2011 03:09 PM, Mathias Burén wrote:
> The script works for me:
>
> $ sudo ./lsdrv.sh
> Password:
> Controller device @ pci0000:00/0000:00:0b.0 [ahci]
> SATA controller: nVidia Corporation MCP79 AHCI Controller (rev b1)
> host0: /dev/sda ATA Corsair CSSD-F60 {SN: 10326505580009990027}
> host1: /dev/sdb ATA WDC WD20EARS-00M {SN: WD-WCAZA1022443}
> host2: /dev/sdc ATA WDC WD20EARS-00M {SN: WD-WMAZ20152590}
> host3: /dev/sdd ATA WDC WD20EARS-00M {SN: WD-WMAZ20188479}
> host4: [Empty]
> host5: [Empty]
> Controller device @ pci0000:00/0000:00:16.0/0000:05:00.0 [sata_mv]
> SCSI storage controller: HighPoint Technologies, Inc. RocketRAID
> 230x 4 Port SATA-II Controller (rev 02)
> host6: [Empty]
> host7: /dev/sde ATA SAMSUNG HD204UI {SN: S2HGJ1RZ800964 }
> host8: /dev/sdf ATA WDC WD20EARS-00M {SN: WD-WCAZA1000331}
> host9: /dev/sdg ATA SAMSUNG HD204UI {SN: S2HGJ1RZ800850 }
>
> So ata3 is the same as host3 then? How come no errors are logged on the drive:

No, generally not. ATA numbering starts from #1. Host numbering starts from #0, but includes non-ATA SCSI devices.

I've attached a version of the script that shows the LUN in addition to the host number, and includes John's adjustment. It might be useful to people with port multipliers, and controllers that show all ports under a single host.

Simon, I'm very curious what this latest script shows for the Supermicro when one or more ports are empty, and whether those LUNs are consistently assigned to specific ports.

Phil

--------------030202080503000407010608
Content-Type: text/plain;
name="lsdrv"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="lsdrv"

IyEgL2Jpbi9iYXNoCiMKIyBFeGFtaW5lIHNwZWNpZmljIHN5c3RlbSBob3N0 IGRldmljZXMg
dG8gaWRlbnRpZnkgdGhlIGRyaXZlcyBhdHRhY2hlZAojCgpmdW5jdGlvbiBk ZXNjcmliZV9j
b250cm9sbGVyICgpIHsKCWxvY2FsIGRldmljZSBkcml2ZXIgbW9kcHJlZml4 IHNlcmlhbCBz
bG90bmFtZQoJZHJpdmVyPSJgcmVhZGxpbmsgLWYgXCIkMS9kcml2ZXJcImAi Cglkcml2ZXI9
ImBiYXNlbmFtZSAkZHJpdmVyYCIKCW1vZHByZWZpeD0iYGN1dCAtZDogLWYx IDxcIiQxL21v
ZGFsaWFzXCJgIgoJZWNobyAiQ29udHJvbGxlciBkZXZpY2UgQCAkezEjIy9z eXMvZGV2aWNl
cy99IFskZHJpdmVyXSIKCWlmIFtbICIkbW9kcHJlZml4IiA9PSAicGNpIiBd XSA7IHRoZW4K
CQlzbG90bmFtZT0iYGJhc2VuYW1lIFwiJDFcImAiCgkJZWNobyAiICBgbHNw Y2kgLXMgJHNs
b3RuYW1lIHxjdXQgLWRcICAtZjItYCIKCQlyZXR1cm4KCWZpCglpZiBbWyAi JG1vZHByZWZp
eCIgPT0gInVzYiIgXV0gOyB0aGVuCgkJaWYgW1sgLWYgIiQxL2J1c251bSIg XV0gOyB0aGVu
CgkJCWRldmljZT0iYGNhdCBcIiQxL2J1c251bVwiYDpgY2F0IFwiJDEvZGV2 bnVtXCJgIgoJ
CQlzZXJpYWw9ImBjYXQgXCIkMS9zZXJpYWxcImAiCgkJZWxzZQoJCQlkZXZp Y2U9ImBjYXQg
XCIkMS8uLi9idXNudW1cImA6YGNhdCBcIiQxLy4uL2Rldm51bVwiYCIKCQkJ c2VyaWFsPSJg
Y2F0IFwiJDEvLi4vc2VyaWFsXCJgIgoJCWZpCgkJZWNobyAiICBgbHN1c2Ig LXMgJGRldmlj
ZWAge1NOOiAkc2VyaWFsfSIKCQlyZXR1cm4KCWZpCgllY2hvIC1lICIgIGBj YXQgXCIkMS9t
b2RhbGlhc1wiYCIKfQoKZnVuY3Rpb24gZGVzY3JpYmVfZGV2aWNlICgpIHsK CWxvY2FsIGVt
cHR5PTEKCXdoaWxlIHJlYWQgZGV2aWNlIDsgZG8KCQllbXB0eT0wCgkJaWYg W1sgIiRkZXZp
Y2UiID1+IF4oLisvWzAtOV0rOikoWzAtOV0rOlswLTldKzpbMC05XSspL2Js b2NrWy86XSgu
KykkIF1dIDsgdGhlbgoJCQliYXNlPSIke0JBU0hfUkVNQVRDSFsxXX0iCgkJ CWx1bj0iJHtC
QVNIX1JFTUFUQ0hbMl19IgoJCQliZGV2PSIke0JBU0hfUkVNQVRDSFszXX0i CgkJCXZuZD0i
JCg8ICR7YmFzZX0ke2x1bn0vdmVuZG9yKSIKCQkJbWRsPSIkKDwgJHtiYXNl fSR7bHVufS9t
b2RlbCkiCgkJCXNuPSJgc2dpbmZvIC1zIC9kZXYvJGJkZXYgfCBcCgkJCQlz ZWQgLXJuIC1l
IFwiL1NlcmlhbCBOdW1iZXIve3MlXi4rJyAqKC4rKSAqJy4qXFxcJCVcXFxc MSU7cDtxfVwi
YCIgJj4vZGV2L251bGwKCQkJaWYgW1sgLW4gIiRzbiIgXV0gOyB0aGVuCgkJ CQllY2hvIC1l
ICIgICAgJDEgYGVjaG8gJGx1biAkYmRldiAkdm5kICRtZGwge1NOOiAkc259 YCIKCQkJZWxz
ZQoJCQkJZWNobyAtZSAiICAgICQxIGBlY2hvICRsdW4gJGJkZXYgJHZuZCAk bWRsYCIKCQkJ
ZmkKCQllbHNlCgkJCWVjaG8gLWUgIiAgICAkMSBVbmtub3duICRkZXZpY2Ui CgkJZmkKCWRv
bmUKCVtbICRlbXB0eSAtZXEgMSBdXSAmJiBlY2hvIC1lICIgICAgJDEgW0Vt cHR5XSIKfQoK
ZnVuY3Rpb24gY2hlY2tfaG9zdCAoKSB7Cglsb2NhbCBmb3VuZD0wCglsb2Nh bCBwQ29udHJv
bGxlcj0KCXdoaWxlIHJlYWQgc2hvc3QgOyBkbwoJCWhvc3Q9YGRpcm5hbWUg IiRzaG9zdCJg
CgkJY29udHJvbGxlcj1gZGlybmFtZSAiJGhvc3QiYAoJCWJob3N0PWBiYXNl bmFtZSAiJGhv
c3QiYAoJCWlmIFtbICIkY29udHJvbGxlciIgIT0gIiRwQ29udHJvbGxlciIg XV0gOyB0aGVu
CgkJCXBDb250cm9sbGVyPSIkY29udHJvbGxlciIKCQkJZGVzY3JpYmVfY29u dHJvbGxlciAi
JGNvbnRyb2xsZXIiCgkJZmkKCQlmaW5kICRob3N0IC1yZWdleCAnLisvdGFy Z2V0WzAtOTpd
Ky9bMC05Ol0rL2Jsb2NrWzovXVteL10rJyB8ZGVzY3JpYmVfZGV2aWNlICIk Ymhvc3QiCglk
b25lCn0KCmZpbmQgL3N5cy9kZXZpY2VzLyAtbmFtZSAnc2NzaV9ob3N0Kicg fGNoZWNrX2hv
c3QK
--------------030202080503000407010608--
--
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

Re: Possible HDD error, how do I find which HDD it is?

am 19.02.2011 23:30:13 von mathias.buren

On 19 February 2011 22:22, Phil Turmel wrote:
> On 02/19/2011 03:09 PM, Mathias Burén wrote:
>> The script works for me:
>>
>>  $ sudo ./lsdrv.sh
>> Password:
>> Controller device @ pci0000:00/0000:00:0b.0 [ahci]
>>   SATA controller: nVidia Corporation MCP79 AHCI Controller (re=
v b1)
>>     host0: /dev/sda ATA Corsair CSSD-F60 {SN: 103265055800=
09990027}
>>     host1: /dev/sdb ATA WDC WD20EARS-00M {SN: WD-WCAZA1022=
443}
>>     host2: /dev/sdc ATA WDC WD20EARS-00M {SN: WD-WMAZ20152=
590}
>>     host3: /dev/sdd ATA WDC WD20EARS-00M {SN: WD-WMAZ20188=
479}
>>     host4: [Empty]
>>     host5: [Empty]
>> Controller device @ pci0000:00/0000:00:16.0/0000:05:00.0 [sata_mv]
>>   SCSI storage controller: HighPoint Technologies, Inc. RocketR=
AID
>> 230x 4 Port SATA-II Controller (rev 02)
>>     host6: [Empty]
>>     host7: /dev/sde ATA SAMSUNG HD204UI {SN: S2HGJ1RZ80096=
4 }
>>     host8: /dev/sdf ATA WDC WD20EARS-00M {SN: WD-WCAZA1000=
331}
>>     host9: /dev/sdg ATA SAMSUNG HD204UI {SN: S2HGJ1RZ80085=
0 }
>>
>> So ata3 is the same as host3 then? How come no errors are logged on =
the drive:
>
> No, generally not.  ATA numbering starts from #1.  Host num=
bering starts from #0, but includes non-ATA SCSI devices.
>
> I've attached a version of the script that shows the LUN in addition =
to the host number, and includes John's adjustment.  It might be u=
seful to people with port multipliers, and controllers that show all po=
rts under a single host.
>
> Simon, I'm very curious what this latest script shows for the Supermi=
cro when one or more ports are empty, and whether those LUNs are consis=
tently assigned to specific ports.
>
> Phil
>

$ sudo ./lsdrv-2.sh
Controller device @ pci0000:00/0000:00:0b.0 [ahci]
SATA controller: nVidia Corporation MCP79 AHCI Controller (rev b1)
host0 0:0:0 sda ATA Corsair CSSD-F60 {SN: 10326505580009990027}
host1 0:0:0 sdb ATA WDC WD20EARS-00M {SN: WD-WCAZA1022443}
host2 0:0:0 sdc ATA WDC WD20EARS-00M {SN: WD-WMAZ20152590}
host3 0:0:0 sdd ATA WDC WD20EARS-00M {SN: WD-WMAZ20188479}
host4 [Empty]
host5 [Empty]
Controller device @ pci0000:00/0000:00:16.0/0000:05:00.0 [sata_mv]
SCSI storage controller: HighPoint Technologies, Inc. RocketRAID
230x 4 Port SATA-II Controller (rev 02)
host6 [Empty]
host7 0:0:0 sde ATA SAMSUNG HD204UI {SN: S2HGJ1RZ800964 }
host8 0:0:0 sdf ATA WDC WD20EARS-00M {SN: WD-WCAZA1000331}
host9 0:0:0 sdg ATA SAMSUNG HD204UI {SN: S2HGJ1RZ800850 }

This is the output of your latest script on my machine. The "0:0:0" is
supposed to be the LUN, which would be ata[1, 2, 3..], no?

// Mahtias
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Possible HDD error, how do I find which HDD it is?

am 19.02.2011 23:40:21 von Phil Turmel

On 02/19/2011 05:30 PM, Mathias Burén wrote:
> On 19 February 2011 22:22, Phil Turmel wrote:
>> On 02/19/2011 03:09 PM, Mathias Burén wrote:
>>> The script works for me:
>>>
>>> $ sudo ./lsdrv.sh
>>> Password:
>>> Controller device @ pci0000:00/0000:00:0b.0 [ahci]
>>> SATA controller: nVidia Corporation MCP79 AHCI Controller (rev b1=
)
>>> host0: /dev/sda ATA Corsair CSSD-F60 {SN: 10326505580009990027}
>>> host1: /dev/sdb ATA WDC WD20EARS-00M {SN: WD-WCAZA1022443}
>>> host2: /dev/sdc ATA WDC WD20EARS-00M {SN: WD-WMAZ20152590}
>>> host3: /dev/sdd ATA WDC WD20EARS-00M {SN: WD-WMAZ20188479}
>>> host4: [Empty]
>>> host5: [Empty]
>>> Controller device @ pci0000:00/0000:00:16.0/0000:05:00.0 [sata_mv]
>>> SCSI storage controller: HighPoint Technologies, Inc. RocketRAID
>>> 230x 4 Port SATA-II Controller (rev 02)
>>> host6: [Empty]
>>> host7: /dev/sde ATA SAMSUNG HD204UI {SN: S2HGJ1RZ800964 }
>>> host8: /dev/sdf ATA WDC WD20EARS-00M {SN: WD-WCAZA1000331}
>>> host9: /dev/sdg ATA SAMSUNG HD204UI {SN: S2HGJ1RZ800850 }
>>>
>>> So ata3 is the same as host3 then? How come no errors are logged on=
the drive:
>>
>> No, generally not. ATA numbering starts from #1. Host numbering st=
arts from #0, but includes non-ATA SCSI devices.
>>
>> I've attached a version of the script that shows the LUN in addition=
to the host number, and includes John's adjustment. It might be usefu=
l to people with port multipliers, and controllers that show all ports =
under a single host.
>>
>> Simon, I'm very curious what this latest script shows for the Superm=
icro when one or more ports are empty, and whether those LUNs are consi=
stently assigned to specific ports.
>>
>> Phil
>>
>=20
> $ sudo ./lsdrv-2.sh
> Controller device @ pci0000:00/0000:00:0b.0 [ahci]
> SATA controller: nVidia Corporation MCP79 AHCI Controller (rev b1)
> host0 0:0:0 sda ATA Corsair CSSD-F60 {SN: 10326505580009990027}
> host1 0:0:0 sdb ATA WDC WD20EARS-00M {SN: WD-WCAZA1022443}
> host2 0:0:0 sdc ATA WDC WD20EARS-00M {SN: WD-WMAZ20152590}
> host3 0:0:0 sdd ATA WDC WD20EARS-00M {SN: WD-WMAZ20188479}
> host4 [Empty]
> host5 [Empty]
> Controller device @ pci0000:00/0000:00:16.0/0000:05:00.0 [sata_mv]
> SCSI storage controller: HighPoint Technologies, Inc. RocketRAID
> 230x 4 Port SATA-II Controller (rev 02)
> host6 [Empty]
> host7 0:0:0 sde ATA SAMSUNG HD204UI {SN: S2HGJ1RZ800964 }
> host8 0:0:0 sdf ATA WDC WD20EARS-00M {SN: WD-WCAZA1000331}
> host9 0:0:0 sdg ATA SAMSUNG HD204UI {SN: S2HGJ1RZ800850 }
>=20
> This is the output of your latest script on my machine. The "0:0:0" i=
s
> supposed to be the LUN, which would be ata[1, 2, 3..], no?

No. You have to look in your dmesg to match the 'ata' initialization r=
eports with the corresponding 'scsi' initialization reports.

dmesg |grep 'ata[0-9]\|scsi[0-9]'

Unless I missed something in sysfs that would make it easy to report it=
in the script?

Phil
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Possible HDD error, how do I find which HDD it is?

am 20.02.2011 00:26:53 von mathias.buren

On 19 February 2011 22:40, Phil Turmel wrote:
> On 02/19/2011 05:30 PM, Mathias Burén wrote:
>> On 19 February 2011 22:22, Phil Turmel wrote:
>>> On 02/19/2011 03:09 PM, Mathias Burén wrote:
>>>> The script works for me:
>>>>
>>>>  $ sudo ./lsdrv.sh
>>>> Password:
>>>> Controller device @ pci0000:00/0000:00:0b.0 [ahci]
>>>>   SATA controller: nVidia Corporation MCP79 AHCI Controller (=
rev b1)
>>>>     host0: /dev/sda ATA Corsair CSSD-F60 {SN: 1032650558=
0009990027}
>>>>     host1: /dev/sdb ATA WDC WD20EARS-00M {SN: WD-WCAZA10=
22443}
>>>>     host2: /dev/sdc ATA WDC WD20EARS-00M {SN: WD-WMAZ201=
52590}
>>>>     host3: /dev/sdd ATA WDC WD20EARS-00M {SN: WD-WMAZ201=
88479}
>>>>     host4: [Empty]
>>>>     host5: [Empty]
>>>> Controller device @ pci0000:00/0000:00:16.0/0000:05:00.0 [sata_mv]
>>>>   SCSI storage controller: HighPoint Technologies, Inc. Rocke=
tRAID
>>>> 230x 4 Port SATA-II Controller (rev 02)
>>>>     host6: [Empty]
>>>>     host7: /dev/sde ATA SAMSUNG HD204UI {SN: S2HGJ1RZ800=
964 }
>>>>     host8: /dev/sdf ATA WDC WD20EARS-00M {SN: WD-WCAZA10=
00331}
>>>>     host9: /dev/sdg ATA SAMSUNG HD204UI {SN: S2HGJ1RZ800=
850 }
>>>>
>>>> So ata3 is the same as host3 then? How come no errors are logged o=
n the drive:
>>>
>>> No, generally not.  ATA numbering starts from #1.  Host n=
umbering starts from #0, but includes non-ATA SCSI devices.
>>>
>>> I've attached a version of the script that shows the LUN in additio=
n to the host number, and includes John's adjustment.  It might be=
useful to people with port multipliers, and controllers that show all =
ports under a single host.
>>>
>>> Simon, I'm very curious what this latest script shows for the Super=
micro when one or more ports are empty, and whether those LUNs are cons=
istently assigned to specific ports.
>>>
>>> Phil
>>>
>>
>> $ sudo ./lsdrv-2.sh
>> Controller device @ pci0000:00/0000:00:0b.0 [ahci]
>>   SATA controller: nVidia Corporation MCP79 AHCI Controller (re=
v b1)
>>     host0 0:0:0 sda ATA Corsair CSSD-F60 {SN: 103265055800=
09990027}
>>     host1 0:0:0 sdb ATA WDC WD20EARS-00M {SN: WD-WCAZA1022=
443}
>>     host2 0:0:0 sdc ATA WDC WD20EARS-00M {SN: WD-WMAZ20152=
590}
>>     host3 0:0:0 sdd ATA WDC WD20EARS-00M {SN: WD-WMAZ20188=
479}
>>     host4 [Empty]
>>     host5 [Empty]
>> Controller device @ pci0000:00/0000:00:16.0/0000:05:00.0 [sata_mv]
>>   SCSI storage controller: HighPoint Technologies, Inc. RocketR=
AID
>> 230x 4 Port SATA-II Controller (rev 02)
>>     host6 [Empty]
>>     host7 0:0:0 sde ATA SAMSUNG HD204UI {SN: S2HGJ1RZ80096=
4 }
>>     host8 0:0:0 sdf ATA WDC WD20EARS-00M {SN: WD-WCAZA1000=
331}
>>     host9 0:0:0 sdg ATA SAMSUNG HD204UI {SN: S2HGJ1RZ80085=
0 }
>>
>> This is the output of your latest script on my machine. The "0:0:0" =
is
>> supposed to be the LUN, which would be ata[1, 2, 3..], no?
>
> No.  You have to look in your dmesg to match the 'ata' initializ=
ation reports with the corresponding 'scsi' initialization reports.
>
> dmesg |grep 'ata[0-9]\|scsi[0-9]'
>
> Unless I missed something in sysfs that would make it easy to report =
it in the script?
>
> Phil
>

$ dmesg |grep 'ata[0-9]\|scsi[0-9]'
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
scsi4 : ahci
scsi5 : ahci
ata1: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76100 irq 40
ata2: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76180 irq 40
ata3: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76200 irq 40
ata4: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76280 irq 40
ata5: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76300 irq 40
ata6: SATA max UDMA/133 abar m8192@0xfae76000 port 0xfae76380 irq 40
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata5: SATA link down (SStatus 0 SControl 300)
ata6: SATA link down (SStatus 0 SControl 300)
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: ATA-8: WDC WD20EARS-00MVWB0, 50.0AB50, max UDMA/133
ata3.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata2.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
ata2.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata3.00: configured for UDMA/133
ata2.00: configured for UDMA/133
ata1.00: ATA-8: Corsair CSSD-F60GB2, 1.1, max UDMA/133
ata1.00: 117231408 sectors, multi 1: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: ATA-8: WDC WD20EARS-00MVWB0, 50.0AB50, max UDMA/133
ata4.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata4.00: configured for UDMA/133
scsi6 : sata_mv
scsi7 : sata_mv
scsi8 : sata_mv
scsi9 : sata_mv
ata7: SATA max UDMA/133 mmio m1048576@0xfeb00000 port 0xfeb22000 irq 19
ata8: SATA max UDMA/133 mmio m1048576@0xfeb00000 port 0xfeb24000 irq 19
ata9: SATA max UDMA/133 mmio m1048576@0xfeb00000 port 0xfeb26000 irq 19
ata10: SATA max UDMA/133 mmio m1048576@0xfeb00000 port 0xfeb28000 irq 1=
9
ata7: SATA link down (SStatus 0 SControl 300)
ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata8.00: ATA-8: SAMSUNG HD204UI, 1AQ10003, max UDMA/133
ata8.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata8.00: configured for UDMA/133
ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata9.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
ata9.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata9.00: configured for UDMA/133
ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata10.00: ATA-8: SAMSUNG HD204UI, 1AQ10003, max UDMA/133
ata10.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata10.00: configured for UDMA/133

Like you said before, ATA numbering starts from #1 & host numbering
starts from #0, if I only go by that the numbers match up. (the script
says host 4, 5 and 6 are empty, and according to ATA in dmesg ata 5, 6
& 7 are down.)

This would mean that the drive in question (ata3) is actually "host2
0:0:0 sdc ATA WDC WD20EARS-00M {SN: WD-WMAZ20152590}". Yet it doesn't
show and SMART errors:


Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail
Always - 0
3 Spin_Up_Time 0x0027 165 163 021 Pre-fail
Always - 6750
4 Start_Stop_Count 0x0032 100 100 000 Old_age
Always - 55
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail
Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age
Always - 0
9 Power_On_Hours 0x0032 094 094 000 Old_age
Always - 5070
10 Spin_Retry_Count 0x0032 100 253 000 Old_age
Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age
Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age
Always - 49
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age
Always - 31
193 Load_Cycle_Count 0x0032 180 180 000 Old_age
Always - 60164
194 Temperature_Celsius 0x0022 114 099 000 Old_age
Always - 36
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age
Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age
Always - 0
198 Offline_Uncorrectable 0x0030 200 200 000 Old_age
Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age
Always - 0
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age
Offline - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 4660 =
-
# 2 Short offline Completed without error 00% 2180 =
-
# 3 Extended offline Completed without error 00% 1408 =
-

I'm beginning to wonder if there's a controller/firmware problem and
not actually a physical HDD problem that causes this error. I've only
seen it happen during consistency checks of the array (and only once
per check, near the 70% mark or so).

Nifty script btw. :-)

Thanks,
// Mathias
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Possible HDD error, how do I find which HDD it is?

am 20.02.2011 04:11:48 von John Robinson

On 19/02/2011 22:40, Phil Turmel wrote:
> On 02/19/2011 05:30 PM, Mathias Burén wrote:
[...]
>> This is the output of your latest script on my machine. The "0:0:0"
>> is supposed to be the LUN, which would be ata[1, 2, 3..], no?
>
> No. You have to look in your dmesg to match the 'ata' initialization
> reports with the corresponding 'scsi' initialization reports.
>
> dmesg |grep 'ata[0-9]\|scsi[0-9]'
>
> Unless I missed something in sysfs that would make it easy to report
> it in the script?

I don't know about easy, but there is a suggestion in the page Simon
McNair linked to earlier in this thread:
http://www.linux-archive.org/centos/316405-how-map-ata-numbe rs-dev-sd-n=
umbers.html#post428370

I suspect that at the very least you'd have to check the proc_name to
see if it matched a driver which used libata before you could say the
unique_id matched the kernel's ata:N though, which is why I say it migh=
t=20
not be easy (well beyond me at any rate)...

Cheers,

John.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Possible HDD error, how do I find which HDD it is?

am 20.02.2011 04:44:33 von mathias.buren

On 20 February 2011 03:11, John Robinson k> wrote:
> On 19/02/2011 22:40, Phil Turmel wrote:
>>
>> On 02/19/2011 05:30 PM, Mathias Burén wrote:
>
> [...]
>>>
>>> This is the output of your latest script on my machine. The "0:0:0"
>>> is supposed to be the LUN, which would be ata[1, 2, 3..], no?
>>
>> No.  You have to look in your dmesg to match the 'ata' initiali=
zation
>> reports with the corresponding 'scsi' initialization reports.
>>
>> dmesg |grep 'ata[0-9]\|scsi[0-9]'
>>
>> Unless I missed something in sysfs that would make it easy to report
>> it in the script?
>
> I don't know about easy, but there is a suggestion in the page Simon
> McNair linked to earlier in this thread:
> http://www.linux-archive.org/centos/316405-how-map-ata-numbe rs-dev-sd=
-numbers.html#post428370
>
> I suspect that at the very least you'd have to check the proc_name to
> see if it matched a driver which used libata before you could say the
> unique_id matched the kernel's ata:N though, which is why I say it mi=
ght not
> be easy (well beyond me at any rate)...
>
> Cheers,
>
> John.
>

Hi,

I think it's safe to assume that in my case, ata3 which showed errors
in dmesg is indeed /dev/sdc based on the following:


$ sudo bin/lsdrv-2.sh
Controller device @ pci0000:00/0000:00:0b.0 [ahci]
SATA controller: nVidia Corporation MCP79 AHCI Controller (rev b1)
host0 0:0:0 sda ATA Corsair CSSD-F60 {SN: 10326505580009990027}
host1 0:0:0 sdb ATA WDC WD20EARS-00M {SN: WD-WCAZA1022443}
host2 0:0:0 sdc ATA WDC WD20EARS-00M {SN: WD-WMAZ20152590}
host3 0:0:0 sdd ATA WDC WD20EARS-00M {SN: WD-WMAZ20188479}
host4 [Empty]
host5 [Empty]
Controller device @ pci0000:00/0000:00:16.0/0000:05:00.0 [sata_mv]
SCSI storage controller: HighPoint Technologies, Inc. RocketRAID
230x 4 Port SATA-II Controller (rev 02)
host6 [Empty]
host7 0:0:0 sde ATA SAMSUNG HD204UI {SN: S2HGJ1RZ800964 }
host8 0:0:0 sdf ATA WDC WD20EARS-00M {SN: WD-WCAZA1000331}
host9 0:0:0 sdg ATA SAMSUNG HD204UI {SN: S2HGJ1RZ800850 }

$ sudo lsscsi -d -v -l
[0:0:0:0] disk ATA Corsair CSSD-F60 1.1 /dev/sda [8:0]
state=3Drunning queue_depth=3D31 scsi_level=3D6 type=3D0 device_block=
ed=3D0 timeout=3D30
dir: /sys/bus/scsi/devices/0:0:0:0
[/sys/devices/pci0000:00/0000:00:0b.0/host0/target0:0:0/0:0: 0:0]
[1:0:0:0] disk ATA WDC WD20EARS-00M 51.0 /dev/sdb [8:16]
state=3Drunning queue_depth=3D31 scsi_level=3D6 type=3D0 device_block=
ed=3D0 timeout=3D30
dir: /sys/bus/scsi/devices/1:0:0:0
[/sys/devices/pci0000:00/0000:00:0b.0/host1/target1:0:0/1:0: 0:0]
[2:0:0:0] disk ATA WDC WD20EARS-00M 50.0 /dev/sdc [8:32]
state=3Drunning queue_depth=3D31 scsi_level=3D6 type=3D0 device_block=
ed=3D0 timeout=3D30
dir: /sys/bus/scsi/devices/2:0:0:0
[/sys/devices/pci0000:00/0000:00:0b.0/host2/target2:0:0/2:0: 0:0]
[3:0:0:0] disk ATA WDC WD20EARS-00M 50.0 /dev/sdd [8:48]
state=3Drunning queue_depth=3D31 scsi_level=3D6 type=3D0 device_block=
ed=3D0 timeout=3D30
dir: /sys/bus/scsi/devices/3:0:0:0
[/sys/devices/pci0000:00/0000:00:0b.0/host3/target3:0:0/3:0: 0:0]
[7:0:0:0] disk ATA SAMSUNG HD204UI 1AQ1 /dev/sde [8:64]
state=3Drunning queue_depth=3D31 scsi_level=3D6 type=3D0 device_block=
ed=3D0 timeout=3D30
dir: /sys/bus/scsi/devices/7:0:0:0
[/sys/devices/pci0000:00/0000:00:16.0/0000:05:00.0/host7/tar get7:0:0/7:=
0:0:0]
[8:0:0:0] disk ATA WDC WD20EARS-00M 51.0 /dev/sdf [8:80]
state=3Drunning queue_depth=3D31 scsi_level=3D6 type=3D0 device_block=
ed=3D0 timeout=3D30
dir: /sys/bus/scsi/devices/8:0:0:0
[/sys/devices/pci0000:00/0000:00:16.0/0000:05:00.0/host8/tar get8:0:0/8:=
0:0:0]
[9:0:0:0] disk ATA SAMSUNG HD204UI 1AQ1 /dev/sdg [8:96]
state=3Drunning queue_depth=3D31 scsi_level=3D6 type=3D0 device_block=
ed=3D0 timeout=3D30
dir: /sys/bus/scsi/devices/9:0:0:0
[/sys/devices/pci0000:00/0000:00:16.0/0000:05:00.0/host9/tar get9:0:0/9:=
0:0:0]

$ for d in /sys/class/scsi_host/host*; do echo "$d $(cat
$d/proc_name) $(cat $d/unique_id)"; done
/sys/class/scsi_host/host0 ahci 1
/sys/class/scsi_host/host1 ahci 2
/sys/class/scsi_host/host2 ahci 3
/sys/class/scsi_host/host3 ahci 4
/sys/class/scsi_host/host4 ahci 5
/sys/class/scsi_host/host5 ahci 6
/sys/class/scsi_host/host6 sata_mv 7
/sys/class/scsi_host/host7 sata_mv 8
/sys/class/scsi_host/host8 sata_mv 9
/sys/class/scsi_host/host9 sata_mv 10

// Mathias
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Possible HDD error, how do I find which HDD it is?

am 20.02.2011 10:52:39 von Simon McNair

Hi Phil,
Results as follows:
proxmox:/home/simon# ./lsdrv2.sh
Controller device @ pci0000:00/0000:00:01.0/0000:01:00.0 [mvsas]
SCSI storage controller: Marvell Technology Group Ltd.
MV64460/64461/64462 System Controller, Revision B (rev 01)
host0 0:0:0 sdf ATA Hitachi HDS72101 {SN: GTA000PAGABXRA}
host0 0:1:0 sdg ATA Hitachi HDS72101 {SN: GTA000PAGAA5DA}
host0 0:2:0 sdh ATA Hitachi HDS72101 {SN: GTA000PAG9NL9A}
host0 0:3:0 sdi ATA Hitachi HDS72101 {SN: GTA000PAGA8V4A}
host0 0:4:0 sdj ATA Hitachi HDS72101 {SN: GTD000PAGMT9GD}
host0 0:5:0 sdk ATA Hitachi HDS72101 {SN: GTG000PAG18BJC}
host0 0:6:0 sdl ATA Hitachi HDS72101 {SN: GTG000PAG1DPLC}
host0 0:7:0 sdm ATA Hitachi HDS72101 {SN: GTA000PAG7WMEA}
Controller device @
pci0000:00/0000:00:1a.7/usb1/1-6/1-6.1/1-6.1.1/1-6.1.1:1.0
[usb-storage]
Bus 001 Device 095: ID 0424:2228 Standard Microsystems Corp. 9-in-2
Card Reader {SN: 08050920003A}
host21 0:0:0 sdo Generic Flash HS-CF
host21 0:0:1 sdp Generic Flash HS-COMBO
Controller device @ pci0000:00/0000:00:1c.4/0000:04:00.0 [ahci]
SATA controller: JMicron Technology Corp. JMB362/JMB363 Serial ATA
Controller (rev 03)
host9 [Empty]
host10 [Empty]
Controller device @ pci0000:00/0000:00:1c.4/0000:04:00.1 [pata_jmicron]
IDE interface: JMicron Technology Corp. JMB362/JMB363 Serial ATA
Controller (rev 03)
host1 [Empty]
host2 [Empty]
Controller device @ pci0000:00/0000:00:1f.2 [ahci]
SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI C=
ontroller
host3 0:0:0 sda ATA STM3500418AS {SN: 9VM3QJ5C}
host4 0:0:0 sr0 Optiarc DVD RW AD-5240S
host5 0:0:0 sds ATA SAMSUNG HD203WI {SN: S1UYJ1CZ404245 }
host6 0:0:0 sdr ATA SAMSUNG HD203WI {SN: S1UYJ1CZ404242 }
host7 0:0:0 sdd ATA Hitachi HDS72101 {SN: GTD000PAGMT8DD}
host8 0:0:0 sde ATA Hitachi HDS72101 {SN: GTG000PAG04V0C}

I can't test the empty ports and/or specific ports assigned to
specific LUNS until I've done the data recovery task. Happy to do it
afterwards once I know the state of my data.
cheers
Simon

On 19 February 2011 22:22, Phil Turmel wrote:
> On 02/19/2011 03:09 PM, Mathias Bur=E9n wrote:
>> The script works for me:
>>
>> =A0$ sudo ./lsdrv.sh
>> Password:
>> Controller device @ pci0000:00/0000:00:0b.0 [ahci]
>> =A0 SATA controller: nVidia Corporation MCP79 AHCI Controller (rev b=
1)
>> =A0 =A0 host0: /dev/sda ATA Corsair CSSD-F60 {SN: 103265055800099900=
27}
>> =A0 =A0 host1: /dev/sdb ATA WDC WD20EARS-00M {SN: WD-WCAZA1022443}
>> =A0 =A0 host2: /dev/sdc ATA WDC WD20EARS-00M {SN: WD-WMAZ20152590}
>> =A0 =A0 host3: /dev/sdd ATA WDC WD20EARS-00M {SN: WD-WMAZ20188479}
>> =A0 =A0 host4: [Empty]
>> =A0 =A0 host5: [Empty]
>> Controller device @ pci0000:00/0000:00:16.0/0000:05:00.0 [sata_mv]
>> =A0 SCSI storage controller: HighPoint Technologies, Inc. RocketRAID
>> 230x 4 Port SATA-II Controller (rev 02)
>> =A0 =A0 host6: [Empty]
>> =A0 =A0 host7: /dev/sde ATA SAMSUNG HD204UI {SN: S2HGJ1RZ800964 }
>> =A0 =A0 host8: /dev/sdf ATA WDC WD20EARS-00M {SN: WD-WCAZA1000331}
>> =A0 =A0 host9: /dev/sdg ATA SAMSUNG HD204UI {SN: S2HGJ1RZ800850 }
>>
>> So ata3 is the same as host3 then? How come no errors are logged on =
the drive:
>
> No, generally not. =A0ATA numbering starts from #1. =A0Host numbering=
starts from #0, but includes non-ATA SCSI devices.
>
> I've attached a version of the script that shows the LUN in addition =
to the host number, and includes John's adjustment. =A0It might be usef=
ul to people with port multipliers, and controllers that show all ports=
under a single host.
>
> Simon, I'm very curious what this latest script shows for the Supermi=
cro when one or more ports are empty, and whether those LUNs are consis=
tently assigned to specific ports.
>
> Phil
>
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html