Not sure if this is the right place to ask or if anyone can help me, but today, I installed the ubuntu ISO & converted it to a bootable format on an 128GB SD card (All my USBs are too small) I ran the installer as normal & here’s where I think I messed up. I allocated a 27GB partition for linux but that option didnt apper on the installer upon being asked where to install to. Thinking nothing of it, I ran the installer clicking on the install to drive option & halfway through it failed saying something like Error16 Drive is busy & the installation was only half done. now on attempt to restart windows is completely gone & all I can do is boot up a very fragmented Ubuntu without internet & firefox works very slowly. If anyone can help, then it’s appreciated. I’ve always wanted to try Linux & just got an SD card large enough to do it, but now this happens.

  • chi-chan~@lemmy.world
    12·
    4 days ago

    Install Windows again, then install Linux.

    Windows is annoying with it’s bootloader, but when you have separate drive, it would be way smoother experience.

    • Fonzie!@ttrpg.network
      2·
      3 days ago

      Or better yet:

      • Run the live Linux environment, run gparted, wipe every partition of the disk
      • Reinstall Windows, wiping everything
      • Launch Windows, launch dskmng, shrink Windows by the needed amount (having another OS shrink it might break it)
      • Reinstall Linux, it should offer to install alongside the other system if there’s enough space
    • chi-chan~@lemmy.world
      21·
      4 days ago

      If it’s on the same drive, after updates, Windows will try to ‘fix’ that you have another OS itself, and remove GRUB.

      • rotopenguin@infosec.pubEnglish
        8·
        4 days ago

        Windows generally isn’t removing grub, it’s just switching the EFI boot priority. You can change that back in bios, or with efibootmgr.

      • Skull giver@popplesburger.hilciferous.nl
        2·
        4 days ago

        If you still use MBR, and Windows has an update to its bootloader, yeah.

        I don’t even know if Windows 11 still supports MBR, though. Maybe it’ll happen if your firmware is broken and always boots from the fallback bootloader instead of the normal boot entry? But in that case Windows is right and the firmware needs an update.