Re: [zfs-discuss] Help identify failed drive

2010-07-21 Thread Marty Scholes
> If the format utility is not displaying the WD drives > correctly, > then ZFS won't see them correctly either. You need to > find out why. > > I would export this pool and recheck all of your > device connections. I didn't see it in the postings, but are the same serial numbers showing up mult

Re: [zfs-discuss] Help identify failed drive

2010-07-20 Thread Linda Messerschmidt
> No, the pool tank consists of 7 physical drives(5 of Seagate and 2 of > Western Digital) See output below I think you are looking at disk label name, and this is confusing you. I had a similar thing happen where the label name from a 64GB SSD got written onto a 1TB HD. That output in format

Re: [zfs-discuss] Help identify failed drive

2010-07-20 Thread marty scholes
Michael Shadle wrote: >Actually I guess my real question is why iostat hasn't logged any > errors in its counters even though the device has been bad in there > for months? One of my arrays had a drive in slot 4 fault -- lots of reset something or other errors. I cleared the errors and the po

Re: [zfs-discuss] Help identify failed drive

2010-07-20 Thread Yuri Homchuk
. I guess C2 is the one that gives me hassles. Is there way to retrieve the model from solaris ? Thanks. From: Haudy Kazemi [mailto:kaze0...@umn.edu] Sent: Monday, July 19, 2010 5:00 PM To: Yuri Homchuk Cc: zfs-discuss@opensolaris.org; Cindy Swearingen Subject: Re: [zfs-discuss] Help identify

Re: [zfs-discuss] Help identify failed drive

