Nothing has changed here. I do have a branch in review that should help
but it broke other vmtests in obscure ways. Now Jenkins is usable again,
I guess I/someone should take a look at it again...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
So much time has past ...
@Michael - do you think this would work (despite the bad devices having the
same id) better nowadays?
I think I can drop the Hirsute tasks :-)
ALso it isn't a probert/curtin/multipath bug if the reported IDs are the same.
Keeping the subiquity task open, but only to cons
I think there is no doubt that Matthias's disks are bad and the default
behaviour is OK, but I would hope that disabling multipath via the
kernel would allow an installation as desired. But it seems curtin
doesn't quite work this way. Part of the issue IIRC is that the curtin
multipath support does
*via the kernel command line
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902855
Title:
two identical disks are only offered as a multipath device
To manage notifications about this bug go to:
ht
based on multipath & installer logs things look okish.
nvme0n1 & nvme2n1 is multipathed Force MP600 NVMe drive
eui.6479a73730830210, which is assembled into mpatha drive (also dm-0)
nvme1n1 is another NVMe drive Seagate FireCuda 520 SSD ZP2000GM30002
eui.0024cf01540022a8
sdc is the usb stick wit
curtin has:
def multipath_assert_supported():
""" Determine if the runtime system supports multipath.
returns: True if system supports multipath
raises: RuntimeError: if system does not support multipath
"""
missing_progs = [p for p in ('multipath', 'multipathd')
> The intent is that what mulitpath-tools does on boot is reflected
> in the installer. If it is disabled by kernel command line or
> whatever, the disks should not be multipathed. It's possible this
> is not what happens, but it's not by design.
yes, that's what is not working. with multipath dis
$ cat /sys/block/nvme[02]n[0-9]/{nguid,eui}
cat: '/sys/block/nvme[02]n[0-9]/nguid': No such file or directory
64 79 a7 37 30 83 02 10
64 79 a7 37 30 83 02 10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
On Thu, 5 Nov 2020 at 21:35, Matthias Klose <1902...@bugs.launchpad.net>
wrote:
> see also LP: #1871611, failing the install with disabled multipath.
>
That bug looked very much like the kernel losing its mind. Are you saying
you can reproduce it?
> However multipath is hard wired into the inst
When both drives connected could you please paste the output of
$ cat /sys/block/nvme[0-9]n[0-9]/{nguid,eui}
https://nvmexpress.org/wp-content/uploads/NVM-Express-
1_4b-2020.09.21-Ratified.pdf
As per ratified NVMe 1.4b specification, in figure 249 Identity
Namespace Data Structure the nguid and/
** Also affects: multipath-tools (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: curtin (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: probert (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: subiquity (Ubu
> eui64 being identical sounds like a violation of NVMe spec!
pointer please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902855
Title:
two identical disks are only offered as a multipath device
** Tags added: fr-898
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902855
Title:
two identical disks are only offered as a multipath device
To manage notifications about this bug go to:
https://b
eui64 being identical sounds like a violation of NVMe spec!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902855
Title:
two identical disks are only offered as a multipath device
To manage notific
see also LP: #1871611, failing the install with disabled multipath.
You find several more reports about multipath being problematic, and
usually you can work around the issue by disabling multipath support on
boot by not loading the module. However multipath is hard wired into the
installer.
I'll
$ sudo nvme id-ns /dev/nvme0n1 | grep eui64
eui64 : 6479a73730830210
$ sudo nvme id-ns /dev/nvme2n1 | grep eui64
eui64 : 6479a73730830210
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902855
Titl
So this is more a bug in multipath-tools then? I mean subiquity _could_
grow a feature for disabling multipath but I'd really rather not unless
this breakage is common.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
no, personal machine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902855
Title:
two identical disks are only offered as a multipath device
To manage notifications about this bug go to:
https://bu
I know I have asked in IRC, but want to avoid forgetting it.
Is that a system of yours or is it in a computing center we might get access
for debugging?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
$ sudo nvme list
Node SN Model
Namespace Usage Format FW Rev
- -- -
> There people also used dm-multipath.blacklist=1 to get around
> it as you mentioned that works for you as well right?
No, as mentioned in the bug description. the installer still seems to
call multipath and multipathd commands which then fail.
--
You received this bug notification because you
Maybe have a look with
sudo apt install nvme-cli
If you can get any "bad same ID" off these devices?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902855
Title:
two identical disks are only offer
Maybe the same as https://bugs.centos.org/view.php?id=16893 ?
There people also used dm-multipath.blacklist=1 to get around it as you
mentioned that works for you as well right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
So here we see multipath is indeed considering it to be one disk:
mpatha (eui.6479a73730830210) dm-0 NVME,Force MP600
size=932G features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=0 status=active
| `- 0:1:1:1 nvme0n1 259:0 active undef running
`-+- polic
** Attachment added: "installer-logs.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1902855/+attachment/5431017/+files/installer-logs.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Attachment added: "multipath.log"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1902855/+attachment/5431016/+files/multipath.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902855
$ cat /sys/block/nvme0n1/device/model
Force MP600
$ cat /sys/block/nvme2n1/device/model
Force MP600
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902855
Title:
two iden
With multipath running in the install environment how does e.g. "sudo multipath
-ll -v 3" look like?
You'd usually expect all multipath devices to be listed with path and ID e.g.:
mpatha (36005076306ffd6b6240a) dm-3 IBM,2107900
size=10G features='1 queue_if_no_path' hwhandler='1 alua'
Maybe also report:
/sys/block/sda/device/[vendor,model,vendor,model}
and
sudo hdparm -i /dev/sd*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902855
Title:
two identical disks are only offered
** Description changed:
two identical SSDs are only offered as a multipath device in the server
installer, not as single devices. The install succeeds, however the
following boot falls back to the initramfs because the volume group
cannot be found. Same hardware configuration as in LP: #19
On bug LP: #1902845 you have had attached the install tgz which contains
cloud-init/curtin/subiquity logs.
Could you attach the same here so that it can be checked why it is behaving the
way it is.
Also required to be able to decide which component we are actually looking at
for the issue.
** A
Also - are these really two SSDs - or one SSD over two paths?
Eventually that is the problem some component of the install fails on, do you
happen to know the box what it really physically is in this case?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
32 matches
Mail list logo
