This should be fixed in Xenial/Yakkety by now. Unfortunately as part of
the backport for bug #1567602 (fixed in 4.4.0-31.50 and later).
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which
The same error appeared in 4.6.1 for amd64 . 4.6.0 works without problem.
Matthew
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1588421
Title:
linux: 4.6 kernel fails to boot on
So I can confirm that above patch cherry picked into 4.6 allows to boot
and configure multipath devices again (as long as there is not that
UNIX=m thing in which case there won't be any disks to multipath on).
--
You received this bug notification because you are a member of Kernel
Packages,
Or maybe not as 4.6 seems to fix that race. Though I found one change in
the ALUA handler post 4.6 which modifies the handling of missing VPD
identification (which leads to the "No device descriptors found"
message):
commit fe8b9534a0a0356f8a76467e2c561194bdb53c84
Author: Hannes Reinecke
Comparing that to the working 4.4 kernel it looks like device handler
fails to receive valid data. The info should look like this:
[1.653229] sd 0:2:0:0: alua: supports implicit TPGS
[1.653395] sd 0:2:0:0: alua: port group c339 rel port c339
[1.653426] sd 0:2:0:0: alua: rtpg failed
Initial data gathered:
- The base disks seem present
- The multipath modules, too (afaiks)
dm_round_robin
dm_multipath
dm_round_robin
scsi_dh_alua
- Trying to manually create the multipath mappings fails
somewhere related to the ALUA device handler.
[ 526.285984] sd 0:2:0:0: alua:
6 matches
Mail list logo
