Migration from DSM 6.2.3 918+ (Jun's Loader) to DSM 7.2.2 SA6400 (Arc Loader)

[ed_co]

Hello guys,

 

It is being a while (I had already an old thread more than a year ago about it, but I wanted to start clean not following the old thread as many things may changed since), and now that it looks like the DSM 7 is very mature and stable, I finally decided is safe enough to do the Migration from DSM 6.2.3 Jun's Loader v1.04b with 918+ to DSM 7.2.2 ARC Loader SA6400.

 

My current system (updated from an original system H370M-ITX/i7 8700/Marvell 88SE9215 as it died) :

- Asrock H610M-ITX/AC (4 SATA, 1 x NIC: i219V)
- i5 12400

- 32GB DDR4 RAM

- ASM1166 M.2 NVME PCIE 6 Port Sata (using 4 SATA ports currently)

- 8x 8Tb disks (at 61% utilisation)

 

What do you think is the best way to go as I wanna migrate the data on the disks?

 

There are 2 aspects to consider:

- Changing to version. I guess direct from 6.2.3 update 3 to 7.2.2 update 3 maybe is quite hardcore.

- Changing platform. From DS918+ to SA6400.

 

Should I do it incrementally as Synology states currently? 6.2.3-25426 --> 6.2.4-25556 --> 7.0.1-42218  --> 7.2.2-72806 --> 7.2.2-72806 Update 3

I guess the 6.2.4/7.0.1 are not an option for ARC, but what about something like 6.2.3 --> 7.1.1 --> 7.2.2? Would be better than 6.2.3 --> 7.2.2?

 

Apart from that I guess I shouldn't jump from DS918+ straight to the SA6400, I guess. So maybe I should reach 7.2.2 first with the same DS918+?

 

What perplexity.ai suggested was:

Quote

 

Practical Migration Steps Suggestion

1) Backup all important data externally.

2) Create a bootable USB with Arc Loader emulating DS918+ first.

3) Boot and upgrade DSM incrementally from 6.2.3 to 7.2.1 using Synology’s official update path. (I guess can't be done, ARC Loader does NOT support the in between versions)

4) Once upgraded to DSM 7.x and stable, switch the Arc Loader USB to SA6400 model and boot.

5) Verify system stability, hardware compatibility, and data integrity.

6) If all is stable, continue using SA6400 loader for better hardware support and features.

 

 

So what I get from all this info, doing something like this?

- 6.2.3 918+ --> 7.1.1 918+

- 7.1.1 918+--> 7.2.2 918+

- 7.2.2 918+--> 7.2.2 SA6400

What do you think?

 

Does anyone have experience on this? Any suggestions/paths?

 

Thank you very much,

 

E.

Edited May 9 by ed_co

[Peter Suh]

First update to 7.2.2 on the DS918+.

After that, you can change it once more by model migration (DS918+ -> SA6400).

There is no need to update the DSM version sequentially.

[ed_co]

1 hour ago, Peter Suh said:

First update to 7.2.2 on the DS918+.

After that, you can change it once more by model migration (DS918+ -> SA6400).

 

Sounds reasonable for sure.

 

1 hour ago, Peter Suh said:

There is no need to update the DSM version sequentially.

 

Are you sure? I am a little bit worried about this, again perplexity.ai stated:

 

Quote

