grub command line boots default, have to manually specify efi. How could I cange this behavior?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP


.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
0
down vote

favorite












First of all I have Kubuntu 18.04.1 LTS installed, fully updated.
It was setup using LVM & Luks Encryption



The BIOS is set to boot UEFI, SecureBoot is disabled. I've also checked all settings their and nothing seems to fix or even attempt to fix this issue.



I know what caused this issue, but dont know why. I was testing live linux distributions that offered encrypted persistence but nothing was 'that good' from what I found. I heard you can just install kubuntu directly to your usb instead of internal disk, which is what I did. I managed to boot from it but never did any diagnostics with it (such as managing or even mounting the internal disk). I wanted this so I have my installed kubuntu as daily driver, and the kubuntu as a live disk in case of system problems and for use as a a portable os.



After this though, I rebooted and took out the usb and it immediately dropped me into a grub shell (not grub rescue). The only way for me to boot computer's os, is typing 'exit' where it then takes me to screen to select boot device.
The 2 options there are 'ubuntu random characters' and 'Boot EFI File Manually'. Selecting the ubuntu boots into grub shell. Selecting boot efi file manually, then navigating to EFI/parrot/grubx64.efi is the only way to boot my os. When I ran command in terminal 'sudo efibootmgr -v' it outputs:



Timeout: 5 seconds
BootOrder: 0000,3000,2001,2002,2004
Boot0000* ubuntu HD(1,GPT,034b05b2-5d55-4e71-ac47-4932eb3edadd,0x800,0x100000)/File(EFIubuntushimx64.efi)
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot3000* Internal Hard Disk or Solid State Disk RC



after I a lot of research on google, everyone else who ran this command has a line on the top showing 'BootCurrent number' showing which one was current. I just learned this command during this issue, so I don't know what it use to show.



I was trying to find out how to change the default efi being used, like if I changed it to automatically boot EFI/parrot/grubx64.efi then my os would boot instead of grub. Although the one selected now is apparently the one supposed to be 'shimx64.efi'. If I selected this file manually in the efi screen or even the grubx64.efi in ubuntu directory it would still boot grub shell. I don't know if this file somehow got corrupted or if something is just messed up with grub. I haven't attempted re-installing grub as others have done that and just messed up their pc even worse. I have a lot of data on my computer, last backed up about a week or so ago. I just don't want to have to go through restoring it or erasing any data. I would like to know how to troubleshoot these issues the best I can to continue learning more about linux as this issue does seem fixable.



in the grub shell if i typed boot, says i need to load kernel first. I am not sure how to even do this, and couldn't find working information online for my setup



Once i type ls in grub shell it gives me partitions like (hd0) (hd0,gpt3) (hd0,gpt2) (hd0,gpt1) (cdrom)



if i try using ls (hd0)/ or ls (hd0,gpt3) it tells me unknown file system. Probably because of the encryption.
If I try ls (hd0,gpt2)/ it list folders like grub and vmlinuz files.
If I try ls (hd0,gpt1)/ it list the folders shown in the EFI menu entry i said earlier like folder EFI.



As I had to get on my pc to ask this question here, I can't also be in the grub shell. Won't have another device for a little while. So I am only explain what I know for sure, dont want to list incorrect information.



Anyone have an idea is whats going on? And maybe why booting a installed kubuntu from usb caused this issue? (When i used live distros like knoppix, puppy linux, kali...) they never caused this issue at all. One thing forgot to mention earlier, my other pc also has kubuntu now has this issue as well right after removing kubuntu usb. The problem with this pc, is that the BIOS has no manual selection of EFI file (after typing exit in grub shell, only 1 drive shown which is the ubuntu one, once selected im in grub shell and do not know how to boot without selecting the efi. Dont know many commands in grub).



I realize that in the EFI folder, there are 4 items. parrot , debian, ubuntu, boot.



parrot was the os I chose to use as a live distro, until i decided to install kubuntu on this same usb. debian I never used as live, it use to be fully installed but don't know why that would still be their as the internal drive was formatted prior to installing Kubuntu. It seems to be that the Parrot efi is whats used to boot my installed kubuntu os. I just need to get the proper efi for ubuntu to be used to boot into os instead of grub



