CertNote/ Commute Study Notes
Roadmap
KOEN
CLF-C02 · FoundationalCloud Practitioner - Foundational
DVA-C02 · AssociateDeveloper - Associate
SAA-C03 · AssociateSolutions Architect - Associate
SOA-C02 · AssociateCloudOps Engineer - Associate
SAP-C02 · ProfessionalSolutions Architect - Professional
DOP-C02 · ProfessionalDevOps Engineer - Professional
Linux Master 2 · 2급KAIT Linux Master - Level 2
  • Week 1
    • 1.Operating Systems and the Kernel: What Linux Does
    • 2.The Birth of Linux: From Unix to Linus
    • 3.Free Software and Open Source: What a License Decides
    • 4.Distributions: The Unit That Bundles the Kernel and Tools for Sale
    • 5.Week 1 Review: The Identity Behind the Name Linux
  • Week 2
    • 1.Installation Types and Preparation: Before You First Install Linux
    • 2.Partitions: How to Divide a Disk
    • 3.File Systems: What to Lay Over the Divided Space
    • 4.The Boot Manager: From Power-On to Login
    • 5.Week 2 Review: From Installation to Boot in One Line
  • Week 3
  • Week 4
  • Week 5
  • Week 6
  • Week 7
  • Week 8
  • Week 9
  • Week 10
  • Week 11
SCS-C03 · SpecialtySecurity - Specialty
Linux Master 1 · 1급KAIT Linux Master - Level 1
MLA-C01 · AssociateMachine Learning Engineer - Associate
AIF-C01 · FoundationalAI Practitioner - Foundational
DEA-C01 · AssociateData Engineer - Associate
MLS-C01 · SpecialtyMachine Learning - Specialty
SQLD · 개발자SQL Developer (SQLD)

© CertNote · 주간랩스

  • About
  • Changelog
  • Contact
  • Terms
  • Privacy
← Linux Master 2/Week 2/Day 5

Based on the Linux Master 2 exam syllabus·Report an error

Linux Master 2· AssociateWeek 2 · Day 5~17 min read

Day 5 - Week 2 Review: From Installation to Boot in One Line

📌 Key Takeaways

  • The flow is disk → partition → file system → mount → boot. This order is this week's backbone.
  • Memorize the pairs — BIOS·MBR / UEFI·GPT·ESP. A good share of questions ask about these pairings.
  • Memorize the numbers — MBR 2TB · 4 primary partitions, FAT32 4GB per file, runlevels 0 shutdown · 6 reboot.
  • Journaling starts with ext3, and the inode has no file name — these two are facts that make good standalone questions.
  • Distinguish the stage of each command: fdisk (divide) → mkfs (lay over) → mount (attach) → fstab (make permanent).

Flow Diagram

  Physical disk  /dev/sda
       │
       │  ① Divide      fdisk · gdisk · parted
       ▼
  Partitions    /dev/sda1  /dev/sda2  swap
       │
       │  ② Lay over    mkfs.ext4 · mkfs.xfs
       ▼
  File systems  ext4 · XFS · FAT32
       │
       │  ③ Attach      mount → temporary
       ▼                /etc/fstab → permanent
  Directory tree  /  /home  /var
       │
       │  ④ Boot        BIOS/UEFI → GRUB2 → kernel → initramfs → systemd
       ▼
  Login screen

What to Memorize as Pairs

LeftRightNote
BIOSMBRThe bootloader sits in the disk's first sector
UEFIGPT + ESPSupports Secure Boot
ext3Journaling introducedext2 doesn't have it
XFSDefault from RHEL 7+Strong with large capacity
BtrfsSUSE defaultSnapshots and compression
LILOReinstall needed after configuringThe old bootloader
GRUB2Edit /etc/default/grubgrub.cfg is auto-generated
Runlevel 3multi-user.targetText
Runlevel 5graphical.targetGUI

Numbers Summary

