Arch Linux

zerophase

Member

Registered: 2015-09-03

Posts: 239

Unable to boot after cloning from AHCI ssd to NVME ssd.

I cloned all of my partitions over to the nvme ssd, changed their UUIDs to something unique. I'm able to boot up fine with the fallback initramfs, but I cannot find the root partitions UUID on the normal initramfs. I even regenerated each of my kernels with mkinitcpio, after booting with the fallback.

Mkinitcpio.conf has these for the modules:

MODULES="ext4 sd_mod ahci ehci_pci xhci_pci nvidia nvidia_modeset nvidia_uvm nvidia_drm nvme"

In refind.conf I have:

menuentry "Arch CK nvme" {
	icon \EFI\refind\themes\rEFInd-minimal\icons\os_arch.png
	volume BOOT
	loader vmlinuz-linux-ck
	initrd initramfs-linux-ck.img
	options "rw root=UUID=820ef439-3938-4cb7-b6bc-5ffc66801817 rootfstype=ext4 audit=0 initrd=intel-ucode.img quiet loglevel=3 udev.log-priority=3 rootflags=noatime,data=ordered nvidia-drm.modeset=1"
	submenuentry "Boot using fallback initramfs" {
		initrd initramfs-linux-ck-fallback.img
	}
}

lsblk -f gives me:

nvme0n1
├─nvme0n1p1 vfat   BOOT          DA02-34EA                            /boot
├─nvme0n1p2 swap   SWAP          0c5f818f-f5c4-41d5-ab23-4d33211df8f6 [SWAP]
├─nvme0n1p3 ext4   ROOT          820ef439-3938-4cb7-b6bc-5ffc66801817 /
├─nvme0n1p4 ext4   VAR           9a6f4b05-fb7b-4f82-a1b1-056e78c0ae50 /var
├─nvme0n1p5 ext4   OPT           4adaf776-2c62-4c34-94ee-4695817fa45c /opt
└─nvme0n1p6 ext4   HOME          b2895641-563e-4a51-a549-caba8c61fc3d /home

pastebin of additional commands

EDIT: If I add keyboard support to my initramfs, and exit I manage to continue booting successfully.

I get the same result booting on any other kernel. Any ideas?

Last edited by zerophase (2017-02-02 01:23:58)

zerophase

Member

Registered: 2015-09-03

Posts: 239

Re: Unable to boot after cloning from AHCI ssd to NVME ssd.

Alright, I had to enable CONFIG_BLK_DEV_NVME_SCSI to boot without udev. After a couple of test boots, I noticed I wasn't always able to boot up successfully without udev, so added udev back. Is there anyway to consistently boot an nvme disk without udev being required?

Last edited by zerophase (2017-02-02 02:43:06)