Announcement

Collapse
No announcement yet.

Issues With a new install on dual boot

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [SOLVED] Issues With a new install on dual boot

    I find it quite queer and odd that I'm stuck and stumbling over a new dual boot install. I've done too many installs to keep track of the number and I'm wondering if I had taken something for granted: The fact that you're always asked on which partition or drive you'd want to place the boot loader. For once, the installer doesn't ask so I assumed putting the flag boot/efi to the efi partition would suffice. Alas, nope. When the install finishes and I reboot, Windows loads. I have to manually press the boot key to get a boot menu but I'm thrown to a grub prompt afterwards. Could it be the option was removed or my iso download got corrupted somehow? The checksum says it's fine so I'm thrown a loop. Of course, there a few things that I didn't say like choosing manually partitioning as that's the ONLY option that allows for encryption. Any help would be appreciated.
    Challenges are what that keeps us from the borderline of boredom in life's journey. Linux user no. 419401 currently running Kubuntu 24.04
    _______________________________________________
    Current System: Beelink Mini PC, AMD Ryzen 7 5800H 8 Core(Up to 4.4GHz), 32GB DDR4 RAM 1TB NVME M.2 SSD, SER5 MAX Mini Desktop Computer with TCL BeyondTV5 serving as my monitor. ​

    #2
    You set the mount point to be /boot/efi, but did you actually set the flag?

    Click image for larger version

Name:	Screenshot_20260214_210050.png
Views:	0
Size:	46.0 KB
ID:	690426

    And I see this here:


    Click image for larger version

Name:	Screenshot_20260214_210558.png
Views:	0
Size:	105.2 KB
ID:	690427

    Granted, I don't have a Windows install that can be used to test with, but this has been the same options I have seen when I do.
    Self-built: Asus PRIME B550M-K/Ryzen 5600GT/32Gb/Intel ARC B580 12Gb/KDE neon
    HP Elitedesk 800 G3 Mini: i5-7500T(35w)/32Gb/KDE Linux
    HP Chromebook 14: i5-1135G7/8Gb/512Gb SSD/KDE neon

    Comment


      #3
      Originally posted by claydoh View Post
      You set the mount point to be /boot/efi, but did you actually set the flag?

      Click image for larger version  Name:	Screenshot_20260214_210050.png Views:	0 Size:	46.0 KB ID:	690426

      And I see this here:


      Click image for larger version  Name:	Screenshot_20260214_210558.png Views:	0 Size:	105.2 KB ID:	690427

      Granted, I don't have a Windows install that can be used to test with, but this has been the same options I have seen when I do.
      Thanks Claydoh, but I had manually shrunk the partition before that using 3rd party tools under windows. I only had the efi partition (which I had enlarged after Windows set up). Windows recovery partition, the Windows installation and the freed space.
      I'm guessing I'd have to re-extend the partition if that's the case. I'm guessing that's a safer way around it.
      Attached Files
      Last edited by Princey; Yesterday, 09:30 PM.
      Challenges are what that keeps us from the borderline of boredom in life's journey. Linux user no. 419401 currently running Kubuntu 24.04
      _______________________________________________
      Current System: Beelink Mini PC, AMD Ryzen 7 5800H 8 Core(Up to 4.4GHz), 32GB DDR4 RAM 1TB NVME M.2 SSD, SER5 MAX Mini Desktop Computer with TCL BeyondTV5 serving as my monitor. ​

      Comment


        #4
        So, did you set the boot flag in the installer?


        Self-built: Asus PRIME B550M-K/Ryzen 5600GT/32Gb/Intel ARC B580 12Gb/KDE neon
        HP Elitedesk 800 G3 Mini: i5-7500T(35w)/32Gb/KDE Linux
        HP Chromebook 14: i5-1135G7/8Gb/512Gb SSD/KDE neon

        Comment


          #5
          Originally posted by claydoh View Post
          So, did you set the boot flag in the installer?

          I did, but it didn't work. Tried it again, no result. Had to end up extending the partition that I shrank, reboot, then let the installer shrink the partition by itself. Found out after that with the installer handling everything, a new 4GB partition was created by the installer labelled kubuntu_2510 and flag set to boot only. Previously, I had the efi partition set to boot/efi and boot. Not sure if that was the issue. Will take some time and learn more about flags and partitioning later on.
          Challenges are what that keeps us from the borderline of boredom in life's journey. Linux user no. 419401 currently running Kubuntu 24.04
          _______________________________________________
          Current System: Beelink Mini PC, AMD Ryzen 7 5800H 8 Core(Up to 4.4GHz), 32GB DDR4 RAM 1TB NVME M.2 SSD, SER5 MAX Mini Desktop Computer with TCL BeyondTV5 serving as my monitor. ​

          Comment


            #6
            Do you know about efibootmgr? Running it from the live USB should show where each boot entry goes. Unfortunately the output is not easy to understand, at least I find it so.

            Getting a grub prompt like that suggests that UEFI has found EFI/ubuntu/grubx64.efi somewhere, but that the grub.cfg there points to somewhere without /boot/grub, or somewhere that doesn't exist.

            Is secure boot enabled? I wonder if you're trying to do an install that secure boot doesn't like.
            Regards, John Little

            Comment

            Users Viewing This Topic

            Collapse

            There are 0 users viewing this topic.

            Working...
            X