NumberWhat
2TBThe maximum disk size MBR can handle
4The maximum number of primary partitions in MBR
1The number of extended partitions per disk
5The number where logical partition numbering starts
4GBFAT32's single-file size limit
1 to 2 timesThe classic swap size rule (relative to memory)
0 / 6Runlevel shutdown / reboot
1The PID of init (systemd)
  • The 2TB and 4 come from MBR being a single 512-byte sector — bootloader 446 + partition table 64 (16 bytes × 4 slots) + signature 2. With four slots, that's 4 primary partitions, and with positions written in 32 bits, that's 2TB.

Configuration Files and Paths Summary

"Which file do you write it in" is the part most often mixed up this week. It sorts out if you split by when it is read.

FileContentsWho reads it and when
/etc/fstabThe list to mount automatically (6 fields)At boot, and at mount -a
/etc/mtab · /proc/mountsThe list mounted right nowThe system records it. Not a file for people to edit
/etc/default/grubGRUB2 default settingsgrub2-mkconfig reads it and creates grub.cfg
grub.cfgThe final configuration GRUB2 actually readsGRUB2 at boot. Don't edit directly
/boot/grub/grub.confOld GRUB configurationOld GRUB at boot. Edit directly
/etc/lilo.confLILO configurationTakes effect only after re-running the lilo command
/etc/inittabDefault runlevel (id:3:initdefault:)init-style boot
/boot/vmlinuz-versionThe kernel itselfThe bootloader loads it into memory
/boot/initramfs-version.imgThe temporary root file systemLoaded together with the kernel

Memorize the six fields of one /etc/fstab line in order.

/dev/sdb1    /data        ext4    defaults   0      2
① device   ② mount point  ③ type  ④ options  ⑤ dump  ⑥ fsck order

Command Sets Used at Each Stage

StageRegular partitionswap
Dividefdisk /dev/sdb → n → wSame. Set the type to 82 with t
Initializemkfs.ext4 /dev/sdb1mkswap /dev/sdb2
Start usingmount /dev/sdb1 /dataswapon /dev/sdb2
Stop usingumount /dataswapoff /dev/sdb2
Checkdf -h, lsblkfree -h, swapon -s
  • fdisk internal commands: p view · n new · d delete · t type · w save and exit · q exit without saving.
  • If Disklabel type in fdisk -l is dos, it's MBR; if gpt, it's GPT. Id is 83 Linux, 82 swap, 5 extended.
  • A hard link is ln, a symbolic link is ln -s. The one with the same inode is the hard link.
Now onlyAlso on the next boot
mount/etc/fstab
swaponThe swap line in /etc/fstab
systemctl isolate …targetsystemctl set-default …target
init 3/etc/inittab
Editing with e in the GRUB menu/etc/default/grub + grub2-mkconfig

Finding the Cause from Symptoms

In real work and in exam passages alike, concepts show up in the form of symptoms.

SymptomCauseCheck / fix
A 5GB file won't copy to the USB driveFAT32's 4GB single-file limitRecreate it as exFAT, etc.
A 3TB disk is recognized only up to 2TBIt was partitioned with MBRPartition it with GPT (gdisk, parted)
Space remains but files can't be created, with a "no space" errorThe inodes ran outdf -i
You mounted a new disk, but after reboot it's emptyIt wasn't written in /etc/fstabAdd one line and test with mount -a
umount refuses with target is busyA process is using that directorycd out of it
You edited /etc/default/grub but nothing changedgrub.cfg wasn't regeneratedgrub2-mkconfig -o …
A server boots to a graphical screen and eats resourcesThe default target is graphical.targetsystemctl set-default multi-user.target
After adding a disk, the mount attaches in the wrong placeThe sdb and sdc order shiftedUse a UUID (blkid) in fstab instead of the device name

Contrasting Confusing Pairs

