denmalley Posted October 13, 2023 Share #1 Posted October 13, 2023 I've been using xpenology for about 6 years now, started out on a Dell T30 baremetal using jun's loader (let's call it server 1). With the build starting to age, and disks reaching capacity, I thought it would be a good time to get a fresh set of disks. This old build has 2 RAID1 pairs of 8TB HDDs. Around December of last year I started to consider upgrade options. Since I had a running server, I felt the best path was to create a new build on different hardware so I'd be able to just fall back to server 1 if things went wrong. I also saw that there were now methods becoming prevalent for loading the newer 7.x software. Since I had acquired 2 14TB and 2 8TB disks I though I'd try out SHR to take advantage of the extra capacity that it affords. I dug out an old PC and used ARPL to create a new loader and used migration assistant to attain all the data from server 1. So now server 2 is running DSM 7.1.1-42962 Update 2. Server 1 has been shut down for a while. Server 2 is running fine, but has 8GB of RAM where Server 1 has 16TB ECC RAM. I'd now like to move my disks back to the Server 1 but I'm unsure of the best way to go about it. I've read up on the importance of disk order with RAID builds and migration, so I think I have the correct order of disks documented and can handle that part fine. I'd like to be able to create a build with the latest version of DSM available on the new loader for server1. I was hoping to just reinitialize the 8TB disks in that machine with a new raid config (probably SHR as well) so I can migrate them to server 2 to use as a backup. My question is, once I set up Server 1 with a new loader, what will happen when I insert the disks from server 2 into this machine? What will happen when I insert disks from a machine running an older version of DSM? Should I rebuild the loader and upgrade server 2 to the newest DSM version before migrating the disks? Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted October 13, 2023 Share #2 Posted October 13, 2023 If possible, the disk DSM version used should be less than or equal to the target DSM version, and in the case of storage pools, it is recommended that the same sequence numbers not overlap. If the above conditions are met, you can proceed with disk assembly. 1 Quote Link to comment Share on other sites More sharing options...
denmalley Posted October 14, 2023 Author Share #3 Posted October 14, 2023 Thanks for the reply! Can you clarify this point? Quote in the case of storage pools, it is recommended that the same sequence numbers not overlap Quote Link to comment Share on other sites More sharing options...
denmalley Posted October 16, 2023 Author Share #4 Posted October 16, 2023 If I had to guess I think this means for example not having a storage pool with disks in bay1,2,4 while having another in bays 3,5,6. With that disk 3 of vol 2 in the middle of the sequence for vol 1 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted October 26, 2023 Share #5 Posted October 26, 2023 On 10/15/2023 at 4:00 AM, denmalley said: Thanks for the reply! Can you clarify this point? It's simple. Storage Pool 1 (NAS1) -> Storage Pool 1 (NAS2) This means that it is good if the same storage pool 1 is not duplicated. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.