Arch Linux

dominicm

Member

Registered: 2015-01-03

Posts: 92

[SOLVED]Can't boot with cloned m.2 NVME drive (LABEL=system not found)

I am trying to migrate from a sata ssd to m.2 nvme drive (Samsung 961) but it's turning into a nightmare. I created an image with ddrescue as the SSD had some bad blocks,  then restored image with Gnome disks however after unplugging sata ssd and booting from nvme drive I get the error in the image. The original sata ssd boots fine even with nvme drive installed. nvme drive appears in /dev as expected and looks like an identical clone with all partitions and labels etc.

Secure boot is or course disabled and enabling or disabling CSM makes no difference. Since arch does attempt to boot from nvme I don't believe it is a bios config issue. The DMAR errors and PTE Read access error disappear when CSM is disabled in bios.

The error complains about the system label which the root partition does have. Commenting out LABEL entry or UUID entries produces the same error while booting.

Here is my /etc/fstab:

# /dev/sda3
UUID=9f642d6d-0956-4f96-8d7c-5b4d81c51d1c      /               ext4            rw,relatime,data=ordered        0 1

# /dev/sda1
UUID=0FEB-C9F4         /boot           vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,$

# /dev/sda2
UUID=e67e5227-6e56-4c35-a73d-a0d413d52cdf      none            swap            defaults        0 0

#LABEL=system / ext4 rw,relatime,data=ordered 0 1

lsblk -f output:

NAME        FSTYPE LABEL     UUID                                 MOUNTPOINT                   
sdc                                                               
├─sdc1      vfat             0FEB-C9F4                            
├─sdc2      swap             e67e5227-6e56-4c35-a73d-a0d413d52cdf [SWAP]
└─sdc3      ext4   system    9f642d6d-0956-4f96-8d7c-5b4d81c51d1c /

nvme0n1                                                           
├─nvme0n1p1 vfat             0FEB-C9F4                            
├─nvme0n1p2 swap             e67e5227-6e56-4c35-a73d-a0d413d52cdf 
└─nvme0n1p3 ext4   system    9f642d6d-0956-4f96-8d7c-5b4d81c51d1c

/boot/loader/entries/arch.conf contents:

title   "Arch Linux VFIO"
linux   /vmlinuz-linux-vfio
initrd  /initramfs-linux-vfio.img
options root=LABEL=system rw splash intel_iommu=on pcie_acs_override=downstream

I also added "nvme" to the MODULES list in /etc/mkinitcpio and regenerated with nvme drive mounted from chroot. Again no change.

What am I doing wrong?

Last edited by dominicm (2017-01-12 15:56:01)

dominicm

Member

Registered: 2015-01-03

Posts: 92

Re: [SOLVED]Can't boot with cloned m.2 NVME drive (LABEL=system not found)

Got it to work after all, here is a list of possible causes of the issue for anyone in the same boat as me:

-Corrupt installation (due to bad blocks or something else)
-mkinitcpio -p command execute on the wrong kernel (linux instead of linux-vfio), rsyncing old and new partition may not have been enough.
-Bad permissions on on some systemd directories due to previous human error. Reinstalling udev showed differing permissions.

Last edited by dominicm (2017-01-12 15:55:38)