NUC7i3BNK安装AMD64 Ubuntu Core16遇'unable to resolve LABEL=writable'错误

I’ve run into this exact issue with older Ubuntu Core versions on NVMe-equipped NUCs before. The core problem here is that Ubuntu Core 16 relies on partition labels to mount critical filesystems, but early NVMe support in its kernel/initramfs can struggle with label detection, or the label might not have been properly applied during your manual copy process. Here’s how to fix it step by step:

Step 1: Boot back into your live environment and mount the NVMe partitions #

First, get back into the live Ubuntu session you used to copy the image. Then:

• List your disks to identify the NVMe device (it’ll look like /dev/nvme0n1):

  lsblk
  

• Mount the main Ubuntu Core system partition (replace /dev/nvme0n1p2 with your actual partition from the lsblk output):

  sudo mount /dev/nvme0n1p2 /mnt
  

• If you’re using UEFI boot (which you almost certainly are on a NUC7), mount the EFI partition too:

  sudo mount /dev/nvme0n1p1 /mnt/boot/efi
  

Step 2: Switch to the chroot environment and fix filesystem references #

Instead of relying on labels (which NVMe might not pick up), use UUIDs for more reliable mounting:

• Enter the chroot to work directly on your installed system:

  sudo chroot /mnt
  

• Get the UUID of your "writable" partition using blkid—look for the line corresponding to your system partition, note the UUID= value:

  blkid
  

• Edit the /etc/fstab file to replace the label reference with the UUID:

  nano /etc/fstab
  

  Find the line that looks like:

  LABEL=writable / writable defaults 0 0
  

  Replace it with:

  UUID=your-partition-uuid-here / writable defaults 0 0
  

• Update the GRUB boot parameters to use the UUID instead of the label:
  Edit /etc/default/grub:

  nano /etc/default/grub
  

  Find the GRUB_CMDLINE_LINUX line and replace root=LABEL=writable with root=UUID=your-partition-uuid-here. Then update GRUB:

  update-grub
  

Step 3: Ensure NVMe drivers are included in the initramfs #

Ubuntu Core 16’s default initramfs might not include the NVMe driver by default, which can cause detection issues early in boot:

• Still in the chroot, edit the initramfs modules list:

  nano /etc/initramfs-tools/modules
  

  Add this line at the bottom:

  nvme
  

• Update the initramfs to include the driver:

  update-initramfs -u
  

Step 4: (Optional) Verify or set the partition label #

If you’d prefer to stick with using labels instead of UUIDs, make sure the label is correctly applied:

• Exit the chroot first:

  exit
  

• Set the label on your system partition (replace /dev/nvme0n1p2 with your actual partition):

  sudo e2label /dev/nvme0n1p2 writable
  

  Note: This only works for ext4 filesystems, which Ubuntu Core uses for the writable partition.

Once you’ve completed these steps, unmount the partitions:

sudo umount /mnt/boot/efi
sudo umount /mnt

Reboot your NUC, and it should now properly detect the writable partition and proceed to the Ubuntu Core configuration screen.

内容的提问来源于stack exchange，提问作者Peter Smith