I've got a custom built NAS with x3 NVME SSD's and I'd like to physically install and migrate my Unraid server to the new PC. Its currently running my plex server

How transportable is my Unraid server? Ideally I'd like to take the Nvme's, pop them into the new PC, plug in the Unraid USB key and off I go... but I suspect it won't be that easy.

Any advice on doing this is appreciated

as long as all disk and the usb in on the new machine. all data and the array should be there and transferable. you may have some issues with device pathing and docker locatoins.

its more geting driver and other plugins fixed for the transfer.

I recoeemnd temp disabling any and all vms, any and all dockers and turn autostart of the array off.

then add all the nvme disk and the unraid usb into the new machine.

launch unraid and get resetup. you should see your disk (pathing may have chnged but as long as you match the corect disk to the corect disk onteh new then start the array all data will be the same and in the same location.

then sloly start systems enable vms tunr on vm fixing any issues along the way same with dockers.

I've have moved a unraid USB between 5-10 different machihes and was able to migrate cahnge disk and move things with the same unraid system and license. It is possble but there are some pre cautions.

step 1 always make a unraid backup file!

Main > Flash > backup

step 2 disable any and all autostarts.
any docker set to auto start, and server set to autostart.

new hardware new devcie paths and some configuratrion chagnes may be needed...
(especal if changining process aritypes ie amd to intel and vise versa)

step 2 bakup things with the appdata backup plugin to keep any dockers and its configurations this way we have a restore point if something fails.

step 3 record what disk is at what slot look for disk identifiers such as device seral numbers.

step 4 turn off / uninstall any and all drive plugins intel top, nvdia, etc this is due to new kerneal load and you may or may not need the plugin or the plugin drivers can cause other issues.

step 5 if vm and you have things bind for passign to a VM. Disalbe and remove all binds!
8as lspci and devcies may not be at the same area/device path on new hardware...

this sets it up with exisitn gdata form the other hrad drives while mainting usb data for dockers, samba shares and orgianl array path of disks.

sometimes the new config is needed whihc is why you need documentation of waht disk is what int he unrad disk array/pool and to turn off auto staart as new system may not see all disk nor all disk may not be at simlar device paths. ie /dev/sdb and sda are now switched.

then going though the log and fising the array maping th ecorect disk where they were, and eanbleing and chaing data paths.

Thanks.

I did it the other day, shutting everything down (VMS, Docker, etc...)... worked great but I did make one mistake... I didn't have space for my 2.5in SSD which was my cache device, so had to cock around with it a bit but all is working great now.