Bug 47421 - UCS updates destroy boot loader configuration
UCS updates destroy boot loader configuration
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Grub
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-07-31 12:22 CEST by Nico Gulden
Modified: 2021-05-14 16:34 CEST (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 7: Crash: Bug causes crash or data loss
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.120
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2018072721000187
Bug group (optional): External feedback
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nico Gulden univentionstaff 2018-07-31 12:22:20 CEST
A user reports that UCS updates destroy the bootloader settings.

An upgrade from UCS 4.2-3 to UCS 4.3-1, as well as, package updates on UCS 4.3-1 destroyed the boot loader configuration. Both systems did not boot anymore and resulted in a blinking prompt.

The partitioning is quite simple:

* Swap (dev/sda1)
* / (dev/sda2)
* Additional hard disk (/dev/sdb) for data, mounted at /media/data
 
The boot loader is installed in the MBR on /dev/sda.

The user restored the boot loader with Super Grub2 CD and the instructions from https://help.univention.com/t/boot-ucs-system-via-super-grub2-disk/6409
Comment 1 Nico Gulden univentionstaff 2018-07-31 16:27:20 CEST
The user executed the updates with apt-get upgrade (for package update) and apt-get dist-upgrade for the upgrade to the next UCS version.
Comment 2 Ingo Steuwer univentionstaff 2021-05-14 15:41:11 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.