3.) on some systems I've found another version of the iostat command to be more
useful, particularly when iostat -En leaves the serial number field empty or
otherwise doesn't read the serial number correctly. Try
this:
' iostat -Eni ' indeed outputs Device ID on some of the drives,but I still
can't understand how it helps me to identify model of specific drive.
See below. Some
# iostat -Eni
c3d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Model: GIGABYTE i-RAM Revision: Device Id:
id1,c...@agigabyte_i-ram=33f100336d9cc244b01d
Size: 2.15GB <2146443264 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0
GIGABYTE i-RAM (2GB RAM based SSD)
Probably serial number: 33F100336D9CC244B01D
c1t0d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA Product: ST3500320AS Revision: SD15 Device Id:
id1,s...@ast3500320as=____________9qm34ybz
Size: 500.11GB <500107862016 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 56 Predictive Failure Analysis: 0
c1t0d0 = controller 1 target 0 device 0. Match zpool status devices
names with this.
ST3500320AS=____________9QM34YBZ
Model: ST3500320AS (ST means Seagate Technologies)
Serial: 9QM34YBZ
c1t1d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA Product: ST3500320AS Revision: SD15 Device Id:
id1,s...@ast3500320as=____________9qm353d2
Size: 500.11GB <500107862016 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 66 Predictive Failure Analysis: 0
c1t1d0 = controller 1 target 1 device 0
ST3500320AS=____________9QM353D2
c0t0d0 Soft Errors: 0 Hard Errors: 198 Transport Errors: 0
Vendor: SONY Product: CD-ROM CDU5212 Revision: 5YS1 Device Id:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 198 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
Sony CDU5212 52X CD optical drive
c2t0d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA Product: ST3500320AS Revision: SD15 Device Id:
id1,s...@n5000c5000b9f49ef
Size: 500.11GB <500107862016 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c2t0d0 = controller 2 target 0 device 0
You should seriously consider checking, and probably updating, the
firmware on all your Seagate ST3500320AS 7200.11 drives. Version SD15
(as reported above) is a known bad firmware.
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207951
c2t1d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA Product: ST3500320AS Revision: SD15 Device Id:
Size: 500.11GB <500107862016 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
controller 2 again
c2t2d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA Product: ST3500320AS Revision: SD15 Device Id:
id1,s...@n5000c5000b9be7ab
Size: 500.11GB <500107862016 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
controller 2 again
c2t3d0 Soft Errors: 0 Hard Errors: 9 Transport Errors: 9
Vendor: ATA Product: ST3500320AS Revision: SD15 Device Id:
id1,s...@n5000c5000b9fa1ab
Size: 500.11GB <500107862016 bytes>
Media Error: 7 Device Not Ready: 0 No Device: 2 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
controller 2 again. This one is the suspect (c2t3d0) but we don't know
the serial number. The controller is telling us it is
'n5000c5000b9fa1ab' which must be a unique ID the controller made up for
itself.
c2t4d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA Product: ST3500320AS Revision: SD15 Device Id:
id1,s...@n5000c5000b9fde5f
Size: 500.11GB <500107862016 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
controller 2 again
c2t5d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA Product: ST3500320AS Revision: SD15 Device Id:
id1,s...@n5000c5000b9fae42
Size: 500.11GB <500107862016 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
controller 2 again
c2t6d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA Product: ST3500320AS Revision: SD15 Device Id:
Size: 500.11GB <500107862016 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
controller 2 again. No Device Id reported. (strange)(not really present?)
c2t7d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA Product: ST3500320AS Revision: SD15 Device Id:
id1,s...@n5000c5000b9f4eb0
Size: 500.11GB <500107862016 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
controller 2 again.
sd11 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA Product: WDC WD5001AALS-0 Revision: 1D05 Device Id:
Size: 500.11GB <500107862016 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
sd11
WD drive. unknown serial number. Might be labeled with firmware 1D05.
sd12 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA Product: WDC WD5001AALS-0 Revision: 0K05 Device Id:
Size: 500.11GB <500107862016 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
sd12
WD drive. unknown serial number. Might be labeled with firmware 0K05.
Try this script from
http://stackoverflow.com/questions/555427/map-sd-sdd-names-to-solaris-disk-names
to see if you can convert the sd11 and sd12 names into the cXtXdX style.
|iostat -x|tail -n +3|awk '{print $1}'>/tmp/f0.txt.$$
iostat -nx|tail -n +3|awk '{print "/dev/dsk/"$11}'>/tmp/f1.txt.$$
paste -d= /tmp/f[01].txt.$$
rm /tmp/f[01].txt.$$|
My hunch is you have controller compatibility or controller
configuration issues. Please describe what controller hardware you are
using and how it is setup. It looks like controller 2 is hiding the
details of the drives from the operating system and assigning its own
unique device IDs (e.g. s...@n5000c5000b9f49ef). Is controller 2 in AHCI
mode right now? (During the initial installation, controller 2 should
have been in AHCI mode not RAID or JBOD mode. I wouldn't change the
mode at the moment unless you are ready to wipe/rebuild.)
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
