August 27, 20196 yr I'm building a new rig with an ASUS Z10PE-D16 WS and Xeon 2637 v3. unRAID (6.7.2) boots fine, but soon as some tasks were initiated, such as logging in to Main web interface, or entering `diagnostics` on command line, the system would freeze after 1-2 minutes, with the CATTERR LED lit up red on the motherboard. After much stripping of peripherals, the tail -f /var/log/syslog reveals nvme nvme0: controller is down: will reset: CSTS=0xffffffff. PCI_STATUS=0xffff I removed the NVMe drive, and the system no longer freezes. The NVMe drive is a WD Black 500GB (the first model), and it's a Windows 10 OS drive. I have booted the same build into this Windows 10 on this drive, and it's running well, with a few test running fine overnight such as Prime95 and Unigine Heaven. So I think this error is Linux and/or unRAID specific. Anyone has any idea on what should I do next to troubleshoot? Edited August 27, 20196 yr by ldrax added unRAID version
August 27, 20196 yr Community Expert Those devices use a Marvell controller and are not recommended, latest models use an in house controller and those are fine, but this might help.
August 27, 20196 yr Author Thank you for the pointer @johnnie.black, I'll try it out later. When you said 'those', are you referring to the controller on the motherboard, or the controller inside the NVMe drive? And 'latest models', is it of the NVMe drives, or of the motherboard?
August 27, 20196 yr Community Expert 1 hour ago, ldrax said: or the controller inside the NVMe drive? 1 hour ago, ldrax said: is it of the NVMe drives these
August 27, 20196 yr Author update, the iommu=pt didn't work in my case, but replacing the drive with a different model did (and without the iommu=pt). The new one is a Samsung PM981. I guess that solves it. Thanks @johnnie.black!
Archived
This topic is now archived and is closed to further replies.