{"id":1891,"date":"2020-05-14T20:55:38","date_gmt":"2020-05-14T20:55:38","guid":{"rendered":"https:\/\/www.liainfraservices.com\/blog\/?p=1891"},"modified":"2022-06-02T05:50:13","modified_gmt":"2022-06-02T05:50:13","slug":"linux-booting-process","status":"publish","type":"post","link":"https:\/\/www.liainfraservices.com\/blog\/linux-booting-process\/","title":{"rendered":"Linux booting process"},"content":{"rendered":"<\/span> 5<\/span> min read<\/span><\/span>
<\/span> 5,571<\/span><\/div>\n
\"Linux<\/figure>\n\n\n\n

The Linux booting process<\/a> is mainly divided into 5 steps.<\/span><\/strong><\/p>\n\n\n\n

\n

1.BIOS \/ UEFI <\/p>\n\n\n\n

2.MBR<\/p>\n\n\n\n

3.GRUB<\/p>\n\n\n\n

4. KERNEL<\/p>\n\n\n\n

SYSTEMD [For new version distro ] or <\/p>\n\n\n\n

INITD [For Old less than CentOS 6 ]<\/p>\n<\/div>\n\n\n\n

BIOS<\/strong> : This performs POST (power on self test) and then based on the boot order mentioned on CMOS, it selects the appropriate boot disk to execute the MBR. So, basically it executes the POST and hands over the task to MBR.<\/p>\n\n\n\n

MBR<\/strong> : MBR actually sits on the 1st sector (or famously known as zero sector) of the boot drive. <\/p>\n\n\n\n

            This is also named as Stage-1 boot loader.<\/p>\n\n\n\n

            MBR hands over the control to a different programme called GRUB.<\/p>\n\n\n\n

GRUB<\/strong> : [Grand Unified Boot Loader] – This the default boot loader of Linux<\/p>\n\n\n\n

            GRUB main purpose is just to Load the Kernel into MEMORY<\/p>\n\n\n\n

Kernel<\/strong> : Once the Kernel is loaded into the Memory, Kernel initialises itself. <\/p>\n\n\n\n

             Then it loads the initrd image(Initial Ram Disk) <\/p>\n\n\n\n

            Eventually, this initrd.img contains the temporary root file system and other essential Kernel Modules, which are used to load the actual (\/) root file system.<\/p>\n\n\n\n

            Once the root file system is loaded into the memory, the kernel goes to the <\/p>\n\n\n\n

background and gives the control to Systemd<\/p>\n\n\n\n

Systemd<\/strong>: Here kernel actually forks the system demon and executes the process known as initd or systemd [This is the first process runs on the Linux upon booting, so it gets the pid as 1 ]<\/p>\n\n\n\n

\"Linux<\/a><\/figure>\n\n\n\n

Explanation of Linux boot process and system initialization  in more details:<\/strong><\/h3>\n\n\n\n

Bios\/UEFI initialization<\/strong> : <\/h4>\n\n\n\n

Once we press the power button on our computer, it initialises its own firmware and gets the CPU running.<\/p>\n\n\n\n

Importantly, one of the CPU processors(multi-core) is chosen as a boot-strap processor[BSP], the remaining processors are called application processor.<\/p>\n\n\n\n

BSP remains active during the boot  process and the AP remains halted.<\/p>\n\n\n\n

the BSP executes the BIOS code, The BIOS code actually executes the POST.<\/p>\n\n\n\n

Once the POST is completed, the BIOS next mission is to boot an OS[Operating system]<\/p>\n\n\n\n

So, it starts to locate the booting device, <\/p>\n\n\n\n

In this case, the booting device can  be a Hard Disk, CD, Flash drive, or a network device.<\/p>\n\n\n\n

At last, the CMOS contains the priority of the booting device, which can be changed by the user by loading the BIOS interface.<\/p>\n\n\n\n

Hard Disk is always the default boot device.<\/p>\n\n\n\n

So, BIOS reads the Zero sector of the disk, which is 1st 512 bytes of the disk.<\/p>\n\n\n\n

The contents on that first 512 bytes, loads into the Memory.<\/p>\n\n\n\n

MBR<\/strong> : <\/h4>\n\n\n\n

The Zero sector of the disk. First 512 Bytes of the disk.<\/p>\n\n\n\n

            It contains the code that is known as Stage-1 boot loader.<\/p>\n\n\n\n

512 Bytes = 440 bytes of Code + 4 Bytes of Disk Signature + 2 Bytes of Nulls + Four 16 bytes(64 Bytes) of partition table + 2 Bytes of MBR signature.<\/td><\/tr><\/tbody><\/table>
This shows how the MBR partition is structured<\/figcaption><\/figure>\n\n\n\n

To see the 440 bytes of code<\/strong> into the MBR, execute the command –> dd if=\/dev\/xvda bs=440 count=1 | hexdump -C<\/span><\/strong><\/p>\n\n\n\n

\"https:\/\/lh6.googleusercontent.com\/GBXu17KhfnbdYTXHWza0IIJyd4zxQkltnZ9dnOS1njM4k8eyGH08SuJm3OanHorxDEYjHj6tjyonnpoJZUazGuk3fYceTYjKgrZqOQr7m5j80pxv-uYsTgYlhvsh3z-SpU8IeLHc\"<\/figure>\n\n\n\n

To See the last 2 bytes of MBR Signature<\/strong> --> dd if=\/dev\/xvda bs=512 count=1 | hexdump -C | tail -c 2 | hexdump -C<\/span><\/strong><\/code><\/p>\n\n\n\n

Remember, the 440 bytes of code residing on the MBR actually cannot load the entire kernel, because it does not have the intelligence to learn about the file system etc. <\/p>\n\n\n\n

Then, why do we care about this 440 bytes of code ?<\/p>\n\n\n\n

Because this is used to load the actual boot loader.<\/p>\n\n\n\n

The Boot Loader<\/strong> : <\/h4>\n\n\n\n

A boot loader is the first software programme that runs when a computer starts.<\/p>\n\n\n\n

For instance,<\/p>\n\n\n\n

Linux, LILO, GRUB-Legacy and GRUB2 are the bootloaders.<\/p>\n\n\n\n

Windows NTLDR (New Technology Loader), Loadlin(DOS)<\/p>\n\n\n\n

For Linux boot loader GRUB2, there are 3 stages.<\/h3>\n\n\n\n

            Stage1<\/strong> – 446 bytes of boot.img resides on MBR –> This is used to load the Stage 1.5 Bootloader<\/p>\n\n\n\n

            Stage1.5<\/strong> – 30 KB of code, known as core.img. [512 B of MBR+30KB of Core.img+1st partition+2nd partition = 1st disk]<\/p>\n\n\n\n

                        This is generally used to store the file system drivers and loadable kernel modules(LKM)<\/p>\n\n\n\n

                        This enables the stage 1.5 to load stage 2 bootloader.<\/p>\n\n\n\n

            Stage2<\/strong> – Let’s identify what files belong to GRUB stage 2.<\/p>\n\n\n\n

                        If you navigate to a Linux terminal on \/boot<\/p>\n\n\n\n

                        You would see the files that is required to boot the OS<\/p>\n\n\n\n

  1. vmlinuz<\/strong> –> Compressed bootable Kernel Image<\/li>
  2. initrd.img<\/strong> or initramfs.img<\/strong>  –> This is the compressed virtual replica of the root file system.<\/li>
  3. config<\/strong> –> File contains the configuration parameters for the Linux kernel<\/li>
  4. system.map<\/strong> –> Symbol table used by the kernel<\/li><\/ol>\n\n\n\n

    Moreover, Grub displays the list of all OS and expects the user to select the OS that it should load.<\/p>\n\n\n\n

    \"Grub<\/figure>\n\n\n\n

    Now, where the flashing screen comes from.<\/span><\/em><\/p>\n\n\n\n

                It comes from \/boot\/Grub\/grub.cfg –> This file contents are shown on the terminal while the machine boots.<\/p>\n\n\n\n

    If by any reason, you need to do some changes to this file, its better to change on the file under cat \/etc\/default\/grub<\/p>\n\n\n\n

    After making any changes, execute either update-grub<\/span> or grub2-mkconfig<\/span><\/p>\n\n\n\n

    Now, once the system boots and we select the kernel that needs to boot. And that leads us to the next stage.<\/p>\n\n\n\n

    Kernel Initialization<\/strong> : <\/h4>\n\n\n\n