Not booting from NVMe after booting from another disk

  • I just booted CloneZilla from USB and cloned the NVMe disk to a 4TB HDD.


    Then I booted from the HDD and everything seemed to be ok.
    I noticed the NVMe was still be used for booting.

    Bash
    $ mount | grep boot
    /dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)

    So I removed the NVMe to check if the HDD would still boot on its own.
    It does. Great.


    But after reinstalling the NVMe I cannot from it.

    Code
    Reboot and Select proper Boot device
    or Insert Boot Media in selected Boot device and press a key

    I can still boot from HDD.


    I guess booting from HDD after cloning did overwrite something in /dev/nvme0n1p1.
    But what? How can I fix this?


    And how can I prevent this "deconstructive behaviour" in the future?
    I guess I have to edit the Grub config after cloning it from the NVMe?!



    My goal is to clone/copy/rsync the content of the system partition to the HDD for redundancy.



    btw: Still experimenting with my new system.

  • While d152af9f-df83-4ed6-ab85-68b7be3adbc7 is pointing to sda2



    I think I would need to change the UUID in the grub.cfg to my NVMe.
    But I cannot find the UUID of the device. :(


    ls -l /dev/disk/by-uuid/ does only show sda1, sda2 and sda3.



    EDIT1:


    I just fund out that clonezilla copies the UUIDs.




    Could this be the problem?
    But I donn't think so. I already tried booting with only the NVMe attached.
    So the UIIDs should not conflict.


    EDIT2:

    SOLVED!!


    First I did sudo update-grub.
    This created new grub menu entries, because Debian was found on my NVMe.
    But that did not help.
    Next I edited the grub.cfg like discribed here:



    I found this: https://askubuntu.com/a/171469
    I deleted the search-lines and replaced the UUID with /dev/nvme0n1p1.


    Now I have to find a way to prevent this from happening again.
    Maybe changing the UUIDs...

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!