Skip to main content

bootloader - primary and secondary boot loaders


From http://www.ibm.com/developerworks/library/l-bootload/index.html



Boot loaders are usually configured in one of two ways: either as a primary boot loader or as a secondary boot loader.


Primary boot loaders are where the first stage of the boot loader is installed on the MBR (per the previous description).


Secondary boot loaders are where the first stage of the boot loader is installed onto a bootable partition.


A separate boot loader must then be installed into the MBR and configured to pass control to the secondary boot loader.



Should "first" in "Secondary boot loaders are where the first stage of the boot loader is installed onto a bootable partition" be "second" instead?


Where is the secondary boot loader stored? Not in MBR where the primary boot loader is stored?


What is "a separate boot loader" in the last sentence? Is it the primary or secondary boot loader?


is the primary boot loader the same concept as the initial program loader (IPL, mentioned in the same link)?



Due to the very small amount of data the BIOS can access, most boot loaders load in two stages. In the first stage of the boot, the BIOS loads a part of the boot loader known as the initial program loader, or IPL. The IPL interrogates the partition table and subsequently is able to load data wherever it may exist on the various media. This action is used initially to locate the second stage boot loader, which holds the remainder of the loader. The second stage boot loader is the real meat of the boot loader; many consider it the only real part of the boot loader. This contains the more disk-intensive parts of the loader, such as user interfaces and kernel loaders. These user interfaces can range from a simple command line to the all-singing, all-dancing GUIs.



Thanks!



Answer



There is an ambiguity in that text actually. Primary boot loader doesn't mean the first stage of a boot loader, and secondary boot loader doesn't mean the second stage of a boot loader.


First stage of a boot loader is the program resides in MBR data which holds partition information and capability to handle very basic disk I/O operations those cannot accomplish to fully load the O.S since MBR boot loader code size is limited to 448-bytes for standart MBR records (lower for spesific O.S implementations, since partition table holds 4*16-Bytes)


First stage of the boot loader's job is to simply load the second stage which now nows the O.S spesifics and it has much more code space. As far as I remember, NTFS second boot loader has 16 512-bytes sectors to load O.S kernel, 8-KBytes.


Primary and secondary terms come in where there are multiple O.S.es to choose to boot. Each O.S has its boot loader that has first and second stages, each boot loader should start from stage one since the primary boot laoder in MBR shouldn't be expected to know about spesifics of the second stages in every boot loader.


Second stages are stored on the beginning of the partition itself which is called VBR, Volume Boot Record.


When there is one O.S to boot, MBR program (IPL) is the first stage and VBR program is the second stage. When there are multiple O.Ss, MBR program becomes the first stage of the primary boot loader, that stage know there are some code in some partition which is second stage to fully load the whole menu and options, and loads it. That second stage knows about the partitions which has VBR, and continues with VBR, now VBR became secondary boot loader.


Yes, I said "each boot loader should start from stage one since the primary boot laoder in MBR shouldn't be expected to know about spesifics of the second stages in every boot loader.". It is why VBR code also has MBR code in itself, too. Windows VBR codes have it.


Comments

Post a Comment

Popular Posts

How do I transmit a single hexadecimal value serial data in PuTTY using an Alt code?

I am trying to sent a specific hexadecimal value across a serial COM port using PuTTY. Specifically, I want to send the hex codes 9C, B6, FC, and 8B. I have looked up the Alt codes for these and they are 156, 182, 252, and 139 respectively. However, whenever I input the Alt codes, a preceding hex value of C2 is sent before 9C, B6, and 8B so the values that are sent are C2 9C, C2 B6, and C2 8B. The value for FC is changed to C3 FC. Why are these values being placed before the hex value and why is FC being changed altogether? To me, it seems like there is a problem internally converting the Alt code to hex. Is there a way to directly input hex values without using Alt codes in PuTTY? Answer What you're seeing is just ordinary text character set conversion. As far as PuTTY is concerned, you are typing (and reading) text , not raw binary data, therefore it has to convert the text to bytes in whatever configured character set before sending it over the wire. In other words, when y...
Post a Comment
Read more

linux - Extract/save a mail attachment using bash

Using normal bash tools (ie, built-ins or commonly-available command-line tools), is it possible, and how to extract/save attachments on emails? For example, say I have a nightly report which arrives via email but is a zip archive of several log files. I want to save all those zips into a backup directory. How would I accomplish that? Answer If you're aiming for portability, beware that there are several different versions of mail(1) and mailx(1) . There's a POSIX mailx command, but with very few requirements. And none of the implementations I have seem to parse attachments anyway. You might have the mpack package . Its munpack command saves all parts of a MIME message into separate files, then all you have to do is save the interesting parts and clean up the rest. There's also metamail . An equivalent of munpack is metamail -wy .
Post a Comment
Read more

ubuntu - Why does my USB hdd returns SG_IO: bad/missing sense data?

I am able to boot and run commands from external USB hdd; the message in question appears for about 45 seconds then booting continues. GRUB2 is installed on internal HDD. When choosing to boot directly to /dev/sdb the message doesn't appear, however boot time is about the same as booting to internal HDD. /dev/sdb: Timing cached reads: 1018 MB in 2.00 seconds = 508.97 MB/sec Timing buffered disk reads: 80 MB in 3.03 seconds = 26.37 MB/sec pfeiffep@de:~$ sudo hdparm -i /dev/sdb /dev/sdb: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 10 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 HDIO_GET_IDENTITY failed: Invalid argument Gparted correctly identifies the drive as SAMSUNG MP0402H. Any ideas how to remedy the HDIO & SG_IO messages?
Post a Comment
Read more

Desktop reboots itself on sleep or hibernate

I have been using an ASUS M2NPV-VM motherboard for main home desktop workstation, operating Windows Vista x64. This computer has right from day one not been able to enter hibernate or standby; after Windows performs its final actions and brings the machine down, it would automatically revive itself for a reboot. Updating to the second latest BIOS (1201)has not helped (the latest BIOS revision would induce video refresh problems rendering it unusable). I have been reading related discussions on incidents similar to mine to no avail of a true workable solution. They appear to be more speculative guesses rather than actual knowledge on the inner workings of motherboard hardware. Does anybody have any electronic engineering experience on PC energy-saving standards to provide a more informed opinion how to go about getting this to work? More stories: this motherboard could not even reboot properly the first thing i used it. It was due to refresh rate of the onboard GPU, which had no influe...
Post a Comment
Read more