Where is the boot loader installed?
Where is the boot loader, such as Grub, installed generally?
When I install 12.04 along side Windows on different partitions of my disk, I encountered a choice for "Device for boot loader installation". If I understand it correctly, it is to specify where to install the boot loader Grub,
I found on the internet that it is to specify the disk that contains the partitions for the OS, not any partition on the disk. E.g.
disk sda, not partition sda1, sda2.
Questions:
I wonder where the boot loader installed actually on the disk?
Is it installed on any of the existing partitions for the OSes and for personal data, or does it have its own partition, which is also visible e.g. from system monitor of Ubuntu?
Thanks and regards!
bootloader
|
show 1 more comment
Where is the boot loader, such as Grub, installed generally?
When I install 12.04 along side Windows on different partitions of my disk, I encountered a choice for "Device for boot loader installation". If I understand it correctly, it is to specify where to install the boot loader Grub,
I found on the internet that it is to specify the disk that contains the partitions for the OS, not any partition on the disk. E.g.
disk sda, not partition sda1, sda2.
Questions:
I wonder where the boot loader installed actually on the disk?
Is it installed on any of the existing partitions for the OSes and for personal data, or does it have its own partition, which is also visible e.g. from system monitor of Ubuntu?
Thanks and regards!
bootloader
1
The bootloader is installed on the HARD DISK and on the ubuntu's root folder (as far as I know)
– Ravi
May 27 '12 at 13:52
(1) Does it have its own partition visible from Ubuntu system monitor, or on some existing partition? (2) By "on the ubuntu's root folder", you mean in the same partition of the installed Ubuntu, i.e. the partition for "/"? But when I chose "/" as "Device for boot loader installation", there was error in loading the OS options to boot into during starting. I can only choose the whole disk not any of its partitions as "Device for boot loader installation".
– Tim
May 27 '12 at 13:55
Edit you title please. I think it is not according to your question
– Ashu
May 27 '12 at 15:24
If UEFI system, part of grub is in the ESP - efi system partition which is shared with Windows boot loader. And UEFI has NVRAM that remembers entries. askubuntu.com/questions/63610/… & this was for deleting Windows but same process: askubuntu.com/questions/794725/…
– oldfred
Sep 19 '17 at 19:21
1
Could you please open a new question if you have a new or follow-up question? If you tack hardly related questions onto existing questions you broaden their scope which makes them harder to answer. On top of that it likely invalidates existing answers. I took the liberty to revert the edit that adds the follow-up question. Thanks.
– David Foerster
Sep 20 '17 at 14:15
|
show 1 more comment
Where is the boot loader, such as Grub, installed generally?
When I install 12.04 along side Windows on different partitions of my disk, I encountered a choice for "Device for boot loader installation". If I understand it correctly, it is to specify where to install the boot loader Grub,
I found on the internet that it is to specify the disk that contains the partitions for the OS, not any partition on the disk. E.g.
disk sda, not partition sda1, sda2.
Questions:
I wonder where the boot loader installed actually on the disk?
Is it installed on any of the existing partitions for the OSes and for personal data, or does it have its own partition, which is also visible e.g. from system monitor of Ubuntu?
Thanks and regards!
bootloader
Where is the boot loader, such as Grub, installed generally?
When I install 12.04 along side Windows on different partitions of my disk, I encountered a choice for "Device for boot loader installation". If I understand it correctly, it is to specify where to install the boot loader Grub,
I found on the internet that it is to specify the disk that contains the partitions for the OS, not any partition on the disk. E.g.
disk sda, not partition sda1, sda2.
Questions:
I wonder where the boot loader installed actually on the disk?
Is it installed on any of the existing partitions for the OSes and for personal data, or does it have its own partition, which is also visible e.g. from system monitor of Ubuntu?
Thanks and regards!
bootloader
bootloader
edited May 27 '12 at 15:25
Tim
asked May 27 '12 at 13:44
TimTim
8,04142103174
8,04142103174
1
The bootloader is installed on the HARD DISK and on the ubuntu's root folder (as far as I know)
– Ravi
May 27 '12 at 13:52
(1) Does it have its own partition visible from Ubuntu system monitor, or on some existing partition? (2) By "on the ubuntu's root folder", you mean in the same partition of the installed Ubuntu, i.e. the partition for "/"? But when I chose "/" as "Device for boot loader installation", there was error in loading the OS options to boot into during starting. I can only choose the whole disk not any of its partitions as "Device for boot loader installation".
– Tim
May 27 '12 at 13:55
Edit you title please. I think it is not according to your question
– Ashu
May 27 '12 at 15:24
If UEFI system, part of grub is in the ESP - efi system partition which is shared with Windows boot loader. And UEFI has NVRAM that remembers entries. askubuntu.com/questions/63610/… & this was for deleting Windows but same process: askubuntu.com/questions/794725/…
– oldfred
Sep 19 '17 at 19:21
1
Could you please open a new question if you have a new or follow-up question? If you tack hardly related questions onto existing questions you broaden their scope which makes them harder to answer. On top of that it likely invalidates existing answers. I took the liberty to revert the edit that adds the follow-up question. Thanks.
– David Foerster
Sep 20 '17 at 14:15
|
show 1 more comment
1
The bootloader is installed on the HARD DISK and on the ubuntu's root folder (as far as I know)
– Ravi
May 27 '12 at 13:52
(1) Does it have its own partition visible from Ubuntu system monitor, or on some existing partition? (2) By "on the ubuntu's root folder", you mean in the same partition of the installed Ubuntu, i.e. the partition for "/"? But when I chose "/" as "Device for boot loader installation", there was error in loading the OS options to boot into during starting. I can only choose the whole disk not any of its partitions as "Device for boot loader installation".
– Tim
May 27 '12 at 13:55
Edit you title please. I think it is not according to your question
– Ashu
May 27 '12 at 15:24
If UEFI system, part of grub is in the ESP - efi system partition which is shared with Windows boot loader. And UEFI has NVRAM that remembers entries. askubuntu.com/questions/63610/… & this was for deleting Windows but same process: askubuntu.com/questions/794725/…
– oldfred
Sep 19 '17 at 19:21
1
Could you please open a new question if you have a new or follow-up question? If you tack hardly related questions onto existing questions you broaden their scope which makes them harder to answer. On top of that it likely invalidates existing answers. I took the liberty to revert the edit that adds the follow-up question. Thanks.
– David Foerster
Sep 20 '17 at 14:15
1
1
The bootloader is installed on the HARD DISK and on the ubuntu's root folder (as far as I know)
– Ravi
May 27 '12 at 13:52
The bootloader is installed on the HARD DISK and on the ubuntu's root folder (as far as I know)
– Ravi
May 27 '12 at 13:52
(1) Does it have its own partition visible from Ubuntu system monitor, or on some existing partition? (2) By "on the ubuntu's root folder", you mean in the same partition of the installed Ubuntu, i.e. the partition for "/"? But when I chose "/" as "Device for boot loader installation", there was error in loading the OS options to boot into during starting. I can only choose the whole disk not any of its partitions as "Device for boot loader installation".
– Tim
May 27 '12 at 13:55
(1) Does it have its own partition visible from Ubuntu system monitor, or on some existing partition? (2) By "on the ubuntu's root folder", you mean in the same partition of the installed Ubuntu, i.e. the partition for "/"? But when I chose "/" as "Device for boot loader installation", there was error in loading the OS options to boot into during starting. I can only choose the whole disk not any of its partitions as "Device for boot loader installation".
– Tim
May 27 '12 at 13:55
Edit you title please. I think it is not according to your question
– Ashu
May 27 '12 at 15:24
Edit you title please. I think it is not according to your question
– Ashu
May 27 '12 at 15:24
If UEFI system, part of grub is in the ESP - efi system partition which is shared with Windows boot loader. And UEFI has NVRAM that remembers entries. askubuntu.com/questions/63610/… & this was for deleting Windows but same process: askubuntu.com/questions/794725/…
– oldfred
Sep 19 '17 at 19:21
If UEFI system, part of grub is in the ESP - efi system partition which is shared with Windows boot loader. And UEFI has NVRAM that remembers entries. askubuntu.com/questions/63610/… & this was for deleting Windows but same process: askubuntu.com/questions/794725/…
– oldfred
Sep 19 '17 at 19:21
1
1
Could you please open a new question if you have a new or follow-up question? If you tack hardly related questions onto existing questions you broaden their scope which makes them harder to answer. On top of that it likely invalidates existing answers. I took the liberty to revert the edit that adds the follow-up question. Thanks.
– David Foerster
Sep 20 '17 at 14:15
Could you please open a new question if you have a new or follow-up question? If you tack hardly related questions onto existing questions you broaden their scope which makes them harder to answer. On top of that it likely invalidates existing answers. I took the liberty to revert the edit that adds the follow-up question. Thanks.
– David Foerster
Sep 20 '17 at 14:15
|
show 1 more comment
6 Answers
6
active
oldest
votes
The boot loader needs to be installed where the BIOS is looking for something to boot. To keep things simple, you usually have a disk drive where your computer boots from, you install a GNU/Linux system in that disk and the bootloader gets there too.
The only things you need from the bootloader are really:
- That the BIOS is able to find it
- That it is able to find and boot your Operating System (with Linux, you just need the bootloader to have somehow access to the kernel and, if you're using one, the initrd image.)
As far as you have these two points covered, you install it where it is more convenient and where the BIOS will look for it.
The BIOS will usually look for bootloaders in the Master Boot Record of hard drives, a small area in the beginning of the drive where you can put some code to be run. You can also have a bootloader installed at the beginning of a partition.
Bootloaders are usually small enough to fit in these small areas, and even if they don't, they must put something there so the BIOS boots the bootloader.
lilo
is a simple bootloader which is installed in those areas. grub
is a bit bigger, and so you install some code in those areas, which, then, loads some more code from a disk partition (where grub
is said to be "installed", where its configuration file lies, along with the binary code, this is usually set to be the system /boot
partition, where kernels and initrds are placed too, for convenience).
In this case, if it is prompting you for the disk, this means it's asking you on which Master Boot Record should grub
get installed, that is, the disk you will be booting the computer from. That part of grub will be installed only on the disk MBR. The rest probably gets installed to the same partition as /
or /boot/
of the Ubuntu system you're installing (and that rest is accessible from Ubuntu, look for directories /boot/grub/
or /grub/
).
1
Thanks! Is that small area, ie MBR of the disk, a partition itself, or in other partitions? Does it show up in Ubuntu system monitor?
– Tim
May 27 '12 at 15:11
1
No, the MBR is not a partition. It's actually the place where, along with (optional) boot code, the partition table itself gets stored. It won't appear in the system monitor, as it is not a partition and doesn't have a filesystem (at least if the "system monitor" is this: dedoimedo.com/images/computers/wubi-ubuntu-system-monitor.jpg -- the table of mounted filesystems). It won't show up in tools that show the partition table either. (It is pretty small, BTW: just 512 bytes.)
– njsg
May 27 '12 at 15:38
1
Is BIOS also installed in MBR of a disk? Where is it then?
– Tim
May 27 '12 at 18:57
2
No, the BIOS is in the motherboard in a small, rewritable memory chip. It deals with low-level hardware stuff and it's what deals with some details in the early stages of the computer boot process (like enabling/disabling/preparing some devices, looking for the boot device, managing network boot, and the POST). Wikipedia has an article on the boot process that you may find interesting.
– njsg
May 27 '12 at 19:30
add a comment |
Grub2 is the standard boot loader for Ubuntu. As always we prefer to have highly configurable applications. Grub2 is one of these. Grub2 will install exactly to where you told it to, irrespective of this being a good idea or not.
Master Boot Record
The usual case will be the Master Boot Record (MBR) of the drive you boot your computer from. This is most likely your first (or only) harddisk /sda
. This will also be the default option when installing Grub2.
Other drives
Of course this boot device can also be another harddrive, a SSD, or even an external device. Then you will have to tell Grub2 where you want it to be installed when it asks you.
Partitions
The case where you need to install Grub to a partition is rare but still it is possible, e.g. in case you use another bootloader and chainload Grub from a partition boot record.
Other bootloaders
Other bootloaders are located in the MBR as well. Grub2 will overwrite these and thus you will no longer be able to boot with these. Grub2 will take the role to boot the OS you chose from a menu displayed on boot.
Grub application and settings
The Grub application, and the settings will not fit to the master boot record due to their size. Therefore they will be installed elsewhere (again you can configure this). Usually and per default Grub2 looks for it's files on the root /
partition where you installed your Ubuntu, but this can also be any other partition on any of your harddrives.
Boot partition
Some people believe that it is a good idea to have a separate dedicated boot partition for this. But you will only need this in special cases, e.g. if you installed a UEFI BIOS which needs a GUID Partition Table (GPT) to boot from.
add a comment |
It's exactly where you chose to install it when you installed Ubuntu. ubiquity
prompts you for this information during installation. See below:
If you are running a legacy system (BIOS) this will typically be the Master Boot Record of the drive you choose or the unusual choice of the Partition Boot Record of the partition you chose to install it on. If you are running a system with a Unified Extensible Firmware Interface the grub bootloader will be installed in the ESP.
Sources:
https://help.ubuntu.com/community/Grub2/Installing
https://en.wikipedia.org/wiki/BIOS
https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface
https://www.rodsbooks.com/efi-bootloaders/installation.html#accessing
Experience
add a comment |
The boot loader is installed on the whole hard disk (/dev/sda). You cannot install it in other partition. You can head to here. That link contains excellent information about GRUB.
2
This information is incorrect. A boot loader(in this case Grub) CAN be installed on a partition and it does not have to be installed into MBR. In such setup you can chainload Windows loader and then Grub. Your own link talks about this and gives examples!
– Mxx
Nov 29 '12 at 8:23
@Mxx Feel free to correct my post. :)
– Ravi
Feb 16 '13 at 5:36
add a comment |
It's in the MBR (see https://en.wikipedia.org/wiki/Master_boot_record , https://en.wikipedia.org/wiki/GUID_Partition_Table , https://en.wikipedia.org/wiki/UEFI . grub
is a Bootloader.
add a comment |
I spent an hour trying to find the configuration of where GRUB is installed in Debian, because it's not stored in GRUB's own configuration files.
It turns out it's handled by debconf:
debconf-show grub-pc
and look for "grub-pc/install_devices".
New contributor
add a comment |
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',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2faskubuntu.com%2fquestions%2f142912%2fwhere-is-the-boot-loader-installed%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
The boot loader needs to be installed where the BIOS is looking for something to boot. To keep things simple, you usually have a disk drive where your computer boots from, you install a GNU/Linux system in that disk and the bootloader gets there too.
The only things you need from the bootloader are really:
- That the BIOS is able to find it
- That it is able to find and boot your Operating System (with Linux, you just need the bootloader to have somehow access to the kernel and, if you're using one, the initrd image.)
As far as you have these two points covered, you install it where it is more convenient and where the BIOS will look for it.
The BIOS will usually look for bootloaders in the Master Boot Record of hard drives, a small area in the beginning of the drive where you can put some code to be run. You can also have a bootloader installed at the beginning of a partition.
Bootloaders are usually small enough to fit in these small areas, and even if they don't, they must put something there so the BIOS boots the bootloader.
lilo
is a simple bootloader which is installed in those areas. grub
is a bit bigger, and so you install some code in those areas, which, then, loads some more code from a disk partition (where grub
is said to be "installed", where its configuration file lies, along with the binary code, this is usually set to be the system /boot
partition, where kernels and initrds are placed too, for convenience).
In this case, if it is prompting you for the disk, this means it's asking you on which Master Boot Record should grub
get installed, that is, the disk you will be booting the computer from. That part of grub will be installed only on the disk MBR. The rest probably gets installed to the same partition as /
or /boot/
of the Ubuntu system you're installing (and that rest is accessible from Ubuntu, look for directories /boot/grub/
or /grub/
).
1
Thanks! Is that small area, ie MBR of the disk, a partition itself, or in other partitions? Does it show up in Ubuntu system monitor?
– Tim
May 27 '12 at 15:11
1
No, the MBR is not a partition. It's actually the place where, along with (optional) boot code, the partition table itself gets stored. It won't appear in the system monitor, as it is not a partition and doesn't have a filesystem (at least if the "system monitor" is this: dedoimedo.com/images/computers/wubi-ubuntu-system-monitor.jpg -- the table of mounted filesystems). It won't show up in tools that show the partition table either. (It is pretty small, BTW: just 512 bytes.)
– njsg
May 27 '12 at 15:38
1
Is BIOS also installed in MBR of a disk? Where is it then?
– Tim
May 27 '12 at 18:57
2
No, the BIOS is in the motherboard in a small, rewritable memory chip. It deals with low-level hardware stuff and it's what deals with some details in the early stages of the computer boot process (like enabling/disabling/preparing some devices, looking for the boot device, managing network boot, and the POST). Wikipedia has an article on the boot process that you may find interesting.
– njsg
May 27 '12 at 19:30
add a comment |
The boot loader needs to be installed where the BIOS is looking for something to boot. To keep things simple, you usually have a disk drive where your computer boots from, you install a GNU/Linux system in that disk and the bootloader gets there too.
The only things you need from the bootloader are really:
- That the BIOS is able to find it
- That it is able to find and boot your Operating System (with Linux, you just need the bootloader to have somehow access to the kernel and, if you're using one, the initrd image.)
As far as you have these two points covered, you install it where it is more convenient and where the BIOS will look for it.
The BIOS will usually look for bootloaders in the Master Boot Record of hard drives, a small area in the beginning of the drive where you can put some code to be run. You can also have a bootloader installed at the beginning of a partition.
Bootloaders are usually small enough to fit in these small areas, and even if they don't, they must put something there so the BIOS boots the bootloader.
lilo
is a simple bootloader which is installed in those areas. grub
is a bit bigger, and so you install some code in those areas, which, then, loads some more code from a disk partition (where grub
is said to be "installed", where its configuration file lies, along with the binary code, this is usually set to be the system /boot
partition, where kernels and initrds are placed too, for convenience).
In this case, if it is prompting you for the disk, this means it's asking you on which Master Boot Record should grub
get installed, that is, the disk you will be booting the computer from. That part of grub will be installed only on the disk MBR. The rest probably gets installed to the same partition as /
or /boot/
of the Ubuntu system you're installing (and that rest is accessible from Ubuntu, look for directories /boot/grub/
or /grub/
).
1
Thanks! Is that small area, ie MBR of the disk, a partition itself, or in other partitions? Does it show up in Ubuntu system monitor?
– Tim
May 27 '12 at 15:11
1
No, the MBR is not a partition. It's actually the place where, along with (optional) boot code, the partition table itself gets stored. It won't appear in the system monitor, as it is not a partition and doesn't have a filesystem (at least if the "system monitor" is this: dedoimedo.com/images/computers/wubi-ubuntu-system-monitor.jpg -- the table of mounted filesystems). It won't show up in tools that show the partition table either. (It is pretty small, BTW: just 512 bytes.)
– njsg
May 27 '12 at 15:38
1
Is BIOS also installed in MBR of a disk? Where is it then?
– Tim
May 27 '12 at 18:57
2
No, the BIOS is in the motherboard in a small, rewritable memory chip. It deals with low-level hardware stuff and it's what deals with some details in the early stages of the computer boot process (like enabling/disabling/preparing some devices, looking for the boot device, managing network boot, and the POST). Wikipedia has an article on the boot process that you may find interesting.
– njsg
May 27 '12 at 19:30
add a comment |
The boot loader needs to be installed where the BIOS is looking for something to boot. To keep things simple, you usually have a disk drive where your computer boots from, you install a GNU/Linux system in that disk and the bootloader gets there too.
The only things you need from the bootloader are really:
- That the BIOS is able to find it
- That it is able to find and boot your Operating System (with Linux, you just need the bootloader to have somehow access to the kernel and, if you're using one, the initrd image.)
As far as you have these two points covered, you install it where it is more convenient and where the BIOS will look for it.
The BIOS will usually look for bootloaders in the Master Boot Record of hard drives, a small area in the beginning of the drive where you can put some code to be run. You can also have a bootloader installed at the beginning of a partition.
Bootloaders are usually small enough to fit in these small areas, and even if they don't, they must put something there so the BIOS boots the bootloader.
lilo
is a simple bootloader which is installed in those areas. grub
is a bit bigger, and so you install some code in those areas, which, then, loads some more code from a disk partition (where grub
is said to be "installed", where its configuration file lies, along with the binary code, this is usually set to be the system /boot
partition, where kernels and initrds are placed too, for convenience).
In this case, if it is prompting you for the disk, this means it's asking you on which Master Boot Record should grub
get installed, that is, the disk you will be booting the computer from. That part of grub will be installed only on the disk MBR. The rest probably gets installed to the same partition as /
or /boot/
of the Ubuntu system you're installing (and that rest is accessible from Ubuntu, look for directories /boot/grub/
or /grub/
).
The boot loader needs to be installed where the BIOS is looking for something to boot. To keep things simple, you usually have a disk drive where your computer boots from, you install a GNU/Linux system in that disk and the bootloader gets there too.
The only things you need from the bootloader are really:
- That the BIOS is able to find it
- That it is able to find and boot your Operating System (with Linux, you just need the bootloader to have somehow access to the kernel and, if you're using one, the initrd image.)
As far as you have these two points covered, you install it where it is more convenient and where the BIOS will look for it.
The BIOS will usually look for bootloaders in the Master Boot Record of hard drives, a small area in the beginning of the drive where you can put some code to be run. You can also have a bootloader installed at the beginning of a partition.
Bootloaders are usually small enough to fit in these small areas, and even if they don't, they must put something there so the BIOS boots the bootloader.
lilo
is a simple bootloader which is installed in those areas. grub
is a bit bigger, and so you install some code in those areas, which, then, loads some more code from a disk partition (where grub
is said to be "installed", where its configuration file lies, along with the binary code, this is usually set to be the system /boot
partition, where kernels and initrds are placed too, for convenience).
In this case, if it is prompting you for the disk, this means it's asking you on which Master Boot Record should grub
get installed, that is, the disk you will be booting the computer from. That part of grub will be installed only on the disk MBR. The rest probably gets installed to the same partition as /
or /boot/
of the Ubuntu system you're installing (and that rest is accessible from Ubuntu, look for directories /boot/grub/
or /grub/
).
answered May 27 '12 at 14:28
njsgnjsg
789513
789513
1
Thanks! Is that small area, ie MBR of the disk, a partition itself, or in other partitions? Does it show up in Ubuntu system monitor?
– Tim
May 27 '12 at 15:11
1
No, the MBR is not a partition. It's actually the place where, along with (optional) boot code, the partition table itself gets stored. It won't appear in the system monitor, as it is not a partition and doesn't have a filesystem (at least if the "system monitor" is this: dedoimedo.com/images/computers/wubi-ubuntu-system-monitor.jpg -- the table of mounted filesystems). It won't show up in tools that show the partition table either. (It is pretty small, BTW: just 512 bytes.)
– njsg
May 27 '12 at 15:38
1
Is BIOS also installed in MBR of a disk? Where is it then?
– Tim
May 27 '12 at 18:57
2
No, the BIOS is in the motherboard in a small, rewritable memory chip. It deals with low-level hardware stuff and it's what deals with some details in the early stages of the computer boot process (like enabling/disabling/preparing some devices, looking for the boot device, managing network boot, and the POST). Wikipedia has an article on the boot process that you may find interesting.
– njsg
May 27 '12 at 19:30
add a comment |
1
Thanks! Is that small area, ie MBR of the disk, a partition itself, or in other partitions? Does it show up in Ubuntu system monitor?
– Tim
May 27 '12 at 15:11
1
No, the MBR is not a partition. It's actually the place where, along with (optional) boot code, the partition table itself gets stored. It won't appear in the system monitor, as it is not a partition and doesn't have a filesystem (at least if the "system monitor" is this: dedoimedo.com/images/computers/wubi-ubuntu-system-monitor.jpg -- the table of mounted filesystems). It won't show up in tools that show the partition table either. (It is pretty small, BTW: just 512 bytes.)
– njsg
May 27 '12 at 15:38
1
Is BIOS also installed in MBR of a disk? Where is it then?
– Tim
May 27 '12 at 18:57
2
No, the BIOS is in the motherboard in a small, rewritable memory chip. It deals with low-level hardware stuff and it's what deals with some details in the early stages of the computer boot process (like enabling/disabling/preparing some devices, looking for the boot device, managing network boot, and the POST). Wikipedia has an article on the boot process that you may find interesting.
– njsg
May 27 '12 at 19:30
1
1
Thanks! Is that small area, ie MBR of the disk, a partition itself, or in other partitions? Does it show up in Ubuntu system monitor?
– Tim
May 27 '12 at 15:11
Thanks! Is that small area, ie MBR of the disk, a partition itself, or in other partitions? Does it show up in Ubuntu system monitor?
– Tim
May 27 '12 at 15:11
1
1
No, the MBR is not a partition. It's actually the place where, along with (optional) boot code, the partition table itself gets stored. It won't appear in the system monitor, as it is not a partition and doesn't have a filesystem (at least if the "system monitor" is this: dedoimedo.com/images/computers/wubi-ubuntu-system-monitor.jpg -- the table of mounted filesystems). It won't show up in tools that show the partition table either. (It is pretty small, BTW: just 512 bytes.)
– njsg
May 27 '12 at 15:38
No, the MBR is not a partition. It's actually the place where, along with (optional) boot code, the partition table itself gets stored. It won't appear in the system monitor, as it is not a partition and doesn't have a filesystem (at least if the "system monitor" is this: dedoimedo.com/images/computers/wubi-ubuntu-system-monitor.jpg -- the table of mounted filesystems). It won't show up in tools that show the partition table either. (It is pretty small, BTW: just 512 bytes.)
– njsg
May 27 '12 at 15:38
1
1
Is BIOS also installed in MBR of a disk? Where is it then?
– Tim
May 27 '12 at 18:57
Is BIOS also installed in MBR of a disk? Where is it then?
– Tim
May 27 '12 at 18:57
2
2
No, the BIOS is in the motherboard in a small, rewritable memory chip. It deals with low-level hardware stuff and it's what deals with some details in the early stages of the computer boot process (like enabling/disabling/preparing some devices, looking for the boot device, managing network boot, and the POST). Wikipedia has an article on the boot process that you may find interesting.
– njsg
May 27 '12 at 19:30
No, the BIOS is in the motherboard in a small, rewritable memory chip. It deals with low-level hardware stuff and it's what deals with some details in the early stages of the computer boot process (like enabling/disabling/preparing some devices, looking for the boot device, managing network boot, and the POST). Wikipedia has an article on the boot process that you may find interesting.
– njsg
May 27 '12 at 19:30
add a comment |
Grub2 is the standard boot loader for Ubuntu. As always we prefer to have highly configurable applications. Grub2 is one of these. Grub2 will install exactly to where you told it to, irrespective of this being a good idea or not.
Master Boot Record
The usual case will be the Master Boot Record (MBR) of the drive you boot your computer from. This is most likely your first (or only) harddisk /sda
. This will also be the default option when installing Grub2.
Other drives
Of course this boot device can also be another harddrive, a SSD, or even an external device. Then you will have to tell Grub2 where you want it to be installed when it asks you.
Partitions
The case where you need to install Grub to a partition is rare but still it is possible, e.g. in case you use another bootloader and chainload Grub from a partition boot record.
Other bootloaders
Other bootloaders are located in the MBR as well. Grub2 will overwrite these and thus you will no longer be able to boot with these. Grub2 will take the role to boot the OS you chose from a menu displayed on boot.
Grub application and settings
The Grub application, and the settings will not fit to the master boot record due to their size. Therefore they will be installed elsewhere (again you can configure this). Usually and per default Grub2 looks for it's files on the root /
partition where you installed your Ubuntu, but this can also be any other partition on any of your harddrives.
Boot partition
Some people believe that it is a good idea to have a separate dedicated boot partition for this. But you will only need this in special cases, e.g. if you installed a UEFI BIOS which needs a GUID Partition Table (GPT) to boot from.
add a comment |
Grub2 is the standard boot loader for Ubuntu. As always we prefer to have highly configurable applications. Grub2 is one of these. Grub2 will install exactly to where you told it to, irrespective of this being a good idea or not.
Master Boot Record
The usual case will be the Master Boot Record (MBR) of the drive you boot your computer from. This is most likely your first (or only) harddisk /sda
. This will also be the default option when installing Grub2.
Other drives
Of course this boot device can also be another harddrive, a SSD, or even an external device. Then you will have to tell Grub2 where you want it to be installed when it asks you.
Partitions
The case where you need to install Grub to a partition is rare but still it is possible, e.g. in case you use another bootloader and chainload Grub from a partition boot record.
Other bootloaders
Other bootloaders are located in the MBR as well. Grub2 will overwrite these and thus you will no longer be able to boot with these. Grub2 will take the role to boot the OS you chose from a menu displayed on boot.
Grub application and settings
The Grub application, and the settings will not fit to the master boot record due to their size. Therefore they will be installed elsewhere (again you can configure this). Usually and per default Grub2 looks for it's files on the root /
partition where you installed your Ubuntu, but this can also be any other partition on any of your harddrives.
Boot partition
Some people believe that it is a good idea to have a separate dedicated boot partition for this. But you will only need this in special cases, e.g. if you installed a UEFI BIOS which needs a GUID Partition Table (GPT) to boot from.
add a comment |
Grub2 is the standard boot loader for Ubuntu. As always we prefer to have highly configurable applications. Grub2 is one of these. Grub2 will install exactly to where you told it to, irrespective of this being a good idea or not.
Master Boot Record
The usual case will be the Master Boot Record (MBR) of the drive you boot your computer from. This is most likely your first (or only) harddisk /sda
. This will also be the default option when installing Grub2.
Other drives
Of course this boot device can also be another harddrive, a SSD, or even an external device. Then you will have to tell Grub2 where you want it to be installed when it asks you.
Partitions
The case where you need to install Grub to a partition is rare but still it is possible, e.g. in case you use another bootloader and chainload Grub from a partition boot record.
Other bootloaders
Other bootloaders are located in the MBR as well. Grub2 will overwrite these and thus you will no longer be able to boot with these. Grub2 will take the role to boot the OS you chose from a menu displayed on boot.
Grub application and settings
The Grub application, and the settings will not fit to the master boot record due to their size. Therefore they will be installed elsewhere (again you can configure this). Usually and per default Grub2 looks for it's files on the root /
partition where you installed your Ubuntu, but this can also be any other partition on any of your harddrives.
Boot partition
Some people believe that it is a good idea to have a separate dedicated boot partition for this. But you will only need this in special cases, e.g. if you installed a UEFI BIOS which needs a GUID Partition Table (GPT) to boot from.
Grub2 is the standard boot loader for Ubuntu. As always we prefer to have highly configurable applications. Grub2 is one of these. Grub2 will install exactly to where you told it to, irrespective of this being a good idea or not.
Master Boot Record
The usual case will be the Master Boot Record (MBR) of the drive you boot your computer from. This is most likely your first (or only) harddisk /sda
. This will also be the default option when installing Grub2.
Other drives
Of course this boot device can also be another harddrive, a SSD, or even an external device. Then you will have to tell Grub2 where you want it to be installed when it asks you.
Partitions
The case where you need to install Grub to a partition is rare but still it is possible, e.g. in case you use another bootloader and chainload Grub from a partition boot record.
Other bootloaders
Other bootloaders are located in the MBR as well. Grub2 will overwrite these and thus you will no longer be able to boot with these. Grub2 will take the role to boot the OS you chose from a menu displayed on boot.
Grub application and settings
The Grub application, and the settings will not fit to the master boot record due to their size. Therefore they will be installed elsewhere (again you can configure this). Usually and per default Grub2 looks for it's files on the root /
partition where you installed your Ubuntu, but this can also be any other partition on any of your harddrives.
Boot partition
Some people believe that it is a good idea to have a separate dedicated boot partition for this. But you will only need this in special cases, e.g. if you installed a UEFI BIOS which needs a GUID Partition Table (GPT) to boot from.
edited Oct 27 '12 at 7:54
answered May 27 '12 at 18:56
TakkatTakkat
106k35249375
106k35249375
add a comment |
add a comment |
It's exactly where you chose to install it when you installed Ubuntu. ubiquity
prompts you for this information during installation. See below:
If you are running a legacy system (BIOS) this will typically be the Master Boot Record of the drive you choose or the unusual choice of the Partition Boot Record of the partition you chose to install it on. If you are running a system with a Unified Extensible Firmware Interface the grub bootloader will be installed in the ESP.
Sources:
https://help.ubuntu.com/community/Grub2/Installing
https://en.wikipedia.org/wiki/BIOS
https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface
https://www.rodsbooks.com/efi-bootloaders/installation.html#accessing
Experience
add a comment |
It's exactly where you chose to install it when you installed Ubuntu. ubiquity
prompts you for this information during installation. See below:
If you are running a legacy system (BIOS) this will typically be the Master Boot Record of the drive you choose or the unusual choice of the Partition Boot Record of the partition you chose to install it on. If you are running a system with a Unified Extensible Firmware Interface the grub bootloader will be installed in the ESP.
Sources:
https://help.ubuntu.com/community/Grub2/Installing
https://en.wikipedia.org/wiki/BIOS
https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface
https://www.rodsbooks.com/efi-bootloaders/installation.html#accessing
Experience
add a comment |
It's exactly where you chose to install it when you installed Ubuntu. ubiquity
prompts you for this information during installation. See below:
If you are running a legacy system (BIOS) this will typically be the Master Boot Record of the drive you choose or the unusual choice of the Partition Boot Record of the partition you chose to install it on. If you are running a system with a Unified Extensible Firmware Interface the grub bootloader will be installed in the ESP.
Sources:
https://help.ubuntu.com/community/Grub2/Installing
https://en.wikipedia.org/wiki/BIOS
https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface
https://www.rodsbooks.com/efi-bootloaders/installation.html#accessing
Experience
It's exactly where you chose to install it when you installed Ubuntu. ubiquity
prompts you for this information during installation. See below:
If you are running a legacy system (BIOS) this will typically be the Master Boot Record of the drive you choose or the unusual choice of the Partition Boot Record of the partition you chose to install it on. If you are running a system with a Unified Extensible Firmware Interface the grub bootloader will be installed in the ESP.
Sources:
https://help.ubuntu.com/community/Grub2/Installing
https://en.wikipedia.org/wiki/BIOS
https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface
https://www.rodsbooks.com/efi-bootloaders/installation.html#accessing
Experience
answered Sep 20 '17 at 0:03
Elder GeekElder Geek
26.5k952126
26.5k952126
add a comment |
add a comment |
The boot loader is installed on the whole hard disk (/dev/sda). You cannot install it in other partition. You can head to here. That link contains excellent information about GRUB.
2
This information is incorrect. A boot loader(in this case Grub) CAN be installed on a partition and it does not have to be installed into MBR. In such setup you can chainload Windows loader and then Grub. Your own link talks about this and gives examples!
– Mxx
Nov 29 '12 at 8:23
@Mxx Feel free to correct my post. :)
– Ravi
Feb 16 '13 at 5:36
add a comment |
The boot loader is installed on the whole hard disk (/dev/sda). You cannot install it in other partition. You can head to here. That link contains excellent information about GRUB.
2
This information is incorrect. A boot loader(in this case Grub) CAN be installed on a partition and it does not have to be installed into MBR. In such setup you can chainload Windows loader and then Grub. Your own link talks about this and gives examples!
– Mxx
Nov 29 '12 at 8:23
@Mxx Feel free to correct my post. :)
– Ravi
Feb 16 '13 at 5:36
add a comment |
The boot loader is installed on the whole hard disk (/dev/sda). You cannot install it in other partition. You can head to here. That link contains excellent information about GRUB.
The boot loader is installed on the whole hard disk (/dev/sda). You cannot install it in other partition. You can head to here. That link contains excellent information about GRUB.
edited May 27 '12 at 14:19
answered May 27 '12 at 14:01
RaviRavi
1,00421526
1,00421526
2
This information is incorrect. A boot loader(in this case Grub) CAN be installed on a partition and it does not have to be installed into MBR. In such setup you can chainload Windows loader and then Grub. Your own link talks about this and gives examples!
– Mxx
Nov 29 '12 at 8:23
@Mxx Feel free to correct my post. :)
– Ravi
Feb 16 '13 at 5:36
add a comment |
2
This information is incorrect. A boot loader(in this case Grub) CAN be installed on a partition and it does not have to be installed into MBR. In such setup you can chainload Windows loader and then Grub. Your own link talks about this and gives examples!
– Mxx
Nov 29 '12 at 8:23
@Mxx Feel free to correct my post. :)
– Ravi
Feb 16 '13 at 5:36
2
2
This information is incorrect. A boot loader(in this case Grub) CAN be installed on a partition and it does not have to be installed into MBR. In such setup you can chainload Windows loader and then Grub. Your own link talks about this and gives examples!
– Mxx
Nov 29 '12 at 8:23
This information is incorrect. A boot loader(in this case Grub) CAN be installed on a partition and it does not have to be installed into MBR. In such setup you can chainload Windows loader and then Grub. Your own link talks about this and gives examples!
– Mxx
Nov 29 '12 at 8:23
@Mxx Feel free to correct my post. :)
– Ravi
Feb 16 '13 at 5:36
@Mxx Feel free to correct my post. :)
– Ravi
Feb 16 '13 at 5:36
add a comment |
It's in the MBR (see https://en.wikipedia.org/wiki/Master_boot_record , https://en.wikipedia.org/wiki/GUID_Partition_Table , https://en.wikipedia.org/wiki/UEFI . grub
is a Bootloader.
add a comment |
It's in the MBR (see https://en.wikipedia.org/wiki/Master_boot_record , https://en.wikipedia.org/wiki/GUID_Partition_Table , https://en.wikipedia.org/wiki/UEFI . grub
is a Bootloader.
add a comment |
It's in the MBR (see https://en.wikipedia.org/wiki/Master_boot_record , https://en.wikipedia.org/wiki/GUID_Partition_Table , https://en.wikipedia.org/wiki/UEFI . grub
is a Bootloader.
It's in the MBR (see https://en.wikipedia.org/wiki/Master_boot_record , https://en.wikipedia.org/wiki/GUID_Partition_Table , https://en.wikipedia.org/wiki/UEFI . grub
is a Bootloader.
answered Sep 19 '17 at 17:45
waltinatorwaltinator
22k74169
22k74169
add a comment |
add a comment |
I spent an hour trying to find the configuration of where GRUB is installed in Debian, because it's not stored in GRUB's own configuration files.
It turns out it's handled by debconf:
debconf-show grub-pc
and look for "grub-pc/install_devices".
New contributor
add a comment |
I spent an hour trying to find the configuration of where GRUB is installed in Debian, because it's not stored in GRUB's own configuration files.
It turns out it's handled by debconf:
debconf-show grub-pc
and look for "grub-pc/install_devices".
New contributor
add a comment |
I spent an hour trying to find the configuration of where GRUB is installed in Debian, because it's not stored in GRUB's own configuration files.
It turns out it's handled by debconf:
debconf-show grub-pc
and look for "grub-pc/install_devices".
New contributor
I spent an hour trying to find the configuration of where GRUB is installed in Debian, because it's not stored in GRUB's own configuration files.
It turns out it's handled by debconf:
debconf-show grub-pc
and look for "grub-pc/install_devices".
New contributor
New contributor
answered 1 hour ago
mmu_manmmu_man
1
1
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f142912%2fwhere-is-the-boot-loader-installed%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
1
The bootloader is installed on the HARD DISK and on the ubuntu's root folder (as far as I know)
– Ravi
May 27 '12 at 13:52
(1) Does it have its own partition visible from Ubuntu system monitor, or on some existing partition? (2) By "on the ubuntu's root folder", you mean in the same partition of the installed Ubuntu, i.e. the partition for "/"? But when I chose "/" as "Device for boot loader installation", there was error in loading the OS options to boot into during starting. I can only choose the whole disk not any of its partitions as "Device for boot loader installation".
– Tim
May 27 '12 at 13:55
Edit you title please. I think it is not according to your question
– Ashu
May 27 '12 at 15:24
If UEFI system, part of grub is in the ESP - efi system partition which is shared with Windows boot loader. And UEFI has NVRAM that remembers entries. askubuntu.com/questions/63610/… & this was for deleting Windows but same process: askubuntu.com/questions/794725/…
– oldfred
Sep 19 '17 at 19:21
1
Could you please open a new question if you have a new or follow-up question? If you tack hardly related questions onto existing questions you broaden their scope which makes them harder to answer. On top of that it likely invalidates existing answers. I took the liberty to revert the edit that adds the follow-up question. Thanks.
– David Foerster
Sep 20 '17 at 14:15