[GH-ISSUE #36] Script worked apparently but system was not reinstalled #3

New issue

Open

opened 2026-03-07 19:09:16 +03:00 by kerem · 1 comment

kerem commented

2026-03-07 19:09:16 +03:00

Owner

Originally created by @Bigsausage64 on GitHub (Feb 21, 2026).
Original GitHub issue: https://github.com/007revad/Synology_DSM_reinstall/issues/36

Hi,

Suddenly my DSM wasn't able to start multiple packages (it has been running OK for months if not for years.....). Repair was not working, uninstall and reinstall was not working. I even tried to udpate DSM to the latest 7.3.2, it did nothing.

So I decided to try to reset mode 2 my unit. I never heard the 3 bips and while looking for some help, I stumbled upon your script.

I gave it a go (through SSH), it worked exactly as described. I manually installed the latest version (the 7.3.2 I tried to update with) and everything went smoothly.

When I logged back in, my system was showing exactly the same problems, nothing was fixed. Is it possible that your script was unable to reinstall/repair the DSM OS ? and if so, what are my options ? I'm still stuck with a non functional system that won't reset.

Thanks for your help

Originally created by @Bigsausage64 on GitHub (Feb 21, 2026). Original GitHub issue: https://github.com/007revad/Synology_DSM_reinstall/issues/36 Hi, Suddenly my DSM wasn't able to start multiple packages (it has been running OK for months if not for years.....). Repair was not working, uninstall and reinstall was not working. I even tried to udpate DSM to the latest 7.3.2, it did nothing. So I decided to try to reset mode 2 my unit. I never heard the 3 bips and while looking for some help, I stumbled upon your script. I gave it a go (through SSH), it worked exactly as described. I manually installed the latest version (the 7.3.2 I tried to update with) and everything went smoothly. When I logged back in, my system was showing exactly the same problems, nothing was fixed. Is it possible that your script was unable to reinstall/repair the DSM OS ? and if so, what are my options ? I'm still stuck with a non functional system that won't reset. Thanks for your help

kerem commented

2026-03-07 19:09:17 +03:00

Author

Owner

@007revad commented on GitHub (Feb 22, 2026):

The script only allows you to reinstall DSM, so it's the same result as upgrading to a newer version of DSM.

Have you tried uninstalling then reinstalling the affected packages?

Assuming you have backed up your data, and package settings, and exported to the DSM settings, you can delete the volume then create a new volume and restore your data and package settings from the backup.

If that doesn't fix those packages you can try via SSH. This is the same as the mode 1 reset:

sudo synodsdefault --reset-config

If that doesn't fix it try this. It is the same as the mode 2 reset:

sudo synodsdefault --reinstall

This will allow you to to do a clean installation of DSM without losing your data.

@007revad commented on GitHub (Feb 22, 2026): The script only allows you to reinstall DSM, so it's the same result as upgrading to a newer version of DSM. Have you tried uninstalling then reinstalling the affected packages? Assuming you have backed up your data, and package settings, and exported to the DSM settings, you can delete the volume then create a new volume and restore your data and package settings from the backup. If that doesn't fix those packages you can try via SSH. This is the same as the mode 1 reset: ``` sudo synodsdefault --reset-config ``` If that doesn't fix it try this. It is the same as the mode 2 reset: ``` sudo synodsdefault --reinstall ``` This will allow you to to do a clean installation of DSM without losing your data.