Hello, Cyril Brulebois, le ven. 23 avril 2021 23:19:08 +0200, a ecrit: > Samuel Thibault <sthiba...@debian.org> (2021-02-16): > > I was reinstalling a laptop after a NVME change, and I realized: what > > if the NVME did not have any namespace set up? The installer would then > > not recognize the disk. We would need at least the nvme command to be > > available on the text console to fix this by hand (Ideally the installer > > would even automatically propose to configure an NVME namespace). > > > > Perhaps the addition of nvme-cli-udeb would be possible for bullseye > > already? I could verify that the binary of the nvme-cli package does > > work already, so it'd be a mere matter of adding the nvme-cli-udeb > > package that just ships the /usr/sbin/nvme file. > > I have absolutely no idea what NVME namespaces are and what they are > needed for; would you have some pointers?
I don't have any particular pointer beyond stackoverflow https://unix.stackexchange.com/questions/520231/what-are-nvme-namespaces-how-do-they-work Basically they are a hardware-level partitioning, before the well-known software partitioning: /dev/nvme0n1p1 is device 0, namespace 1, partition 1. > (My only experience was a fresh install on an NVMe device replacing an > aging SSD, and I haven't had to do anything specific.) I guess usually NVMe are shipped with a default namespace spanning the whole disk, but that could be not always true. Samuel
