Error on Zpool

[yena]

Hello,
i have a backup server with this Zpool error and the pool is off line
------------------------------------------------------------------------------------------------------
zpool status -xv
pool: STORAGE
state: ONLINE
status: One or more devices are faulted in response to IO failures.
action: Make sure the affected devices are connected, then run 'zpool clear'.
see: http://zfsonlinux.org/msg/ZFS-8000-HC
scan: resilver canceled on Thu Jan 1 01:00:00 1970
config:

NAME STATE READ WRITE CKSUM
STORAGE ONLINE 2 0 0
mirror-0 ONLINE 7 0 0
sdc1 ONLINE 13 477 18
sdd1 ONLINE 5 5.90K 0

errors: List of errors unavailable (insufficient privileges)

------------------------------------------------------------------------------------------------------

If i try zpool import,
both disk go in resilver state for some time and than the pool come back off line.

SMART on both disk is OK

Someone have experienced same issue ? ..Solutions ?

Thanks!

 

[wolfgang]

Hi,

as the message says you have io problems.
This has not categorical something to do with the disks.
May be your controller is the problem.
Also Smart tell not always trues.

 

[yena]

Hi,

as the message says you have io problems.
This has not categorical something to do with the disks.
May be your controller is the problem.
Also Smart tell not always trues.

Yes i think y are right, maybe the Motherboard.
Now i have done a zpool clear
and after resilver seem ok:

zpool status
pool: STORAGE
state: ONLINE
scan: resilvered 8.01G in 0h6m with 0 errors on Thu Apr 27 09:32:50 2017
config:

NAME STATE READ WRITE CKSUM
STORAGE ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
sdc1 ONLINE 0 0 0
sdd1 ONLINE 0 0 0

but i will change the Mainboard...
Thanks

 

[guletz]

It is not a smart idea to change your MB. First try to put your disks in another server/pc for at least 2 or 3 days. this kind of error are hard to diagnosed . It could be your MB, your RAM, your sata cables or your HDDs.
Anyway run a zfs scrub as many times as you can, so you can see if the problem is persistent . I see many situations when the problem like this was happend to me, it was not a MB fault(none to be exactly ).