Bug 24720

Summary: Little boot problem
Product: Mageia Reporter: christoph hagen <ch.hagen>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: minor    
Priority: Normal CC: lovaren, marja11, ouaurelien
Version: 6   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: Bug report about this boot problem

Description christoph hagen 2019-04-25 23:00:52 CEST
Description of problem: when I boot the computer fails to find how to boot and gets to the emergency mode. I manage to boot doing Ctrl + D


Version-Release number of selected component (if applicable):


How reproducible: Every time I attempt to boot (but just since a few days ; before there was no problem)


Steps to Reproduce:
1.
2.
3.
Comment 1 christoph hagen 2019-04-25 23:05:59 CEST
Created attachment 10968 [details]
Bug report about this boot problem
Comment 2 Kristoffer Grundström 2019-04-25 23:40:15 CEST
You forgot to mention the steps to reproduce this issue.

Add the resulting output (run dmesg in a terminal window) as a file attachment here and NOT in the comment section.

When you start the computer and get to the GRUB boot menu edit the kernel boot command line and delete the word quiet to get some more info on where it stops.

How did you install Mageia 6?

Did you use the DVD iso or the netinstall iso?

The net install iso is usually better since it uses online medias to install packages and its updates, but you're free to use any iso you like.

Did you check the md5sum of the iso you used before you put it in the media you used to install Mageia with?

glxinfo will show you what kind of graphics card you have if it's a problem with the driver.

If you add nomodeset and blacklist.modprobe=nouveau might be a working solution if nouveau is used as a module.

Other than that you could always dump journalctl log to a USB drive.

CC: (none) => hamnisdude

Comment 3 Marja Van Waes 2019-04-26 21:15:25 CEST

(In reply to christoph hagen from comment #1)
> Created attachment 10968 [details]
> Bug report about this boot problem

Hi Christoph

It seems that your root partition sda6 got corrupted:


[   14.503256] dracut Warning: /dev/disk/by-uuid/e5eef0f4-ad82-4df9-ad23-a76f29912ac7 contains a file system with errors, check forced.
[   14.503736] dracut Warning: /dev/disk/by-uuid/e5eef0f4-ad82-4df9-ad23-a76f29912ac7: Inodes that were part of a corrupted orphan linked list found.
[   14.504555] dracut Warning: *** An error occurred during the file system check.
[   14.504774] dracut Warning: *** Dropping you to a shell; the system will try
[   14.504983] dracut Warning: *** to mount the filesystem(s), when you leave the shell.
[   14.505484] dracut Warning: 

Please boot in safe mode, make sure /dev/sda6 isn't mounted  with

     umount /dev/sda6

and then run

    fsck -y /dev/sda6

CC: (none) => marja11

Comment 4 Aurelien Oudelet 2020-08-02 22:51:04 CEST
This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Status: NEW => RESOLVED
CC: (none) => ouaurelien
Resolution: (none) => OLD