Thank you :)







share|improve this question





















  • I always back up ESP. And any second install of Ubuntu overwrites the /EFI/ubuntu folder. Only change is /EFI/ubuntu/grub.cfg which changes to the newest installs UUID & partition. I now edit that back to my main install. But if external you need to partition in advance so you have an ESP on the external drive. UEFI only boots external drives from /EFI/Boot/bootx64.efi, but if always booting from internal drive, you can just use grub. askubuntu.com/questions/913716/… & askubuntu.com/questions/786986/boot-ubuntu-from-external-drive
    – oldfred
    2 days ago










  • I didn't think of this earlier but my backup I made about a week or 2 ago with clone zilla contains all partitions as they were then. Would restoring just the one fix this issue? I didn't know if it was considered safe to restore just single partition since my main partition containing /home has of course had new data on it since backup was made. If so, then I would need to figure out how to prevent that kubuntu usb stick from causing this issue again. Maybe that link you supplied will help. I did want to know how to manually fix this issue, in case it happens again and I don't have backup.
    – computer_guy
    2 days ago










  • While this answer is for older version and UUIDs are specific to OP, the process is the same. You need to know UUID and edit /EFI/ubuntu/grub.cfg. askubuntu.com/questions/957914/…
    – oldfred
    2 days ago










  • Ok, after looking over those post you linked to, if Im correct you mean to say that I just have to find out my install system's UUID and the edit grub.cfg with that UUID? Does that mean that the install of kubuntu on usb changed the UUID on grub locally and thats why it boots to grub shell because it can't find usb as its not plugged in?
    – computer_guy
    2 days ago










  • Yes. You can always plug USB in to boot internal drive, but better to edit /EFI/ubuntu/grub.cfg. You may have to change settings in fstab to allow editing as fstab in newer versions of Ubuntu uses 0077 to mount efi partition. Older versions or if you run Boot-Repair will change to defaults as setting. They may have changed to 0077 for security reasons. I may start changing mine back to 0077 once fully configured. askubuntu.com/questions/794725/…
    – oldfred
    2 days ago
















up vote
0
down vote

favorite












First of all I have Kubuntu 18.04.1 LTS installed, fully updated.
It was setup using LVM & Luks Encryption



The BIOS is set to boot UEFI, SecureBoot is disabled. I've also checked all settings their and nothing seems to fix or even attempt to fix this issue.



I know what caused this issue, but dont know why. I was testing live linux distributions that offered encrypted persistence but nothing was 'that good' from what I found. I heard you can just install kubuntu directly to your usb instead of internal disk, which is what I did. I managed to boot from it but never did any diagnostics with it (such as managing or even mounting the internal disk). I wanted this so I have my installed kubuntu as daily driver, and the kubuntu as a live disk in case of system problems and for use as a a portable os.



After this though, I rebooted and took out the usb and it immediately dropped me into a grub shell (not grub rescue). The only way for me to boot computer's os, is typing 'exit' where it then takes me to screen to select boot device.
The 2 options there are 'ubuntu random characters' and 'Boot EFI File Manually'. Selecting the ubuntu boots into grub shell. Selecting boot efi file manually, then navigating to EFI/parrot/grubx64.efi is the only way to boot my os. When I ran command in terminal 'sudo efibootmgr -v' it outputs:



Timeout: 5 seconds
BootOrder: 0000,3000,2001,2002,2004
Boot0000* ubuntu HD(1,GPT,034b05b2-5d55-4e71-ac47-4932eb3edadd,0x800,0x100000)/File(EFIubuntushimx64.efi)
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot3000* Internal Hard Disk or Solid State Disk RC



after I a lot of research on google, everyone else who ran this command has a line on the top showing 'BootCurrent number' showing which one was current. I just learned this command during this issue, so I don't know what it use to show.



