Back up synoboot after each DSM update so you can recover from a corrupt USBDOM
For Synology models that have a USBDOM only.
When you run the script, either via SSH or Task Scheduler, it backs up synoboot to the path you set at the top of the script.
It backs up synoboot, as well as synoboot1 and synoboot2.
It only creates a new backup if there are no backups with the same filename. So it will only create backups on the first run and after a DSM update.
The backup filenames include:
- The Synology model.
- The Synology's serial number.
- synoboot or synoboot1 or synoboot2.
- The DSM version.
1 and 2 are needed so you don't accidentially try to recover a corrupted USBDOM or EEPROM with the wrong image file (in case you have more than one Synology, or migrate the drives to a new Synology).
- Download the latest version Source code (zip) from https://github.com/007revad/Synoboot_backup/releases
- Save the download zip file to a folder on the Synology.
- Unzip the zip file.
Schedule the script to run at bootup to automatically create new backups after each DMS update.
See How to run from task scheduler
How to enable SSH and login to DSM via SSH
sudo -s /volume1/scripts/synoboot_backup.shNote: Replace /volume1/scripts/ with the path to where the script is located.
If the script won't run check the following:
- Make sure you download the zip file and unzipped it to a folder on your Synology (not on your computer).
- If the path to the script contains any spaces you need to enclose the path/scriptname in double quotes:
sudo -s "/volume1/my scripts/synoboot_backup.sh" - Make sure you unpacked the zip or rar file that you downloaded and are trying to run the synoboot_backup.sh file.
- Set the script file as executable:
sudo chmod +x "/volume1/scripts/synoboot_backup.sh"
Backing up synoboot
synoboot already backed up for this NAS and DSM version
