Additional info: $ sudo multipath -ll mpath2 (1IBM IPR-0 5EC2A900000000A0) dm-2 IBM,IPR-0 5EC2A900 size=264G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw |-+- policy='round-robin 0' prio=130 status=active | `- 0:2:2:0 sdc 8:32 active ready running `-+- policy='round-robin 0' prio=10 status=enabled `- 1:2:2:0 sdi 8:128 active ready running mpath1 (1IBM IPR-0 5EC2A90000000060) dm-1 IBM,IPR-0 5EC2A900 size=264G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw |-+- policy='round-robin 0' prio=130 status=active | `- 0:2:1:0 sdb 8:16 active ready running `-+- policy='round-robin 0' prio=10 status=enabled `- 1:2:1:0 sdh 8:112 active ready running mpath0 (1IBM IPR-0 5EC2A90000000080) dm-0 IBM,IPR-0 5EC2A900 size=264G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw |-+- policy='round-robin 0' prio=130 status=active | `- 0:2:0:0 sda 8:0 active ready running `-+- policy='round-robin 0' prio=10 status=enabled `- 1:2:0:0 sdg 8:96 active ready running mpath5 (1IBM IPR-0 5EC2A90000000020) dm-5 IBM,IPR-0 5EC2A900 size=264G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw |-+- policy='round-robin 0' prio=130 status=active | `- 0:2:5:0 sdf 8:80 active ready running `-+- policy='round-robin 0' prio=10 status=enabled `- 1:2:5:0 sdl 8:176 active ready running mpath4 (1IBM IPR-0 5EC2A900000000C0) dm-4 IBM,IPR-0 5EC2A900 size=264G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw |-+- policy='round-robin 0' prio=130 status=active | `- 0:2:4:0 sde 8:64 active ready running `-+- policy='round-robin 0' prio=10 status=enabled `- 1:2:4:0 sdk 8:160 active ready running mpath3 (1IBM IPR-0 5EC2A90000000040) dm-3 IBM,IPR-0 5EC2A900 size=264G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw |-+- policy='round-robin 0' prio=130 status=active | `- 0:2:3:0 sdd 8:48 active ready running `-+- policy='round-robin 0' prio=10 status=enabled `- 1:2:3:0 sdj 8:144 active ready running
After installation via maas , system hung with the boot log attached as 'console boot from wily (boot hangs)'. I then did and ipmi reset and it came up this time. system is currently up in this kernel and Stefan's ssh keys should be able to get in as 'ubuntu' user. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1462530 Title: multipath errors on vivid and wily kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462530/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
