X11 SPi-TF new build, Truenas UI can’t list any HDD and M.2 (but shown in shell)

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

Crouching_Camper

New Member
Jan 8, 2026
13
7
3
Hi everyone, first post. I just upgraded my hardware (See signature for old rig) and I decided to wipe the old pools clean and rebuilt.

The new hardware:

Xeon Xeon Silver 4214R

Supermicro X11 SPI-TF

64GB (4x16GB) PC4-17000 (2133 MHz) ECC (I know the RAM is slower than what I should have used, but it shouldn’t cause problems, right?)

Carryover from old rig:

2x Kingston 120GB for boot pool
4x IronWolf pro 10GB (Mirror VDEV for main storage)
4x Barracuda 2GB (Mirror VDEV for temp storage)
(all plugged to onboard SATA)
2x WD Blue SN570 1TB M.2 on Supermicro AOC-SLG3-2M2 (Mirrored for Apps and VM), plugged to slot 2
Quadro RTX (for transcoding)
All old pools were destroyed by the old rig so I can rebuild in new rig

Issue: After boot, I went to UI to create pool and I got the Validation error, (KeyError: “Array Device Slot”) – See attachment
https://forums.truenas.com/uploads/...d89af906ed59157ae800dd4d5a53aeab04995169.jpeg
2026-01-07_1-10-57
No disk is shown in UI

When I run lsblk in shell, I can see all drives (see attachments)

When I go to Disk, I see "Cannot retrieve response" (see attachments)

2026-01-07_18-52-45


Things I have tried and observed:

1. Bios → Disable Intel VT-D, confirm VMD disabled, all drives are visible in Bios

2. SATA are running in AHCI mode so no RAID

3. All drives are visible when running lsblk, including the 2xM.2, so bifurcation is working.

2026-01-07_1-10-20


4. Restarted middleware (service middlewared restart)

5. So I proceed by removing things. I have removed some HDD (removed the 4xBarracuda), to ALL 8xHDD, then I even removed the M.2 adapter, and then GPU. In all case the error message remain even when there are no drives, no M.2, and no GPU.

6. I have gone back previous version of Truenas, so far I have tried 25.10.1, 25.04.2.6, 24.10.2.4, and 24.10.2.

7. Obviously, none of the above fix the problem.

8. I notice in web UI, under System, there is “Enclousure” which I don’t think it exist in generic hardware (I double check with my Truenas VM and it doesn’t have that. Which means that this board was pulled from a real IXsystem unit. And guess what? The Enclosure page also has the “‘Array Device Slot’“ error

See attachments
2026-01-07_20-08-57


9. And I notice in the IPMI → System → Hardware information, there are IXSystem model name…

2026-01-07_20-13-28

My big question:

1. Is this issue hardware related (I hope not) or software? If it is hardware, then why I can see all drives in bios and listed in shell?

2. Why was the error retained even after I removed all drives? I understand HBA is preferred instead of onboard SATA, but even in my old rig (X10 SRi-F) the drives were plugged into onboard SATA and nothing happened. (In both case the SATA was set to be AHCI)

3. I suspect this has something to do with the Hardware info in IPMI. So how do I remove these info? May be making the board a real generic board will resolve the issue? (Before the whole saga I already flash the BIOS and IPMI)

4. All my data was backed up in a Window server but it was Storage spaces in stripped formation so no redundancy. I am hoping to get my new rig work ASAP so I can get the data back (before Windows server crap out on me)

Any help is very much appreciated
:folded_hands:
 
  • Like
Reactions: etorix

RolloZ170

Well-Known Member
Apr 24, 2016
9,247
2,963
113
germany
Issue: After boot, I went to UI to create pool and I got the Validation error, (KeyError: “Array Device Slot”) – See attachment
do you use the old install ? maybe a drive letter is changed.
or a secure key id used and changed because other motherboard/cpu now.
 

Crouching_Camper

New Member
Jan 8, 2026
13
7
3
do you use the old install ? maybe a drive letter is changed.
or a secure key id used and changed because other motherboard/cpu now.
This is a new install, boot pool and data pool are new.

I have gone back (reinstall) previous version of Truenas, so far I have tried 25.10.1, 25.04.2.6, 24.10.2.4, and 24.10.2

Can you explain a bit more about "secure key id" I am not sure what you are referring to...

BTW, I have also updated the BIOS and BMC firmware, also clear the CMOS (remove battery)
 

etorix

Active Member
Sep 28, 2021
219
124
43
Great work finding out the issue…
The question now is to find how to set up (delete) this hardware information in IPMI so your build is correctly recognised as "generic" and not tied to how iX uses this board in their own hardware. iX obviously knows how to do that but may not want to share this information—or try to reach their consumer support directly.
 

Crouching_Camper

New Member
Jan 8, 2026
13
7
3
Great work finding out the issue…
The question now is to find how to set up (delete) this hardware information in IPMI so your build is correctly recognised as "generic" and not tied to how iX uses this board in their own hardware. iX obviously knows how to do that but may not want to share this information—or try to reach their consumer support directly.
So you think the Chassis info and Product name in FRM (as in screenshot in original post) is what trigger this behaviour in Truenas?
I will see if I can replace these FRM values (I don't think you can erase) and see if this make any difference
(BTW, the board is returnable only until this Sunday, so I have less than 2 days to find out)
 

Crouching_Camper

New Member
Jan 8, 2026
13
7
3
i don't think this is the issue, iXsystems or supermicro is both not generic.
Then what causes this behaviour in Truenas? The Enclosure is not appear in generic hw (VM)
Do you think Truenas read specific value in FRU and trigger additional IXsystem features?
 

Crouching_Camper

New Member
Jan 8, 2026
13
7
3
i recommend to force your energy at the truenas community.
Sadly I have more replies here than in Truenas forum

 

kapone

Well-Known Member
May 23, 2015
1,850
1,236
113
That iXsystems information is most likely coming from the FRU data on the motherboard and Truenas can access the Supermicro BMC by default (and is enabled by default). As an e.g., on one of my Truenas systems, this is already in System-->Network:

Screenshot 2026-01-09 at 12.52.28 PM.png

It's accessing and getting this from the BMC and is most likely detecting it as Truenas Enterprise hardware, but...you don't have an enterprise license...

So..something to try. Use ipmicfg and issue the "ipmicfg -fde" command if running locally, or using the network parameters if running remotely.


The "fde" command should reset the BMC to default, including clearing the FRU data, VLANs etc. You may need to reinstall Truenas to clear any residual traces of this info.

Edit: Oh, and please clear the NVRAM as well. Many different ways to do that.
 
  • Like
Reactions: RolloZ170

RolloZ170

Well-Known Member
Apr 24, 2016
9,247
2,963
113
germany
..but a msg from truenas "pls enter your activation key" or something similar would be better thought.