DynaGATE 10-14 EL Software Manual EN 1 The Software (EL 33.0.0)
© 2023 Eurotech SpA - Via Fratelli Solari, 3/a - 33020 Amaro (UD) - Italy
Document code: DYGATE-10-14_ELM_EN_1-0
Document revision: 1-0 (2023.08.02)
10 / 45
1.5.1.3 Factory restore
The factory restore is a function that makes an entry in the boot environment to instruct the system to
reboot, and to force the system to do a restore.
By default, after the restore is completed:
1. The system shows a flashing LED sequence to indicate that the process is completed.
2. The system automatically boots with the restored image .
To support multiple scenarios, and to provide flexibility for new ones, the restore mechanism can use
some “policies” to support the use case in the best way.
The system currently supports these restore policies:
Restore Policy Description
0The system boots from the Rescue image and restores both file-systems to factory default
1The system boots from the Rescue image and restores the primary file-system to factory default
2 (default) The system boots from the Rescue image and restores the secondary file-systems to factory default
To start the factory restore, keep the User-programmable button pushed for at least 10 seconds.
For more information, refer to:
l"User-programmable button and factory restore" on page36
l"USER LEDs status reporting" on the next page.
1.5.2 Limitations in failover and recovery
Handling failure conditions can be complex so the failover and recovery scheme has been designed to
be as simple as possible and to solve the most likely kinds of problem that can occur in normal system
use. It cannot solve all potential problems.
The following is a list of issues that are not covered and are outside of the scope of the current
implementation. Should these issues occur, user intervention may be required for the system to be re-
installed using an SD card installer, or returned to Eurotech if the SD card install is prohibited due to
security restrictions:
lIf the recovery image is corrupted, renamed, or missing, the recovery cannot occur.
In these conditions, the system may get stuck in an endless reboot loop.
To clear this loop, a solution, depending on the type of failure that has occurred, is to execute
stop at the bootloader prompt and set restore_policy to 0.
At this time, the system should be able to boot from the primary file system and you can rename
or re-install the missing recovery image file
lAlthough fstab will perform an fsck check of the log and data partitions before mounting them, if
the log partition is damaged or wiped, the recovery scheme is not designed to detect or correct
this kind of issue.
In this scenario, the system is likely to encounter boot issues because the start-up service that
launches journald may fail to run. The default scheme is not configured to re-format the log
partition, favoring to preserve the logs that may still exist to aid diagnosis of the root cause.
Should this issue occur, the system will drop to emergency mode with the following message:
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, " systemctl default" or ^D to try again to boot into default mode.
Cannot open access to console, the root account is locked.
See sulogin(8)man page for more details.
Press Enter to continue.