Please refer to this FAQ:
Fantastic, thank you! I’ll be giving this a try in the next couple of days and I’ll share back how it goes.
Question @SteveKo - will this work if my TS-451 isn’t using a storage pool? It’s a legacy volume.
What about booting the 464 with your 451+ array making sure that boots fine then load the 451+ with old drives and reset it.
With the 451 reset, build your staging array on the 451+ and make sure the data gets on it uncorrupted.
Then pull the RAID5 drives and load m.2s in the 464.
Note: you can think about QuTS since you will be starting from scratch.
Get the 464 running on m.2s and hot swap the raid5 drives and initialise them.
Or maybe it lets you import. You would need to figure out nuking the system array if you don’t initialise.
As everyone said, the RAID0 staging array is a time bomb, try to avoid doing it.
But if you’re going to do it, I wouldn’t move it once it’s up a running.
Hence, I vote build it on the 451.
Edit: You want the same QTS version on both machines when you move the RAID5 disks.
If you want the M.2 drives to be the system drives and you want to reuse your 451 drives, then AFAIK, the only way to do this would be to save the 451 data to an external drive. Start the new NAS and when in guided setup, choose to completely initialize everything. You will need to start from scratch basically.
Then copy your old data back. It takes a long time to do it all. I’ve done it at least twice.
Updating for everyone – took a min to get all of the hardware (ordered the wrong drives initially), but just got my new TS-464 set up following the guide that @SteveKo shared above.
- Installed my NVMe drives.
- Went through initial QNAP setup, configured NVMe drives’ data volume as RAID1 (mirrored). I named it DataVol0 just in case since my old system used DataVol1 and didn’t want to have a naming conflict (don’t know if this would have happened).
- Upgraded firmware to be equal or higher than what my TS-451+ was running.
- Shut down both QNAP systems.
- Moved HDD drives from TS-451+ in the same order over to the TS-464.
- Powered up the TS-464.
- Used the Recover > Attach process outlined in the guide.
And everything just worked! My new NVMe drives are the system volume, and it found all the existing shares from the previous data volume as well.
Hope this helps others.
1 Like
Good for you! Amazing what happens when instructions get followed! 
Thank you for reporting back and for posting these instructions. I am sure you will save someone else some grief! Nice work!
1 Like
The internal system label and the designated volume name are not the same, you cannot touch the internal name from the GUI
1 Like
A post was split to a new topic: Single NVMe as System Drive