1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
|
#+date: <2024-02-13 Tue 00:00:00>
#+title: How to Fix Ubuntu Emergency Mode by Correcting Your Fstab File
#+description: Step-by-step guide to resolve Ubuntu emergency mode boot issues caused by incorrect /etc/fstab entries. Learn how to edit fstab and restore normal boot.
#+slug: ubuntu-emergency-mode
* The Problem
I recently [[../zfs/][migrated my hard drives to a ZFS pool]] and found myself stuck in
Ubuntu's emergency mode after the first reboot I performed after creating the
ZFS pool.
My server was stuck in the boot process and showed the following error on the
screen:
#+begin_src txt
You are in emergency mode.
After logging in, type "journalctl -xb" to view system logs,
"systemctl reboot" to reboot, "systemctl default"
or ^D to try again to boot into default mode".
#+end_src
After rebooting the server and watching the logs scroll on a monitor, I noticed
the root cause was related to a very long search for certain drives. I kept
seeing errors like this:
#+begin_src txt
[ TIME ] Timed out waiting of device dev-disk-by/[disk-uuid]
#+end_src
I realized that I had not removed the =/etc/fstab= references that asked Ubuntu
to mount two disks on boot, but I had recently changed those disks to be part of
my ZFS pool instead. Therefore, Ubuntu was trying to identify and mount a disk
that was not available.
Now that we have an idea of the issue, let's move to solution.
* The Solution
In order to fix the issue, I waited until I was allowed to type the root user's
password, and then I executed the following command:
#+begin_src sh
nano /etc/fstab
#+end_src
Within the =fstab= file, I needed to comment/remove the following lines at the
bottom of the file. You can comment-out a line by prepending a =#= symbol at the
beginning of the line. You can also delete the line entirely.
#+begin_src conf
# What it looked like when running into the issue:
UUID=B64E53824E5339F7 /mnt/white-01 ntfs-3g uid=1000,gid=1000 0 0
UUID=E69867E59867B32B /mnt/white-02 ntfs-3g uid=1000,gid=1000 0 0
# What I changed it to, in order to fix the issue:
# UUID=B64E53824E5339F7 /mnt/white-01 ntfs-3g uid=1000,gid=1000 0 0
# UUID=E69867E59867B32B /mnt/white-02 ntfs-3g uid=1000,gid=1000 0 0
#+end_src
Once removing the lines above from the =/etc/fstab= file, save and exit the file
by hitting the =Ctrl= + =x= key combo.
You can now hit =Ctrl= + =D= to continue, or reboot:
#+begin_src sh
systemctl reboot
#+end_src
Once rebooted, I was able to watch the machine boot properly and launch to the
TTY login screen without errors!
|
