I’m going nuts here. I hope dual boot questions are ok here.

For backstory, I was dual booting windows 10 and linux mint. Things were fine, until I think when windows was trying to update and on a restart it went to linux, and afterwards I wasn’t able to boot up windows. I tried repairing windows with a usb but that was giving me hell about drivers, so I just wiped that hdd and installed windows fresh. Worked fine, got to play a game on there which was why I wanted to get back on windows, lol, all good.

UNTIL, I try to boot back to linux. Getting the grub screen, everything I’m seeing online about setting root to the harddrive where grub is was not working. Back to my tried and true method of wiping it all and starting fresh. I wipe it, get a new linux usb iso, boot into it, install linux, it says to remove media and hit enter to continue. I do that. reboot, get this zoomed in grub window where I can’t type at all.

So I’m on windows, trying to hope someone here has had this happen before and knows what I’m missing or what I did wrong because this is really making me crazy.

  • Presi300@lemmy.worldEnglish
    2·
    8 months ago

    Yeah, windows tends to sometimes nuke grub when it updates, if they are in the same drive. I’ve found that the easiest way to fix it is to chroot into the Linux system from a live iso, re-install grub and re-make it’s config…

    As for preventing this from happening again, the dumb way would be to use something like AtlasOS, ReviOS or Chris Titus’s windows deboating script and disabling Windows update entirely.

    The smart way would be to move Linux, grub and grub’s EFI partition to a separate disk all together… That way windows has a harder time nuking them (though it still does it sometimes).

    And no, this issue is not grub specific, windows can and will occasionally nuke any other bootloader when it updates…

  • Blaster M@lemmy.worldEnglish
    1·
    9 months ago

    First off, how old is your hardware? Are you using EFI or MBR when booting? To check that, go into your “bios” setup on the motherboard and see if CSM (compatability support module) is enabled - if so, it may be best to have that disabled and go full EFI. This will save you a lot of headaches with the multiboot menagerie.

    Second, are you using two disk drives? Or are you using multiple partitions on the same disk? The best way (read: least likely to muck up) is to have Windows and Linux on separate drives, with the only shared partition being the EFI Boot partition (which is fine and intentional).

    To use EFI boot, your disks need to be GPT formatted.

    Install Windows 10 first, then install Mint. If done right, you can switch which OS you want to boot in your ‘bios’ or firmware setup should Windows assert dominance again. Mint’s boot loader should detect the Windows bootloader and boot Windows if chosen as well.

    • remotedevOPEnglish
      1·
      9 months ago

      I messed with the CSM settings, and then didn’t see the disk with Linux at all to boot lmao. After awhile it did show up again, still to the broken grub screen where I can’t type. I feel like I’m stuck with windows for the time being

      • Blaster M@lemmy.worldEnglish
        2·
        9 months ago

        You may have to enable Legacy USB support to get the bootloader working. To clarify, Mint showed up with CSM Enabled or Disabled? If it showed up when Enabled, you may have inadvertently installed Mint using MBR / BIOS method instead of GPT / UEFI method. You will want to rectify that by redoing Mint install disk and the install as a GPT/UEFI setup. CSM should be Disabled.

    • remotedevOPEnglish
      1·
      9 months ago

      I did do separate drives this time hoping to avoid what happened before. I believe I’m using EFI but I’ll double check and check the CSM is enabled. Thanks

  • CorneliusTalmadge@lemmy.worldEnglish
    1·
    9 months ago

    I am sure there are plenty of people with more technical knowledge on the subject, but I had something similar happen not too long ago.

    My issue was in the bios on my laptop had secure boot enabled which wouldn’t allow gnu/linux to boot.

    Caused me a huge headache. But after I disabled it and went through the install with the USB again it booted right up. Might be worth checking.

    • remotedevOPEnglish
      1·
      9 months ago

      I’ll go look for that setting, thanks!

    • remotedevOPEnglish
      1·
      9 months ago

      It’s just a big GRUB with the flashing icont to type, yet I can’t type anything

      • jackoneill@lemmy.worldEnglish
        1·
        9 months ago

        Google super grub 2 - it’s a live CD with a version of grub that can boot just about anything, and you can overwrite your grub with it.

        I don’t bother with that though, on my dual boot setup if I want to play a game I f12 and pick windows manually, otherwise just boot to Linux. Easier that way

  • vivavideri@lemmy.worldEnglish
    1·
    9 months ago

    I am a heathen in the eyes of the hackintoshers because I use clover bootloader. Grub is cool and all but clover has themes. I’ve also got it set to not automatically boot, I’ve got to select os upon powering up.