Bug 25039

Summary:	Mageia 7 does not start on RAID 1 System after Installation without any errormessages
Product:	Mageia	Reporter:	Werner Brinkmann <mail>
Component:	Installer	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	major
Priority:	Normal	CC:	lewyssmith, sysadmin-bugs
Version:	7
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	rdsosreport.txt

Description Werner Brinkmann 2019-07-03 21:07:30 CEST

Description of problem:
After starting Mageia (and some minutes) I get the following message:
dracut Warning: Could not boot.
dracut Warning: /dev/mapper/isw_bhfgfajagj_Volume1p1 does not exist

Generating "/run/initramfs/rdsosreport.txt"
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report.

Version-Release number of selected component (if applicable):
On first try: Mageia-7-x86_64
On second try: Mageia-7-Live-Plasma-x86_64

How reproducible:
At every attempt to start the system

I may add that I have a running Installation of Mageia 6 on one of the other Partitions of the same Raid.

If rdsosreport.txt is of any help let me know. Got a copy of it on my working system.

Comment 1 Werner Brinkmann 2019-07-03 21:51:33 CEST

Created attachment 11146 [details]
rdsosreport.txt

I realised that Bug 25027 deals with the same problem.
I tried to get that journal.txt but failed to do so getting this message:
[root@BlackBox ~]# journalctl -D /mnt/Mageia7/var/log/journal/da74004ee429438c9d291346f090242d/ > journal.txt
Journal file /mnt/Mageia7/var/log/journal/da74004ee429438c9d291346f090242d//user-1000.journal uses an unsupported feature, ignoring file.

Werner Brinkmann 2019-07-03 22:39:51 CEST

Component: Release (media or process) => Installer

Comment 2 Lewis Smith 2019-07-03 23:00:29 CEST

(In reply to Werner Brinkmann from comment #1)
> I realised that Bug 25027 deals with the same problem.
True, so marking this bug as a duplicate of that.

> I tried to get that journal.txt but failed to do so getting this message:
> [root@BlackBox ~]# journalctl -D /mnt/Mageia7/var/log/journal/da74004ee429438c9d291346f090242d/ > journal.txt
> Journal file /mnt/Mageia7/var/log/journal/da74004ee429438c9d291346f090242d//user-1000.journal uses an unsupported feature, ignoring file.
We shall come back to you about this.

*** This bug has been marked as a duplicate of bug 25027 ***

Status: NEW => RESOLVED
CC: (none) => lewyssmith
Resolution: (none) => DUPLICATE

Comment 3 Werner Brinkmann 2019-07-04 17:37:26 CEST

(In reply to Lewis Smith from comment #2)
> (In reply to Werner Brinkmann from comment #1)
> > I realised that Bug 25027 deals with the same problem.
> True, so marking this bug as a duplicate of that.
> 
> > I tried to get that journal.txt but failed to do so getting this message:
> > [root@BlackBox ~]# journalctl -D /mnt/Mageia7/var/log/journal/da74004ee429438c9d291346f090242d/ > journal.txt
> > Journal file /mnt/Mageia7/var/log/journal/da74004ee429438c9d291346f090242d//user-1000.journal uses an unsupported feature, ignoring file.
> We shall come back to you about this.
> 
> *** This bug has been marked as a duplicate of bug 25027 ***

Would that journal.txt file of my installation be of any help, or am I just waiting for bug 25027 to be solved, hoping that this solves my problem too?
I did manage to get that journal.txt by using the Mageia 7 Live DVD.

Comment 4 Lewis Smith 2019-07-06 16:09:23 CEST

Thank you for getting the journal.txt file in the end. If it is large, please compress it with "xz journal.txt".
Then:
- Add the [compressed] file as an *attachment to BUG 25027*, using the text box to describe the problem as you did here:
 After starting Mageia (and some minutes) I get the following message:
 dracut Warning: Could not boot.
 dracut Warning: /dev/mapper/isw_bhfgfajagj_Volume1p1 does not exist
 Generating "/run/initramfs/rdsosreport.txt"
- Also in that text, note the equivalent rdsosreport.txt file URL you attached to this bug:
 https://bugs.mageia.org/attachment.cgi?id=11146
- And add a note describing your system.

It should help to have two separate examples of the bug.