Mailinglist Archive: opensuse-bugs (2746 mails)

< Previous Next >
[Bug 823125] New: mkinitrd writes an incorrect md entry into /etc/mdadm in initrd
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 4 Jun 2013 16:15:09 +0000
  • Message-id: <>

Summary: mkinitrd writes an incorrect md entry into /etc/mdadm
in initrd
Classification: openSUSE
Product: openSUSE 12.2
Version: Final
Platform: x86-64
OS/Version: openSUSE 12.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Update Problems
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: dihewo@xxxxxx
QAContact: jsrain@xxxxxxxx
Found By: ---
Blocker: ---

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101

I have the following setup (System setup new with 12.2):
- Multiple raid1
- Raid1 for /boot (md0)
- Raid1 for system vg (/, /usr, /var, ---) (md1)
- Raid1 (md2)
- Raid1 (md3)

After generating a new initrd /etc/mdadm.cpnf contains the entry for md3
instead of md1. So, the system vg is not found during boot and it goes through
a very long loop of error messages, basically saying, that the system vg was
not found. Only after then I can enter that emergency shell with limited
features, where I can assemble md1, do a vgscan and activate the system vg.
From that point the boot process continues normally.

The problem seems to be, that mkinitrd and tools seem to extract the wrong
entry (md3 instead of me1) from /etc/mdadm.conf, because, when I unpack the
initrd, replace /etc/mdadm.conf with one containing md1 data from system
/etc/mdadm.conf and repack it, then the system boots without problem until the
ext kernel update.

Reproducible: Always

Steps to Reproduce:
Don't know how to reproduce it on any system, because I have other systems
(also 12.2 and multiple raid1 setup), where this does not happen. On the
described system it happens regularly.

Actual Results:
Barely bootable system

Expected Results:
Normally booting system

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
Follow Ups