I was trying to find out how to change the default efi being used, like if I changed it to automatically boot EFI/parrot/grubx64.efi then my os would boot instead of grub. Although the one selected now is apparently the one supposed to be 'shimx64.efi'. If I selected this file manually in the efi screen or even the grubx64.efi in ubuntu directory it would still boot grub shell. I don't know if this file somehow got corrupted or if something is just messed up with grub. I haven't attempted re-installing grub as others have done that and just messed up their pc even worse. I have a lot of data on my computer, last backed up about a week or so ago. I just don't want to have to go through restoring it or erasing any data. I would like to know how to troubleshoot these issues the best I can to continue learning more about linux as this issue does seem fixable.



in the grub shell if i typed boot, says i need to load kernel first. I am not sure how to even do this, and couldn't find working information online for my setup



Once i type ls in grub shell it gives me partitions like (hd0) (hd0,gpt3) (hd0,gpt2) (hd0,gpt1) (cdrom)



if i try using ls (hd0)/ or ls (hd0,gpt3) it tells me unknown file system. Probably because of the encryption.
If I try ls (hd0,gpt2)/ it list folders like grub and vmlinuz files.
If I try ls (hd0,gpt1)/ it list the folders shown in the EFI menu entry i said earlier like folder EFI.



As I had to get on my pc to ask this question here, I can't also be in the grub shell. Won't have another device for a little while. So I am only explain what I know for sure, dont want to list incorrect information.



Anyone have an idea is whats going on? And maybe why booting a installed kubuntu from usb caused this issue? (When i used live distros like knoppix, puppy linux, kali...) they never caused this issue at all. One thing forgot to mention earlier, my other pc also has kubuntu now has this issue as well right after removing kubuntu usb. The problem with this pc, is that the BIOS has no manual selection of EFI file (after typing exit in grub shell, only 1 drive shown which is the ubuntu one, once selected im in grub shell and do not know how to boot without selecting the efi. Dont know many commands in grub).



I realize that in the EFI folder, there are 4 items. parrot , debian, ubuntu, boot.



parrot was the os I chose to use as a live distro, until i decided to install kubuntu on this same usb. debian I never used as live, it use to be fully installed but don't know why that would still be their as the internal drive was formatted prior to installing Kubuntu. It seems to be that the Parrot efi is whats used to boot my installed kubuntu os. I just need to get the proper efi for ubuntu to be used to boot into os instead of grub



Thank you :)







share|improve this question





















  • I always back up ESP. And any second install of Ubuntu overwrites the /EFI/ubuntu folder. Only change is /EFI/ubuntu/grub.cfg which changes to the newest installs UUID & partition. I now edit that back to my main install. But if external you need to partition in advance so you have an ESP on the external drive. UEFI only boots external drives from /EFI/Boot/bootx64.efi, but if always booting from internal drive, you can just use grub. askubuntu.com/questions/913716/… & askubuntu.com/questions/786986/boot-ubuntu-from-external-drive
    – oldfred
    2 days ago










  • I didn't think of this earlier but my backup I made about a week or 2 ago with clone zilla contains all partitions as they were then. Would restoring just the one fix this issue? I didn't know if it was considered safe to restore just single partition since my main partition containing /home has of course had new data on it since backup was made. If so, then I would need to figure out how to prevent that kubuntu usb stick from causing this issue again. Maybe that link you supplied will help. I did want to know how to manually fix this issue, in case it happens again and I don't have backup.
    – computer_guy
    2 days ago










  • While this answer is for older version and UUIDs are specific to OP, the process is the same. You need to know UUID and edit /EFI/ubuntu/grub.cfg. askubuntu.com/questions/957914/…
    – oldfred
    2 days ago










  • Ok, after looking over those post you linked to, if Im correct you mean to say that I just have to find out my install system's UUID and the edit grub.cfg with that UUID? Does that mean that the install of kubuntu on usb changed the UUID on grub locally and thats why it boots to grub shell because it can't find usb as its not plugged in?
    – computer_guy
    2 days ago










  • Yes. You can always plug USB in to boot internal drive, but better to edit /EFI/ubuntu/grub.cfg. You may have to change settings in fstab to allow editing as fstab in newer versions of Ubuntu uses 0077 to mount efi partition. Older versions or if you run Boot-Repair will change to defaults as setting. They may have changed to 0077 for security reasons. I may start changing mine back to 0077 once fully configured. askubuntu.com/questions/794725/…
    – oldfred
    2 days ago












up vote
0
down vote

