Paravirtual
Dabbler
- Joined
- Nov 8, 2020
- Messages
- 13
This question is partly an extension of two other topics but differs from each slightly that I didn't just want to tack it onto the end of either of those.
The first being Patrick Hausen's Guide on How to Install to just a smaller Partition on SSD (instead of using the entire disk) - https://www.ixsystems.com/community...sds-for-boot-pool-and-data.81409/#post-590563
and the second being ClinderW's question as to why this doesn't appear to work anymore (which comes down to mismatched ashift between USB and SSD) - https://www.truenas.com/community/t...-attach-to-mirrors-and-top-level-disks.89276/
So I've done a basic install to USB, but want to transfer this to a mirror vdev on SSDs but I want the ashift to be set to 12 instead of 9. Attaching SSD to the exist boot-pool to create a mirror vdev with the USB device da0p2 works but the ashift will be set to 9 (and maybe this doesn't even matter but I've yet to give up and accept it this way)
So,
I snapshotted the entirety of boot-pool,
Created a partition layout on a pair of 120GB SSDs that matched (for the first two partitions) the layout of the USB disk containing boot-pool
Created a new zpool called "boot-poolA" with mirror vdev of the SSD's 2nd Partitions (using gptid) with ashift=12
Used zfs send / zfs receive to copy the boot-pool snapshot (and all underlying datasets) to boot-poolA
Used dd to copy the da0p1 freebsd-boot partition (512K) to the corresponding 1st partitions on each of the two SSDs
but at this point the boot-pool I want to used has the "wrong name" so I tried (and apparently failed) to fix this by,
Booting the TrueNAS Installer stick, and selecting console
Importing boot-poolA as boot-pool
Exporting it again
Rebooting, removing all USB sticks and ensure SSDs were 1st boot device in BIOS
It didn't work.
I feel I must be close but don't understand quite how to set it to try and boot using this new pool that exists on the SSDs. It has the right label/name, but I'm guessing there's more to it, than that.
FWIW, The system is an HP Microserver N36L and boots BIOS, not UEFI.
I've no data on it yet so no risk of harm by getting something wrong at this stage.
Having rebooted via the USB stick that system is installed to, I can see this;
Can anyone help me get this other boot-pool as the main bootable system pool?
The first being Patrick Hausen's Guide on How to Install to just a smaller Partition on SSD (instead of using the entire disk) - https://www.ixsystems.com/community...sds-for-boot-pool-and-data.81409/#post-590563
and the second being ClinderW's question as to why this doesn't appear to work anymore (which comes down to mismatched ashift between USB and SSD) - https://www.truenas.com/community/t...-attach-to-mirrors-and-top-level-disks.89276/
So I've done a basic install to USB, but want to transfer this to a mirror vdev on SSDs but I want the ashift to be set to 12 instead of 9. Attaching SSD to the exist boot-pool to create a mirror vdev with the USB device da0p2 works but the ashift will be set to 9 (and maybe this doesn't even matter but I've yet to give up and accept it this way)
So,
I snapshotted the entirety of boot-pool,
Created a partition layout on a pair of 120GB SSDs that matched (for the first two partitions) the layout of the USB disk containing boot-pool
Created a new zpool called "boot-poolA" with mirror vdev of the SSD's 2nd Partitions (using gptid) with ashift=12
Used zfs send / zfs receive to copy the boot-pool snapshot (and all underlying datasets) to boot-poolA
Used dd to copy the da0p1 freebsd-boot partition (512K) to the corresponding 1st partitions on each of the two SSDs
but at this point the boot-pool I want to used has the "wrong name" so I tried (and apparently failed) to fix this by,
Booting the TrueNAS Installer stick, and selecting console
Importing boot-poolA as boot-pool
Exporting it again
Rebooting, removing all USB sticks and ensure SSDs were 1st boot device in BIOS
It didn't work.
I feel I must be close but don't understand quite how to set it to try and boot using this new pool that exists on the SSDs. It has the right label/name, but I'm guessing there's more to it, than that.
FWIW, The system is an HP Microserver N36L and boots BIOS, not UEFI.
I've no data on it yet so no risk of harm by getting something wrong at this stage.
Having rebooted via the USB stick that system is installed to, I can see this;
Code:
Warning: settings changed through the CLI are not written to the configuration database and will be reset on reboot. root@alexandria[~]# zpool status pool: boot-pool state: ONLINE scan: resilvered 1.19G in 00:01:21 with 0 errors on Tue Dec 29 16:06:56 2020 config: NAME STATE READ WRITE CKSUM boot-pool ONLINE 0 0 0 gptid/03b5202b-70ab-11bd-b287-3cd92b0c2433 ONLINE 0 0 0 errors: No known data errors root@alexandria[~]# zpool import pool: boot-pool id: 17078519315175409940 state: ONLINE action: The pool can be imported using its name or numeric identifier. config: boot-pool ONLINE mirror-0 ONLINE gptid/579a1b25-4843-11eb-8109-3cd92b0c2433 ONLINE gptid/4257c2cc-4845-11eb-8109-3cd92b0c2433 ONLINE
Can anyone help me get this other boot-pool as the main bootable system pool?