Reinitializing controller

[EugenioTF]

Good afternoon, I suddenly got a reinitializing controller error. Who faced this problem? Help, who has solutions? Thanks!

Intel Xeon E5-2650 v4
2 * LSI 9211-8i SAS SATA FM20.00.07.00
1 * LSI 9201-16e
RAM 80GB ECC
Truenas 12 - U6
26 * HDD WD 4TB NAS
Motheboard Supermicro X10SRi-F
Seasonic Prime Gold 750 Watt ATX

The controller is initialized constant.

 

[jgreco]

Help us help you. Please describe your hardware and system, as outlined in the Forum Rules, conveniently linked in red at the top of every page.

In particular, explain why you have more than one HBA in your system, and whether you have taken care to keep these properly cooled. LSI HBA's are server components, and if you have cobbled together your own "server" from a random consumer-grade chassis and you haven't engineered airflow and cooling for the HBAs, overheating can cause random communications errors.

 

[EugenioTF]

Help us help you. Please describe your hardware and system, as outlined in the Forum Rules, conveniently linked in red at the top of every page.

In particular, explain why you have more than one HBA in your system, and whether you have taken care to keep these properly cooled. LSI HBA's are server components, and if you have cobbled together your own "server" from a random consumer-grade chassis and you haven't engineered airflow and cooling for the HBAs, overheating can cause random communications errors.

LSI HBAs are under constant airflow. The system has been in use for 3 years.

 

[EugenioTF]

Intel Xeon E5-2650 v4
2 * LSI 9211-8i SAS SATA FW20.00.07.00
1 * LSI 9201-16e FW20.00.07.00
RAM 80GB ECC
Truenas 12 - U6
26 * HDD WD 4TB NAS
Motheboard Supermicro X10SRi-F
Seasonic Prime Gold 750 Watt ATX

 

[awasb]

Did you enable any kind of power management?

 

[EugenioTF]

Did you enable any kind of power management?

No, I didn't do anything. In the morning, access to folders began to freeze, and this began to happen at regular intervals.

If everything is in order, then there is no point in managing the power management.

If I did something, then I would roll back.

 

[Samuel Tai]

I started experiencing similar problems with the backplane downstream of my controller a few months ago: any drive in a specific slot would throw errors during a scrub, but would work fine otherwise. Either your mps1 controller or the downstream backplane is starting to go bad.

 

[EugenioTF]

I started experiencing similar problems with the backplane downstream of my controller a few months ago: any drive in a specific slot would throw errors during a scrub, but would work fine otherwise. Either your mps1 controller or the downstream backplane is starting to go bad.

That is, you mean either the motherboard or the controller HBAs


I read your post earlier in the forum. I have a couple of spare LSI HBAs, I've tried swapping them out, but still have errors. Now I also ordered two sas controllers. I had a similar problem a year ago, I changed the controller and everything was fine, but now again. Are these low-quality controllers?

thanks for your reply

 

[Spearfoot]

This might very well be the HBAs, as suggested by @Samuel Tai -- the controller reset and timeouts you're seeing look a lot like the errors I've seen from bad controller cards.

Have you tried swapping disks da8 and da9, putting other disks into the slots where they're currently located? If the errors follows the disks, they may be the problem instead of the controller.

 

[EugenioTF]

This might very well be the HBAs, as suggested by @Samuel Tai -- the controller reset and timeouts you're seeing look a lot like the errors I've seen from bad controller cards.

Have you tried swapping disks da8 and da9, putting other disks into the slots where they're currently located? If the errors follows the disks, they may be the problem instead of the controller.

Yes, that's exactly what I'm doing now. I connected them to a separate controller. Updated BIOS. Swap slots. I ordered new discs. One disk gave me errors for a long time, but I put off replacing it.

Thank you very much for responding.