favorite









up vote
0
down vote

favorite











First of all I have Kubuntu 18.04.1 LTS installed, fully updated.
It was setup using LVM & Luks Encryption



The BIOS is set to boot UEFI, SecureBoot is disabled. I've also checked all settings their and nothing seems to fix or even attempt to fix this issue.



I know what caused this issue, but dont know why. I was testing live linux distributions that offered encrypted persistence but nothing was 'that good' from what I found. I heard you can just install kubuntu directly to your usb instead of internal disk, which is what I did. I managed to boot from it but never did any diagnostics with it (such as managing or even mounting the internal disk). I wanted this so I have my installed kubuntu as daily driver, and the kubuntu as a live disk in case of system problems and for use as a a portable os.



After this though, I rebooted and took out the usb and it immediately dropped me into a grub shell (not grub rescue). The only way for me to boot computer's os, is typing 'exit' where it then takes me to screen to select boot device.
The 2 options there are 'ubuntu random characters' and 'Boot EFI File Manually'. Selecting the ubuntu boots into grub shell. Selecting boot efi file manually, then navigating to EFI/parrot/grubx64.efi is the only way to boot my os. When I ran command in terminal 'sudo efibootmgr -v' it outputs:



Timeout: 5 seconds
BootOrder: 0000,3000,2001,2002,2004
Boot0000* ubuntu HD(1,GPT,034b05b2-5d55-4e71-ac47-4932eb3edadd,0x800,0x100000)/File(EFIubuntushimx64.efi)
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot3000* Internal Hard Disk or Solid State Disk RC



after I a lot of research on google, everyone else who ran this command has a line on the top showing 'BootCurrent number' showing which one was current. I just learned this command during this issue, so I don't know what it use to show.



I was trying to find out how to change the default efi being used, like if I changed it to automatically boot EFI/parrot/grubx64.efi then my os would boot instead of grub. Although the one selected now is apparently the one supposed to be 'shimx64.efi'. If I selected this file manually in the efi screen or even the grubx64.efi in ubuntu directory it would still boot grub shell. I don't know if this file somehow got corrupted or if something is just messed up with grub. I haven't attempted re-installing grub as others have done that and just messed up their pc even worse. I have a lot of data on my computer, last backed up about a week or so ago. I just don't want to have to go through restoring it or erasing any data. I would like to know how to troubleshoot these issues the best I can to continue learning more about linux as this issue does seem fixable.



in the grub shell if i typed boot, says i need to load kernel first. I am not sure how to even do this, and couldn't find working information online for my setup



Once i type ls in grub shell it gives me partitions like (hd0) (hd0,gpt3) (hd0,gpt2) (hd0,gpt1) (cdrom)



if i try using ls (hd0)/ or ls (hd0,gpt3) it tells me unknown file system. Probably because of the encryption.
If I try ls (hd0,gpt2)/ it list folders like grub and vmlinuz files.
If I try ls (hd0,gpt1)/ it list the folders shown in the EFI menu entry i said earlier like folder EFI.



As I had to get on my pc to ask this question here, I can't also be in the grub shell. Won't have another device for a little while. So I am only explain what I know for sure, dont want to list incorrect information.



Anyone have an idea is whats going on? And maybe why booting a installed kubuntu from usb caused this issue? (When i used live distros like knoppix, puppy linux, kali...) they never caused this issue at all. One thing forgot to mention earlier, my other pc also has kubuntu now has this issue as well right after removing kubuntu usb. The problem with this pc, is that the BIOS has no manual selection of EFI file (after typing exit in grub shell, only 1 drive shown which is the ubuntu one, once selected im in grub shell and do not know how to boot without selecting the efi. Dont know many commands in grub).



I realize that in the EFI folder, there are 4 items. parrot , debian, ubuntu, boot.



parrot was the os I chose to use as a live distro, until i decided to install kubuntu on this same usb. debian I never used as live, it use to be fully installed but don't know why that would still be their as the internal drive was formatted prior to installing Kubuntu. It seems to be that the Parrot efi is whats used to boot my installed kubuntu os. I just need to get the proper efi for ubuntu to be used to boot into os instead of grub



Thank you :)







