Mageia forum

I have quite suddenly (I did not knowingly change anything) encountered a problem with Grub on one of my computers when booting Mageia7. Mageia is the only OS; there is no other OS on the system.
It can not boot any more and I'm getting into the Grub rescue> mode.
However, by using a booting CD with Super Grub I'm able to boot into my existing Mageia and everything else seems normal so far.

Now, as I didn't change anything on my computer either a kernel update must have broken it - or there was some change in my UEFI system.
How you evaluate the problem? If it is of interest I could provide more data.

One additional information: I tried an old Kubuntu Live version 16.4 and was able to get it running without problems, while the repair version of Mageia7 on my installation CD was unable to recognize the bootdisk on my CD-drive as an installation medium. It is that, what makes me believe that the problem might be specific to Mageia or rather a specific problem of Mageia with my hardware. In this case the question would be: Did the most recent security update of Mageia change anything regarding the booting process?

Start from the installation DVD. Use update the existing version.
The post-installation menu will allow you to choose the Grub-2 installation location.
Check if you have the correct path HDD for Mageia-7.
Single disk /dev/sda (disk manufacturer)
After saving and restarting from HDD, the boot menu should appear.

xtapetae wrote:It can not boot any more and I'm getting into the Grub rescue> mode.

usual reasons:

loose data cable / power connection to HDD. check hdd cables are pressed home.
failing HDD. check with HDD utility: smartmontools, install via MCC or urpmi. run as

Code: Select all

smartctl -a  /dev/sdx

where "x" is your boot HDD
shut down / reboot of system before grub completed updating after kernel update. multiple methods to fix

Thank you for the answers. Actually as I had not Boot DVD I used the Mageia Control Center (Set up boot system) to readjust my boot mechanism and it worked. Interestingly, after that there was a second incident of no-booting but after again dialing into the Control Center everything seems to work fine now.
This and the fact that only my computer was affected has led me to believe that it is probably an instable UEFI configuration on this computer that has caused the problem.

Use GSmartControl and check the HDD. A common cause is problems with damaged sectors or power interruptions during recording.

Thanks mirej for drawing my attention to GSmartControl. That is a cool program I did not know. I made it check my ssd, however it did not find a problem.

FWIW, GSmartControl is only a GUI frontend to smartctl, which was already recommended to you by benmc earlier.

True, thanks also to benmc. OTH I'm especially thankful for the GUI of this tool.