You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have noticed that if the checksum test at the end of the installation from an ISO built using kiwi fails, the installation process will wait on the checksum test failure screen for user confirmation for a short period of time (less than 1 minute), but eventually times out and will continue booting into the OS. This means that unless someone is sitting through the whole installation process (which can take hours depending on the ISO size and hardware specs) and watches the checksum verification process and makes sure it passes, the checksum verification can actually fail because of some data corruption that is not big enough to break the OS boot, and by the time user gets back to the system, the checksum test failure screen could have timed out and the corrupted OS installation could have booted up, leaving the user confused as to why there are random failures happening across different parts of the OS.
Is there a way to disable the timeout of the checksum failure screen, and force the installation to stall on that screen until the failure is acknowledged through user input?
The text was updated successfully, but these errors were encountered:
We have noticed that if the checksum test at the end of the installation from an ISO built using kiwi fails, the installation process will wait on the checksum test failure screen for user confirmation for a short period of time (less than 1 minute), but eventually times out and will continue booting into the OS. This means that unless someone is sitting through the whole installation process (which can take hours depending on the ISO size and hardware specs) and watches the checksum verification process and makes sure it passes, the checksum verification can actually fail because of some data corruption that is not big enough to break the OS boot, and by the time user gets back to the system, the checksum test failure screen could have timed out and the corrupted OS installation could have booted up, leaving the user confused as to why there are random failures happening across different parts of the OS.
Is there a way to disable the timeout of the checksum failure screen, and force the installation to stall on that screen until the failure is acknowledged through user input?
The text was updated successfully, but these errors were encountered: