http://bugzilla.novell.com/show_bug.cgi?id=588840
http://bugzilla.novell.com/show_bug.cgi?id=588840#c14
Dennis Olsson changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |REOPENED
InfoProvider|DOlsson@WEB.de |
--- Comment #14 from Dennis Olsson 2010-07-07 18:28:56 CEST ---
The MD device was created like this:
# mdadm --create /dev/md/raid1 --name="raid1" --homehost="MyPC" --level="raid1"
--metadata="1.0" --auto=part3 -v -n 2 /dev/sda /dev/sdb
# mdadm --examine --scan
ARRAY /dev/md/raid1 metadata=1.0 UUID=ade8dad3:cfd1ea1e:5cd4ba89:54ef4b14
name=MyPC:raid1
# mdadm --stop /dev/md/raid1
# mdadm -A --scan
mdadm: /dev/md/MyPC:raid1 has been started with 2 drives.
# ll /dev/md
total 0
lrwxrwxrwx 1 root root 8 Jul 7 14:29 MyPC:raid1 -> ../md127
#
After rebooting into Installation, we have:
# ll /dev/md
total 0
lrwxrwxrwx 1 root root 8 2010-07-07 10:34 raid1 -> ../md127
In YaST *only* "/dev/md127" is being displayed -- But no "/dev/md/raid1"!!
It seems the problem with the MD device name comes from the fact that
"/proc/partitions" is being used to find the block devices in use, and while
this is "/dev/md127*" the naming path "/dev/md/raid1*" is being ignored --
except when looking for "container"s, there the device name is being fetched
correctly (mdadm --examine --brief --scan).
After the first reboot during installation, I booted into "rescue" to see, what
had been written into "/etc/mdadm.conf":
# cat /mnt/etc/mdadm.conf
DEVICE containers partitions
ARRAY /dev/md/raid1 UUID=d3dae8ad:1eead1cf:89bad45c:144bef54
Interesting, especially the UUID, while doing:
# mdadm --examine --scan
ARRAY /dev/md/raid1 metadata=1.0 UUID=ade8dad3:cfd1ea1e:5cd4ba89:54ef4b14
name=MyPC:raid1
gives another (correct) result!
Notice the UUID -- For some odd/strange reason the UUID entered into the
"/etc/mdadm.conf" file seems to be a newly generated UUID which has nothing to
do with the UUID found on the MD device! From where did that come from???
On the other hand, the "/etc/mdadm.conf" file in "initrd" has the contents:
ARRAY /dev/md127 metadata=1.00 name=MyPC:raid1
UUID=ade8dad3:cfd1ea1e:5cd4ba89:54ef4b14
Notice that the UUID here is correct, but the MD device path has been shorten
to "/dev/md127" instead of "/dev/md/raid1" (manual named) or
"/dev/md/MyPC:raid1".(automagically named by "mdadm -A --scan").
Rebooted the system in order to allow for the installation to finish, and ends
up with having "/dev/md/raid1*" as well as "/dev/md127*" exists, *but* after
having rebooted the system (once more) _only_ "/dev/md127*" is created!!
During shutdown the error message:
mdadm: error opening /dev/md/raid1: No such file or directory
is printed just after the last "Sending all processes the KILL signal...".
Changing the "/etc/mdadm.conf" file in "initrd" to:
DEVICE containers partitions
ARRAY /dev/md/raid1 metadata=1.0 name=MyPC:raid1
UUID=ade8dad3:cfd1ea1e:5cd4ba89:54ef4b14
results in having "/dev/md/raid1*" as well as "/dev/md127*" nodes created, when
system is up, but also results during booting in the error message just after
"Creating device nodes with udev":
mdadm: /dev/md127 not identified in config file.
but do not result in any error message from "mdadm" later on during the
shutdown process.
Assuming that this error message is due to the fact that the startup scripts in
"initrd" are referring to "/dev/md127*" and not to "/dev/md/raid1*", I changed
all occurrences of "/dev/md127*" to "/dev/md/raid1*" in the "initrd" and
rebooted with this new "initrd".
Unfortunately, the result is that *no* MD devices at all have been created in
"/dev"! In fact, the system is starting up using "/dev/sda*" instead"!!
Sigh. ;-)
BTW, there is a minor typo in the shutdown message of the MD devices:
/dev/md127p3 umounted (<== BUG - should be: unmounted ("n" missing))
Shutting down MD Raid
:-D
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.