Timeout errors when mving files to TrueNAS Server

[Konrad.Jaschke]

TrueNAS Core, latest version
ASUS PRIME B450M-A/CSM
AMD Ryzen 5 3400G
64GB (not ECC)

• m/b, CPU, memory all brand new

SAS9207-8i with latest FW 20….
6x WD40EFRX-68N

• Drives and LSI card never used before, but are about 5 years old
• Was going to do this project five years ago and never got to it

Server install and setup went without any problems. Created pool, DS, Share. Connected to share and moved about 1TB of files to the server. Then started to use two computers to copy to the server and the speeds went down to zero. Had a look on the console and had the below and attached errors. Only a restart helps. Sometimes the console is even frozen, you can’t type anything, error on screen is attached.

Looking for suggestions, don’t know what else to try. Should I get a new, up to date LSI card? It can’t be the drives since it seems to be all of the drives an error happens on.

Currently moving all 1TB of files back to external drive and then need to figure out what this problem is.


Dec 26 23:00:03 CIMSITNAS01 (da2:mps0:0:8:0): WRITE(10). CDB: 2a 00 6f 52 20 38 00 00 a0 00
Dec 26 23:00:03 CIMSITNAS01 (da2:mps0:0:8:0): CAM status: Unrecoverable Host Bus Adapter Error
Dec 26 23:00:03 CIMSITNAS01 (da2:mps0:0:8:0): Retrying command, 3 more tries remain

Dec 26 23:41:18 CIMSITNAS01 mps0: Sending abort to target 7 for SMID 1795
Dec 26 23:41:18 CIMSITNAS01 (da1:mps0:0:7:0): WRITE(10). CDB: 2a 00 65 48 88 20 00 06 00 00 length 786432 SMID 1795 Aborting command 0xfffffe00e7696c08
Dec 26 23:41:18 CIMSITNAS01 (da4:mps0:0:10:0): WRITE(10). CDB: 2a 00 65 48 88 a8 00 05 80 00 length 720896 SMID 1806 Command timeout on target 10(0x000d) 60000 set, 60.54572506 elapsed
Dec 26 23:41:18 CIMSITNAS01 mps0: Sending abort to target 10 for SMID 1806
Dec 26 23:41:18 CIMSITNAS01 (da4:mps0:0:10:0): WRITE(10). CDB: 2a 00 65 48 88 a8 00 05 80 00 length 720896 SMID 1806 Aborting command 0xfffffe00e7697ad0
Dec 26 23:41:18 CIMSITNAS01 (da5:mps0:0:11:0): WRITE(10). CDB: 2a 00 65 48 88 60 00 05 40 00 length 688128 SMID 1797 Command timeout on target 11(0x000e) 60000 set, 60.55096775 elapsed
Dec 26 23:41:18 CIMSITNAS01 mps0: Sending abort to target 11 for SMID 1797
Dec 26 23:41:18 CIMSITNAS01 (da5:mps0:0:11:0): WRITE(10). CDB: 2a 00 65 48 88 60 00 05 40 00 length 688128 SMID 1797 Aborting command 0xfffffe00e7696eb8
Dec 26 23:41:18 CIMSITNAS01 (da2:mps0:0:8:0): WRITE(10). CDB: 2a 00 65 48 87 e8 00 04 c0 00 length 622592 SMID 1798 Command timeout on target 8(0x000b) 60000 set, 60.55769840 elapsed
Dec 26 23:41:18 CIMSITNAS01 mps0: Sending abort to target 8 for SMID 1798
Dec 26 23:41:18 CIMSITNAS01 (da2:mps0:0:8:0): WRITE(10). CDB: 2a 00 65 48 87 e8 00 04 c0 00 length 622592 SMID 1798 Aborting command 0xfffffe00e7697010
Dec 26 23:41:18 CIMSITNAS01 (da2:mps0:0:8:0): WRITE(10). CDB: 2a 00 65 48 8d 28 00 00 80 00 length 65536 SMID 1803 Command timeout on target 8(0x000b) 60000 set, 60.57001258 elapsed
Dec 26 23:41:18 CIMSITNAS01 (da3:mps0:0:9:0): WRITE(10). CDB: 2a 00 65 48 82 a0 00 05 00 00 length 655360 SMID 1820 Command timeout on target 9(0x000c) 60000 set, 60.60155660 elapsed
Dec 26 23:41:18 CIMSITNAS01 mps0: Sending abort to target 9 for SMID 1820
Dec 26 23:41:18 CIMSITNAS01 (da3:mps0:0:9:0): WRITE(10). CDB: 2a 00 65 48 82 a0 00 05 00 00 length 655360 SMID 1820 Aborting command 0xfffffe00e7698da0
Dec 26 23:41:18 CIMSITNAS01 (da0:mps0:0:6:0): WRITE(10). CDB: 2a 00 65 48 82 a8 00 05 00 00 length 655360 SMID 1691 Command timeout on target 6(0x0009) 60000 set, 60.67151391 elapsed
Dec 26 23:41:18 CIMSITNAS01 mps0: Sending abort to target 6 for SMID 1691
Dec 26 23:41:18 CIMSITNAS01 (da0:mps0:0:6:0): WRITE(10). CDB: 2a 00 65 48 82 a8 00 05 00 00 length 655360 SMID 1691 Aborting command 0xfffffe00e768e048

 

