Problems with my Dual Boot after Installation

Hey erverybody, i switched from Nobara to Bazzite to couple of days ago. I have Bazzite on my NVME and have a Win10 Installation on a Old SSD in my Case. With nobara i always had the option to boot in nobara or in win10. now this option just disappeared. Bazzite sees the device, but i cant start from it.
11 Replies
wolfyreload
wolfyreload•2d ago
Open the terminal and run ujust regenerate-grub and see if it picks up your Windows install. If it does, your next reboot will give you the option to boot Windows or Bazzite
billy
billyOP•2d ago
i did it, restarted my system but it doesnt changed anything. is it possible that i messed up with something while installing bazzite? i cleared my whole nvme, just to have a fresh restart
wolfyreload
wolfyreload•2d ago
Are you able to boot into Windows from the BIOS? Might be worth running sudo fdisk -l and seeing is you can see all your Windows partitions My setup looks like this, I have a shared EFI and I can see the Windows partitions in /dev/nvme0n1p2 and /dev/nvme0n1p3.
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 534527 532480 260M EFI System
/dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved
/dev/nvme0n1p3 567296 382925454 382358159 182.3G Microsoft basic data
/dev/nvme0n1p4 997326848 999682047 2355200 1.1G Windows recovery environment
/dev/nvme0n1p5 999682048 1000214527 532480 260M Windows recovery environment
/dev/nvme0n1p6 382926848 385023999 2097152 1G Linux extended boot
/dev/nvme0n1p7 385024000 631402495 246378496 117.5G Linux filesystem
/dev/nvme0n1p8 631402496 997326847 365924352 174.5G Linux filesystem
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 534527 532480 260M EFI System
/dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved
/dev/nvme0n1p3 567296 382925454 382358159 182.3G Microsoft basic data
/dev/nvme0n1p4 997326848 999682047 2355200 1.1G Windows recovery environment
/dev/nvme0n1p5 999682048 1000214527 532480 260M Windows recovery environment
/dev/nvme0n1p6 382926848 385023999 2097152 1G Linux extended boot
/dev/nvme0n1p7 385024000 631402495 246378496 117.5G Linux filesystem
/dev/nvme0n1p8 631402496 997326847 365924352 174.5G Linux filesystem
billy
billyOP•2d ago
no, thats the thing that confuses me most. in the past i could push F11 and choose the disk i wanna boot from. now i realized i just can see the disk in the partionsmanager, but not in my fileexplorer. i probably deleted more than i should have. i just copy this disk and reinstall windows after the holidays. even with fdisk the device isnt there oh, sorry. fdisk shows the device like this: Device Start End Sectors Size Type /dev/sda1 2048 488396799 488394752 232,9G EFI System the whole fdisk looks like this Disk /dev/sda: 232,89 GiB, 250059350016 bytes, 488397168 sectors Disk model: Samsung SSD 840 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 24CC0A96-7BF6-4874-B32F-8FF35B496DE4 Device Start End Sectors Size Type /dev/sda1 2048 488396799 488394752 232,9G BIOS boot Disk /dev/nvme0n1: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: Samsung SSD 980 PRO 1TB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E5C07F37-6E11-4541-8F64-93EB81CC1E41 Device Start End Sectors Size Type /dev/nvme0n1p1 2048 1230847 1228800 600M EFI System /dev/nvme0n1p2 1230848 3327999 2097152 1G Linux extended boot /dev/nvme0n1p3 3328000 1953523711 1950195712 929,9G Linux filesystem Disk /dev/zram0: 4 GiB, 4294967296 bytes, 1048576 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
wolfyreload
wolfyreload•2d ago
I think I can see your issue. In your BIOS see if you have an option of EFI with CSM Legacy mode because it looks like you might have legacy boot enabled for Windows. See if that makes Windows bootable
billy
billyOP•17h ago
i have this option, but the system wont boot. i have no idea, when i booted it the last time. maybe the problem exists a long time and the installation of bazzite wasnt the tipping point. i have no idea. i take the ssd out and put it in a case. so i dont lose the data. after my christmas holiday i will buy a second NVME and put windows there. but before i start such a thing: should i install bazzite, or windows first? i would like to have a boot loader, to choose which one a wanna start. but the standard option should be bazzite.
wolfyreload
wolfyreload•17h ago
I usually run ujust regenerate-grub and then I can select between Bazzite and Windows from the grub boot menu. In your setup with both on different disks, you can install either one first. However, when you install Windows, unplug all other drives, as Windows likes to put it's EFI partition on the first drive that it finds rather than the drive that you install it on. Do the same with Bazzite and unplug the other drive. That way you are guaranteed to not have a shared EFI partition or either install messing with the other install. Have much less issues this way
billy
billyOP•17h ago
ok, thanks. so i will install both with only one connected. sound like a solid idea to stop anyone from messing around with the other one. and i change my bios to uefi again?
wolfyreload
wolfyreload•17h ago
Yeah when you do the installation, make sure that you only allow EFI boot. That will also save you from ending up with Windows or Bazzite installed with CSM
billy
billyOP•17h ago
okay. thanks a lot for the help. i will try this in the new year. when i ran into problems i will come by again. have a good time with christmas and hopefully not to much family trouble
wolfyreload
wolfyreload•17h ago
Thank you! You too 🙂

Did you find this page helpful?