- 1 1. Introduction
- 2 2. What Is Recovery Mode in Ubuntu 24?
- 3 3. How to Enter Recovery Mode in Ubuntu 24
- 4 4. Detailed Explanation of Each Recovery Mode Option
- 5 5. Practical Troubleshooting Examples Using Recovery Mode
- 6 6. Precautions When Using Recovery Mode
- 7 7. Frequently Asked Questions (FAQ)
- 8 8. Conclusion
1. Introduction
Ubuntu is widely used as a simple and user-friendly Linux distribution. However, due to system updates or configuration changes, there are cases where Ubuntu suddenly fails to boot. In such situations, it is important to use the Recovery Mode feature to repair the system.
Recovery Mode is a special startup mode that allows the system to boot with minimal functionality. Even if the system becomes unbootable due to corrupted components or incorrect settings, you can still perform repair tasks.
What Is Recovery Mode?
Ubuntu Recovery Mode is a special troubleshooting environment accessed through GRUB (GNU GRand Unified Bootloader). Unlike normal booting, it loads with minimal resources and grants administrative shell access for repairs.
In Recovery Mode, you can perform the following tasks:
- Repair corrupted system files
- Repair or reinstall packages
- Check and fix file system errors
- Enable network connectivity
- Repair and reinstall GRUB
- Perform system operations with root privileges
Purpose of This Article
This article explains how to use Recovery Mode in Ubuntu 24. It covers the following topics in detail:
- What is Recovery Mode in Ubuntu 24?
- How to enter Recovery Mode in Ubuntu 24
- Explanation of Recovery Mode options
- Practical troubleshooting examples
- Precautions when using Recovery Mode
- Frequently Asked Questions (FAQ)
This article aims to help Ubuntu users resolve system issues effectively by using Recovery Mode.
2. What Is Recovery Mode in Ubuntu 24?
The Recovery Mode in Ubuntu 24 is a specialized boot environment designed for system troubleshooting and repairs. Unlike the regular boot sequence, it starts the system with minimal functions and provides shell access with administrative privileges, making it possible to resolve various system issues.
This section explains the overview of Recovery Mode, how it differs from normal booting, and what tasks can be performed with it.
What Is Recovery Mode?
Recovery Mode is a system repair boot option accessible from the Ubuntu GRUB menu. Instead of loading all services, it starts only essential components, allowing you to identify and repair system problems.
Common scenarios where Recovery Mode becomes useful include:
- Ubuntu fails to boot after an update
- Incorrect settings prevent the GUI from launching
- Package issues cause malfunctioning applications
- Damaged system files prevent normal booting
- GRUB (bootloader) corruption prevents the OS from loading
By using Recovery Mode, you can resolve problems that cannot be fixed through a normal boot process.
Differences Between Normal Boot and Recovery Mode
Normally, Ubuntu boots through the following steps:
- The bootloader (GRUB) starts when powering on the PC
- The system loads the kernel in normal mode
- Required system services and drivers are loaded
- The GUI launches and displays the login screen
However, Recovery Mode operates differently:
- Manually open the GRUB menu when powering on
- Select Recovery Mode, which loads a minimal kernel
- Boot without launching the GUI, using a CLI-based interface
- Display a repair-oriented menu (package repair, disk check, etc.)
- Return to normal boot after resolving issues
What You Can Do in Recovery Mode
Recovery Mode offers the following capabilities:
1. Repair broken packages
- If package corruption occurs during updates, you can repair them using
dpkg. - Example:
dpkg --configure -a2. Fix disk errors
- If the file system is damaged and Ubuntu cannot boot, use
fsckto repair disk errors. - Example:
fsck -y /dev/sda13. Enable network support
- Use the
networkoption when repairs require internet access.
4. Repair GRUB
- If the bootloader is corrupted, reinstall GRUB from Recovery Mode.
- Example:
grub-install /dev/sda5. Access a root shell
- Unlike normal booting, Recovery Mode grants direct access to a root shell via the
rootoption. - Example:
passwd usernameWhen Should You Use Recovery Mode?
Below are common situations where Recovery Mode is recommended:
| Situation | What You Can Do |
|---|---|
| Ubuntu won’t boot | Repair GRUB or reinstall kernel |
| After updates cause issues | Repair packages or roll back updates |
| Disk errors detected | Repair with fsck |
| Forgot password | Reset via root shell |
| No network available | Enable via network option |
Summary
Recovery Mode in Ubuntu is an essential troubleshooting feature. Even if normal booting fails, it lets you start the system with minimal components, identify problems, and fix them efficiently.
3. How to Enter Recovery Mode in Ubuntu 24
The process of entering Recovery Mode in Ubuntu 24 varies slightly depending on the system state and whether the machine uses BIOS or UEFI boot. This section explains how to open the GRUB menu, access Recovery Mode, and what to do if the GRUB menu does not appear.
Opening the GRUB Menu
To use Recovery Mode, you must first open the GRUB (GNU GRUB bootloader) menu.
For BIOS (Legacy Boot) Systems
- Power on the PC
- Before the Ubuntu logo appears, hold down the
Shiftkey - The GRUB menu will be displayed
For UEFI Systems
- Power on the PC
- Press the
Esckey repeatedly before the Ubuntu logo appears - The GRUB menu will be displayed
💡 Tips:
- If the GRUB menu does not appear, adjust the timing when pressing
ShiftorEsc. - In dual-boot environments, an OS selection screen may appear instead of GRUB.
Selecting Recovery Mode
Once the GRUB menu appears, follow these steps:
- Select “Advanced options for Ubuntu”
- Use the ↑ and ↓ arrow keys to select it and press
Enter.
- Select a Recovery Mode kernel
- Example:
Ubuntu, with Linux 6.5.0-XX-generic (recovery mode) - Selecting the newest kernel is recommended.
- The Recovery Mode menu will be displayed
- Choose the required repair options from the displayed list.
What to Do if the GRUB Menu Does Not Appear
Case 1: The GRUB menu is skipped automatically
- Cause: The GRUB timeout may be set to zero.
- Solution: Modify GRUB settings.
sudo nano /etc/default/grubChange GRub_TIMEOUT=0 to GRUB_TIMEOUT=10, then save (Ctrl + X → Y → Enter) and apply:
sudo update-grubCase 2: GRUB is corrupted
- Solution: Boot with a live USB and reinstall GRUB.
sudo mount /dev/sdaX /mnt # Mount the Ubuntu partition
sudo grub-install --boot-directory=/mnt/boot /dev/sda
sudo update-grubCase 3: In dual-boot systems, Windows overwrote GRUB
- Solution: Use the
Boot Repairtool to restore GRUB.
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt update
sudo apt install -y boot-repair
boot-repairRecovery Mode Options Overview
Once inside Recovery Mode, you will see options such as:
| Option | Description |
|---|---|
| resume | Exit Recovery Mode and resume normal boot |
| clean | Free disk space by removing unnecessary packages |
| dpkg | Repair broken packages |
| fsck | Check and repair file system errors |
| network | Enable network access for online repairs |
| root | Open a root shell for advanced repairs |
Summary
- Recovery Mode is accessed from the Ubuntu GRUB menu
- Use
Shifton BIOS systems andEscon UEFI systems - If GRUB does not appear, modify settings or repair GRUB
- Recovery Mode provides multiple repair options for system issues
4. Detailed Explanation of Each Recovery Mode Option
Ubuntu 24 provides several Recovery Mode options designed to repair different types of system problems. This section explains each option and shows how to use them effectively.
Overview of Recovery Mode Menu
The Recovery Mode menu contains the following options:
| Option | Description |
|---|---|
| resume | Exit Recovery Mode and boot normally |
| clean | Remove unnecessary packages and reclaim disk space |
| dpkg | Repair damaged packages |
| fsck | Scan and repair file system errors |
| network | Enable the network for online repair tasks |
| root | Open a root shell with administrator privileges |
Let’s look at each option in detail.
resume (Boot Normally)
Overview
This option exits Recovery Mode and boots Ubuntu normally. Use this after finishing repair operations or when the system no longer requires recovery mode access.
How to Use
- Select
resumefrom the Recovery Mode menu - Press
Enterand follow the on-screen instructions - Ubuntu will boot normally
clean (Free Disk Space)
Overview
This option removes unnecessary packages to increase available disk space. If the disk becomes full, Ubuntu can behave unpredictably, making this option important in low-storage scenarios.
How to Use
- Select
cleanand pressEnter - Ubuntu removes cached and old packages automatically
- Select
resumeto return to normal boot
Check disk usage manually:
df -hCheck directory sizes:
du -sh /*Remove unused packages:
sudo apt autoremovedpkg (Repair Broken Packages)
Overview
The dpkg option uses Ubuntu’s package manager to repair corrupted packages. This is useful when errors occur during updates and packages become unusable.
How to Use
- Select
dpkgand pressEnter - Ubuntu scans for damaged packages and attempts automatic repair
- Select
resumeto boot normally after repairs
Manual package repair commands:
sudo dpkg --configure -a
sudo apt --fix-broken installfsck (Repair File System)
Overview
The fsck (File System Check) command detects and repairs file system errors. This is useful when the cause of boot failure is a disk error.
How to Use
- Select
fsckand pressEnter - Ubuntu scans and fixes file system issues
- Select
resumewhen complete
Manual file system repair:
- Choose
rootfrom the Recovery Mode menu - Run the following command (example for
/dev/sda1):
fsck -y /dev/sda1- Type
exitand reboot
network (Enable Network Access)
Overview
This option enables the network interface even while in Recovery Mode. It is essential when downloading packages, updating repositories, or performing online troubleshooting.
How to Use
- Select
networkand pressEnter - The system activates the network connection
- After activation, you can use commands that require internet access
Restart the network manually:
sudo systemctl restart NetworkManagerroot (Open a Root Shell)
Overview
This option opens a shell session with root privileges. It is used for advanced repairs such as resetting passwords, modifying configuration files, reinstalling GRUB, or repairing packages that cannot be fixed automatically.
How to Use
- Select
rootand pressEnter - Access the command line with administrator privileges
- Execute the required commands, then exit the shell with
exit
Examples of advanced operations:
- Reset a user password:
passwd username- Repair GRub:
grub-install /dev/sda
update-grubSummary
Ubuntu 24 offers a variety of recovery options. Understanding how each option works enables you to perform repairs efficiently and safely.

5. Practical Troubleshooting Examples Using Recovery Mode
Ubuntu 24 includes several powerful tools within Recovery Mode to fix system boot issues, repair damaged packages, and correct file system errors. This section walks through step-by-step troubleshooting procedures for common problems.
Case 1: Ubuntu Does Not Boot
Symptoms
- A black screen appears during startup
- GRUB does not appear and Windows boots directly in dual-boot systems
- Error message: “Kernel Panic – not syncing: VFS”
Solution
1. Repair GRUB
GRUB may be corrupted. Use Recovery Mode to reinstall it.
- Open the GRUB menu (
ShiftorEscduring boot) - Select Recovery Mode and choose the
rootoption - Run the following commands:
grub-install /dev/sda
update-grub
reboot- Restart and verify whether GRUB appears
2. Repair the Kernel
If the latest kernel is damaged, boot with an older one:
- Select Advanced options for Ubuntu from GRUB
- Select an older kernel version
- Reinstall the kernel:
sudo apt update
sudo apt reinstall linux-genericCase 2: Ubuntu Fails Due to Insufficient Disk Space
Symptoms
- Error message: “No space left on device”
- The GUI does not launch
Solution
1. Remove Unnecessary Packages
- Select
cleanfrom Recovery Mode - Remove unnecessary logs or files manually:
du -sh /*
rm -rf /var/log/*2. Delete Temporary Files
rm -rf ~/.cache/*
rm -rf /tmp/*Case 3: Damaged Ubuntu Packages
Symptoms
apt-getanddpkgcommands return errors- Applications stop working after system updates
Solution
1. Repair Packages
- Select
dpkgin Recovery Mode - Perform manual repair if necessary:
sudo dpkg --configure -a
sudo apt --fix-broken install2. Reinstall Packages
sudo apt reinstall $(dpkg --list | awk '/^rc/ { print $2 }')Case 4: Network Cannot Be Used
Symptoms
- Ethernet/Wi-Fi does not work
- Network configuration files are corrupted
Solution
1. Enable the Network
Select network in Recovery Mode.
2. Restart Network Services
sudo systemctl restart NetworkManager3. Reinstall Network Drivers
sudo apt update
sudo apt install --reinstall network-managerCase 5: GRUB Boot Entries Are Broken
Symptoms
- Ubuntu no longer appears in the boot list
- Only Windows boots in a dual-boot setup
Solution
1. Use Boot Repair
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt update
sudo apt install -y boot-repair
boot-repair2. Modify GRUB Configuration
sudo nano /etc/default/grub
GRUB_TIMEOUT=10
update-grubCase 6: Forgot the Root Password
Symptoms
- Unable to perform administrative tasks
sudodoes not work without a password
Solution
- Select
rootin Recovery Mode - Reset the password:
passwd username- Restart the system:
rebootSummary
With Ubuntu 24 Recovery Mode, you can resolve a wide range of problems efficiently. Understanding these procedures allows you to restore your system without reinstalling Ubuntu.
6. Precautions When Using Recovery Mode
While Recovery Mode in Ubuntu 24 is extremely useful for troubleshooting and repairing system issues, incorrect operations may cause severe system damage. This section explains important points to consider before making changes.
Cautions When Using Root Privileges
Recovery Mode grants access to a root shell, but incorrect commands may corrupt or destroy the operating system. Extreme care is required.
❌ Dangerous Commands You Should Never Run
| Command | Impact |
|---|---|
rm -rf / | Deletes all system data, making Ubuntu unbootable |
dd if=/dev/zero of=/dev/sda | Erases the entire disk |
chmod 000 /etc/shadow | Prevents all users from logging into the system |
mv /bin /bin_backup | Removes essential binaries, breaking shell access |
✅ Safe Usage Guidelines
- Understand what each command does before executing it
- Use
lsorcatto verify files before modifying them - When possible, use
sudoinstead of full root operations - Create backups before making major changes
The Importance of Backups Before Making Changes
Recovery Mode is designed to modify critical parts of the system. Incorrect modifications may prevent Ubuntu from booting. Therefore, backing up important files is strongly recommended.
Backup Methods
1. Copy Important Data Manually
Open a root shell and copy files to external storage:
cp -r /home/username/Documents /mnt/usb/2. Create a Full System Snapshot with Timeshift
sudo apt install timeshift
sudo timeshift --create --comments "Before Recovery Mode"Precautions When Working with Disks
Disk and partition modifications should be done carefully. Using fsck on the wrong device may cause irreversible damage.
Steps to Work Safely
- Check partition info
lsblk- Repair file system (example for
/dev/sda1)
fsck -y /dev/sda1Precautions When Enabling Network Access
Enabling the network in root mode poses security risks. Only connect to trusted networks and avoid unknown scripts.
Best Practices
- Do not modify Wi-Fi passwords or configuration files unnecessarily
- Use secure and trusted networks
- Never install unknown scripts from the internet
curl http://example.com/install.sh | sh # Do NOT run this!Precautions When Repairing GRUB
Incorrect GRUB configuration may cause both Ubuntu and Windows to stop booting.
Best Practices
- Specify the correct disk, not a partition
grub-install /dev/sda # Correct
# NOT /dev/sda1- Run
update-grubafter making changes
sudo update-grub- Do not delete Windows Boot Manager in dual-boot environments
Precautions When Resetting a Password
Changing the root password may modify privilege groups. Some users may lose sudo access if not configured properly.
Best Practices
- Select
rootin Recovery Mode - Reset the password:
passwd username- Add the user back to the sudo group (if necessary):
usermod -aG sudo usernameSummary
| Risk | Precaution |
|---|---|
| Misuse of root permissions | Commands may destroy the system if used improperly |
| No backups before changes | Always create backups before modifying critical files |
| Misuse during file system repairs | Verify device names before running fsck |
| Incorrect GRUB repairs | Specify /dev/sda and update GRUB afterwards |
| Unsafe network operations | Avoid running unknown scripts |
| Password reset issues | Ensure the user remains in the sudo group |
7. Frequently Asked Questions (FAQ)
This section provides answers to common questions related to Ubuntu 24 Recovery Mode. If you encounter any problems, refer to this FAQ first.
Unable to Enter Recovery Mode
Q1: Pressing Shift or Esc doesn’t display the GRUB menu. What should I do?
A: The GRUB timeout may be too short. Modify settings as follows:
- Press
Shift(BIOS) orEsc(UEFI) repeatedly during boot - Change GRUB timeout:
sudo nano /etc/default/grubReplace GRUB_TIMEOUT=0 with:
GRUB_TIMEOUT=10- Apply changes:
sudo update-grub- Reboot and test again
Keyboard or Mouse Not Working
Q2: My keyboard doesn’t work in Recovery Mode. Why?
A: Some wireless keyboards are not recognized in early boot stages.
Solutions:
- Try a wired USB keyboard
- Enable “USB Legacy Support” in BIOS
- Try another USB port
Network Not Working
Q3: The network won’t connect even after selecting network.
A: Some configurations require manual activation.
- Restart the network:
sudo systemctl restart NetworkManager- Request an IP address:
sudo dhclient- Connect to Wi-Fi manually:
nmcli d wifi connect "SSID" password "PASSWORD"File System Repair Fails
Q4: fsck says the file system is mounted. What now?
A: Remount it as read-only:
mount -o remount,ro /fsck -y /dev/sda1Package Repair Problems
Q5: dpkg still errors out. What should I try?
A: Remove problematic packages:
sudo apt remove --purge packagenameThen update packages:
sudo apt update && sudo apt upgrade -yGRUB Repair Not Working
Q6: Running grub-install doesn’t fix GRUB. Why?
- Verify disk layout:
lsblk- Install GRUB to the EFI partition:
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=ubuntuPassword Reset Issues
Q7: Can I reset a forgotten password using Recovery Mode?
A: Yes. Use root in Recovery Mode:
passwd usernameSummary
With the correct commands and procedures, Recovery Mode allows you to fix almost any Ubuntu boot or configuration issue.
8. Conclusion
Recovery Mode in Ubuntu 24 is a powerful diagnostic and repair tool. This guide has covered the fundamentals, how to access Recovery Mode, detailed explanations of each option, specific repair examples, FAQs, and best practices.
Key Takeaways
- Recovery Mode provides essential repair tools such as
dpkg,fsck, and GRUB restoration - Access via
Shift(BIOS) orEsc(UEFI) - Use different options for different problems—package repair, file system validation, GRUB fixes, and more
- Backups are critical before modifying core system components
Recommended Troubleshooting Flow
- Open the GRUB menu → select
Advanced options for Ubuntu - Select the appropriate Recovery Mode option
- Perform repairs and reboot
rebootAlternative Solutions
- Use a Live USB for GRUB or disk repair if Recovery Mode fails
- Reinstall Ubuntu if the system is beyond repair
- Create regular backups using tools like
Timeshift
Final Thoughts
By understanding and properly using Recovery Mode, you can solve most Ubuntu system issues without reinstalling the operating system. With careful steps and backups, Ubuntu 24 can remain a stable and reliable environment for both everyday users and professionals.



