Abstract: Embodiments are described for a secure boot monitoring and validation process during operating system (OS) upgrade operations from a previous OS version. A validated copy of OS boot files is made during OS installation. A checksum comparator or OS boot file filesystem check (FSCK) component validates the boot files upon initial installation of the OS. Any validation failure indicates corruption or unwanted modification of the boot file data, and an alert is sent. The file system is locked to prevent any exposure of user data. The validated copy is then used to recover the boot files. An OS boot file monitor component periodically monitors the boot files during OS run time and if any corruption is detected during a system boot after OS installation, the boot blocking, alert, and recovery procedures can be invoked.

Abstract: Embodiments are described for a secure boot monitoring and validation process during operating system (OS) upgrade operations from a previous OS version. A validated copy of OS boot files is made during OS installation. A checksum comparator or OS boot file filesystem check (FSCK) component validates the boot files upon initial installation of the OS. Any validation failure indicates corruption or unwanted modification of the boot file data. In case of a failure, an autorecovery operation using different boot partitions is attempted, and the OS boot filesystem check is performed again. If the second filesystem check fails a critical alert notification is sent, otherwise a warning alert notification is sent. The file system for storing user data is also shutdown to prevent any potential damage of user data.

Abstract: Embodiments are described for a secure boot monitoring and validation process during operating system (OS) initial installation or upgrade operations. A validated copy of OS boot files is made during OS installation. The boot files are stored in a first RAID array. A checksum comparator or OS boot file filesystem check (FSCK) component validates the boot files upon initial installation of the OS by comparison with a secure copy of the boot files, which are stored in a second RAID array. Any validation failure indicates corruption or unwanted modification of the boot file data, and an autorecovery operation using different boot partitions is attempted.

Abstract: Embodiments are described for a secure boot monitoring and validation process during operating system (OS) installation and runtime. A validated copy of OS boot files is made during OS installation. A checksum comparator or OS boot file filesystem check (FSCK) component validates the boot files upon initial installation of the OS. Any validation failure indicates corruption or unwanted modification of the boot file data, and an alert is sent. The file system is locked to prevent any exposure of user data. The validated copy is then used to recover the boot files. An OS boot file monitor component periodically monitors the boot files during OS run time and if any corruption is detected during a system boot after OS installation, the boot blocking, alert, and recovery procedures can be invoked.

Abstract: One embodiment provides a computer implemented method for recovering an operating system (OS) after an upgrade hang using a dual-flash device. The method includes detecting a system hang during an OS upgrade; initiating a boot from the dual-flash device; checking for OS configuration data in the dual-flash device; creating a hook in OS boot scripts to recover the OS configuration data after OS boot; and applying the OS configuration data after OS boot.

Abstract: One embodiment provides a computer implemented method of for monitoring and upgrading a dual-flash device. The method includes performing an OS upgrade on a server; writing an upgraded OS to the dual-flash device; updating a grub.cfg file corresponding to the upgraded OS; and deleting old OS files from the dual-flash device.

Abstract: One embodiment provides a computer implemented method for recovering an operating system (OS) after a runtime hang using a dual-flash device. The method includes detecting a first runtime hang of a server; initiating a first reboot from a hard disk; detecting a second runtime hang of the server; and initiating a second reboot from the dual-flash device.

Abstract: One embodiment provides a computer implemented method for installing an operating system (OS) using a dual-flash device. The method includes burning an OS version to the dual-flash device located on a server. The method also includes setting BIOS to boot the server from the dual-flash device; triggering installation of the OS version on the server from the dual-flash device; and setting BIOS to boot from a hard disk of the server after installation of the OS version.

Abstract: One embodiment provides a computer implemented method for recovering an operating system (OS) after a runtime hang using a dual-flash device. The method includes detecting a first runtime hang of a server; initiating a first reboot from a hard disk; detecting a second runtime hang of the server; and initiating a second reboot from the dual-flash device.

Abstract: One embodiment provides a computer implemented method of for monitoring and upgrading a dual-flash device. The method includes performing an OS upgrade on a server; writing an upgraded OS to the dual-flash device; updating a grub.cfg file corresponding to the upgraded OS; and deleting old OS files from the dual-flash device.

Abstract: One embodiment provides a computer implemented method for installing an operating system (OS) using a dual-flash device. The method includes burning an OS version to the dual-flash device located on a server. The method also includes setting BIOS to boot the server from the dual-flash device; triggering installation of the OS version on the server from the dual-flash device; and setting BIOS to boot from a hard disk of the server after installation of the OS version.

Abstract: One embodiment provides a computer implemented method for recovering an operating system (OS) after an upgrade hang using a dual-flash device. The method includes detecting a system hang during an OS upgrade; initiating a boot from the dual-flash device; checking for OS configuration data in the dual-flash device; creating a hook in OS boot scripts to recover the OS configuration data after OS boot; and applying the OS configuration data after OS boot.