Problem booting NVME after cloning drive

General system Kernel, boot, graphics & hardware
1

I cloned my SATA drive to an NVME drive using dd and when I try to boot the NVME, the process hangs on “A start job is running for /dev/disk/by-uuid/”. I do not have a swap file or partition. I cannot figure out what process is not starting properly. All of the solutions I have found point to the swap file. I have used dd to clone SATA to SATA in the past and it works fine. Does this have something to do with the fact it is an NVME drive?

2

Welcome to the forum @tmilliken ,
You must edit /etc/fstab because mount points changes: /dev/sda1 (SATA SSD) must be switch to /dev/nvme0n1p1 (NVMe SSD) and so on.
If mounting is by UUID and both drive are plugged in then a new UUID should be generated
This may help

3

I did remove the old drive from the system so there wouldn’t be a conflict. I was just trying to figure out what service is hanging on boot. My other option is to install a clean system on the new drive and copy my home folder contents to the new drive if I can’t figure this out.

4

Check the UUIDs and see if they match. It is possible the UUIDs changed and need to be updated in /etc/fstab and in the bootloader.

Also, have you tried booting the fallback?

5

Do you have a live usb to boot from. If you have you could chroot into the system, check the UUID for partitions and see they are correct in fstab. Also you could update and rebuild your kernels as well.

6

I did check the uuids and they are the same. I did check the fstab and it does match the system.

7

Did booting the fallback make any difference?

8

  1. make a new UUID with the uuidgen utility :
    ‘uuidgen’
    it creates a new uuid

  2. put the new uuid into your partition/device/.. with the tune2fs command
    tune2fs -U ‘the new uuid’ /dev/…
    (maybe gparted can do it also)

  3. adapt your /etc/fstab

maybe you have to create also a new machine id with the command systemd-machine-id-setup
‘systemd-machine-id-setup’
adapt your /etc/machine-id and /var/lib/dbus/machine-id

check afterwards

  • cat /etc/machine-id
  • cat /var/lib/dbus/machine-id

if you use systemd-boot check also your /efi/loader/entries and
cp -r /efi/your old machine-id /efi/your new machine-id

change the hostname adapt also the file
/etc/hostname

9

I just tried the fallback and yes, I was able to boot with it. I just need to figure out the next step.

10

sudo reinstall-kernels

This is from EndeavorOS Wiki

The script reinstall-kernels both regenerate the initrds and create/update the boot entries. It works with both dracut and mkinitcpio as long as you have either kernel-install-for-dracut(The default) or kernel-install-mkinitcpio(AUR) installed.

11

If the fallback works, you should run sudo dracut-rebuild

12

This doesn’t work in this situation? It does a bit more that it is not needed perhaps?

13

It will work if they are running systemd-boot. dracut-rebuild will work for all bootloaders.

1 Like
14

After booting, I ran a system update and a new kernel was installed. The system booted normally, so reinstall-kernels probably would have worked. Thanks for the help.

1 Like
15

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.