Truenas Scale on Qnap TS-453BE whit extension QM2-2P2G2T and 2x NVMe boot problems

Errorbit#

Cadet
Joined
Jul 14, 2023
Messages
2
Hello dear Community,
I try to get TrueNAS SCALE 22.12.3.2 booting from the on the PCI Nmvme over the extension Card QM2-2P2G2T on mz old QNAP NAS TS-453BE there are 16GB RAM installed.

Problem is the QNAP motherboard is not able to see boot device on PCIe Cards, for testing added singl 2,5" SSD to the NAS. bootet from USB installed Truenas but after installation the drive is unvisible during boot.
After booting in tu TruNAS installer all drives are visible !
Only working is installation on USB.

My Question : How to install only the TrueNAS bootloader on the usb stick but use the boot_pool on the Nvme for the OS ?
 

Errorbit#

Cadet
Joined
Jul 14, 2023
Messages
2
Installed Truenas SCALE 3 times over bootable usb-stick:
1) usb stick
2) usb-ssd
3) 3-pcie-evme

Very interessted is if more than one device in usb is present the trueNAS system fails too boot and fails into "initramfs"


Code:
Command: /sbin/zpool import -N -f 'boot-pool'
Message: cannot import 'boot-pool' : more than one matching pool
import by numeric ID instead

Failed to impoert poll 'boot-pool'
Manually import the pool and exit.


In my Case the 3th installtion on PCI Nvme hast the boot-pool on the 3 Partition of nvme0n1 (/dev/nvme0n1p3)

Code:
ls -hals /dev/disk/by-uuid
total 0
0 drwxr-xr-x 2 root root 340 Jul 15 04:14 .
0 drwxr-xr-x 8 root root 160 Jul 15 04:03 ..
0 lrwxrwxrwx 1 root root  15 Jul 15 04:04 11340228271234053102 -> ../../nvme1n1p1
0 lrwxrwxrwx 1 root root  15 Jul 15 04:04 1675f897-f7d6-4770-adf1-52b4029caa6b -> ../../mmcblk1p5
0 lrwxrwxrwx 1 root root  15 Jul 15 04:14 2216120249608619314 -> ../../nvme0n1p3
0 lrwxrwxrwx 1 root root  10 Jul 15 04:15 3822902373947804465 -> ../../sda4
0 lrwxrwxrwx 1 root root  10 Jul 15 04:14 42BE-72FB -> ../../sdb2
0 lrwxrwxrwx 1 root root  10 Jul 15 04:14 42F2-9E75 -> ../../sda2
0 lrwxrwxrwx 1 root root  10 Jul 15 04:14 4509290095352989673 -> ../../sda3
0 lrwxrwxrwx 1 root root  15 Jul 15 04:04 64b9bf06-7771-4c21-b3fc-adb6b884a0e5 -> ../../mmcblk1p6
0 lrwxrwxrwx 1 root root  15 Jul 15 04:14 677e0164-0876-4352-9ca8-76a3d27e079c -> ../../mmcblk1p2
0 lrwxrwxrwx 1 root root  15 Jul 15 04:17 6966886231355698758 -> ../../nvme0n1p5
0 lrwxrwxrwx 1 root root  15 Jul 15 04:04 82460c04-4f95-4a53-b73e-baf17bbe477d -> ../../mmcblk1p3
0 lrwxrwxrwx 1 root root  10 Jul 15 04:14 826100353712116707 -> ../../sdb3
0 lrwxrwxrwx 1 root root  10 Jul 15 04:14 908abe59-bac2-4cb9-ad04-9d43d28597a2 -> ../../dm-0
0 lrwxrwxrwx 1 root root  15 Jul 15 04:04 9C37-41B5 -> ../../nvme0n1p2
0 lrwxrwxrwx 1 root root  15 Jul 15 04:04 DF29-556E -> ../../mmcblk1p1


Found the UUID : 2216120249608619314

now its posible to boot it by doing:

Code:
/sbin/zpool import -a -d /dev/disk/by-uuid/2216120249608619314
exit


And the system boots from the NVMe!

But after restart the system hangs again in the iniramfs ... how can it be changed permanently ?
 
Top