Bug 15850

Summary:	after update 4-5rc or install 5rc system fails to boot thanks to misconfigured raid
Product:	Mageia	Reporter:	Henk Elbers <henk>
Component:	Installer	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	critical
Priority:	Normal	CC:	marja11, thierry.vignaud
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	/root/drakx/report.bug.xz /etc/mdadm.conf

Description Henk Elbers 2015-05-05 13:58:46 CEST

Description of problem:

I tried to upgrade mga4 to mga5rc. During the installation I got several messages
that 149 or 20  packages failed. After <enter> the installation continues and in
the end tried to reboot. This failed. After some hours I decided to do a fresh
install. Again it failed to boot. After a lot of investigating, rebooting, etc...
I found out that my raid5 array consisted of /dev/sdb1 sdc1 sdi1 and sdj1
(in mga4 and also during the install of mga5rc) but after booting it was
sdb1 sdc1 sdd1 sde1.
After changing /etc/mdadm.conf I could finally boot my system.


Version-Release number of selected component (if applicable): MGA 5 RC (x86_64)


How reproducible:

upgrade mga4 to mga4rc or just install mga5rc on a system with a raid5 array consisting of more than 2 disks. In nga4 the disks should be sdb/c/i/j.



Reproducible: 

Steps to Reproduce:

Comment 1 Henk Elbers 2015-05-05 14:00:41 CEST

I have an Asus M5A88-V evo motherboard.

Comment 2 Thierry Vignaud 2015-05-05 19:08:53 CEST

Please attach your /root/drakx/report.bug.xz & your new /etc/mdadm.conf

CC: (none) => thierry.vignaud

Thierry Vignaud 2015-05-05 19:09:05 CEST

Keywords: (none) => NEEDINFO

Comment 3 Henk Elbers 2015-05-05 20:09:08 CEST

Created attachment 6453 [details]
/root/drakx/report.bug.xz

Comment 4 Henk Elbers 2015-05-05 20:10:34 CEST

Created attachment 6454 [details]
/etc/mdadm.conf

Rémi Verschelde 2015-05-05 20:13:08 CEST

Keywords: NEEDINFO => (none)

Comment 5 Thierry Vignaud 2015-05-19 14:48:55 CEST

Are you sure that's the log corresponding to your install?
There's no failed transaction in that one.

Keywords: (none) => NEEDINFO

Comment 6 Henk Elbers 2015-05-19 18:37:15 CEST

During the update from 4-5rc I had a lot of failed packages but in the end the update was complete. It did NOT reboot!!

Finally I decided to do a fresh install, it completed and did NOT reboot!!
The logfile must be of this last install.

Then I found out that the numbering of the disks had changed,

sda sdb sdc sdi sdj (mga4)               -->
sda sdb sdc sdh sdi (mga5rc install dvd) -->
sda sdb sdc sdd sde (mga5)

So, to get it to boot, I had to change /etc/mdadm.conf:

mga4: DEVICE /dev/sdb1 /dev/sdc1 /dev/sdi1 /dev/sdj1
      ARRAY /dev/md0 UUID=40867e37:a1b8f0ee:705928dd:5ccc2dd4 auto=yes

mga5 after update/install:
      DEVICE /dev/sdb1 /dev/sdc1 /dev/sdh1 /dev/sdi1
      ARRAY /dev/md127 UUID=40867e37:a1b8f0ee:705928dd:5ccc2dd4 auto=yes

to

      DEVICE /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1
      ARRAY /dev/md127 UUID=40867e37:a1b8f0ee:705928dd:5ccc2dd4 auto=yes

Comment 7 Marja Van Waes 2015-12-19 07:00:12 CET

(In reply to Thierry Vignaud from comment #5)
> Are you sure that's the log corresponding to your install?
> There's no failed transaction in that one.

It was an upgrade, so he probably shouldn't have attached 
/root/drakx/report.bug.xz (which is of the old install), but 
/root/drakx/report.bug of the date of the upgrade (after compressing it)

@ Henk

Do you happen to still have that report.bug of the correct date?

CC: (none) => marja11

Comment 8 Marja Van Waes 2015-12-19 07:12:48 CET

(In reply to Henk Elbers from comment #6)
> During the update from 4-5rc I had a lot of failed packages but in the end
> the update was complete. It did NOT reboot!!
> 
> Finally I decided to do a fresh install, it completed and did NOT reboot!!
> The logfile must be of this last install.

Oops, so: no, you no longer have the report.bug from the upgrade
> 
> Then I found out that the numbering of the disks had changed,
> 

Without matching report.bug of when that happened, this bug report is useless.

Closing as OLD (also because everyone will have upgraded to MGA5 now)

If anyone sees this again, when upgrading to a later version of Mageia, then please file a new bug report and _attach_:
 
new /root/drakx/report.bug.xz or new /root/drakx/report.bug (after compressing)
new /etc/mdadm.conf

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