Moderator Warning: This HOWTO will damage the ability of your TrueNAS appliance to properly maintain itself, will break the ability to replace failed drives, and may cause problems with upgrades and updates. TrueNAS is not designed to do this sort of partitioning, and the developers are not interested in supporting this. You may be on your own if you do this. Further discussion of the topic is available here in this resource.
This is the SCALE version of this howto. It is very similar, the differences are due to Linux-specific commands to copy partition info and bootloader data.
I'm currently running Proxmox with a TrueNAS VM for my filer, and another couple of VMs for Docker containers, and an Unifi controller. I am very interested in SCALE because it would allow me to use a single system for all three tasks, thereby making more efficient use of resources (also, it would avoid using non-really-supported SATA passthrough from the hypervisor to the TrueNAS VM).
Since I want to improve the performance of the overall system (which also hosts a Windows VM using GPU passthrough that I'm typing this from), I wanted to see if using a mirror of Samsung 970 EVO NVMe drives for both boot and high-perf VM pool was doable with SCALE. I don't have the NVMe drives yet, so I ran this experiment with a Proxmox VM.
Assumptions:
1. You're installing onto additional, non-partitioned disks /dev/sdb and /dev/sdc. Be careful to choose the right disks! I suspect that NVMe drives will look something like /dev/nvmeXnY, based on how it looks in Proxmox VE which is also Debian-based.
2. SCALE has been installed on /dev/sda.
Now you can power off, remove your original install drive (e.g. a USB stick), make sure that your new boot drives are selected in the BIOS/UEFI and be on your merry way.
This is the SCALE version of this howto. It is very similar, the differences are due to Linux-specific commands to copy partition info and bootloader data.
I'm currently running Proxmox with a TrueNAS VM for my filer, and another couple of VMs for Docker containers, and an Unifi controller. I am very interested in SCALE because it would allow me to use a single system for all three tasks, thereby making more efficient use of resources (also, it would avoid using non-really-supported SATA passthrough from the hypervisor to the TrueNAS VM).
Since I want to improve the performance of the overall system (which also hosts a Windows VM using GPU passthrough that I'm typing this from), I wanted to see if using a mirror of Samsung 970 EVO NVMe drives for both boot and high-perf VM pool was doable with SCALE. I don't have the NVMe drives yet, so I ran this experiment with a Proxmox VM.
Assumptions:
1. You're installing onto additional, non-partitioned disks /dev/sdb and /dev/sdc. Be careful to choose the right disks! I suspect that NVMe drives will look something like /dev/nvmeXnY, based on how it looks in Proxmox VE which is also Debian-based.
2. SCALE has been installed on /dev/sda.
Code:
# Copy the partition information between disks > sfdisk -d /dev/sda | sfdisk --force /dev/sdb > sfdisk -d /dev/sda | sfdisk --force /dev/sdc # Attach the newly created partitions to the pool > zpool attach boot-pool sda3 sdb3 > zpool attach boot-pool sda3 sdc3 # Copy the boot partition > dd if=/dev/sda1 of=/dev/sdb1 > dd if=/dev/sda1 of=/dev/sdc1 # Copy the EFI partition > dd if=/dev/sda2 of=/dev/sdb2 > dd if=/dev/sda2 of=/dev/sdc2 # Install GRUB on the disks > grub-install /dev/sdb > grub-install /dev/sdc # Wait for boot-pool to resilver. I monitor with: > watch -n 5 -d zpool status boot-pool # Remove the initial install drive from the pool > zpool offline boot-pool sda3 > zpool detach boot-pool sda3
Now you can power off, remove your original install drive (e.g. a USB stick), make sure that your new boot drives are selected in the BIOS/UEFI and be on your merry way.
Last edited by a moderator: