General Disclaimer on Modifying the Synology Server

[Pawlu]

Note: at the time that this was disclaimer was written, if you brick your system while modifying it, it may be possible to restore system functionality by performing a clean install of the Synology product

Does the above quote mean that you could corrupt/brick your system to the point of not being able to perform a reinstall of the synology product?
The OS is commonly called firmware, however I find this confusing, firmware is code that works directly with hardware and is typically read only and resides on a chip. The OS on the NAS units is not really firmware its a custom linux distro that runs off the hard drive. Do Synology NAS units, in my case the 207+ contain a chip with true firmware that cannot be damaged by use of CLI?

[Franklin]

Greetings Pawlu

There is an EEPROM on the Synology Hardware, and if this EEPROM is damaged by improper manipulation of the CLI, it will brick the unit. I have already seen this done already in the USA and once in Europe, so you have been warned. How these users did this is not known, I just know it's possible.

Most of the time, most users who brick their system only damage the OS on the HDD (where a clean install or deleting all partitions of the HDD will restore factory functionality); it is still possible (but unlikely/difficult) to affect the EEPROM of the Synology system; where it will never boot.

Hope this helps, have a Happy New Year.

[Pawlu]

Thank you Franklin, appreciate your response. I'm assuming the EEPROM code is reponsible for functions such as putting the unit into "install mode", resetting it, and allowing it to accept over the network installations from the synology assistant applications.

Happy New year to you and your team.

Regards.

[Franklin]

Greetings Pawlu

The EEPROM contains the Linux Kernel and is responsible for starting the booting process/detection of the Synology OS on the HDD.