Ubuntu
linux package

  1. Bug #1902179
  2. Comment #32

Comment 32 for bug 1902179

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2021-01-15 08:35 EDT-------
(In reply to comment #82)
> Is the NVMe drive with or without nvme-multipath support?
> Does it help to disable multipath?
>
> Please see the below pullrequest from Canonical employee in efivar project
> that explains the issue a bit, and the various paths that the NVMe devices
> can have.
>
> https://github.com/rhboot/efivar/pull/158
>
> This also affected efibootmgr project for the EFI platforms with newer
> kernels, as shipped in focal.
>
> You can also try booting with the following kernel cmdline option appended
> in the param file i.e. `nvme_core.multipath=N` to get the "non-multipath
> nvme0 nodes in the sysfs".
>
> BTW
> https://www.ibm.com/support/knowledgecenter/STSLR9_8.3.1/com.ibm.fs9100_831.
> doc/svc_fc_nvme_multipathconfighosts.html has an excellent summary of nvme
> multipath situation in various distros.

Yes, multipath is the problem here. When multipath is enabled we have a different sysfs structure. I'll have to work up a fix.

Can you move ahead with the code as it is, and then we can provide a bug fix patch when ready? This chreipl bug should not impede NVMe installation or a normal boot process.