Switching boot loader to GRUB2
Applies to:
Cryptshare Appliance with openSUSE 42.3
Symptom:
After the OS update the appliance cannot start and goes into a reboot loop
Cause:
During the previous OS upgrade the switching of boot loader from GRUB to GRUB2 has been performed incomplete
Solution:
Please follow the steps below to complete the switching to GRUB2:
1. log in as root on your appliance
2. run the command yast2 to start YaST Control Center
3. navigate to System → Boot Loader and press Enter
4. select Use on the next screen
5. press F10 to start the installation of GRUB2
6. press Enter to install the needed package
7. press F9 to finish
Related Articles
Outlook crashes when switching to a certain folder
Affected to All versions of Cryptshare for Office 365 and Outlook Symptom When switching to a certain Outlook folder while the Add-in is enabled, Outlook may crash due to an unknown view setting. Cause This is caused by a view setting which the ...Restoring distribution upgrade backup
Inhaltsverzeichnis 1 Applies to: 2 Symptom: 3 Cause: 4 Solution: Applies to: All versions of Cryptshare Appliance Symptom: If the Cryptshare Appliance does not respond after upgrading your system or not automatically loads its service after reboot, ...Outlook crashes sporadically when ESET Add-In is enabled
Applies to All versions of Cryptshare for Outlook Symptom When the user performs regular work in Outlook, e.g. switching between different emails, and the ESET Outlook Add-in is also enabled, Outlook crashes without any error message or warning. ...Outlook crashes sporadically when Third Party Add-Ins are also enabled
Applies to All versions of Cryptshare for Outlook Symptom When the user performs regular work in Outlook, e.g. switching between different emails, and a third party Outlook Add-in (for example ESET) is also enabled, Outlook crashes sporadically with ...Network Interface Naming Changes in openSUSE Leap 16.0
Inhaltsverzeichnis 1 Applies To 2 Problem 3 Cause 4 Solution/Workaround Applies To OpenSUSE upgrade performing from version Leap 15.6 to Leap 16.0. Problem After upgrading to openSUSE Leap 16.0, network interfaces are renamed from legacy names (e.g., ...