Dual boot error
I have 2 boots on a legion when I join using the boot manager. I get the screen of need authenticate and then when I restart and go again I have the grub asking the os tree 0 didn't work but the 1 yes how can I solve that
Solution
I was having a problem where GRUB showed two Bazzite entries:
Bazzite (ostree:0) → broken (booted into emergency mode)
Bazzite (ostree:1) → working
To fix it, I removed the corrupted OSTree deployment.
Here’s exactly what I did:
1. Booted into the working deployment
Selected:
Bazzite (ostree:1)
so I could login normally
2. Checked the current deployments
sudo ostree admin status
It showed:
a broken .0 deployment (pending)
a good .1 deployment (active)
3. Deleted the corrupted deployment
sudo ostree admin undeploy 0
This removed the broken version and automatically updated the bootloader.
4. Verified the system
sudo ostree admin status
Now only the good deployment .1 remained.
5. Rebooted
After rebooting, GRUB displayed only the working entry:
Bazzite (ostree:1)
The broken entry (ostree:0) is gone, and the system boots normally again.
If anyone runs into the same issue:
Just boot into the good deployment and run sudo ostree admin undeploy 0. It cleans everything up.
Bazzite (ostree:0) → broken (booted into emergency mode)
Bazzite (ostree:1) → working
To fix it, I removed the corrupted OSTree deployment.
Here’s exactly what I did:
1. Booted into the working deployment
Selected:
Bazzite (ostree:1)
so I could login normally
2. Checked the current deployments
sudo ostree admin status
It showed:
a broken .0 deployment (pending)
a good .1 deployment (active)
3. Deleted the corrupted deployment
sudo ostree admin undeploy 0
This removed the broken version and automatically updated the bootloader.
4. Verified the system
sudo ostree admin status
Now only the good deployment .1 remained.
5. Rebooted
After rebooting, GRUB displayed only the working entry:
Bazzite (ostree:1)
The broken entry (ostree:0) is gone, and the system boots normally again.
If anyone runs into the same issue:
Just boot into the good deployment and run sudo ostree admin undeploy 0. It cleans everything up.
