Home / ubuntu / Questions / 1430401
Accepted
Exquisite Mong
Asked: 2022-09-21 08:52:56 +0800 CST

Emergency Boot Mode Error

  • 772

I'm on Ubuntu 22.04.01 LTS.

There are similar questions, but the poster was already much further along before posting and I don't know how to get to their initial step.

What's happening?

When I turn on my computer it boots to emergency mode. I was able to print the journal and have included photos further down.

There are options to go to recovery mode. When I'm in recovery mode I can't move down the menu, but am able to write into a command line.

How did this happen?

An external HD suddenly wouldn't mount. It's NTFS and I concluded there was some read/write issue. Therefore I found some code online. After entering this code I rebooted. This is when the issues started. My OS is on an internal drive and I'm fairly sure its file system is fuse.

This is the code I entered. The code executed.

sudo apt-get purge ntfsprogs 
sudo apt-get purge ntfs-3g 
sudo apt-get install ntfs-3g

Examples of errors

I've photographed some of the journal. If there's a better way please let me know.

I don't understand how an NTFS.

EDIT 1:

It wouldn't let me boot into recovery mode unless the external HD was connected. Weird. As said previously my OS is on an internal.

EDIT 2:

Tried

fsck /dev/nvme0n1p2

Output was

fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
/dev/nvme0n1p2 is mounted.
e2fsck: cannot continue, aborting

EDIT 3:

Tried

fsck -nf /dev/nvme0n1p2

The output is here: https://postimg.cc/Th9Hx2vM

I then tried to unmount the drive but it said 'target is busy.'

boot

2 Answers

  1. Execute the following code by replacing diskname with the partition in which your home is installed

    $ fsck /dev/diskname

    From your uploaded images nvme0n1p2 is where your file systems likely exists so you could run;

    $ fsck /dev/nvme0n1p2
    • 0
  2. Best Answer
    • 0