This bug was fixed in the package multipath-tools - 0.4.9-3ubuntu7.9
---
multipath-tools (0.4.9-3ubuntu7.9) trusty; urgency=medium
* debian/patches/kpartx-support-device-names-with-spaces.patch: fix loopback
files unmapping. (LP: #1543430)
multipath-tools (0.4.9-3ubuntu7.8)
Hello Stuart, or anyone else affected,
Accepted multipath-tools into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/multipath-
tools/0.4.9-3ubuntu7.9 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
FWIW, it's not so much as a flat no for fixing this with a sleep as that
any possible value for sleep (unless it's unreasonably high) will still
fail for some people... and high values are just inconvenient since they
slow the boot down. It's generally just not a very useful general fix,
even if
This was already verified successfully before; the additional update
does not need reverification, only checking the regression in bug
1543430.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server
Haven't had a chance to raise it yet (having to use the environment for
something else atm so I wouldn't be able to capture logs), though plan
to do it next week once the environment is free.
Some thoughts around potential workarounds/fixes:
- Boot option (similar to rootwait/rootdelay) to impose
Hi,
Given the conversation/explanation on this bug (1: problem is lack of
SCSI wait scan, and 2: this bug targets to remove the error message),
and my additional comments on bug 1526984 comment #18 (summary: the SCSI
wait scan problem is not supposed to be fixed with either udevadm settle
/
Brian,
Package tested (0.4.9-3ubuntu7.8) and can confirm that it does resolve
the problem around loading the missing module. It doesn't however fix
the issue of the multipath root device working (as my system is back to
sda rather than mpath). As per Matthiew's comment (4) I will update
Stuart,
I'm aware of that, but there are two different issues at play here: the
detection and scanning of drives, and the fact that scsi_wait_scan is
still in the script. The upload should likely fix both; but I'm closing
this bug here because it's about scsi_wait_scan. The other bugs are
Hello Stuart, or anyone else affected,
Accepted multipath-tools into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/multipath-
tools/0.4.9-3ubuntu7.8 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Also affects: multipath-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: multipath-tools (Ubuntu)
Status: New => Fix Released
** Changed in: multipath-tools (Ubuntu Trusty)
Status: New => In Progress
** Changed in: multipath-tools (Ubuntu Trusty)
Just to be clear, it isn't the error message that is a problem when
attempting to boot, its that the system will not boot with multipath
support because the multipath discovery in the initrd is performed
before the SCSI devices are available. Removing the current code
referring to the removed
This is already fixed in 0.5.0 so Fix Released for xenial; not
applicable to wily (which also has the fix already).
Work to land this fix in 14.04 in progress.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
12 matches
Mail list logo