https://bugzilla.novell.com/show_bug.cgi?id=331604#c8
Thomas Fehr changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fehr@novell.com
Status|NEW |NEEDINFO
Info Provider| |joe_morris@ntm.org
--- Comment #8 from Thomas Fehr 2007-10-25 05:51:02 MST ---
I also doubt this is due to device names being in mdadm.conf, there should be
none. libstorage puts a line with "DEVICE partitions" into mdadm.conf since SL
10.1. So there should be no references to partition device names in mdadm.conf
normally. In comment #1 the user explicitly stated that there were no
reference to devices in mdadm.conf.
Only reason for devices names being part of mdadm.conf could be if the update
was hitting a mdadm.conf from a system older than SL 10.1 or if the user
manually edited mdadm.conf.
So far there is no code that touches mdadm.conf during update.
So it could happen that someone still has a pre-10.1 mdadm.conf in its system
even if he did updates to 10.1, 10.2 and now 10.3. Most of the problems
with booting from mdadm were due to bootloader not handling being /boot on md
raid, not because of device names in mdadm.conf but the issue with mdadm.conf
of pretty old installations still existing could be also hit.
Please attach your mdadm.conf.
Please tell us which was the version you installed SuSE Linux first and if you
manually edited mdadm.conf. Additionally please attach complete content of the
directory /var/log/YaST2.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.