I am new to TrueNAS (any NAS for that matter) and before storing all my precious data on the system I wanted to run it with disposable/non critical data for a few weeks before “committing”. So if this doesn’t work it’s not a problem since there’s no relevant data in that pool, but I wanted to use this as an opportunity to debug a real problem without any risks.
The hardware:
-Terramaster F2 424 in stock 8GB config.
-Bootdrive is a 128GB SSD connected over a USB-Sata bridge to the internal USB2.0 port of the Terramaster
-The currently only other drive is a 1TB Samsung 980 NVME in one of the M.2 slots
I had the boot drive connected to the rear USB 3.0 port for the first week until I got a low profile adapter for the internal USB port to mount the boot drive. When I installed said adapter and booted the NAS, the pool on the NVME didn’t show up anymore. I had this once before, which could be solved by manually exporting the pool and importing it via the GUI. SO I tried the same this time, but now the pool doesn’t show up at all and can’t be imported. The drive itself shows up.
Heres the output of lsblk
truenas_admin@truenas[~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 119.2G 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 512M 0 part
└─sda3 8:3 0 118.7G 0 part
nvme0n1 259:0 0 931.5G 0 disk
└─nvme0n1p4 259:1 0 37G 0 part
zpool list
truenas_admin@truenas[~]$ sudo zpool list
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
boot-pool 118G 2.96G 115G - - 0% 2% 1.00x ONLINE -
zpool status
truenas_admin@truenas[~]$ sudo zpool status
pool: boot-pool
state: ONLINE
config:
NAME STATE READ WRITE CKSUM
boot-pool ONLINE 0 0 0
sda3 ONLINE 0 0 0
errors: No known data errors
What steps can I further take to try and import the pool on the NVME? Thanks!
I would suggest running: zpool import
from the CLI. This command will output the pools that are available to import. The output from the command might give you some clues as to what’s causing the import to fail.
It could be something as simple as the name of the pool is conflicting with the running boot-pool. If this is the case, you can try:
zpool import boot-pool new-pool
This will import and rename the pool at the same time, if my memory is correct.
/dev/sda is the boot disk - AAB9C328-0652-4A94-84B3-703590146BC9 is the partition-uuid for the boot pool which is already imported and mounted, but if it was some other disk, then you would need to do zpool import /dev/disk/by-partuuid/AAB9C328-0652-4A94-84B3-703590146BC9.
lsblk says the nvme disk has a partition, but fdisk says no partitions and so no pool.
Since there are only two drives in this NAS and I had some data on the SMB share and installed some apps and containers there must be a pool. I wonder why it doesn’t show up.