Grub rescue! After Updating to 4.1-1


#1

17 of Feb 2016, Updated to version 4.1-1 and grub failed, can’t boot.

error: symbol ’ grub -term-highlight-color’ not found.
Entering rescue mode…
grub rescue>

What to do???

OK Solved, using www.supergrubdisk.org/wizard-restore-gr … -rescatux/ to restore grub.
Then reboot.

Thanks!!!


#2

Hi PLek!

[quote=“PLek”]17 of Feb 2016, Updated to version 4.1-1 and grub failed, can’t boot.

error: symbol ’ grub -term-highlight-color’ not found.
Entering rescue mode…
grub rescue>

What to do???

OK Solved, using supergrubdisk.org/wizard-res … -rescatux/ to restore grub.
Then reboot.

Thanks!!![/quote]

We would like to know some details about your current setup to prevent this error in future:
[ul][li]Which UCS version has been used for initial installation?[/li]
[li]Are you using more than one (virtual) harddisk?[/li]
[li]Was GRUB installed on any of your harddisks before (by UCS or any other Linux distro)?[/li][/ul]

Regards

Sönke


#3

My license Key ID: 39a925f4-cb8f-46ee-83c1-ac0bf4f08810

The initial installation of UCS version is 4.0, and it has been on constant package updating for every one to two weeks.
The previous update was done on last week, not very sure but I think its at 4.1-0 errata 110.
The system is running fine with every update except for this last release update 4.1-1.

I’m using two scsi harddisk with adaptec controller, but it is not running in RAID mode. I installed the home partition separately on a the second disk.

The system was install from clean without any other OS, and the partition was created manually during the initial installation with the home partition on the second disk.

Regards,
PLek


#4

I just got the same error while updating to UCS 4.1-1
Initial install was 4.0 and it has been kept updated since, last was 2 weeks ago.
Running as a ESXi instance. I did install using the ESXi image.
1 CPU
1 GB RAM
1 virtual disk

I am using it as a test platform.

Regards
Bengt


#5

Hi!

Thanks for sharing information about your affected systems. This helped a lot in locating the exact problem.

The erratum 116 for UCS 4.1-0 and UCS 4.1-1 (http://errata.software-univention.de/ucs/4.1/116.html) has been announced today, to prevent this problem in future.

@Bengt and @PLek:
We added a new SDB article http://sdb.univention.de/1356 that describes the neccessary steps to boot your UCS system and to reconfigure GRUB to prevent the rescue shell in future.

Best regards

Sönke Schwardt-Krummrich