Direct Migration Risks:
Many users and experts advise caution when upgrading directly from DSM 6.2.x (with Jun's loader) to DSM 7.x. This is because DSM 7 changes partition layouts and system structures, which can cause issues if the migration is not clean or properly staged.

 

Thanks Peter! Is not that I don't trust you, as you are a big fish here. I am just a little bit scared of losing my data.

 

Please, I invite other people with experience (like @polanskiman or any other) in the matter to comment any point of view! Don't wanna lose my data here. Thank you guys

Edited May 9 by ed_co

[Peter Suh]

7 hours ago, ed_co said:

 

Sounds reasonable for sure.

 

 

Are you sure? I am a little bit worried about this, again perplexity.ai stated:

 

 

Thanks Peter! Is not that I don't trust you, as you are a big fish here. I am just a little bit scared of losing my data.

 

Please, I invite other people with experience (like @polanskiman or any other) in the matter to comment any point of view! Don't wanna lose my data here. Thank you guys

 

 

As you said, there was one time when the system partition size changed in DSM 7.

I think it was when it changed from 7.1.x to 7.2.0. Since you are planning to migrate multiple times,

it is not a bad idea to check that the system partition /dev/md0 has enough free space.

 

 

 

There was a case in the past when Synology did not use this space smartly.

This space is temporarily where the package for dsm update stays.

 

Since arc has copied most of the functions that rr initially implemented,

it may also have a system partition cleaning function. As the developer of mshell,

I do not have the capacity to understand the functions of other loaders.

Edited May 10 by Peter Suh

[ed_co]

2 hours ago, Peter Suh said:

 

 

As you said, there was one time when the system partition size changed in DSM 7.

I think it was when it changed from 7.1.x to 7.2.0. Since you are planning to migrate multiple times,

it is not a bad idea to check that the system partition /dev/md0 has enough free space.

 

 

 

There was a case in the past when Synology did not use this space smartly.

This space is temporarily where the package for dsm update stays.

 

Since arc has copied most of the functions that rr initially implemented,

it may also have a system partition cleaning function. As the developer of mshell,

I do not have the capacity to understand the functions of other loaders.

 

I have no idea what you are talking about right now. I don't know what is /dev/md0, and the two pictures you sent me. I don't know how to get that info, and when to request the info.

[ed_co]

What happened to me this evening was very weird.

I was doing my homework and tried to experiment with Arc Loader 2.2.7 before installing in the real disks.

 

So:

- I removed my 8 disks (is easy, as I have trays) and my Jun's loader USB.

- I added a couple of old disks to do some testing.

- I created a Arc Loader USB.

- I boot the Arc Loader USB, configured the loader to DSM 7.2.2 with DS918+, then built and boot the loader. I was able to install (online) DSM 7.2.2 DS918+ to disks and run it.

- Play a little with it. With no issues.

- Then I boot the Arc Loader and configured the loader to DSM 7.2.2 with SA6400, built and boot the loader again. I was able to migrate to SA6400 with no problems.

- Play a little with it. With no issues.

- I didn't register my hardware ID with Discord.

 

I was so happy, and impress how well the Arc Loader was and I was like: I should do it before. So straight forward and easy!!

 

Had a picture when I run it for the first time (before migrating to SA6400):

 

 

Then I stopped for having dinner and rest for a while before trying with the real disks.

 

Then came back:

- Then I connected the 8 original disks back.

- Unplug the Arc Loader USB, and connect the Jun's Loader.

- Tested the original system (DSM 6.2.3 with Jun's Loader), just in case. Still works properly.

- Then shut down the server.

- Recreated the Arc Loader USB from scratch again with Balena Etcher (as it was configured to SA6400), and wanna start clean.

- And tried to load it and build it once again with DS918+ 7.2.2. And... The DISASTER

 

Now TONS of problems with the loader:

* After loading it, when I select the platform I want (918+), and select the version I want (7.2), it does not offer me to build it and continue with the process!!! Tried with 7.1 and 7.0 (just in case the version), same problem.

* Build option does not appear in the menu after selecting the platform.

* I tried with SA6400 and does not work either.

* Tried different platforms and DSM versions. The only one that looks it works is DS920+ (is DT, but SA6400 is DT too and does not work). With DS920+, I can be able to keep with the normal process. The ones I wanted -and used before- failed...

* Recreated the Arc Loader USB, nothing. Tried with another USB drive too. Same thing. Another, same thing again.

* I was thinking, maybe something happened to the disk or the computer. So, I removed the 8 disks again, and use my previous 2 old test disks again, with no luck. It behaves the same way. Is like the Loader does not work well anymore. AND IT WAS WORKING PERFECT FOR ME BEFORE!!!

* The 8 disks and the computer are fine, I can run my DSM 6.2.3 DS918+ with Jun's loader USB. No change whatsoever, still works well.

* Don't know WTF is happening. I was even thinking that maybe is something that could happen in a server as the USB requires online connection and does stuff through internet?

* Tried tons of things...

* The script errors out trying to change to Easy UI, like not finding some commands... (I tried tons of stuff with no luck).

 

 

I just hope is not related with registering my hardware ID with Discord (being banned or something? I hope not).

 

Is 5:14 am, I am tired and I feel so frustrated and I don't understand anything. So disappointed. It was from HEAVEN with zero problems, to HELL. It does not make any sense to me.

 

Don't know what to do next, I would appreciate some help. But first, will try to sleep. Hopefully, I could have better news tomorrow.

 

Thanks

 

 

[Peter Suh]

4 hours ago, ed_co said:

What happened to me this evening was very weird.

I was doing my homework and tried to experiment with Arc Loader 2.2.7 before installing in the real disks.

 

So:

- I removed my 8 disks (is easy, as I have trays) and my Jun's loader USB.

- I added a couple of old disks to do some testing.

- I created a Arc Loader USB.

- I boot the Arc Loader USB, configured the loader to DSM 7.2.2 with DS918+, then built and boot the loader. I was able to install (online) DSM 7.2.2 DS918+ to disks and run it.

- Play a little with it. With no issues.

- Then I boot the Arc Loader and configured the loader to DSM 7.2.2 with SA6400, built and boot the loader again. I was able to migrate to SA6400 with no problems.

- Play a little with it. With no issues.

- I didn't register my hardware ID with Discord.

 

I was so happy, and impress how well the Arc Loader was and I was like: I should do it before. So straight forward and easy!!

 

Had a picture when I run it for the first time (before migrating to SA6400):

 

Then I stopped for having dinner and rest for a while before trying with the real disks.

 

Then came back:

- Then I connected the 8 original disks back.

- Unplug the Arc Loader USB, and connect the Jun's Loader.

- Tested the original system (DSM 6.2.3 with Jun's Loader), just in case. Still works properly.

- Then shut down the server.

- Recreated the Arc Loader USB from scratch again with Balena Etcher (as it was configured to SA6400), and wanna start clean.

- And tried to load it and build it once again with DS918+ 7.2.2. And... The DISASTER

 

Now TONS of problems with the loader:

* After loading it, when I select the platform I want (918+), and select the version I want (7.2), it does not offer me to build it and continue with the process!!! Tried with 7.1 and 7.0 (just in case the version), same problem.

* Build option does not appear in the menu after selecting the platform.

* I tried with SA6400 and does not work either.

* Tried different platforms and DSM versions. The only one that looks it works is DS920+ (is DT, but SA6400 is DT too and does not work). With DS920+, I can be able to keep with the normal process. The ones I wanted -and used before- failed...

* Recreated the Arc Loader USB, nothing. Tried with another USB drive too. Same thing. Another, same thing again.

* I was thinking, maybe something happened to the disk or the computer. So, I removed the 8 disks again, and use my previous 2 old test disks again, with no luck. It behaves the same way. Is like the Loader does not work well anymore. AND IT WAS WORKING PERFECT FOR ME BEFORE!!!

* The 8 disks and the computer are fine, I can run my DSM 6.2.3 DS918+ with Jun's loader USB. No change whatsoever, still works well.

* Don't know WTF is happening. I was even thinking that maybe is something that could happen in a server as the USB requires online connection and does stuff through internet?

* Tried tons of things...

* The script errors out trying to change to Easy UI, like not finding some commands... (I tried tons of stuff with no luck).

 

I just hope is not related with registering my hardware ID with Discord (being banned or something? I hope not).

 

Is 5:14 am, I am tired and I feel so frustrated and I don't understand anything. So disappointed. It was from HEAVEN with zero problems, to HELL. It does not make any sense to me.

 

Don't know what to do next, I would appreciate some help. But first, will try to sleep. Hopefully, I could have better news tomorrow.

 

Thanks

 

 

 

I know there are a lot of Russian users actively using ARC in the community.

Although there are limitations of having to use a Russian translator,

why don't you ask about your situation where you want to migrate from DSM 6.2.3 DS918+ to DSM 7.2.2 SA6400?

 

[ed_co]

Today, I wanted to start again with energy and try to make it work.

 

I turned on my server with no change in the Arc Loader USB, and load it, and SURPRISE!! It worked as before, with no problems. So I quickly disconnected the old test disks and connect my 8x 8Tb disks.

 

I made the process EXACTLY like I did in the tests before, with NO hassle whatsoever: Easy as butter

 

What I learned from this, after wasting hours and hours??? NOTHING AT ALL!!

I have no idea WTF happened. I guess was a problem in the servers Arc uses for doing whatever. The bad thing was the lack of error handling, which was totally misleading.

 

If someone is curious about my path route, this is what I did:

6.2.3-25426 DS918+ --> 7.0.1-42218 DS918+ --> 7.2.2-72806 DS918+

7.2.2-72806 DS918+ --> 7.2.2-72806 DS6400+

I read a lot and the safest way was doing first 7.0.1 because from DSM 6.2 to DSM 7.0 there are a lot of changes, and to scale it properly Synology advices that, so I did it.

 

But why no doing it directly from 6.2.3 to 7.2.2? Well probably you can, but I didn't take that risk, as I thought it was risky enough. What was clear is I wouldn't do DS918+ to SA6400 straight away, changing platform is better when you have already the last update in place with your old platform, and then perform the migration seamlessly.

 

After performing successfully the full 6.2.3 DS918+ to 7.2.2 SA6400, I updated some packages and stuff in DSM.

 

For the moment, everything seems alright. I see no problems (knock on wood), so I consider a success (again, for the moment).

 

 

 

 

 

I documented this here for anyone wanting to do something similar. Enjoy!