Mailinglist Archive: opensuse-bugs (4216 mails)

< Previous Next >
[Bug 743718] New: mdadm: error opening /dev/mdX during during the shutdown process
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 27 Jan 2012 02:34:54 +0000
  • Message-id: <>

Summary: mdadm: error opening /dev/mdX during during the
shutdown process
Classification: openSUSE
Product: openSUSE 12.1
Version: Final
Platform: Other
OS/Version: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: ray@xxxxxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---
Blocker: ---

User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.7 (KHTML,
like Gecko) Chrome/16.0.912.77 Safari/535.7

When I have been solving #743717 I switched back to System V instead of systemd
and found that when rebooting/halting there is a following error message:

mdadm: error opening /dev/md/2

(it is / partition)

/etc/mdadm.conf file was:
DEVICE containers partitions
ARRAY /dev/md/1 UUID=7d6b05f2:c4ca4c78:aac6bf1b:9da6b8ef
ARRAY /dev/md/2 UUID=003589a4:9aa5e883:41cb207e:8a8c8541
ARRAY /dev/md/3 UUID=b9a9b25d:215c7531:0916e080:b9e2b338

openSUSE should use /dev/mdX devices in this file (otherwise disaster with
systemd may happen - I created separate bug and fix for this) but the problem
is that even with current setup /dev/md/2 file is missing when shutdown is
started (this file should be created by udev). If /etc/mdadm.conf is changed to
use /dev/mdX naming convention then there is an error "can not get exclusive
lock". I know System V is probably not priority but this problem exists there.

Reproducible: Always

Steps to Reproduce:
1. Install openSUSE with / partition on md device
2. Switch to System V
3. Reboot/Halt system

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

< Previous Next >