[Konrad.Jaschke]

Forgot boot drives, 2x Samsung 120GB 840 SSD, from memory, not onsite to look at right now.

 

[Kris Moore]

Since its across multiple drives I'd suspect controller is at fault here. Try the usual, reseat, check temps, and if all else fails, replace.

 

[Konrad.Jaschke]

Replaced the LSI adapter, same problem, replaced cables, same problem. :(

Don't know what to try next. Maybe an older Intel board.

 

[Konrad.Jaschke]

Not 100% sure yet, but I changed the mainboard/CPU to a little older Intel board (used same RAM) and so far the problem hasn't happened.

So at the moment Its looking like its something to do with the m/b and CPU combo, BIOS setting, etc? Maybe something with m/b x16 PCIe slot? Its only got the one though and a couple x1 slots. So can't plug adapter anywhere else. :(

Currently moving everything I copied previously, off the NAS and then going to wipe it all out and start off nice and fresh with this old m/b and see how it all goes.

 

[Konrad.Jaschke]

Not 100% sure yet, but I changed the mainboard/CPU to a little older Intel board (used same RAM) and so far the problem hasn't happened.

So at the moment Its looking like its something to do with the m/b and CPU combo, BIOS setting, etc? Maybe something with m/b x16 PCIe slot? Its only got the one though and a couple x1 slots. So can't plug adapter anywhere else. :(

Currently moving everything I copied previously, off the NAS and then going to wipe it all out and start off nice and fresh with this old m/b and see how it all goes.

No more errors for a few days so looks like its the mainboard/CPU combination. :(

Anyone have any suggestions on getting the ASUS MB and CPU working with TrueNAS? BIOS settings?

 

[Vlad_Chudo]

Hi. As you say that memory never was used you must run memtest to test your memory. After a day or so testing, and have no errors, you can say that it can be m/b or cup or something else. That is wy you need to replace m/b battery it can couse a problems too. Or it can be a bad contact of m/b and any component.

 

[Konrad.Jaschke]

Hi. As you say that memory never was used you must run memtest to test your memory. After a day or so testing, and have no errors, you can say that it can be m/b or cup or something else. That is wy you need to replace m/b battery it can couse a problems too. Or it can be a bad contact of m/b and any component.

Doesn't look like memory since its been running perfectly for almost a week now with the 64GBs of memory, used m/b, and intel CPU. And the new CPU and new m/b is working great as a Windows 10 desktop. To me it looks like a setting or problem with adapter in the x16 slot?

Thanks,

 

[Vlad_Chudo]

Than you can watch in which mode working pci-e interface. With how many lines. But you can do it only from Windows he info I think can help. Maybe you can watch on pci card contacts and clean them. Update bios, reset bios. In my practice I saw cpu which was freezing only in excel and was one that resets when stress gpu on it. So much variants)))

 

[Vlad_Chudo]

HWinfo would help. Also say does pci card and cables new?