Back up synoboot after each DSM update so you can recover from a corrupt USBDOM or EEPROM

[dil88]

Very interesting, thanks for the insides and details. I could reproduce what you are describing.

DS423+

cat /proc/sys/kernel/syno_hw_version
DS423+

"synogetkeyvalue /etc/synoinfo.conf pushservice_dsserial" delivers the serial-number as does "cat /proc/sys/kernel/syno_serial" etc.

DS214+

cat /proc/sys/kernel/syno_hw_version
DS214+-j

ls /dev | grep -E 'syno|boot'
synobios

cat /dev/mtd
cat: /dev/mtd: No such file or directory

dmidecode -s system-serial-number
-ash: dmidecode: command not found

There are /dev/mtd0, /dev/mtd1, ... but these output some binary stuff. "synogetkeyvalue /etc/synoinfo.conf pushservice_dsserial" delivers the serial-number as does "cat /proc/sys/kernel/syno_serial"

 

[Stationary]

On some devices /proc/cmdline contains key/value pairs for the model number, serial number, and the MAC addresse(s): e.g. syno_hw_version=DS1817+, sn=###..., macs=001132######,001132######,...
but I have read that this is not general.

 

[DaveR]

DSM mounts the USBDOM at boot as /dev/synoboot. It mounts the 2 partitions on the USBDOM as synotboot1 and synoboot2.

For those 2 and 4 bay Synology models that don't have /dev/synoboot I assume it's because the smaller, cheaper, models don't have a USBDOM.

Try "cat /proc/sys/kernel/syno_serial".
Works on 7.2.2, too...

Nice.

Does cat /proc/sys/kernel/syno_hw_version[/CODE] return the correct model?

EDIT never mind. I see you already answered this in a previous comment.

 

[Adama]

cat /proc/sys/kernel/syno_hw_version

On my DS918+ I get DS918+

On my DS420+ I get DS420+

On my DS413 I get DS413-j

 

[DaveR]

DS214+

dmidecode -s system-serial-number
-ash: dmidecode: command not found

I just remembered that my scripts don't use dmidecode because DSM 6 does not have dmidecode.

 

[dil88]

I use DSM 7.1.1 on my DS214+ and that doesn't provide dmidecode, too.

 

[Adama]

And even on 7.2.2 it's not really usable:

root@GalacticaNAS1:~# dmidecode -s system-serial-number
123456789

 

[DaveR]

I just checked DSM 7.2.1 and out of the 117 NAS models that can use DSM 7.2.1 only 87 of them have dmidecode. I don't know why that is, and I probably won't bother investigating as dmidecode is not usable for this topic.

 

[DaveR]

v1.0.1
- Bug fix for not getting the serial number in some situations.
- Bug fix for some models returning extra characters after the model.

https://github.com/007revad/Synoboot_backup/releases

I'm still trying to find how to backup the DOM or EEPROM on models that don't have /dev/synoboot (which I assume is because they don't have a USBDOM).

 

[Adama]

Maybe Thomas @TN-Notebooks can shed some light on this?

 

[EinhornAction]

Thanks for your great work!

I have a few questions regarding this script:

• Do you know which models have a USBDOM? / EEPROM? (I have a DS920+) Is it determined by the existence of the file under /dev/synoboot?
• How can you detect if the USBDOM / EEPROM is corrupted? So what is the case that this backup will be needed?
• How can you restore a backed‑up synoboot in case of a failure?