Can't boot Bazzite from new drive

[Shijiale]

Hello everyone and thanks for the interest in the problem I’m having.

I’m totally new to Linux and Installed Bazzite about 2 weeks ago and everything went pretty smoothly so far.

The problem I’m having now is that I wanted to move my Bazzite installation from my 1tb SSD drive to my 1tb nvme drive.

I made a full system backup with Rescuezilla and installed this one to the nvme (which had a windows filesystem but no OS on it).

When I restarted my pc and went into the bios to choose the nvme as 1st boot drive it wasn’t available.

I therefore booted into my old drive and it gave first some weird black screen messages (see image) but ended up booting pressing ctrl+d.

After being inside I was able to see in Disks that the nvme did have Bazzite installed.

After trying to access the drive in Dolphin the system stopped responding and I wasn’t even able to shut down without pressing the power button.

I’ve read that the problem might have to do with the fstab file not using the correct drive IDs and therefore there being problems.

Does anyone have time to explain to me, step by step, for a noob, how to solve this?

Thanks in advance.

Note

Is it possible that since Bazzite is an immutable OS, that I actually can’t take an image of it, but just my data, configurations etc, and that I need to do a fresh Install of Bazzite on the new drive and then update it with the backup I made?

Note 2

I tried installing Bazzite 41 with ventoy and got this message, which seems to be the problem I thought I was having. I will format the nvme and reinstall then Bazzite on it with ventoy.

Can someone tell me how best I can transfer all data and settings from my current installation, if making an image creates problems?

[Shijiale]

Hi lostitall,

Thanks for the reply.

Is dev/sda a system folder? Wouldn’t know what to do.

I ran lsblk in the terminal and I can see all drives how they are names in Linux, with their partitions and folders.

What is dd?

I’ve already used Rescuezilla (clonezilla), but didn’t clone the disk. Just made a backup of the whole system and later ran it again to install that image on the new drive.

The problem seems to be that something about the drive naming/UUID gets messed up and therefore I can’t see the new drive as bootable.

I read using super grub2 disk could fix this, but not sure how and if I should use it.

[Shijiale]

I think my Bazzite disk drive and boot partitions are on the 3rd recognized drive (SDC)?

Nvme1n1 is the drive I installed the backup image to with no success (I formatted it shortly ago and everything is working fine again)

Should I still try to clone the drive instead of making a system backup?

I’m going to sleep in a bit, so will be replying tomorrow.

Thanks again for the help!

[Shijiale]

Hey again,

This is the result I get after cloning

After rebooting and checking the bios, as before with the image backup, I can’t see my nvme as a bootable device. But at least I don’t get that black screen message when booting in my usual drive.

I think this has to do with the fact that rescuezilla doesnt update the bootloader maybe?

Output from lsblk

[Shijiale]

Update

I have tried disconnecting the original Bazzite installation SSD and after booting and checking the bios the cloned Bazzite on the nvme drive was suddenly being recognized and I could boot it no problems.

After reattaching the SSD and booting the nvme boot drive disappeared and only the SSD boot drive was available

I guess the BIOS is not able to see 2 Bazzite OS on 2 different drives simultaneously? Or is there maybe a BIOS setting preventing that?

I am able to see my windows OS drive, which is on another nvme drive, and boot from it no problems.

Note

I know I could boot ventoy with Bazzite boot media and format the SSD so it doesn’t interfere with the nvme, but I’d like to keep both installations and both drives attached.