Mailinglist Archive: opensuse-bugs (5243 mails)

< Previous Next >
[Bug 810293] New: System boot fails due to systemd not able to mount multipathed FC disk
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 19 Mar 2013 16:03:26 +0000
  • Message-id: <bug-810293-21960@http.bugzilla.novell.com/>

https://bugzilla.novell.com/show_bug.cgi?id=810293

https://bugzilla.novell.com/show_bug.cgi?id=810293#c0


Summary: System boot fails due to systemd not able to mount
multipathed FC disk
Classification: openSUSE
Product: openSUSE 12.3
Version: Final
Platform: x86-64
OS/Version: All
Status: NEW
Severity: Major
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: steffen.hau@xxxxxxxxxxxxxxxxxx
QAContact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---


Created an attachment (id=530434)
--> (http://bugzilla.novell.com/attachment.cgi?id=530434)
journalctl -b output of a failed boot attempt

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

I've updated one of my openSuSE 12.2 machines to the new 12.3 release. We've
also switched from sysvinit-init to systemd.

After a reboot, the machine fails to boot. It displays a welcome message for
emergency mode and asks me for the root users password.

In journalctl -b, I can see that it failed to mount /dev/dm-1 to /wwwcache.

I've enabled multipathd with systemctl enable. But according to journalctl, it
doesn't get started.

If I uncomment the corresponding line in /etc/fstab, the system boots fine and
multipathd.service gets executed.

I'll attach a journalctl output, when I'm in the rescue shell again.

If you need further information, please let me know.

Reproducible: Always

Steps to Reproduce:
1. Add a device-mapper (FC multipathed) disk to /etc/fstab
2. Reboot
3.
Actual Results:
Boot fails at mounting the device-mapper (FC multipathed) disk

Expected Results:
Mount the disk and continue booting

--
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.

< Previous Next >