share|improve this question













First of all I have Kubuntu 18.04.1 LTS installed, fully updated.
It was setup using LVM & Luks Encryption



The BIOS is set to boot UEFI, SecureBoot is disabled. I've also checked all settings their and nothing seems to fix or even attempt to fix this issue.



I know what caused this issue, but dont know why. I was testing live linux distributions that offered encrypted persistence but nothing was 'that good' from what I found. I heard you can just install kubuntu directly to your usb instead of internal disk, which is what I did. I managed to boot from it but never did any diagnostics with it (such as managing or even mounting the internal disk). I wanted this so I have my installed kubuntu as daily driver, and the kubuntu as a live disk in case of system problems and for use as a a portable os.



After this though, I rebooted and took out the usb and it immediately dropped me into a grub shell (not grub rescue). The only way for me to boot computer's os, is typing 'exit' where it then takes me to screen to select boot device.
The 2 options there are 'ubuntu random characters' and 'Boot EFI File Manually'. Selecting the ubuntu boots into grub shell. Selecting boot efi file manually, then navigating to EFI/parrot/grubx64.efi is the only way to boot my os. When I ran command in terminal 'sudo efibootmgr -v' it outputs:



Timeout: 5 seconds
BootOrder: 0000,3000,2001,2002,2004
Boot0000* ubuntu HD(1,GPT,034b05b2-5d55-4e71-ac47-4932eb3edadd,0x800,0x100000)/File(EFIubuntushimx64.efi)
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot3000* Internal Hard Disk or Solid State Disk RC



after I a lot of research on google, everyone else who ran this command has a line on the top showing 'BootCurrent number' showing which one was current. I just learned this command during this issue, so I don't know what it use to show.



I was trying to find out how to change the default efi being used, like if I changed it to automatically boot EFI/parrot/grubx64.efi then my os would boot instead of grub. Although the one selected now is apparently the one supposed to be 'shimx64.efi'. If I selected this file manually in the efi screen or even the grubx64.efi in ubuntu directory it would still boot grub shell. I don't know if this file somehow got corrupted or if something is just messed up with grub. I haven't attempted re-installing grub as others have done that and just messed up their pc even worse. I have a lot of data on my computer, last backed up about a week or so ago. I just don't want to have to go through restoring it or erasing any data. I would like to know how to troubleshoot these issues the best I can to continue learning more about linux as this issue does seem fixable.



in the grub shell if i typed boot, says i need to load kernel first. I am not sure how to even do this, and couldn't find working information online for my setup



Once i type ls in grub shell it gives me partitions like (hd0) (hd0,gpt3) (hd0,gpt2) (hd0,gpt1) (cdrom)



if i try using ls (hd0)/ or ls (hd0,gpt3) it tells me unknown file system. Probably because of the encryption.
If I try ls (hd0,gpt2)/ it list folders like grub and vmlinuz files.
If I try ls (hd0,gpt1)/ it list the folders shown in the EFI menu entry i said earlier like folder EFI.



As I had to get on my pc to ask this question here, I can't also be in the grub shell. Won't have another device for a little while. So I am only explain what I know for sure, dont want to list incorrect information.



Anyone have an idea is whats going on? And maybe why booting a installed kubuntu from usb caused this issue? (When i used live distros like knoppix, puppy linux, kali...) they never caused this issue at all. One thing forgot to mention earlier, my other pc also has kubuntu now has this issue as well right after removing kubuntu usb. The problem with this pc, is that the BIOS has no manual selection of EFI file (after typing exit in grub shell, only 1 drive shown which is the ubuntu one, once selected im in grub shell and do not know how to boot without selecting the efi. Dont know many commands in grub).



I realize that in the EFI folder, there are 4 items. parrot , debian, ubuntu, boot.



parrot was the os I chose to use as a live distro, until i decided to install kubuntu on this same usb. debian I never used as live, it use to be fully installed but don't know why that would still be their as the internal drive was formatted prior to installing Kubuntu. It seems to be that the Parrot efi is whats used to boot my installed kubuntu os. I just need to get the proper efi for ubuntu to be used to boot into os instead of grub



Thank you :)









share|improve this question












share|improve this question