CategoryABDistinguishing criterion
Primary vs extended partitionHolds dataA shell, holds logical onesCan it store directly?
/dev/hda vs /dev/sdaOld IDESATA, SCSI, USBInterface type
ext2 vs ext3No journalingHas journalingFailure recovery speed
FAT32 vs exFAT4GB limitNo limitSingle file size
mount vs /etc/fstabNow onlyEven after rebootPermanence
mkfs vs fsckCreates anewChecks and repairsCreating or fixing
BIOS vs UEFIMBR · 2TBGPT · Secure BootFirmware generation
init vs systemdRunlevel numbersTarget namesBoot management approach
Superblock vs inodeInformation about the whole file systemInformation about one fileScope of information
Hard link vs symbolic linkSame inodeSeparate inodeDoes it survive deleting the original?
mkfs vs mkswapCreates a file systemCreates a swap areaDoes it hold files?
fstab vs mtabWhat to do at bootThe current stateDoes a person write it?
isolate vs set-defaultImmediatelyFrom the next bootPermanence
DVD image vs network install imageContains the packagesDownloads during installIs the internet needed?
Live image vs minimal installRuns without installingInstalls only what's neededDoes it write to disk?

Commonly Mistaken Points

  1. "You store files in an extended partition" → No. It's only a shell, and the actual storage is done by logical partitions.
  2. "Logical partitions start from 3" → They start from 5. It doesn't matter how many primary partitions there are.
  3. "The inode has the file name" → It doesn't. The directory manages the name.
  4. "ext2 also supports journaling" → No. It starts from ext3.
  5. "You edit grub.cfg directly" → It's an auto-generated file, so it gets overwritten. Edit /etc/default/grub.
  6. "Runlevel 0 is reboot" → 0 is shutdown, and 6 is reboot.
  7. "Just mount and it stays forever" → It disappears on reboot. You must write it in /etc/fstab.

Command Summary

CommandWhat it does
fdisk -lList of disks and partitions
lsblkDisk structure as a tree
mkfs.ext4 /dev/sdb1Create a file system
mount /dev/sdb1 /dataMount
umount /dataUnmount
df -h / df -iCapacity / inode usage
fsck /dev/sdb1Check a file system
systemctl get-defaultThe current default target
grub2-mkconfig -o …Regenerate the GRUB configuration

Next week we finally type commands ourselves — from the first steps in the shell through file, directory, and account commands.

📖 Glossary

  • Partition table : A table recording how the disk is divided. There are two schemes, MBR and GPT.
  • ESP : The EFI System Partition. The area that holds the bootloader in UEFI boot.
  • initramfs : A temporary file system loaded first in order to mount the root file system.
  • Journaling : A technique that records changes in advance to speed up failure recovery.
  • Hard link : Several names pointing to the same inode.
  • target : The unit of system state that systemd uses in place of runlevels.

📝 Practice Questions

Click a choice to reveal the answer and explanation.

Question 1

Which of the following is the correct order up to the point of using a new disk in Linux?

Question 2

Which of the following is the number at which device numbers given to logical partitions start?

Question 3

Which of the following is the command that checks and repairs file system errors?

Question 4

Which of the following correctly pairs BIOS/UEFI with a partition scheme?

Question 5

Which of the following is the task you must perform after changing settings in GRUB2?

Question 6

Which of the following is the systemd target that specifies booting the system into a text-mode multi-user environment?

PreviousThe Boot Manager: From Power-On to LoginWeek 2 · Day 4Next First Steps in the Shell: How to Read a Single Command LineWeek 3 · Day 1

Official references

  • Linux Master 2 official exam syllabus(opens in a new tab)

On this page

  • Key Takeaways
  • Flow Diagram
  • What to Memorize as Pairs
  • Numbers Summary
  • Configuration Files and Paths Summary
  • Command Sets Used at Each Stage
  • Finding the Cause from Symptoms
  • Contrasting Confusing Pairs
  • Commonly Mistaken Points
  • Command Summary
  • Glossary
  • Practice Questions