[OpenIndiana-discuss] [zfs] problem on my zpool

[Sebastian Gabler]

 From 'zpool status' this looks very much like an issue I had myself 2.5 
years ago with a pool containing WD20EARS and some other 2 TB disks. It 
started exactly when I moved them from the Intel ICH to an LSI SAS 1068 
controller, and added more disks to the enclosure. I decided then to 
destroy the whole pool and restore the data from a backup (well, 
actually the original source because the broken pool was the backup), 
without the WD20EARS involved.

I wonder if there is any rescue for the pool moving them to an adapter 
they are compatible. I think that in any case the WD20EARS should be 
fine, given you can make them work.

However, there is another issue to keep in mind: Vibration. WD20EARS are 
not specified to run in multi-disk enclosures. They are quite 
susceptible to vibration issues. It could be that you simple hit your 
head to the wall at that point. Better use disks with better vibration 
management.

BR

Sebastian

------------------------------ Message: 2 Date: Wed, 23 Oct 2013 
20:21:39 +1300 From: Mark <mark0x01 at gmail.com> To: Discussion list for 
OpenIndiana <openindiana-discuss at openindiana.org> Subject: Re: 
[OpenIndiana-discuss] [zfs] problem on my zpool Message-ID: 
<52677903.3030002 at gmail.com> Content-Type: text/plain; 
charset=ISO-8859-1; format=flowed One suggestion for the future for 
better reliability. Avoid using WDC WD20EARS, they aren't great, and 
hopeless on SAS controllers. Avoid mixing disk brands or models in a 
zpool. The different behaviour can trigger issues. On 23/10/2013 7:46 
p.m., Clement BRIZARD wrote:
>> I cleared the "degraded" disk. we will see what happens  in 131hours
>>
>>     pool: nas
>>    state: ONLINE
>> status: One or more devices is currently being resilvered.  The pool will
>>       continue to function, possibly in a degraded state.
>> action: Wait for the resilver to complete.
>>     scan: resilver in progress since Wed Oct 23 08:25:56 2013
>>       2.23G scanned out of 22.2T at 48.6M/s, 133h22m to go
>>       6.10M resilvered, 0.01% done
>> config:
>>
>>       NAME                         STATE     READ WRITE CKSUM
>> CAP            Product
>>       nas                          ONLINE       0     0     0
>>         raidz1-0                   ONLINE       0     0     0
>>           c8t50024E9004993E6Ed0p0  ONLINE       0     0     0     2
>> TB           SAMSUNG HD204UI
>>           c8t50024E92062E7524d0    ONLINE       0     0     0     2
>> TB           SAMSUNG HD204UI
>>           c8t50024E900495BE84d0p0  ONLINE       0     0     0     2
>> TB           SAMSUNG HD204UI
>>           c8t50014EE25A5EEC23d0p0  ONLINE       0     0     0     2
>> TB           WDC WD20EARS-00M
>>           c8t50024E9003F03980d0p0  ONLINE       0     0     0     2
>> TB           SAMSUNG HD204UI
>>           c8t50014EE2B0D3EFC8d0    ONLINE       0     0     0     2
>> TB           WDC WD20EARX-00P
>>           c8t50014EE6561DDB4Cd0p0  ONLINE       0     0     0     2
>> TB           WDC WD20EARS-00M
>>           c8t50024E9003F03A09d0p0  ONLINE       0     0     0     2
>> TB           SAMSUNG HD204UI
>>         raidz1-1                   ONLINE       0     0     0
>>           c50t8d0                  ONLINE       0     0     0
>> (resilvering)     2 TB           ST2000DL004 HD20
>>           c2d0                     ONLINE       0     0     0
>> (resilvering)     2 TB
>>           c1d0                     ONLINE       0     0     0
>> (resilvering)     2 TB
>>           c50t11d0                 ONLINE       0     0     0     2
>> TB           SAMSUNG HD204UI
>>           c50t10d0                 ONLINE       0     0     0
>> (resilvering)     2 TB           SAMSUNG HD204UI
>>
>>