share|improve this question








edited 2 days ago
























asked 2 days ago









computer_guy

12




12











  • I always back up ESP. And any second install of Ubuntu overwrites the /EFI/ubuntu folder. Only change is /EFI/ubuntu/grub.cfg which changes to the newest installs UUID & partition. I now edit that back to my main install. But if external you need to partition in advance so you have an ESP on the external drive. UEFI only boots external drives from /EFI/Boot/bootx64.efi, but if always booting from internal drive, you can just use grub. askubuntu.com/questions/913716/… & askubuntu.com/questions/786986/boot-ubuntu-from-external-drive
    – oldfred
    2 days ago










  • I didn't think of this earlier but my backup I made about a week or 2 ago with clone zilla contains all partitions as they were then. Would restoring just the one fix this issue? I didn't know if it was considered safe to restore just single partition since my main partition containing /home has of course had new data on it since backup was made. If so, then I would need to figure out how to prevent that kubuntu usb stick from causing this issue again. Maybe that link you supplied will help. I did want to know how to manually fix this issue, in case it happens again and I don't have backup.
    – computer_guy
    2 days ago










  • While this answer is for older version and UUIDs are specific to OP, the process is the same. You need to know UUID and edit /EFI/ubuntu/grub.cfg. askubuntu.com/questions/957914/…
    – oldfred
    2 days ago










  • Ok, after looking over those post you linked to, if Im correct you mean to say that I just have to find out my install system's UUID and the edit grub.cfg with that UUID? Does that mean that the install of kubuntu on usb changed the UUID on grub locally and thats why it boots to grub shell because it can't find usb as its not plugged in?
    – computer_guy
    2 days ago










  • Yes. You can always plug USB in to boot internal drive, but better to edit /EFI/ubuntu/grub.cfg. You may have to change settings in fstab to allow editing as fstab in newer versions of Ubuntu uses 0077 to mount efi partition. Older versions or if you run Boot-Repair will change to defaults as setting. They may have changed to 0077 for security reasons. I may start changing mine back to 0077 once fully configured. askubuntu.com/questions/794725/…
    – oldfred
    2 days ago
















  • I always back up ESP. And any second install of Ubuntu overwrites the /EFI/ubuntu folder. Only change is /EFI/ubuntu/grub.cfg which changes to the newest installs UUID & partition. I now edit that back to my main install. But if external you need to partition in advance so you have an ESP on the external drive. UEFI only boots external drives from /EFI/Boot/bootx64.efi, but if always booting from internal drive, you can just use grub. askubuntu.com/questions/913716/… & askubuntu.com/questions/786986/boot-ubuntu-from-external-drive
    – oldfred
    2 days ago










  • I didn't think of this earlier but my backup I made about a week or 2 ago with clone zilla contains all partitions as they were then. Would restoring just the one fix this issue? I didn't know if it was considered safe to restore just single partition since my main partition containing /home has of course had new data on it since backup was made. If so, then I would need to figure out how to prevent that kubuntu usb stick from causing this issue again. Maybe that link you supplied will help. I did want to know how to manually fix this issue, in case it happens again and I don't have backup.
    – computer_guy
    2 days ago










  • While this answer is for older version and UUIDs are specific to OP, the process is the same. You need to know UUID and edit /EFI/ubuntu/grub.cfg. askubuntu.com/questions/957914/…
    – oldfred
    2 days ago










  • Ok, after looking over those post you linked to, if Im correct you mean to say that I just have to find out my install system's UUID and the edit grub.cfg with that UUID? Does that mean that the install of kubuntu on usb changed the UUID on grub locally and thats why it boots to grub shell because it can't find usb as its not plugged in?
    – computer_guy
    2 days ago










  • Yes. You can always plug USB in to boot internal drive, but better to edit /EFI/ubuntu/grub.cfg. You may have to change settings in fstab to allow editing as fstab in newer versions of Ubuntu uses 0077 to mount efi partition. Older versions or if you run Boot-Repair will change to defaults as setting. They may have changed to 0077 for security reasons. I may start changing mine back to 0077 once fully configured. askubuntu.com/questions/794725/…
    – oldfred
    2 days ago















