tomoki Posted June 2, 2022 #1 Posted June 2, 2022 I am using N54L with DSM 6.2.3 and recently i try to upgrade to DSM 7. However i got a recover loop after the ds3615xs_42218 / 42661.pat has been uploaded. Does any one can help me? Quote
2 renegadeBE Posted June 8, 2022 #2 Posted June 8, 2022 1. BOOT TO TINYCORE 2. EXECUTE FOLLOW COMMANDS ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh backup sudo su ./rploader.sh postupdate bromolow-7.0.1-42218 (WARNING : if update is detect, confirm with "Y" fur use this. reboot 3. BOOT NORMAL MOD (USB) Decompressing Linux... Parsing ELF... done. Booting the kernel. 4. Go to DSM 1 Quote
0 Peter Suh Posted June 2, 2022 #3 Posted June 2, 2022 (edited) It looks like your USB stick's bootloader is still stuck at 7.0.1-42218. Rebuild the 7.1.0-42661 bootloader and use it. However, do not change S/N Edited June 2, 2022 by Peter Suh Quote
0 tomoki Posted June 2, 2022 Author #4 Posted June 2, 2022 omg!!! i have already flashed my USB. what should i do? Quote
0 flyride Posted June 2, 2022 #5 Posted June 2, 2022 If you change your SN it will just require a Migration. Not to worry. Quote
0 Peter Suh Posted June 3, 2022 #6 Posted June 3, 2022 If the OLD S/N is not the source Synology used to synchronize the shared folder, there will be no problem. In shared folder synchronization, S/N becomes the standard for recognizing each other. If it is changed, you can start syncing again from the beginning, but it will be very painful. Quote
0 tomoki Posted June 3, 2022 Author #7 Posted June 3, 2022 /Thx for your great support Peter. However, seems the problem that I facing right now is not that simple. first I use redpill to build the loader USB, however after finishing the tinycore steps, I found that it kept reboot after the kernel was loaded. the BIOS is then reflashed (the bay one, v. 041) and the DMS is successfully loaded and found by find.synology.com. and the nightmare is that come after the first reboot, the system keep saying that my HDD needs to recover. the recover is very fast (from 0-4% only few secs, then jump to 100%) and then start recover loop. I tried to pull out all my HDD and start the machine with a new HDD, but this loop is still occurred. what a nightmare. 😭😭😭😭😭😭😭😭 Quote
0 billat29 Posted June 8, 2022 #8 Posted June 8, 2022 While I was testing upgrades, I got into this recovery loop. Looking at the logs. what seemed to be happening was that it was trying to download something to do the recovery and not finding it. I think that redpill by design blocks Synology and so this, I thought, could be the problem. In my case, as I was testing, I gave up and started again. What you might do is follow flyride's troubleshooting instructions in their tutorial to try and post what you find Quote
0 flyride Posted June 8, 2022 #9 Posted June 8, 2022 I just added a note in the installation tutorial. For a migration install only, DSM will reset the Manual Update option to Automatic. It tells you this during the migration install. Unfortunately that means it can download an incompatible update and apply it before you can do anything. At minimum, go into Control Panel and change the setting ASAP. Alternatively you may want to disconnect your Internet when you see the notification and leave it offline until you can get to the setting in Control Panel. If someone knows the configuration file options that force the Manual Update setting maybe we can get the loader to address this for migrations. Quote
0 flyride Posted June 8, 2022 #10 Posted June 8, 2022 On 6/2/2022 at 9:34 PM, tomoki said: I tried to pull out all my HDD and start the machine with a new HDD, but this loop is still occurred. what a nightmare. 😭😭😭😭😭😭😭😭 I think the postupdate feature will fix this. Quote
0 Ahmandonk Posted August 24, 2022 #11 Posted August 24, 2022 On 6/9/2022 at 4:41 AM, renegadeBE said: 1. BOOT TO TINYCORE 2. EXECUTE FOLLOW COMMANDS ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh backup sudo su ./rploader.sh postupdate bromolow-7.0.1-42218 (WARNING : if update is detect, confirm with "Y" fur use this. reboot 3. BOOT NORMAL MOD (USB) Decompressing Linux... Parsing ELF... done. Booting the kernel. 4. Go to DSM Thank you!!! i got same problem... and now resolved! Quote
Question
tomoki
I am using N54L with DSM 6.2.3 and recently i try to upgrade to DSM 7. However i got a recover loop after the ds3615xs_42218 / 42661.pat has been uploaded. Does any one can help me?
10 answers to this question
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.