[Bug 1733276] [NEW] Cannot resize partitions on NVME devices due to bad device name parsing

[Trent Lloyd]

Public bug reported:

It is not possible to resize NVME partitions in the Ubiquity installer.
This appears to affect multiple filesystem types including NTFS and
ext4.

NVME devices have an unusual device format, specifically e.g.
/dev/nvme0n1p1 that has two 'sections' that potentially look like
partitions.

Based on the error message, it seems that this device name is being
parsed incorrectly and it attempts to use the device path /dev/nvme0n1
instead of /dev/nvme0n1p1

You can test this using qemu and a virtual NVME device.  If you toggle
the same device/partition between a virtual SCSI/IDE and an NVME device
- the issue appears and disappears.

Commands you can use to replicate the issue - unpack netboot.tar.gz into
the local directory and then

dd if=/dev/zero of=nvme.disk bs=1M count=16384

NVME:
qemu-system-x86_64 -drive file=nvme.disk,if=none,id=drv0,format=raw -device nvme,drive=drv0,serial=foo -enable-kvm -smp 2 -m 1024 -kernel xenial/ubuntu-installer/amd64/linux -initrd xenial/ubuntu-installer/amd64/initrd.gz

SCSI:
qemu-system-x86_64 -drive file=nvme.disk,if=none,id=drv0,format=raw  -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drv0,id=virtio-disk0,bootindex=1  -enable-kvm -smp 2 -m 1024 -kernel ubuntu-installer/amd64/linux -initrd ubuntu-installer/amd64/initrd.gz

** Affects: debian-installer (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1733276

Title:
  Cannot resize partitions on NVME devices due to bad device name
  parsing

Status in debian-installer package in Ubuntu:
  New

Bug description:
  It is not possible to resize NVME partitions in the Ubiquity
  installer.  This appears to affect multiple filesystem types including
  NTFS and ext4.

  NVME devices have an unusual device format, specifically e.g.
  /dev/nvme0n1p1 that has two 'sections' that potentially look like
  partitions.

  Based on the error message, it seems that this device name is being
  parsed incorrectly and it attempts to use the device path /dev/nvme0n1
  instead of /dev/nvme0n1p1

  You can test this using qemu and a virtual NVME device.  If you toggle
  the same device/partition between a virtual SCSI/IDE and an NVME
  device - the issue appears and disappears.

  Commands you can use to replicate the issue - unpack netboot.tar.gz
  into the local directory and then

  dd if=/dev/zero of=nvme.disk bs=1M count=16384

  NVME:
  qemu-system-x86_64 -drive file=nvme.disk,if=none,id=drv0,format=raw -device nvme,drive=drv0,serial=foo -enable-kvm -smp 2 -m 1024 -kernel xenial/ubuntu-installer/amd64/linux -initrd xenial/ubuntu-installer/amd64/initrd.gz

  SCSI:
  qemu-system-x86_64 -drive file=nvme.disk,if=none,id=drv0,format=raw  -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drv0,id=virtio-disk0,bootindex=1  -enable-kvm -smp 2 -m 1024 -kernel ubuntu-installer/amd64/linux -initrd ubuntu-installer/amd64/initrd.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1733276/+subscriptions