No grub menu after Ubuntu install, booting directly into UbuntuCannot access GRUB after deleting Win 8Dual...
Good examples of "two is easy, three is hard" in computational sciences
How to play vs. 1.e4 e5 2.Nf3 Nc6 3.Bc4 d6?
Gambler's Fallacy Dice
What should I wear to go and sign an employment contract?
How to safely discharge oneself
What does it mean for a program to be 32 or 64 bit?
Existence of a model of ZFC in which the natural numbers are really the natural numbers
How did Jean Parisot de Valette, 49th Grand Master of the Order of Malta, die?
pwaS eht tirsf dna tasl setterl fo hace dorw
Way of refund if scammed?
Is there any mention of ghosts who live outside the Hogwarts castle?
Department head said that group project may be rejected. How to mitigate?
On a piano, are the effects of holding notes and the sustain pedal the same for a single chord?
What is this dime sized black bug with white on the segments near Loveland Colorodao?
Is there a way to generate a mapping graph like this?
Is there a realtime, uncut video of Saturn V ignition through tower clear?
Do seaplanes need to get clearance for takeoff?
1950s or earlier book with electrical currents living on Pluto
How could Dwarves prevent sand from filling up their settlements
How can I prevent Bash expansion from passing files starting with "-" as argument?
tikz: 5 squares on a row, roman numbered 1 -> 5
How do we explain the use of a software on a math paper?
US F1 Visa grace period attending a conference
Vehemently against code formatting
No grub menu after Ubuntu install, booting directly into Ubuntu
Cannot access GRUB after deleting Win 8Dual booting Ubuntu and Windows 8. w8 boots through grub shell, but not from menuHow to add Puppy Linux to grub menu installed by Ubuntu?Can I safely delete the Ubuntu 12.04 partition and use the unallocated space for my Elementary OS?Problem dual booting windows 8 and ubuntu 14.04Problem booting Ubuntu (or any OS), even after doing clean installsDisk Partition when dual booting Ubuntu 14.04 onto Windows 10Add scound Linux OS dual with Centos 7Can't boot into Windows after updating boot partition tableGRUB menu doesn't appear after Ubuntu install alongside with Windows 10
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I have two separate SSD's. One of them has Windows 10 Pro installed, and the other has Ubuntu 14.04.3 LTS.
When my computer boots I get no grub menu to choose the operating system I want to boot into, it directly boots into Ubuntu automatically. I can boot into windows with on problems when setting its SSD as the first one in the boot sequence in the BIOS.
I have a third 2TB HDD that I use only for storage. Here is the information summary after running bootinfoscript
============================= Boot Info Summary: ===============================
=> Windows is installed in the MBR of /dev/sda.
=> Windows is installed in the MBR of /dev/sdb.
=> Grub2 (v1.99) is installed in the MBR of /dev/sdc and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 112 for .
sda1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD
sda2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /Windows/System32/winload.exe
sda3: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sdb1: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 14.04.3 LTS
Boot files: /boot/grub/grub.cfg /etc/fstab
sdb2: __________________________________________________________________________
File system: swap
Boot sector type: -
Boot sector info:
sdb3: __________________________________________________________________________
File system: vfat
Boot sector type: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/ubuntu/grubx64.efi /efi/ubuntu/MokManager.efi
/efi/ubuntu/shimx64.efi
sdb4: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
sdc1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
I have installed Linux before many times, however this is my first time installing it on a separate drive. Do I need to do anything extra/different seeing that is is installed on a separate drive to Windows?
linux ubuntu grub2 dual-boot
add a comment |
I have two separate SSD's. One of them has Windows 10 Pro installed, and the other has Ubuntu 14.04.3 LTS.
When my computer boots I get no grub menu to choose the operating system I want to boot into, it directly boots into Ubuntu automatically. I can boot into windows with on problems when setting its SSD as the first one in the boot sequence in the BIOS.
I have a third 2TB HDD that I use only for storage. Here is the information summary after running bootinfoscript
============================= Boot Info Summary: ===============================
=> Windows is installed in the MBR of /dev/sda.
=> Windows is installed in the MBR of /dev/sdb.
=> Grub2 (v1.99) is installed in the MBR of /dev/sdc and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 112 for .
sda1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD
sda2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /Windows/System32/winload.exe
sda3: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sdb1: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 14.04.3 LTS
Boot files: /boot/grub/grub.cfg /etc/fstab
sdb2: __________________________________________________________________________
File system: swap
Boot sector type: -
Boot sector info:
sdb3: __________________________________________________________________________
File system: vfat
Boot sector type: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/ubuntu/grubx64.efi /efi/ubuntu/MokManager.efi
/efi/ubuntu/shimx64.efi
sdb4: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
sdc1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
I have installed Linux before many times, however this is my first time installing it on a separate drive. Do I need to do anything extra/different seeing that is is installed on a separate drive to Windows?
linux ubuntu grub2 dual-boot
There are two ways actually: WIndows boot manager detects Linux, or let Grub detects Windows. The latter might requires to manually configuregrub.cfg
to add entry for chainloading Windows at the other partition. I don't use Windows anymore, so I can't put this as answer; This shall be a clue for others to answer or to solve it on own.
– clearkimura
Nov 8 '15 at 10:21
add a comment |
I have two separate SSD's. One of them has Windows 10 Pro installed, and the other has Ubuntu 14.04.3 LTS.
When my computer boots I get no grub menu to choose the operating system I want to boot into, it directly boots into Ubuntu automatically. I can boot into windows with on problems when setting its SSD as the first one in the boot sequence in the BIOS.
I have a third 2TB HDD that I use only for storage. Here is the information summary after running bootinfoscript
============================= Boot Info Summary: ===============================
=> Windows is installed in the MBR of /dev/sda.
=> Windows is installed in the MBR of /dev/sdb.
=> Grub2 (v1.99) is installed in the MBR of /dev/sdc and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 112 for .
sda1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD
sda2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /Windows/System32/winload.exe
sda3: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sdb1: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 14.04.3 LTS
Boot files: /boot/grub/grub.cfg /etc/fstab
sdb2: __________________________________________________________________________
File system: swap
Boot sector type: -
Boot sector info:
sdb3: __________________________________________________________________________
File system: vfat
Boot sector type: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/ubuntu/grubx64.efi /efi/ubuntu/MokManager.efi
/efi/ubuntu/shimx64.efi
sdb4: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
sdc1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
I have installed Linux before many times, however this is my first time installing it on a separate drive. Do I need to do anything extra/different seeing that is is installed on a separate drive to Windows?
linux ubuntu grub2 dual-boot
I have two separate SSD's. One of them has Windows 10 Pro installed, and the other has Ubuntu 14.04.3 LTS.
When my computer boots I get no grub menu to choose the operating system I want to boot into, it directly boots into Ubuntu automatically. I can boot into windows with on problems when setting its SSD as the first one in the boot sequence in the BIOS.
I have a third 2TB HDD that I use only for storage. Here is the information summary after running bootinfoscript
============================= Boot Info Summary: ===============================
=> Windows is installed in the MBR of /dev/sda.
=> Windows is installed in the MBR of /dev/sdb.
=> Grub2 (v1.99) is installed in the MBR of /dev/sdc and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 112 for .
sda1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD
sda2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /Windows/System32/winload.exe
sda3: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
sdb1: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 14.04.3 LTS
Boot files: /boot/grub/grub.cfg /etc/fstab
sdb2: __________________________________________________________________________
File system: swap
Boot sector type: -
Boot sector info:
sdb3: __________________________________________________________________________
File system: vfat
Boot sector type: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/ubuntu/grubx64.efi /efi/ubuntu/MokManager.efi
/efi/ubuntu/shimx64.efi
sdb4: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
sdc1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
I have installed Linux before many times, however this is my first time installing it on a separate drive. Do I need to do anything extra/different seeing that is is installed on a separate drive to Windows?
linux ubuntu grub2 dual-boot
linux ubuntu grub2 dual-boot
asked Nov 8 '15 at 9:09
SylvooSylvoo
3114
3114
There are two ways actually: WIndows boot manager detects Linux, or let Grub detects Windows. The latter might requires to manually configuregrub.cfg
to add entry for chainloading Windows at the other partition. I don't use Windows anymore, so I can't put this as answer; This shall be a clue for others to answer or to solve it on own.
– clearkimura
Nov 8 '15 at 10:21
add a comment |
There are two ways actually: WIndows boot manager detects Linux, or let Grub detects Windows. The latter might requires to manually configuregrub.cfg
to add entry for chainloading Windows at the other partition. I don't use Windows anymore, so I can't put this as answer; This shall be a clue for others to answer or to solve it on own.
– clearkimura
Nov 8 '15 at 10:21
There are two ways actually: WIndows boot manager detects Linux, or let Grub detects Windows. The latter might requires to manually configure
grub.cfg
to add entry for chainloading Windows at the other partition. I don't use Windows anymore, so I can't put this as answer; This shall be a clue for others to answer or to solve it on own.– clearkimura
Nov 8 '15 at 10:21
There are two ways actually: WIndows boot manager detects Linux, or let Grub detects Windows. The latter might requires to manually configure
grub.cfg
to add entry for chainloading Windows at the other partition. I don't use Windows anymore, so I can't put this as answer; This shall be a clue for others to answer or to solve it on own.– clearkimura
Nov 8 '15 at 10:21
add a comment |
2 Answers
2
active
oldest
votes
Perhaps update-grub2
was not run after Linux installation completed? This usually helped refresh my boot options menu.
I see clearkimura
's comment about modifying /boot/grub/grub.cfg
, but this file clearly says not to modify its contents as it is automatically generated based on /etc/default/grub
and /etc/grub.d/
.
You are correct about modifyinggrub.cfg
. But have you wondered why? Becausegrub.cfg
file will be regenerated automatically by runningupdate-grub
command. Hence, I suggested "manually configuregrub.cfg
" which will not require to run the command. This is especially true if you are working on system installed on external storage or live media.
– clearkimura
Nov 9 '15 at 8:54
@clearkimura: Now I see your point. My point was to make sure Sylvoo is aware that manual changes togrub.cfg
will be wiped out every timeupdate-grub
is triggered by a package manager, that is at any kernel image addition to boot options orGRUB
update itself.
– Xavras Wyzryn
Nov 10 '15 at 18:04
add a comment |
Answer posted here: https://askubuntu.com/questions/726972/dual-boot-windows-10-and-linux-ubuntu-on-separate-hard-drives
here is the quoted text---------------------
This should work for most systems that use UEFI and which have two HDD.
Specification used for the tutorial below:
Dell Inspiron E5440:
Main HDD - 256GB Samsung SSD (Windows 10 installed)
Secondary HDD - 64GB Transcend mSATA SSD (Mint 18 was installed to this drive)
A) UEFI/BIOS
Set to "UEFI mode only" (no legacy/CSM).
Disable "secure boot"
Disable "Intel Rapid Start" (if equipped)
Disable "fast boot" in UEFI (note this is different than the "fastboot" setting in Windows 8/10). The options in your UEFI/BIOS might say something like Full/Minimal/Automatic for boot mode. Select Full (or thorough, or complete, etc whatever your UEFI vendor has chosen to call it).
B) Advanced Power Options (Fastboot)
Disable fastboot in Windows 8/10 under "advanced power options". Restart computer to ensure that this subsequent boot and the next reboot/shutdown will be in "normal" mode.
Optional:
Install Macrium Reflect (free) and create a backup image and reinstallation media should something go wrong with Windows 10.
C) Rufus / Bootable USB stick
Use Rufus to create a bootable USB stick with your choice of Ubuntu based distro. Make sure in Rufus that you CHOOSE the option UEFI/GPT only. This ensures the Linux environment boots only into UEFI mode during your install.
D) Boot Menu
Reboot your computer and press key for one time boot menu (Dell is typically F12). Select your USB stick from the boot options.
Note:
Make sure it says UEFI in front of the USB stick in the boot menu.
If not, return to Windows and recreate your USB stick with Rufus ensuring you choose the UEFI/GPT (only) option.
E) Boot into USB Stick
Boot into Linux live environment and begin install.
F) Installation type
When you get to the installation option, choose "Something else" at the bottom of the Ubiquity installer.
G) Create partitions
Find your secondary HDD that you will be installing Linux to.
In my case it was listed as /dev/sdc (with /dev/sda being the windows drive and /dev/sdb the USB drive [which was invisible in the installer]).
So basically:
+--------------+--------+---------------------------+--------------------------------+
| Device path | Device | Operating System (OS) | Visible in Ubiquity installer? |
+--------------+--------+---------------------------+--------------------------------+
| /dev/sda | HDD | Windows 10 | yes |
| /dev/sdb | USB | Ubuntu 16.04 (Live Stick) | no |
| /dev/sdc | HDD | None | yes |
+--------------+--------+---------------------------+--------------------------------+
1st Partition / EFI
Select your target drive (in my case /dev/sdc)
Select "Make New Partition Table"
Partition the target drive as follows:
Size: 650 MB
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: EFI (this will be listed as /dev/sdc1 efi in the partitioning tool once you create it)
2nd Partition / Root
Select "free space" under your target drive (in my case /dev/sdc)
Select "+"
Partition the target drive as follows:
Size: min. 10 GB (20+GB better)
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: ext4
Mount point: Choose "/"
3rd Partition / Swap
Select "free space" under your target drive (in my case /dev/sdc)
Select "+"
Partition the target drive as follows:
Size: min. 2 GB (20+GB better)
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: swap (if you wish to use hibernation, the swap needs to be just slightly larger than your total amount of RAM - example I have 8 GB so the size of this parition was set at 9000 MB)
4th Partition / Home
Select "free space" under your target drive (in my case /dev/sdc)
Select "+"
Partition the target drive as follows:
Size: remainder of space on drive
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: ext4
Mount point: Choose "/home"
H) Boot loader Device
BEFORE clicking "Install Now", from the "device for boot loader installation" option button, select the 650MB EFI partition you just created as the target for the bootloader. (example /dev/sdc1 in my case).
Click "Install Now".
I) Installation & Reboot
Finish installation process and reboot (removing the USB stick when your UEFI/BIOS screen logo appears).
J) Upon reboot
After UEFI/BIOS reads the new bootloader entry that Linux has added to it, you will be presented with the grub menu with a listing of your Linux distro as well as a listing to boot Windows 10.
Boot into Linux
Install any updates and then reboot and attempt to enter Windows 10 from the grub menu to make sure that grub correctly handles the hand-off to the Windows 10 bootloader.
What you have done:
You have installed the Linux EFI bootloader to the newly created EFI partition. In the process of this, Linux has added an entry to your UEFI listings in your systems UEFI/BIOS. Linux has also automatically detected your Windows 10 install and added a grub menu item to boot it. Your computer at this point will now automatically boot to Linux unless you choose to boot to Windows (from the Grub menu).
What you have not done:
You have not in any way altered your Windows 10 install or its bootloader or even so much as touched the Windows 10 EFI partition. Everything is reversible simply by removing the Linux UEFI listing from your UEFI/BIOS settings. How to do so varies from each vendor.
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f241603%2fno-grub-menu-after-ubuntu-install-booting-directly-into-ubuntu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Perhaps update-grub2
was not run after Linux installation completed? This usually helped refresh my boot options menu.
I see clearkimura
's comment about modifying /boot/grub/grub.cfg
, but this file clearly says not to modify its contents as it is automatically generated based on /etc/default/grub
and /etc/grub.d/
.
You are correct about modifyinggrub.cfg
. But have you wondered why? Becausegrub.cfg
file will be regenerated automatically by runningupdate-grub
command. Hence, I suggested "manually configuregrub.cfg
" which will not require to run the command. This is especially true if you are working on system installed on external storage or live media.
– clearkimura
Nov 9 '15 at 8:54
@clearkimura: Now I see your point. My point was to make sure Sylvoo is aware that manual changes togrub.cfg
will be wiped out every timeupdate-grub
is triggered by a package manager, that is at any kernel image addition to boot options orGRUB
update itself.
– Xavras Wyzryn
Nov 10 '15 at 18:04
add a comment |
Perhaps update-grub2
was not run after Linux installation completed? This usually helped refresh my boot options menu.
I see clearkimura
's comment about modifying /boot/grub/grub.cfg
, but this file clearly says not to modify its contents as it is automatically generated based on /etc/default/grub
and /etc/grub.d/
.
You are correct about modifyinggrub.cfg
. But have you wondered why? Becausegrub.cfg
file will be regenerated automatically by runningupdate-grub
command. Hence, I suggested "manually configuregrub.cfg
" which will not require to run the command. This is especially true if you are working on system installed on external storage or live media.
– clearkimura
Nov 9 '15 at 8:54
@clearkimura: Now I see your point. My point was to make sure Sylvoo is aware that manual changes togrub.cfg
will be wiped out every timeupdate-grub
is triggered by a package manager, that is at any kernel image addition to boot options orGRUB
update itself.
– Xavras Wyzryn
Nov 10 '15 at 18:04
add a comment |
Perhaps update-grub2
was not run after Linux installation completed? This usually helped refresh my boot options menu.
I see clearkimura
's comment about modifying /boot/grub/grub.cfg
, but this file clearly says not to modify its contents as it is automatically generated based on /etc/default/grub
and /etc/grub.d/
.
Perhaps update-grub2
was not run after Linux installation completed? This usually helped refresh my boot options menu.
I see clearkimura
's comment about modifying /boot/grub/grub.cfg
, but this file clearly says not to modify its contents as it is automatically generated based on /etc/default/grub
and /etc/grub.d/
.
answered Nov 9 '15 at 5:29
Xavras WyzrynXavras Wyzryn
16615
16615
You are correct about modifyinggrub.cfg
. But have you wondered why? Becausegrub.cfg
file will be regenerated automatically by runningupdate-grub
command. Hence, I suggested "manually configuregrub.cfg
" which will not require to run the command. This is especially true if you are working on system installed on external storage or live media.
– clearkimura
Nov 9 '15 at 8:54
@clearkimura: Now I see your point. My point was to make sure Sylvoo is aware that manual changes togrub.cfg
will be wiped out every timeupdate-grub
is triggered by a package manager, that is at any kernel image addition to boot options orGRUB
update itself.
– Xavras Wyzryn
Nov 10 '15 at 18:04
add a comment |
You are correct about modifyinggrub.cfg
. But have you wondered why? Becausegrub.cfg
file will be regenerated automatically by runningupdate-grub
command. Hence, I suggested "manually configuregrub.cfg
" which will not require to run the command. This is especially true if you are working on system installed on external storage or live media.
– clearkimura
Nov 9 '15 at 8:54
@clearkimura: Now I see your point. My point was to make sure Sylvoo is aware that manual changes togrub.cfg
will be wiped out every timeupdate-grub
is triggered by a package manager, that is at any kernel image addition to boot options orGRUB
update itself.
– Xavras Wyzryn
Nov 10 '15 at 18:04
You are correct about modifying
grub.cfg
. But have you wondered why? Because grub.cfg
file will be regenerated automatically by running update-grub
command. Hence, I suggested "manually configure grub.cfg
" which will not require to run the command. This is especially true if you are working on system installed on external storage or live media.– clearkimura
Nov 9 '15 at 8:54
You are correct about modifying
grub.cfg
. But have you wondered why? Because grub.cfg
file will be regenerated automatically by running update-grub
command. Hence, I suggested "manually configure grub.cfg
" which will not require to run the command. This is especially true if you are working on system installed on external storage or live media.– clearkimura
Nov 9 '15 at 8:54
@clearkimura: Now I see your point. My point was to make sure Sylvoo is aware that manual changes to
grub.cfg
will be wiped out every time update-grub
is triggered by a package manager, that is at any kernel image addition to boot options or GRUB
update itself.– Xavras Wyzryn
Nov 10 '15 at 18:04
@clearkimura: Now I see your point. My point was to make sure Sylvoo is aware that manual changes to
grub.cfg
will be wiped out every time update-grub
is triggered by a package manager, that is at any kernel image addition to boot options or GRUB
update itself.– Xavras Wyzryn
Nov 10 '15 at 18:04
add a comment |
Answer posted here: https://askubuntu.com/questions/726972/dual-boot-windows-10-and-linux-ubuntu-on-separate-hard-drives
here is the quoted text---------------------
This should work for most systems that use UEFI and which have two HDD.
Specification used for the tutorial below:
Dell Inspiron E5440:
Main HDD - 256GB Samsung SSD (Windows 10 installed)
Secondary HDD - 64GB Transcend mSATA SSD (Mint 18 was installed to this drive)
A) UEFI/BIOS
Set to "UEFI mode only" (no legacy/CSM).
Disable "secure boot"
Disable "Intel Rapid Start" (if equipped)
Disable "fast boot" in UEFI (note this is different than the "fastboot" setting in Windows 8/10). The options in your UEFI/BIOS might say something like Full/Minimal/Automatic for boot mode. Select Full (or thorough, or complete, etc whatever your UEFI vendor has chosen to call it).
B) Advanced Power Options (Fastboot)
Disable fastboot in Windows 8/10 under "advanced power options". Restart computer to ensure that this subsequent boot and the next reboot/shutdown will be in "normal" mode.
Optional:
Install Macrium Reflect (free) and create a backup image and reinstallation media should something go wrong with Windows 10.
C) Rufus / Bootable USB stick
Use Rufus to create a bootable USB stick with your choice of Ubuntu based distro. Make sure in Rufus that you CHOOSE the option UEFI/GPT only. This ensures the Linux environment boots only into UEFI mode during your install.
D) Boot Menu
Reboot your computer and press key for one time boot menu (Dell is typically F12). Select your USB stick from the boot options.
Note:
Make sure it says UEFI in front of the USB stick in the boot menu.
If not, return to Windows and recreate your USB stick with Rufus ensuring you choose the UEFI/GPT (only) option.
E) Boot into USB Stick
Boot into Linux live environment and begin install.
F) Installation type
When you get to the installation option, choose "Something else" at the bottom of the Ubiquity installer.
G) Create partitions
Find your secondary HDD that you will be installing Linux to.
In my case it was listed as /dev/sdc (with /dev/sda being the windows drive and /dev/sdb the USB drive [which was invisible in the installer]).
So basically:
+--------------+--------+---------------------------+--------------------------------+
| Device path | Device | Operating System (OS) | Visible in Ubiquity installer? |
+--------------+--------+---------------------------+--------------------------------+
| /dev/sda | HDD | Windows 10 | yes |
| /dev/sdb | USB | Ubuntu 16.04 (Live Stick) | no |
| /dev/sdc | HDD | None | yes |
+--------------+--------+---------------------------+--------------------------------+
1st Partition / EFI
Select your target drive (in my case /dev/sdc)
Select "Make New Partition Table"
Partition the target drive as follows:
Size: 650 MB
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: EFI (this will be listed as /dev/sdc1 efi in the partitioning tool once you create it)
2nd Partition / Root
Select "free space" under your target drive (in my case /dev/sdc)
Select "+"
Partition the target drive as follows:
Size: min. 10 GB (20+GB better)
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: ext4
Mount point: Choose "/"
3rd Partition / Swap
Select "free space" under your target drive (in my case /dev/sdc)
Select "+"
Partition the target drive as follows:
Size: min. 2 GB (20+GB better)
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: swap (if you wish to use hibernation, the swap needs to be just slightly larger than your total amount of RAM - example I have 8 GB so the size of this parition was set at 9000 MB)
4th Partition / Home
Select "free space" under your target drive (in my case /dev/sdc)
Select "+"
Partition the target drive as follows:
Size: remainder of space on drive
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: ext4
Mount point: Choose "/home"
H) Boot loader Device
BEFORE clicking "Install Now", from the "device for boot loader installation" option button, select the 650MB EFI partition you just created as the target for the bootloader. (example /dev/sdc1 in my case).
Click "Install Now".
I) Installation & Reboot
Finish installation process and reboot (removing the USB stick when your UEFI/BIOS screen logo appears).
J) Upon reboot
After UEFI/BIOS reads the new bootloader entry that Linux has added to it, you will be presented with the grub menu with a listing of your Linux distro as well as a listing to boot Windows 10.
Boot into Linux
Install any updates and then reboot and attempt to enter Windows 10 from the grub menu to make sure that grub correctly handles the hand-off to the Windows 10 bootloader.
What you have done:
You have installed the Linux EFI bootloader to the newly created EFI partition. In the process of this, Linux has added an entry to your UEFI listings in your systems UEFI/BIOS. Linux has also automatically detected your Windows 10 install and added a grub menu item to boot it. Your computer at this point will now automatically boot to Linux unless you choose to boot to Windows (from the Grub menu).
What you have not done:
You have not in any way altered your Windows 10 install or its bootloader or even so much as touched the Windows 10 EFI partition. Everything is reversible simply by removing the Linux UEFI listing from your UEFI/BIOS settings. How to do so varies from each vendor.
New contributor
add a comment |
Answer posted here: https://askubuntu.com/questions/726972/dual-boot-windows-10-and-linux-ubuntu-on-separate-hard-drives
here is the quoted text---------------------
This should work for most systems that use UEFI and which have two HDD.
Specification used for the tutorial below:
Dell Inspiron E5440:
Main HDD - 256GB Samsung SSD (Windows 10 installed)
Secondary HDD - 64GB Transcend mSATA SSD (Mint 18 was installed to this drive)
A) UEFI/BIOS
Set to "UEFI mode only" (no legacy/CSM).
Disable "secure boot"
Disable "Intel Rapid Start" (if equipped)
Disable "fast boot" in UEFI (note this is different than the "fastboot" setting in Windows 8/10). The options in your UEFI/BIOS might say something like Full/Minimal/Automatic for boot mode. Select Full (or thorough, or complete, etc whatever your UEFI vendor has chosen to call it).
B) Advanced Power Options (Fastboot)
Disable fastboot in Windows 8/10 under "advanced power options". Restart computer to ensure that this subsequent boot and the next reboot/shutdown will be in "normal" mode.
Optional:
Install Macrium Reflect (free) and create a backup image and reinstallation media should something go wrong with Windows 10.
C) Rufus / Bootable USB stick
Use Rufus to create a bootable USB stick with your choice of Ubuntu based distro. Make sure in Rufus that you CHOOSE the option UEFI/GPT only. This ensures the Linux environment boots only into UEFI mode during your install.
D) Boot Menu
Reboot your computer and press key for one time boot menu (Dell is typically F12). Select your USB stick from the boot options.
Note:
Make sure it says UEFI in front of the USB stick in the boot menu.
If not, return to Windows and recreate your USB stick with Rufus ensuring you choose the UEFI/GPT (only) option.
E) Boot into USB Stick
Boot into Linux live environment and begin install.
F) Installation type
When you get to the installation option, choose "Something else" at the bottom of the Ubiquity installer.
G) Create partitions
Find your secondary HDD that you will be installing Linux to.
In my case it was listed as /dev/sdc (with /dev/sda being the windows drive and /dev/sdb the USB drive [which was invisible in the installer]).
So basically:
+--------------+--------+---------------------------+--------------------------------+
| Device path | Device | Operating System (OS) | Visible in Ubiquity installer? |
+--------------+--------+---------------------------+--------------------------------+
| /dev/sda | HDD | Windows 10 | yes |
| /dev/sdb | USB | Ubuntu 16.04 (Live Stick) | no |
| /dev/sdc | HDD | None | yes |
+--------------+--------+---------------------------+--------------------------------+
1st Partition / EFI
Select your target drive (in my case /dev/sdc)
Select "Make New Partition Table"
Partition the target drive as follows:
Size: 650 MB
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: EFI (this will be listed as /dev/sdc1 efi in the partitioning tool once you create it)
2nd Partition / Root
Select "free space" under your target drive (in my case /dev/sdc)
Select "+"
Partition the target drive as follows:
Size: min. 10 GB (20+GB better)
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: ext4
Mount point: Choose "/"
3rd Partition / Swap
Select "free space" under your target drive (in my case /dev/sdc)
Select "+"
Partition the target drive as follows:
Size: min. 2 GB (20+GB better)
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: swap (if you wish to use hibernation, the swap needs to be just slightly larger than your total amount of RAM - example I have 8 GB so the size of this parition was set at 9000 MB)
4th Partition / Home
Select "free space" under your target drive (in my case /dev/sdc)
Select "+"
Partition the target drive as follows:
Size: remainder of space on drive
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: ext4
Mount point: Choose "/home"
H) Boot loader Device
BEFORE clicking "Install Now", from the "device for boot loader installation" option button, select the 650MB EFI partition you just created as the target for the bootloader. (example /dev/sdc1 in my case).
Click "Install Now".
I) Installation & Reboot
Finish installation process and reboot (removing the USB stick when your UEFI/BIOS screen logo appears).
J) Upon reboot
After UEFI/BIOS reads the new bootloader entry that Linux has added to it, you will be presented with the grub menu with a listing of your Linux distro as well as a listing to boot Windows 10.
Boot into Linux
Install any updates and then reboot and attempt to enter Windows 10 from the grub menu to make sure that grub correctly handles the hand-off to the Windows 10 bootloader.
What you have done:
You have installed the Linux EFI bootloader to the newly created EFI partition. In the process of this, Linux has added an entry to your UEFI listings in your systems UEFI/BIOS. Linux has also automatically detected your Windows 10 install and added a grub menu item to boot it. Your computer at this point will now automatically boot to Linux unless you choose to boot to Windows (from the Grub menu).
What you have not done:
You have not in any way altered your Windows 10 install or its bootloader or even so much as touched the Windows 10 EFI partition. Everything is reversible simply by removing the Linux UEFI listing from your UEFI/BIOS settings. How to do so varies from each vendor.
New contributor
add a comment |
Answer posted here: https://askubuntu.com/questions/726972/dual-boot-windows-10-and-linux-ubuntu-on-separate-hard-drives
here is the quoted text---------------------
This should work for most systems that use UEFI and which have two HDD.
Specification used for the tutorial below:
Dell Inspiron E5440:
Main HDD - 256GB Samsung SSD (Windows 10 installed)
Secondary HDD - 64GB Transcend mSATA SSD (Mint 18 was installed to this drive)
A) UEFI/BIOS
Set to "UEFI mode only" (no legacy/CSM).
Disable "secure boot"
Disable "Intel Rapid Start" (if equipped)
Disable "fast boot" in UEFI (note this is different than the "fastboot" setting in Windows 8/10). The options in your UEFI/BIOS might say something like Full/Minimal/Automatic for boot mode. Select Full (or thorough, or complete, etc whatever your UEFI vendor has chosen to call it).
B) Advanced Power Options (Fastboot)
Disable fastboot in Windows 8/10 under "advanced power options". Restart computer to ensure that this subsequent boot and the next reboot/shutdown will be in "normal" mode.
Optional:
Install Macrium Reflect (free) and create a backup image and reinstallation media should something go wrong with Windows 10.
C) Rufus / Bootable USB stick
Use Rufus to create a bootable USB stick with your choice of Ubuntu based distro. Make sure in Rufus that you CHOOSE the option UEFI/GPT only. This ensures the Linux environment boots only into UEFI mode during your install.
D) Boot Menu
Reboot your computer and press key for one time boot menu (Dell is typically F12). Select your USB stick from the boot options.
Note:
Make sure it says UEFI in front of the USB stick in the boot menu.
If not, return to Windows and recreate your USB stick with Rufus ensuring you choose the UEFI/GPT (only) option.
E) Boot into USB Stick
Boot into Linux live environment and begin install.
F) Installation type
When you get to the installation option, choose "Something else" at the bottom of the Ubiquity installer.
G) Create partitions
Find your secondary HDD that you will be installing Linux to.
In my case it was listed as /dev/sdc (with /dev/sda being the windows drive and /dev/sdb the USB drive [which was invisible in the installer]).
So basically:
+--------------+--------+---------------------------+--------------------------------+
| Device path | Device | Operating System (OS) | Visible in Ubiquity installer? |
+--------------+--------+---------------------------+--------------------------------+
| /dev/sda | HDD | Windows 10 | yes |
| /dev/sdb | USB | Ubuntu 16.04 (Live Stick) | no |
| /dev/sdc | HDD | None | yes |
+--------------+--------+---------------------------+--------------------------------+
1st Partition / EFI
Select your target drive (in my case /dev/sdc)
Select "Make New Partition Table"
Partition the target drive as follows:
Size: 650 MB
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: EFI (this will be listed as /dev/sdc1 efi in the partitioning tool once you create it)
2nd Partition / Root
Select "free space" under your target drive (in my case /dev/sdc)
Select "+"
Partition the target drive as follows:
Size: min. 10 GB (20+GB better)
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: ext4
Mount point: Choose "/"
3rd Partition / Swap
Select "free space" under your target drive (in my case /dev/sdc)
Select "+"
Partition the target drive as follows:
Size: min. 2 GB (20+GB better)
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: swap (if you wish to use hibernation, the swap needs to be just slightly larger than your total amount of RAM - example I have 8 GB so the size of this parition was set at 9000 MB)
4th Partition / Home
Select "free space" under your target drive (in my case /dev/sdc)
Select "+"
Partition the target drive as follows:
Size: remainder of space on drive
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: ext4
Mount point: Choose "/home"
H) Boot loader Device
BEFORE clicking "Install Now", from the "device for boot loader installation" option button, select the 650MB EFI partition you just created as the target for the bootloader. (example /dev/sdc1 in my case).
Click "Install Now".
I) Installation & Reboot
Finish installation process and reboot (removing the USB stick when your UEFI/BIOS screen logo appears).
J) Upon reboot
After UEFI/BIOS reads the new bootloader entry that Linux has added to it, you will be presented with the grub menu with a listing of your Linux distro as well as a listing to boot Windows 10.
Boot into Linux
Install any updates and then reboot and attempt to enter Windows 10 from the grub menu to make sure that grub correctly handles the hand-off to the Windows 10 bootloader.
What you have done:
You have installed the Linux EFI bootloader to the newly created EFI partition. In the process of this, Linux has added an entry to your UEFI listings in your systems UEFI/BIOS. Linux has also automatically detected your Windows 10 install and added a grub menu item to boot it. Your computer at this point will now automatically boot to Linux unless you choose to boot to Windows (from the Grub menu).
What you have not done:
You have not in any way altered your Windows 10 install or its bootloader or even so much as touched the Windows 10 EFI partition. Everything is reversible simply by removing the Linux UEFI listing from your UEFI/BIOS settings. How to do so varies from each vendor.
New contributor
Answer posted here: https://askubuntu.com/questions/726972/dual-boot-windows-10-and-linux-ubuntu-on-separate-hard-drives
here is the quoted text---------------------
This should work for most systems that use UEFI and which have two HDD.
Specification used for the tutorial below:
Dell Inspiron E5440:
Main HDD - 256GB Samsung SSD (Windows 10 installed)
Secondary HDD - 64GB Transcend mSATA SSD (Mint 18 was installed to this drive)
A) UEFI/BIOS
Set to "UEFI mode only" (no legacy/CSM).
Disable "secure boot"
Disable "Intel Rapid Start" (if equipped)
Disable "fast boot" in UEFI (note this is different than the "fastboot" setting in Windows 8/10). The options in your UEFI/BIOS might say something like Full/Minimal/Automatic for boot mode. Select Full (or thorough, or complete, etc whatever your UEFI vendor has chosen to call it).
B) Advanced Power Options (Fastboot)
Disable fastboot in Windows 8/10 under "advanced power options". Restart computer to ensure that this subsequent boot and the next reboot/shutdown will be in "normal" mode.
Optional:
Install Macrium Reflect (free) and create a backup image and reinstallation media should something go wrong with Windows 10.
C) Rufus / Bootable USB stick
Use Rufus to create a bootable USB stick with your choice of Ubuntu based distro. Make sure in Rufus that you CHOOSE the option UEFI/GPT only. This ensures the Linux environment boots only into UEFI mode during your install.
D) Boot Menu
Reboot your computer and press key for one time boot menu (Dell is typically F12). Select your USB stick from the boot options.
Note:
Make sure it says UEFI in front of the USB stick in the boot menu.
If not, return to Windows and recreate your USB stick with Rufus ensuring you choose the UEFI/GPT (only) option.
E) Boot into USB Stick
Boot into Linux live environment and begin install.
F) Installation type
When you get to the installation option, choose "Something else" at the bottom of the Ubiquity installer.
G) Create partitions
Find your secondary HDD that you will be installing Linux to.
In my case it was listed as /dev/sdc (with /dev/sda being the windows drive and /dev/sdb the USB drive [which was invisible in the installer]).
So basically:
+--------------+--------+---------------------------+--------------------------------+
| Device path | Device | Operating System (OS) | Visible in Ubiquity installer? |
+--------------+--------+---------------------------+--------------------------------+
| /dev/sda | HDD | Windows 10 | yes |
| /dev/sdb | USB | Ubuntu 16.04 (Live Stick) | no |
| /dev/sdc | HDD | None | yes |
+--------------+--------+---------------------------+--------------------------------+
1st Partition / EFI
Select your target drive (in my case /dev/sdc)
Select "Make New Partition Table"
Partition the target drive as follows:
Size: 650 MB
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: EFI (this will be listed as /dev/sdc1 efi in the partitioning tool once you create it)
2nd Partition / Root
Select "free space" under your target drive (in my case /dev/sdc)
Select "+"
Partition the target drive as follows:
Size: min. 10 GB (20+GB better)
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: ext4
Mount point: Choose "/"
3rd Partition / Swap
Select "free space" under your target drive (in my case /dev/sdc)
Select "+"
Partition the target drive as follows:
Size: min. 2 GB (20+GB better)
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: swap (if you wish to use hibernation, the swap needs to be just slightly larger than your total amount of RAM - example I have 8 GB so the size of this parition was set at 9000 MB)
4th Partition / Home
Select "free space" under your target drive (in my case /dev/sdc)
Select "+"
Partition the target drive as follows:
Size: remainder of space on drive
Type for the new partition: Primary
Location for the new partition: Beginning of this space
Use as: ext4
Mount point: Choose "/home"
H) Boot loader Device
BEFORE clicking "Install Now", from the "device for boot loader installation" option button, select the 650MB EFI partition you just created as the target for the bootloader. (example /dev/sdc1 in my case).
Click "Install Now".
I) Installation & Reboot
Finish installation process and reboot (removing the USB stick when your UEFI/BIOS screen logo appears).
J) Upon reboot
After UEFI/BIOS reads the new bootloader entry that Linux has added to it, you will be presented with the grub menu with a listing of your Linux distro as well as a listing to boot Windows 10.
Boot into Linux
Install any updates and then reboot and attempt to enter Windows 10 from the grub menu to make sure that grub correctly handles the hand-off to the Windows 10 bootloader.
What you have done:
You have installed the Linux EFI bootloader to the newly created EFI partition. In the process of this, Linux has added an entry to your UEFI listings in your systems UEFI/BIOS. Linux has also automatically detected your Windows 10 install and added a grub menu item to boot it. Your computer at this point will now automatically boot to Linux unless you choose to boot to Windows (from the Grub menu).
What you have not done:
You have not in any way altered your Windows 10 install or its bootloader or even so much as touched the Windows 10 EFI partition. Everything is reversible simply by removing the Linux UEFI listing from your UEFI/BIOS settings. How to do so varies from each vendor.
New contributor
New contributor
answered 53 mins ago
WillWill
1
1
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f241603%2fno-grub-menu-after-ubuntu-install-booting-directly-into-ubuntu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
There are two ways actually: WIndows boot manager detects Linux, or let Grub detects Windows. The latter might requires to manually configure
grub.cfg
to add entry for chainloading Windows at the other partition. I don't use Windows anymore, so I can't put this as answer; This shall be a clue for others to answer or to solve it on own.– clearkimura
Nov 8 '15 at 10:21