2010-07-20 Thread Yuri Homchuk
2t6d0 sd10=/dev/dsk/c2t7d0 sd11=/dev/dsk/sd11 sd12=/dev/dsk/sd12 From: Haudy Kazemi [mailto:kaze0...@umn.edu] Sent: Monday, July 19, 2010 4:12 PM To: zfs-discuss@opensolaris.org Cc: Yuri Homchuk; Cindy Swearingen Subject: Re: [zfs-discuss] Help identify failed drive 3.) on some systems I&#

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Richard Elling
more below... On Jul 19, 2010, at 4:42 PM, Michael Shadle wrote: > On Mon, Jul 19, 2010 at 4:35 PM, Richard Elling wrote: > >> I depends on if the problem was fixed or not. What says >>zpool status -xv >> >> -- richard > > [r...@nas01 ~]# zpool status -xv > pool: tank > state: DEGR

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Haudy Kazemi
Yuri Homchuk wrote: Well, this is a REALLY 300 users production server with 12 VM's running on it, so I definitely won't play with a firmware J I can easily identify which drive is what by physically looking at it. It's just sad to realize that I cannot trust solaris anymore. I never

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Michael Shadle
On Mon, Jul 19, 2010 at 4:35 PM, Richard Elling wrote: > I depends on if the problem was fixed or not.  What says >        zpool status -xv > >  -- richard [r...@nas01 ~]# zpool status -xv pool: tank state: DEGRADED status: One or more devices has experienced an unrecoverable error. An

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Richard Elling
On Jul 19, 2010, at 4:30 PM, Michael Shadle wrote: > On Mon, Jul 19, 2010 at 4:26 PM, Richard Elling wrote: > >> Aren't you assuming the I/O error comes from the drive? >> fmdump -eV > > okay - I guess I am. Is this just telling me "hey stupid, a checksum > failed" ? In which case why did this

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Haudy Kazemi
Marty Scholes wrote: ' 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. Get and install smartmontools. Period. I resisted it for a few weeks but it has been an amazing tool. It will tell you

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Michael Shadle
On Mon, Jul 19, 2010 at 4:26 PM, Richard Elling wrote: > Aren't you assuming the I/O error comes from the drive? > fmdump -eV okay - I guess I am. Is this just telling me "hey stupid, a checksum failed" ? In which case why did this never resolve itself and the specific device get marked as degra

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Richard Elling
On Jul 19, 2010, at 4:21 PM, Michael Shadle wrote: > On Mon, Jul 19, 2010 at 4:16 PM, Marty Scholes wrote: > >> Start a scrub or do an obscure find, e.g. "find /tank_mointpoint -name core" >> and watch the drive activity lights. The drive in the pool which isn't >> blinking like crazy is a fau

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Michael Shadle
On Mon, Jul 19, 2010 at 4:16 PM, Marty Scholes wrote: > Start a scrub or do an obscure find, e.g. "find /tank_mointpoint -name core" > and watch the drive activity lights.  The drive in the pool which isn't > blinking like crazy is a faulted/offlined drive. Actually I guess my real question is

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Michael Shadle
On Mon, Jul 19, 2010 at 4:16 PM, Marty Scholes wrote: > Start a scrub or do an obscure find, e.g. "find /tank_mointpoint -name core" > and watch the drive activity lights.  The drive in the pool which isn't > blinking like crazy is a faulted/offlined drive. > > Ugly and oh-so-hackerish, but it

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Marty Scholes
> > ' 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. Get and install smartmontools. Period. I resisted it for a few weeks but it has been an amazing tool. It will tell you more than you

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Haudy Kazemi
This is Supermicro Server. I really don't remember controller model, I set it up about 3 years ago. I just remember that I needed to reflush controller firmware to make it work in JBOD mode. Remember, changing controller firmware may affect your ability to access drives. Backup first, as

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Michael Shadle
On Mon, Jul 19, 2010 at 3:11 PM, Haudy Kazemi wrote: > ' 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. Curious: [r...@nas01 ~]# zpool status -x pool: tank state: DEGRADED status: One or more de

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Haudy Kazemi
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,bu

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Yuri Homchuk
0 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

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Yuri Homchuk
w if c2t3d0 Seagate or Western Digital. > > Thanks, > > -Original Message- > From: Cindy Swearingen [mailto:cindy.swearin...@oracle.com] > Sent: Monday, July 19, 2010 9:48 AM > To: Yuri Homchuk > Cc: zfs-discuss@opensolaris.org > Subject: Re: [zfs-discuss] Help identify

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Yuri Homchuk
[mailto:cindy.swearin...@oracle.com] > Sent: Monday, July 19, 2010 9:16 AM > To: Yuri Homchuk > Cc: zfs-discuss@opensolaris.org > Subject: Re: [zfs-discuss] Help identify failed drive > > Hi-- > > I don't know what's up with iostat -En but I think I remember a problem where &

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Yuri Homchuk
again. -Original Message- From: Cindy Swearingen [mailto:cindy.swearin...@oracle.com] Sent: Monday, July 19, 2010 9:16 AM To: Yuri Homchuk Cc: zfs-discuss@opensolaris.org Subject: Re: [zfs-discuss] Help identify failed drive Hi-- I don't know what's up with iostat -En but I think

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Cindy Swearingen
07862016 bytes> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal Request: 0 Predictive Failure Analysis: 0 -Original Message- From: Cindy Swearingen [mailto:cindy.swearin...@oracle.com] Sent: Monday, July 19, 2010 10:28 AM To: Yuri Homchuk Cc: zfs-discuss@opensolari

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Haudy Kazemi
its number): ^C Thanks again. -Original Message- From: Cindy Swearingen [mailto:cindy.swearin...@oracle.com] Sent: Monday, July 19, 2010 9:16 AM To: Yuri Homchuk Cc: zfs-discuss@opensolaris.org Subject: Re: [zfs-discuss] Help identify failed drive Hi-- I don't know what's up

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Cindy Swearingen
2010 9:48 AM To: Yuri Homchuk Cc: zfs-discuss@opensolaris.org Subject: Re: [zfs-discuss] Help identify failed drive Hi-- A google search of ST3500320AS turns up Seagate Barracuda drives. All 7 drives in the pool tank are ST3500320AS. The other two c1t0d0 and c3d0 are unknown, but are not part of

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Cindy Swearingen
number): ^C Thanks again. -Original Message- From: Cindy Swearingen [mailto:cindy.swearin...@oracle.com] Sent: Monday, July 19, 2010 9:16 AM To: Yuri Homchuk Cc: zfs-discuss@opensolaris.org Subject: Re: [zfs-discuss] Help identify failed drive Hi-- I don't know what's up with

Re: [zfs-discuss] Help identify failed drive

2010-07-19 Thread Cindy Swearingen
Hi-- I don't know what's up with iostat -En but I think I remember a problem where iostat does not correctly report drives running in legacy IDE mode. You might use the format utility to identify these devices. Thanks, Cindy On 07/18/10 14:15, Alxen4 wrote: This is a situation: I've got an e