[Bug 921570] New: after dist upgrade system boots to emergency mode
http://bugzilla.opensuse.org/show_bug.cgi?id=921570 Bug ID: 921570 Summary: after dist upgrade system boots to emergency mode Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: steffen.hau@rz.uni-mannheim.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I've started upgrading systems from openSUSE 13.1 to 13.2. Virtual machines without special stuff like mdadm raid devices oder multipathed FC LUN's went fine. But systems (IBM HS22 Blades) with mdadm raid devices are booting to emergency mode. The systems have three raid 1 devices (swap, / and /srv or /home), swap and / are correctly assembled but the third md device is missing and it also does not appear in /proc/mdstat. Manually running "mdadm -A --scan" brings it up and "systemctl default" continues booting. To dig deeper into this issue, I've installed openSUSE 13.2 from scratch on a spare blade and here md2 is correctly assembled. This is the content of /etc/systemd/system/ of the upgraded system: /etc/systemd/system/dbus-org.opensuse.Network.AUTO4.service /etc/systemd/system/dbus-org.opensuse.Network.DHCP4.service /etc/systemd/system/dbus-org.opensuse.Network.DHCP6.service /etc/systemd/system/dbus-org.opensuse.Network.Nanny.service /etc/systemd/system/default.target /etc/systemd/system/default.target.wants/sysstat.service /etc/systemd/system/default.target.wants/systemd-readahead-collect.service /etc/systemd/system/default.target.wants/systemd-readahead-replay.service /etc/systemd/system/getty.target.wants/getty@tty1.service /etc/systemd/system/multi-user.target.wants/acpid.service /etc/systemd/system/multi-user.target.wants/apache2.service /etc/systemd/system/multi-user.target.wants/auditd.service /etc/systemd/system/multi-user.target.wants/cron.service /etc/systemd/system/multi-user.target.wants/dsmc.service /etc/systemd/system/multi-user.target.wants/irqbalance.service /etc/systemd/system/multi-user.target.wants/mcelog.service /etc/systemd/system/multi-user.target.wants/ntpd.service /etc/systemd/system/multi-user.target.wants/postfix.service /etc/systemd/system/multi-user.target.wants/remote-fs.target /etc/systemd/system/multi-user.target.wants/smartd.service /etc/systemd/system/multi-user.target.wants/sshd.service /etc/systemd/system/multi-user.target.wants/syslog-ng.service /etc/systemd/system/multi-user.target.wants/wicked.service /etc/systemd/system/network-online.target.wants/wicked.service /etc/systemd/system/network.service /etc/systemd/system/sysinit.target.wants/multipathd.service /etc/systemd/system/syslog.service /etc/systemd/system/system-update.target.wants/systemd-readahead-drop.service /etc/systemd/system/timers.target.wants/logrotate.timer /etc/systemd/system/wickedd.service.wants/wickedd-auto4.service /etc/systemd/system/wickedd.service.wants/wickedd-dhcp4.service /etc/systemd/system/wickedd.service.wants/wickedd-dhcp6.service /etc/systemd/system/wickedd.service.wants/wickedd-nanny.service /etc/systemd/system/wicked.service.wants/wickedd.service I've made the scratch system identical to the problematic system (identical installed packages, conf files in /etc, active systemd services, and so on) and it still assembles md2. I've no more ideas where to search for possible causes. Please let me know what kind of information I should provide in order to help you to find the cause. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=921570
--- Comment #1 from Steffen Hau
http://bugzilla.opensuse.org/show_bug.cgi?id=921570
--- Comment #2 from Steffen Hau
http://bugzilla.opensuse.org/show_bug.cgi?id=921570
Steffen Hau
http://bugzilla.opensuse.org/show_bug.cgi?id=921570
Steffen Hau
http://bugzilla.opensuse.org/show_bug.cgi?id=921570
Bernhard Wiedemann
http://bugzilla.opensuse.org/show_bug.cgi?id=921570
--- Comment #4 from Steffen Hau
http://bugzilla.opensuse.org/show_bug.cgi?id=921570
http://bugzilla.opensuse.org/show_bug.cgi?id=921570#c6
--- Comment #6 from Steffen Hau
http://bugzilla.opensuse.org/show_bug.cgi?id=921570
http://bugzilla.opensuse.org/show_bug.cgi?id=921570#c7
--- Comment #7 from Steffen Hau
http://bugzilla.opensuse.org/show_bug.cgi?id=921570
Peter B
http://bugzilla.opensuse.org/show_bug.cgi?id=921570
http://bugzilla.opensuse.org/show_bug.cgi?id=921570#c9
--- Comment #9 from Steffen Hau
http://bugzilla.opensuse.org/show_bug.cgi?id=921570
http://bugzilla.opensuse.org/show_bug.cgi?id=921570#c10
Steffen Hau
http://bugzilla.opensuse.org/show_bug.cgi?id=921570
http://bugzilla.opensuse.org/show_bug.cgi?id=921570#c12
--- Comment #12 from Hannes Reinecke
http://bugzilla.opensuse.org/show_bug.cgi?id=921570
http://bugzilla.opensuse.org/show_bug.cgi?id=921570#c13
--- Comment #13 from Steffen Hau
If you were to enable multipath on a non-multipathed root system you need to blacklist the root filesystem. I don't know why I should have to do that. OpenSUSE 13.1 works fine with Swap, / and /srv each on RAID1 md devices and additional multipathed FC LUN's. OpenSUSE 13.2 also assembles SWAP and /, but misses /srv if multipathd.service is enabled.
Also, due to the timing involved multipath might claim the device for MD, so if MD references the devices as raw block devices (ie using /dev/sdX) it won't be able to start. If already written that I have checked that point. While in emergency mode, dmsetup does not report /dev/sd[a,b]3 to be claimed (see #c4). I can manually assemble the missing array and continue booting.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=921570
http://bugzilla.opensuse.org/show_bug.cgi?id=921570#c14
--- Comment #14 from Steffen Hau
http://bugzilla.opensuse.org/show_bug.cgi?id=921570
Ben K
participants (1)
-
bugzilla_noreply@novell.com