Disk detected in BIOS does not show in truenas

TrueNAS General
1

Hello, I just got a pair of disks. Refurbished I must confess, but from a vendor with very good reputation.

Both of them show in the BIOS but only the one with SN: ZJV2MBS3 shows on truenas. Both of them show on my computer when using a SATA to USB converter.

bios
bios828×213 73.1 KB

truenas
truenas1657×478 36.8 KB

The ports connected were always used without issue with older disks.
Also tried connecting only the invisible disk with same result:

single_disk
single_disk817×625 236 KB

truenas2
truenas21637×312 27.5 KB

There is no trace of the disk.

My setup is 7 years old and this is first time I get this problem. What should I check?

TrueNAS-12.0-U6.1
X10SLL-F
32 GiB

EDIT: clicked post by mistake.

2

Another update. Because I’m searching and there are scenarios where the disk does not show in the webUI. In my case the disk does not show at all. In fact it should be ada2 because the port I’m using. It does not appear in the OS at all.

root@lavochkin:~ # camcontrol devlist
<ST3250310CS 3.ACD>                at scbus0 target 0 lun 0 (pass0,ada0)
<WDC WD20EZRZ-00Z5HB0 80.00A80>    at scbus1 target 0 lun 0 (pass1,ada1)
<WDC WD20EARS-00MVWB0 51.0AB51>    at scbus5 target 0 lun 0 (pass2,ada2)
<WDC WD20EZRZ-00Z5HB0 80.00A80>    at scbus6 target 0 lun 0 (pass3,ada3)
<WDC WD20EZRZ-00Z5HB0 80.00A80>    at scbus7 target 0 lun 0 (pass4,ada4)
<AHCI SGPIO Enclosure 2.00 0001>   at scbus8 target 0 lun 0 (pass5,ses0)
root@lavochkin:~ #
3

Hi, geom disk list show something different?
I remember a similar thread (but can’t find It) and if im not wrong the issue was related to data/partitions contained in the disk itself

4

No, geom disk list shoes the same list, allow to grep only the name:

root@lavochkin:~ # geom disk list|grep name
Geom name: ada0
Geom name: ada1
Geom name: ada2
Geom name: ada3
Geom name: ada4

I know the issue you mention about the disk already being formatted. In all those cases the disk does not show in the UI but it does shows in the CLI. I think my case is completely different.

Anyhow the vendor will replace it. I’m documenting dmesg and other relevant logs to compare with the replacement disk and see if I see any difference.