Bug 16158

Summary:	dmraid creates incompatible mapper names
Product:	Mageia	Reporter:	Dan Fandrich <dan>
Component:	RPM Packages	Assignee:	Thomas Backlund <tmb>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	marja11, thierry.vignaud, tmb
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	dmraid-1.0.0-0.rc16.20.mga5.src.rpm, drakx-installer-stage2	CVE:
Status comment:

Description Dan Fandrich 2015-06-21 10:31:32 CEST

Description of problem:
This may be a recurrence of bug#6180 but in Mageia 5. After upgrading in place from Magiea 4, my system failed to boot due to the soft RAID device being different. Instead of /dev/mapper/pdc_gchidfeda6 the device actually created was called /dev/mapper/pdc_gchidfeda6 (note the lack of a "p" before the #).

Version-Release number of selected component (if applicable):
dmraid-1.0.0-0.rc16.20.mga5.src.rpm

How reproducible:
Only tried one upgrade, but it consistently creates the same different named device on every boot.

Steps to Reproduce:
See above

Reproducible: 

Steps to Reproduce:

David Walser 2015-06-22 00:02:07 CEST

Assignee: bugsquad => tmb

Comment 1 Thierry Vignaud 2015-07-31 09:55:50 CEST

This is expected.
So the real issue is that we didn't update /etc/fstab on upgrade.
Please attach your /root/drakx/report.bug.xz

CC: (none) => thierry.vignaud, tmb
Source RPM: dmraid-1.0.0-0.rc16.20.mga5.src.rpm => dmraid-1.0.0-0.rc16.20.mga5.src.rpm, drakx-installer-stage2

Comment 2 Marja Van Waes 2018-04-14 12:03:34 CEST

(In reply to Thierry Vignaud from comment #1)
> This is expected.
> So the real issue is that we didn't update /etc/fstab on upgrade.
> Please attach your /root/drakx/report.bug.xz

Almost three years later, no reply.

Closing as old.

Please reopen this report if you still have this issue with an officially supported, up-to-date Mageia release and adjust the "Version:" field accordingly.

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