I have a failing drive, and no way to correlate the device with errors in the zpool status with an actual physical drive. If I could get the device''s serial number, I could use that as it''s printed on the drive. I come from linux, so I tried dmesg, as that''s what''s familiar (I see that the man page for dmesg on opensolaris says that I should be using syslogd but I haven''t been able to figure out how to get the same output from syslogd). But, while I see at the top the serial numbers for some other drives, I don''t see the one I want because it seems to be scrolled off the top. Can anyone tell me how to get the serial number of my failing drive? Or some other way to correlate the device with the physical drive? -Ethan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100307/a7ffa0d9/attachment.html>
On Sun, Mar 7, 2010 at 12:30 PM, Ethan <notethan at gmail.com> wrote:> I have a failing drive, and no way to correlate the device with errors in > the zpool status with an actual physical drive. > If I could get the device''s serial number, I could use that as it''s printed > on the drive. > I come from linux, so I tried dmesg, as that''s what''s familiar (I see that > the man page for dmesg on opensolaris says that I should be using syslogd > but I haven''t been able to figure out how to get the same output from > syslogd). But, while I see at the top the serial numbers for some other > drives, I don''t see the one I want because it seems to be scrolled off the > top. > Can anyone tell me how to get the serial number of my failing drive? Or > some other way to correlate the device with the physical drive? > > -Ethan > > >smartctl will do what you''re looking for. I''m not sure if it''s included by default or not with the latest builds. Here''s the package if you need to build from source: http://smartmontools.sourceforge.net/ --Tim -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100307/837275c1/attachment.html>
> On Sun, Mar 7, 2010 at 12:30 PM, Ethan <notethan at gmail.com> wrote: > >> I have a failing drive, and no way to correlate the device with errors >> in >> the zpool status with an actual physical drive. >> If I could get the device''s serial number, I could use that as it''s >> printed >> on the drive. >> I come from linux, so I tried dmesg, as that''s what''s familiar (I see >> that >> the man page for dmesg on opensolaris says that I should be using >> syslogd >> but I haven''t been able to figure out how to get the same output from >> syslogd). But, while I see at the top the serial numbers for some other >> drives, I don''t see the one I want because it seems to be scrolled off >> the >> top. >> Can anyone tell me how to get the serial number of my failing drive? Or >> some other way to correlate the device with the physical drive? >> >> -Ethan >> >> >> > smartctl will do what you''re looking for. I''m not sure if it''s included > by > default or not with the latest builds. Here''s the package if you need to > build from source: > http://smartmontools.sourceforge.net/ >You can find it at http://blastwave.network.com/csw/unstable/ Just install it with pkgadd or use pkgtrans to extract it and then run the binary. -- Dennis Clarke dclarke at opensolaris.ca <- Email related to the open source Solaris dclarke at blastwave.org <- Email related to open source for Solaris
On Sun, Mar 7, 2010 at 1:05 PM, Dennis Clarke <dclarke at blastwave.org> wrote:> > > On Sun, Mar 7, 2010 at 12:30 PM, Ethan <notethan at gmail.com> wrote: > > > >> I have a failing drive, and no way to correlate the device with errors > >> in > >> the zpool status with an actual physical drive. > >> If I could get the device''s serial number, I could use that as it''s > >> printed > >> on the drive. > >> I come from linux, so I tried dmesg, as that''s what''s familiar (I see > >> that > >> the man page for dmesg on opensolaris says that I should be using > >> syslogd > >> but I haven''t been able to figure out how to get the same output from > >> syslogd). But, while I see at the top the serial numbers for some other > >> drives, I don''t see the one I want because it seems to be scrolled off > >> the > >> top. > >> Can anyone tell me how to get the serial number of my failing drive? Or > >> some other way to correlate the device with the physical drive? > >> > >> -Ethan > >> > >> > >> > > smartctl will do what you''re looking for. I''m not sure if it''s included > > by > > default or not with the latest builds. Here''s the package if you need to > > build from source: > > http://smartmontools.sourceforge.net/ > > > > You can find it at http://blastwave.network.com/csw/unstable/ > > Just install it with pkgadd or use pkgtrans to extract it and then run the > binary. >Speaking of which, what happened to the IPS mirror? Using a separate utility just for that repository is a bit ridiculous. --Tim>-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100307/4c80653e/attachment.html>
On Sun, Mar 7, 2010 at 15:30, Tim Cook <tim at cook.ms> wrote:> > > On Sun, Mar 7, 2010 at 2:10 PM, Ethan <notethan at gmail.com> wrote: > >> On Sun, Mar 7, 2010 at 14:55, Tim Cook <tim at cook.ms> wrote: >> >>> >>> >>> On Sun, Mar 7, 2010 at 1:05 PM, Dennis Clarke <dclarke at blastwave.org>wrote: >>> >>>> >>>> > On Sun, Mar 7, 2010 at 12:30 PM, Ethan <notethan at gmail.com> wrote: >>>> > >>>> >> I have a failing drive, and no way to correlate the device with >>>> errors >>>> >> in >>>> >> the zpool status with an actual physical drive. >>>> >> If I could get the device''s serial number, I could use that as it''s >>>> >> printed >>>> >> on the drive. >>>> >> I come from linux, so I tried dmesg, as that''s what''s familiar (I see >>>> >> that >>>> >> the man page for dmesg on opensolaris says that I should be using >>>> >> syslogd >>>> >> but I haven''t been able to figure out how to get the same output from >>>> >> syslogd). But, while I see at the top the serial numbers for some >>>> other >>>> >> drives, I don''t see the one I want because it seems to be scrolled >>>> off >>>> >> the >>>> >> top. >>>> >> Can anyone tell me how to get the serial number of my failing drive? >>>> Or >>>> >> some other way to correlate the device with the physical drive? >>>> >> >>>> >> -Ethan >>>> >> >>>> >> >>>> >> >>>> > smartctl will do what you''re looking for. I''m not sure if it''s >>>> included >>>> > by >>>> > default or not with the latest builds. Here''s the package if you need >>>> to >>>> > build from source: >>>> > http://smartmontools.sourceforge.net/ >>>> > >>>> >>>> You can find it at http://blastwave.network.com/csw/unstable/ >>>> >>>> Just install it with pkgadd or use pkgtrans to extract it and then run >>>> the >>>> binary. >>>> >>> >>> Speaking of which, what happened to the IPS mirror? Using a separate >>> utility just for that repository is a bit ridiculous. >>> --Tim >>> >>>> >>> >>> >> Thanks. Actually I already had smartmontools built from source previously, >> but I was never able to get it to do much of anything. It outputs >> >> ####################################################################### >> ATA command routine ata_command_interface() NOT IMPLEMENTED under Solaris. >> Please contact smartmontools-support at lists.sourceforge.net if >> you want to help in porting smartmontools to Solaris. >> ####################################################################### >> >> Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) >> >> I''m not sure if that last line means I''m giving it the wrong thing - in >> fact I''m not really sure what to give it. I tried >> # smartctl -d ata /dev/dsk/c9t1d0p0 >> and >> # smartctl -d ata /devices/pci at 0,0/pci1043,82d4 at 1f,2/disk at 1,0 >> but I am not sure if either of those correctly specifies the disk as >> smartctl wants it. or if the first message is the import one, and I just >> can''t use smartctl as it hasn''t implemented what I need. >> >> -Ethan >> >> > > What kind of drive is it? Is it ATA or SATA? > > http://opensolaris.org/jive/thread.jspa?threadID=120402 > > --Tim > >(whoops, meant to reply to the list before.) It is sata, but ata seems to be the closest option available. # ./smartctl /devices/pci at 0,0/pci1043,82d4 at 1f,2/disk at 1,0 smartctl 5.39.1 2010-01-28 r3054 [i386-pc-solaris2.11] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net /devices/pci at 0,0/pci1043,82d4 at 1f,2/disk at 1,0: Unable to detect device type Smartctl: please specify device type with the -d option. =======> VALID ARGUMENTS ARE: ata, scsi, sat[,N][+TYPE], usbcypress[,X], usbjmicron[,x][,N], usbsunplus, marvell, areca,N, 3ware,N, hpt,L/M/N, cciss,N, test <====== Is that the right device to be giving it? It seems to behave the same when I try /dev/dsk/c9t1d0s0 or /dev/dsk/c9t1d0s2 or /dev/dsk/c9t1d0p0. The controller is: Marvell Technology Group Ltd. 88SE6121 SATA II Controller and I see marvell a a type in that list, a connection I hadn''t made before. but when I do -d marvell, it says: # ./smartctl -d marvell /devices/pci at 0,0/pci1043,82d4 at 1f,2/disk at 1,0 Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) (again, same when I try various /dev/dsk/c9t1d0* devices) Reading http://opensolaris.org/jive/thread.jspa?messageID=384927 one person says "SATA drives are ATA and unsupported in smartmontools for Solaris." Any ideas? -Ethan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100307/292942d0/attachment.html>
On Mar 7, 2010, at 10:30 AM, Ethan wrote:> I have a failing drive, and no way to correlate the device with errors in the zpool status with an actual physical drive. > If I could get the device''s serial number, I could use that as it''s printed on the drive. > I come from linux, so I tried dmesg, as that''s what''s familiar (I see that the man page for dmesg on opensolaris says that I should be using syslogd but I haven''t been able to figure out how to get the same output from syslogd). But, while I see at the top the serial numbers for some other drives, I don''t see the one I want because it seems to be scrolled off the top. > Can anyone tell me how to get the serial number of my failing drive? Or some other way to correlate the device with the physical drive?For SATA: cfgadm -v -- richard ZFS storage and performance consulting at http://www.RichardElling.com ZFS training on deduplication, NexentaStor, and NAS performance http://nexenta-atlanta.eventbrite.com (March 16-18, 2010)
On Sun, Mar 7, 2010 at 3:12 PM, Ethan <notethan at gmail.com> wrote:> On Sun, Mar 7, 2010 at 15:30, Tim Cook <tim at cook.ms> wrote: > >> >> >> On Sun, Mar 7, 2010 at 2:10 PM, Ethan <notethan at gmail.com> wrote: >> >>> On Sun, Mar 7, 2010 at 14:55, Tim Cook <tim at cook.ms> wrote: >>> >>>> >>>> >>>> On Sun, Mar 7, 2010 at 1:05 PM, Dennis Clarke <dclarke at blastwave.org>wrote: >>>> >>>>> >>>>> > On Sun, Mar 7, 2010 at 12:30 PM, Ethan <notethan at gmail.com> wrote: >>>>> > >>>>> >> I have a failing drive, and no way to correlate the device with >>>>> errors >>>>> >> in >>>>> >> the zpool status with an actual physical drive. >>>>> >> If I could get the device''s serial number, I could use that as it''s >>>>> >> printed >>>>> >> on the drive. >>>>> >> I come from linux, so I tried dmesg, as that''s what''s familiar (I >>>>> see >>>>> >> that >>>>> >> the man page for dmesg on opensolaris says that I should be using >>>>> >> syslogd >>>>> >> but I haven''t been able to figure out how to get the same output >>>>> from >>>>> >> syslogd). But, while I see at the top the serial numbers for some >>>>> other >>>>> >> drives, I don''t see the one I want because it seems to be scrolled >>>>> off >>>>> >> the >>>>> >> top. >>>>> >> Can anyone tell me how to get the serial number of my failing drive? >>>>> Or >>>>> >> some other way to correlate the device with the physical drive? >>>>> >> >>>>> >> -Ethan >>>>> >> >>>>> >> >>>>> >> >>>>> > smartctl will do what you''re looking for. I''m not sure if it''s >>>>> included >>>>> > by >>>>> > default or not with the latest builds. Here''s the package if you >>>>> need to >>>>> > build from source: >>>>> > http://smartmontools.sourceforge.net/ >>>>> > >>>>> >>>>> You can find it at http://blastwave.network.com/csw/unstable/ >>>>> >>>>> Just install it with pkgadd or use pkgtrans to extract it and then run >>>>> the >>>>> binary. >>>>> >>>> >>>> Speaking of which, what happened to the IPS mirror? Using a separate >>>> utility just for that repository is a bit ridiculous. >>>> --Tim >>>> >>>>> >>>> >>>> >>> Thanks. Actually I already had smartmontools built from source >>> previously, but I was never able to get it to do much of anything. It >>> outputs >>> >>> ####################################################################### >>> ATA command routine ata_command_interface() NOT IMPLEMENTED under >>> Solaris. >>> Please contact smartmontools-support at lists.sourceforge.net if >>> you want to help in porting smartmontools to Solaris. >>> ####################################################################### >>> >>> Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) >>> >>> I''m not sure if that last line means I''m giving it the wrong thing - in >>> fact I''m not really sure what to give it. I tried >>> # smartctl -d ata /dev/dsk/c9t1d0p0 >>> and >>> # smartctl -d ata /devices/pci at 0,0/pci1043,82d4 at 1f,2/disk at 1,0 >>> but I am not sure if either of those correctly specifies the disk as >>> smartctl wants it. or if the first message is the import one, and I just >>> can''t use smartctl as it hasn''t implemented what I need. >>> >>> -Ethan >>> >>> >> >> What kind of drive is it? Is it ATA or SATA? >> >> http://opensolaris.org/jive/thread.jspa?threadID=120402 >> >> --Tim >> >> > (whoops, meant to reply to the list before.) > > It is sata, but ata seems to be the closest option available. > > # ./smartctl /devices/pci at 0,0/pci1043,82d4 at 1f,2/disk at 1,0 > smartctl 5.39.1 2010-01-28 r3054 [i386-pc-solaris2.11] (local build) > Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net > > /devices/pci at 0,0/pci1043,82d4 at 1f,2/disk at 1,0: Unable to detect device type > Smartctl: please specify device type with the -d option. > > =======> VALID ARGUMENTS ARE: ata, scsi, sat[,N][+TYPE], usbcypress[,X], > usbjmicron[,x][,N], usbsunplus, marvell, areca,N, 3ware,N, hpt,L/M/N, > cciss,N, test <======> > > Is that the right device to be giving it? It seems to behave the same when > I try /dev/dsk/c9t1d0s0 or /dev/dsk/c9t1d0s2 or /dev/dsk/c9t1d0p0. > The controller is: Marvell Technology Group Ltd. 88SE6121 SATA II > Controller > and I see marvell a a type in that list, a connection I hadn''t made before. > but when I do -d marvell, it says: > # ./smartctl -d marvell /devices/pci at 0,0/pci1043,82d4 at 1f,2/disk at 1,0 > Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) > > (again, same when I try various /dev/dsk/c9t1d0* devices) > > Reading http://opensolaris.org/jive/thread.jspa?messageID=384927 one > person says "SATA drives are ATA and unsupported in smartmontools > for Solaris." > Any ideas? > > -Ethan > >what do you get from: smartctl -a /dev/dsk/c9t1d0s0 --Tim -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100307/d1578626/attachment.html>
I''m imagining that OpenSolaris isn''t *too* different from Solaris 10 in this regard. I believe Richard Elling recommended "cfgadm -v". I''d also suggest "iostat -E", with and without "-n" for good measure. So that''s "iostat -E" and "iostat -En". As long as you know the physical drive specification for the drive (c<X>t<y>d<z> which appears to be c9t1d0 from the other e-mail you sent), "iostat -E" has never failed me. If you need to know the drive identifier, then that''s an additional issue. On Sun, Mar 7, 2010 at 13:30, Ethan <notethan at gmail.com> wrote:> I have a failing drive, and no way to correlate the device with errors in > the zpool status with an actual physical drive. > If I could get the device''s serial number, I could use that as it''s printed > on the drive. > I come from linux, so I tried dmesg, as that''s what''s familiar (I see that > the man page for dmesg on opensolaris says that I should be using syslogd > but I haven''t been able to figure out how to get the same output from > syslogd). But, while I see at the top the serial numbers for some other > drives, I don''t see the one I want because it seems to be scrolled off the > top. > Can anyone tell me how to get the serial number of my failing drive? Or > some other way to correlate the device with the physical drive? > > -Ethan > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > >-- "You can choose your friends, you can choose the deals." - Equity Private "If Linux is faster, it''s a Solaris bug." - Phil Harman Blog - http://whatderass.blogspot.com/ Twitter - @khyron4eva -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100308/92d1087c/attachment.html>
Khyron wrote:> I believe Richard Elling recommended "cfgadm -v". I''d also suggest > "iostat -E", with and without "-n" for good measure. > > So that''s "iostat -E" and "iostat -En". As long as you know the > physical drive > specification for the drive (c<X>t<y>d<z> which appears to be c9t1d0 from > the other e-mail you sent), "iostat -E" has never failed me. If you > need to > know the drive identifier, then that''s an additional issue.iostat and cfgadm frequently return no serial number for me, where other tools do (luxadm, smartctl, etc.). For example, with Seagate SATA drives hanging off an LSI SAS 3081ER: $ cfgadm -alv | grep c7t13d0 c7::dsk/c7t13d0 connected configured unknown ST31500341AS ST31500341AS unavailable disk n /devices/pci at 0,0/pci8086,27d0 at 1c/pci1000,3140 at 0:scsi::dsk/c7t13d0 $ iostat -nE c7t13d0 c7t13d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 Vendor: ATA Product: ST31500341AS Revision: CC1H Serial No: Size: 1500.30GB <1500301910016 bytes> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal Request: 0 Predictive Failure Analysis: 0 carson:gandalf 0 $ pfexec smartctl -i /dev/rdsk/c7t13d0 smartctl version 5.38 [i386-pc-solaris2.11] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION ==Device Model: ST31500341AS Serial Number: 9VS2JRR7 Firmware Version: CC1H User Capacity: 1,500,301,910,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Mon Mar 8 01:01:21 2010 PST SMART support is: Available - device has SMART capability. SMART support is: Enabled -- Carson
On Mon, Mar 8, 2010 at 04:03, Carson Gaspar <carson at taltos.org> wrote:> Khyron wrote: > > I believe Richard Elling recommended "cfgadm -v". I''d also suggest >> "iostat -E", with and without "-n" for good measure. >> >> So that''s "iostat -E" and "iostat -En". As long as you know the physical >> drive >> specification for the drive (c<X>t<y>d<z> which appears to be c9t1d0 from >> the other e-mail you sent), "iostat -E" has never failed me. If you need >> to >> know the drive identifier, then that''s an additional issue. >> > > iostat and cfgadm frequently return no serial number for me, where other > tools do (luxadm, smartctl, etc.). For example, with Seagate SATA drives > hanging off an LSI SAS 3081ER: > > $ cfgadm -alv | grep c7t13d0 > c7::dsk/c7t13d0 connected configured unknown > ST31500341AS ST31500341AS > unavailable disk n /devices/pci at 0,0/pci8086,27d0 at 1c > /pci1000,3140 at 0:scsi::dsk/c7t13d0 > > $ iostat -nE c7t13d0 > c7t13d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 > Vendor: ATA Product: ST31500341AS Revision: CC1H Serial No: > Size: 1500.30GB <1500301910016 bytes> > Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 > Illegal Request: 0 Predictive Failure Analysis: 0 > > carson:gandalf 0 $ pfexec smartctl -i /dev/rdsk/c7t13d0 > smartctl version 5.38 [i386-pc-solaris2.11] Copyright (C) 2002-8 Bruce > Allen > Home page is http://smartmontools.sourceforge.net/ > > === START OF INFORMATION SECTION ==> Device Model: ST31500341AS > Serial Number: 9VS2JRR7 > Firmware Version: CC1H > User Capacity: 1,500,301,910,016 bytes > Device is: Not in smartctl database [for details use: -P showall] > ATA Version is: 8 > ATA Standard is: ATA-8-ACS revision 4 > Local Time is: Mon Mar 8 01:01:21 2010 PST > SMART support is: Available - device has SMART capability. > SMART support is: Enabled > > > -- > Carson > >cfgadm -v gave exactly what I needed. iostat -E was blank after "Serial No:" smartctl, I can''t seem to get working with my devices. luxadm doesn''t appear to apply to my setup as best I can tell from its man page. anyway, I got what I needed - thank you guys for all your help. -Ethan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100308/628e3903/attachment.html>