New HW, same zvol [solved]

[graylion]

I find myself in the situation that I need to put a new mobo into my TrueNAS Scale. Given that I am (perforce) moving from AMD to Intel this presumably means a new installation. Is it as simple as doing a backup of the config, swapping out HW, installing Truenas, and restoring config to have everything back, including zvol?

 

[Ericloewe]

I'll point you to the concise documentation on this subject: https://www.truenas.com/community/resources/moving-truenas-to-new-hardware.89/

 

[Davvo]

Why would going from AMD to Intel require a new install?

 

[graylion]

Why would going from AMD to Intel require a new install?

I have had this issue with Linux.

 

[graylion]

further question: do zvol disks have opinions on which SATA port they need to be on?

 

[NugentS]

further question: do zvol disks have opinions on which SATA port they need to be on?

No

 

[HoneyBadger]

I have had this issue with Linux.

Generally speaking, this problem has been mostly abstracted away by the appliance-like nature of TrueNAS - there's no install-time options to configure/compile for Intel vs AMD, it will just load what's needed on boot. What may be necessary is reconfiguring your network settings (or maybe just changing cables) depending on how the network cards map to the slot/port topology in Linux.

further question: do zvol disks have opinions on which SATA port they need to be on?

Provided that all disks are present, and the storage controller is supported, ZFS doesn't tend to care which port they're connected to. With that said, zvols are usually created as a sub-element of a pool - if you've created one that's actually mapping the extent to a single physical disk (can you even do that any more?) as a legacy export, it might experience "undefined behavior."

 

[graylion]

Thanks folks!