NVMe disks aren't recognized

Bug #1697695 reported by Kenny Lindberg
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cloud-initramfs-tools
Expired
Undecided
Unassigned

Bug Description

While booting on a NVMe disk it doesn't seems to be recognized as they're named:

/dev/nvme0n1
/dev/nvme1n1
/dev/nvme2n1
/dev/nvme3n1

Therefore growroot isn't run and the root partition isn't being resized.

Kenny Lindberg (kennyl)
description: updated
Revision history for this message
Scott Moser (smoser) wrote :

Hi, this is quite possible.
Can you explain more of your case ?

What is the partition table on the device? what is the kernel command line?

I'm asking because if the disk is partitioned, then bug 1236380 should have fixed this.
(in my experience, we have /dev/nvme0n1p1 for partition 1 and such).

If you're booting off an un-partitioned nvme device, then growroot does not need to do anything, it only grows partition tables.

Please give some more info and set this to New.
Sorry for the slow reply.

Changed in cloud-initramfs-tools:
status: New → Incomplete
Revision history for this message
Kenny Lindberg (kennyl) wrote :

Hello,

We've a partition table on the first disk which is the root and the only partition. This partition is named /dev/nvme0n1p1.

We boot the server from this partition but growroot isn't run.

Any suggestions?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for cloud-initramfs-tools because there has been no activity for 60 days.]

Changed in cloud-initramfs-tools:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.