Greetings everyone - unsure if "System hardware" or "storage" is better, but this seemed more basic so I chose the former:
I've got a new dual Asus AMD Epyc 7742 based server (model #RS700A-E11-RS12U). It's unique in that it has PCIe lanes going directly to NVME disk slots on the front of the chassis. No SAS/SATA, and no controller. Upon attempting to install FreeBSD (either 12 or 13 have the issue), I get through the installer which sees no disks in the system, though there is one 7.68TB NVME disk. I noticed the installer probe showed:
So it appears to understand what it is, but for whatever reason, can't initialize it. Ubuntu 22.04 and Windows 10 and 11 both install to this disk without issue, in case it matters. I only found one other mention of this error in the nvme context and the discussion just kinda trailed off and wasn't quite the same details (it was interrupt related).
We have not deployed the system yet so if this is a more sinister problem, I'd love to assist with the debug/investigation/beta testing. Thank you!
I've got a new dual Asus AMD Epyc 7742 based server (model #RS700A-E11-RS12U). It's unique in that it has PCIe lanes going directly to NVME disk slots on the front of the chassis. No SAS/SATA, and no controller. Upon attempting to install FreeBSD (either 12 or 13 have the issue), I get through the installer which sees no disks in the system, though there is one 7.68TB NVME disk. I noticed the installer probe showed:
Code:
nvme0: <WDC SN200> at device 0.0 numa-domain 0 on pci4
nvme0: unable to allocate pci resource
nvme0: <WDC SN200> at device 0.0 numa-domain 0 on pci4
nvme0: unable to allocate pci resource
We have not deployed the system yet so if this is a more sinister problem, I'd love to assist with the debug/investigation/beta testing. Thank you!