Scrub of pool A cuase freenas to become unresponsive! Scrub on pool b has no problems.

Snow

Patron
Joined
Aug 1, 2014
Messages
309
Its my main pool that is doing it. After 11.3 when I do a Scrub it causes FreeNas to become unresponsive.
The hardware is my main system posted below. I have never had this problem in the 8 or so years ruining FreeNas.
I am not sure where to start? It seems to me to point to a disk, but I have not received any smart test errors.
But I also have not ran a smart test from the cli. Any help would be welcome. I am stumped on this one.

This is the 2nd time it has done this to me. When I come home and freenas is locked up.
Only way I can fix it is to forces a reboot via IPMI.

Freenas Zpool status.png
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,700
You can do zpool scrub -s poolname to stop the scrub (just a general trick if you find yourself in that situation and need things to return to normal immediately)

Where is your system dataset? if it's in that pool that may be it.
 

Snow

Patron
Joined
Aug 1, 2014
Messages
309
it is the dataset on the spindle disks, the larger of the 2 arrays.
 

Snow

Patron
Joined
Aug 1, 2014
Messages
309
Looks like In IPMI I see I am having a Error. Error That I see is OME" CPLD" CATERR". If any one Know this error better would be great All I can find is its a CPU or Ram Problem.
 

Snow

Patron
Joined
Aug 1, 2014
Messages
309
Well I did some more searching and found that the error is do to the restart. So It looks like the system is hanging well doing a scrub. Not sure why as it has more then enough Ram & CPU. What should I do next? I feel from what I was reading off of Supermicro support page. That I should be looking at the software. As the software is Freenas, It is what is causing the hanging?

I read other stuff off a different site that says it could be the CPU or Ram. But then again Supermicro support says that this errors is due to the hanging of the system. Then if you reboot it well it is hanging it cause that error. Should I just do a Memtest86? Its not like it is happening all the time, So I can not just pull dimms to see if it is fixed. I am not sure how to test the CPU's ? Is their a boot able stress tester for CPU's?
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,700
You might want to try moving the system dataset to the boot pool or another ssd pool if you have the option and see if the problem abates.
 

Snow

Patron
Joined
Aug 1, 2014
Messages
309
boot is on dual ssd's
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,700
Top