1144283 – multipath error meesage prevents systemd boots

Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1144283 - multipath error meesage prevents systemd boots

Summary: multipath error meesage prevents systemd boots

Keywords:
Status:	CLOSED DUPLICATE of bug 1160478
Alias:	None
Product:	Fedora
Classification:	Fedora
Component:	device-mapper-multipath
Sub Component:
Version:	21
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	---
Assignee:	Ben Marzinski
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2014-09-19 07:11 UTC by Peng Wu
Modified:	2014-11-26 17:14 UTC (History)
CC List:	10 users (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2014-11-26 17:14:55 UTC
Type:	Bug
Embargoed:
Dependent Products:

Attachments	(Terms of Use)

Description Peng Wu 2014-09-19 07:11:24 UTC

Description of problem:
In Fedora 21 installations with disk encryption from Live Workstation iso, multipath try to "adding target to table", but failed.
systemd waits for mounting to finish, then fall back to emergence mode.


Version-Release number of selected component (if applicable):
device-mapper-multipath-0.4.9-67.fc21.i686

How reproducible:
Install Fedora 21 workstation, choose MBR partition table, and full disk encryption.
Upgrade packages to the latest version.

Steps to Reproduce:
1. boot the system.
2. fall back to emergence mode.

Actual results:
Failed to boot, and get the error message from `dmesg`:
device-mapper: table: 253:2: multipath: error getting device
device-mapper: ioctl: error adding target to table

From the console, systemd waits for the devices but timeout.

Expected results:
System boots normally.

Additional info:
After adding the following line, systemd boots successfully:
blacklist {
	wwid QEMU_HARDDISK_QM00001
}

From URL: https://bugzilla.redhat.com/show_bug.cgi?id=675366

Comment 1 Peng Wu 2014-09-19 07:21:06 UTC

system config:

# cat /etc/multipath.conf 

blacklist {
	wwid QEMU_HARDDISK_QM00001
}

defaults {
	user_friendly_names yes
}

# cat /proc/partitions 
major minor  #blocks  name

   8        0   10485760 sda
   8        1     512000 sda1
   8        2    1048576 sda2
   8        3    8924160 sda3
  11        0    1048575 sr0
 253        0    8922112 dm-0
 253        1    1046528 dm-1

Comment 2 Ben Marzinski 2014-09-23 14:51:12 UTC

It doesn't appear from /proc/partitions that you need multipath running, so why is it configured at all?

If you delete /etc/multipath.conf, and remake your initramfs, does this just go away?

The way multipath works, you either need to set

find_multipaths yes

in the defaults section, or multipath will assume that every device type in can run on, it should run on, and your are responsible for blacklisting the devices you don't want it to try to use.

If you create the multipath.conf file using the

# mpathconf --enable

method, it should set find_multipaths by default.  This will make multipath only run on devices that have (or have had) multiple paths.

Comment 3 Peng Wu 2014-09-24 07:20:30 UTC

Thanks for the information, it works!

Actually I didn't enable multipath, just install from Workstation Live iso,
then yum upgrade several times, the bug occurs.

Comment 4 Peng Wu 2014-09-24 07:23:35 UTC

Here are the content of /etc/multipath.conf, after running "mpathconf --enable":
# mpathconf --enable
# cat /etc/multipath.conf 

blacklist {
}

defaults {
}

Comment 5 Ben Marzinski 2014-09-24 19:15:51 UTC

Do you have

/usr/share/doc/device-mapper-multipath-0.4.9/multipath.conf

That should have been installed with your package, and if no /etc/multipath.conf
file exists, it should have used that as a base for your configuration file, and that file should have

find_multipaths yes

If /etc/multipath.conf already exists when you run

# mpathconf --enable

It will just use your existing file, and make sure that blacklist isn't set to

devnode ".*"

which disables multipathing on all devices.

Comment 6 Peng Wu 2014-09-26 05:42:31 UTC

it seems multipath is enabled by anaconda.

Sorry, last time I run anaconda by mistake, then quit immediately.
But the multipath.conf is generated, the bug occurs.

Comment 7 Ben Marzinski 2014-11-26 17:14:55 UTC


*** This bug has been marked as a duplicate of bug 1160478 ***

Note You need to log in before you can comment on or make changes to this bug.