I always back up ESP. And any second install of Ubuntu overwrites the /EFI/ubuntu folder. Only change is /EFI/ubuntu/grub.cfg which changes to the newest installs UUID & partition. I now edit that back to my main install. But if external you need to partition in advance so you have an ESP on the external drive. UEFI only boots external drives from /EFI/Boot/bootx64.efi, but if always booting from internal drive, you can just use grub. askubuntu.com/questions/913716/… & askubuntu.com/questions/786986/boot-ubuntu-from-external-drive
– oldfred
2 days ago




I always back up ESP. And any second install of Ubuntu overwrites the /EFI/ubuntu folder. Only change is /EFI/ubuntu/grub.cfg which changes to the newest installs UUID & partition. I now edit that back to my main install. But if external you need to partition in advance so you have an ESP on the external drive. UEFI only boots external drives from /EFI/Boot/bootx64.efi, but if always booting from internal drive, you can just use grub. askubuntu.com/questions/913716/… & askubuntu.com/questions/786986/boot-ubuntu-from-external-drive
– oldfred
2 days ago












I didn't think of this earlier but my backup I made about a week or 2 ago with clone zilla contains all partitions as they were then. Would restoring just the one fix this issue? I didn't know if it was considered safe to restore just single partition since my main partition containing /home has of course had new data on it since backup was made. If so, then I would need to figure out how to prevent that kubuntu usb stick from causing this issue again. Maybe that link you supplied will help. I did want to know how to manually fix this issue, in case it happens again and I don't have backup.
– computer_guy
2 days ago




I didn't think of this earlier but my backup I made about a week or 2 ago with clone zilla contains all partitions as they were then. Would restoring just the one fix this issue? I didn't know if it was considered safe to restore just single partition since my main partition containing /home has of course had new data on it since backup was made. If so, then I would need to figure out how to prevent that kubuntu usb stick from causing this issue again. Maybe that link you supplied will help. I did want to know how to manually fix this issue, in case it happens again and I don't have backup.
– computer_guy
2 days ago












While this answer is for older version and UUIDs are specific to OP, the process is the same. You need to know UUID and edit /EFI/ubuntu/grub.cfg. askubuntu.com/questions/957914/…
– oldfred
2 days ago




While this answer is for older version and UUIDs are specific to OP, the process is the same. You need to know UUID and edit /EFI/ubuntu/grub.cfg. askubuntu.com/questions/957914/…
– oldfred
2 days ago












Ok, after looking over those post you linked to, if Im correct you mean to say that I just have to find out my install system's UUID and the edit grub.cfg with that UUID? Does that mean that the install of kubuntu on usb changed the UUID on grub locally and thats why it boots to grub shell because it can't find usb as its not plugged in?
– computer_guy
2 days ago




Ok, after looking over those post you linked to, if Im correct you mean to say that I just have to find out my install system's UUID and the edit grub.cfg with that UUID? Does that mean that the install of kubuntu on usb changed the UUID on grub locally and thats why it boots to grub shell because it can't find usb as its not plugged in?
– computer_guy
2 days ago












Yes. You can always plug USB in to boot internal drive, but better to edit /EFI/ubuntu/grub.cfg. You may have to change settings in fstab to allow editing as fstab in newer versions of Ubuntu uses 0077 to mount efi partition. Older versions or if you run Boot-Repair will change to defaults as setting. They may have changed to 0077 for security reasons. I may start changing mine back to 0077 once fully configured. askubuntu.com/questions/794725/…
– oldfred
2 days ago




Yes. You can always plug USB in to boot internal drive, but better to edit /EFI/ubuntu/grub.cfg. You may have to change settings in fstab to allow editing as fstab in newer versions of Ubuntu uses 0077 to mount efi partition. Older versions or if you run Boot-Repair will change to defaults as setting. They may have changed to 0077 for security reasons. I may start changing mine back to 0077 once fully configured. askubuntu.com/questions/794725/…
– oldfred
2 days ago















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1062118%2fgrub-command-line-boots-default-have-to-manually-specify-efi-how-could-i-cange%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1062118%2fgrub-command-line-boots-default-have-to-manually-specify-efi-how-could-i-cange%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491