Quantcast
Channel: Active questions tagged 22.04 - Ask Ubuntu
Viewing all articles
Browse latest Browse all 4439

Ubuntu will boot in emergency mode every time you boot

$
0
0

You are in emergency mode.When I start ubuntu, I get the following message

You are in emergency mode.After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to reboot"systemctl reboot" to reboot, "systemctl default"or ^D to try again to boot into default mode".

I have found similar questions in the past, but it appears that the recovery partition and CD_ROM are not mounted in my environment.(Stuck in emergency mode and nothing works?)

Here are the results of running less /etc/fstab and sudo blkid.

root@ubuntu:*# less /etc/fstab# /etc/fstab: static file system information.#Use'bikid' to print the universally unique identifier for adevice; this may be used with UUID= as a more robust way to name devices that works even if disks are added and removed. See fstab(5).#‹file system›‹mount point>    <type>  ‹options>    ‹dump>  ‹pass># / was on /dev/nvme1n1p2 during installationUUID=69b38a28-4cc5-43dc-988f-e704b253f 4da /         ext4  errors_remount_ro 0      1# /boot/efi was on /dev/nvme1n1p1 during installationUUID=F84C-8C81 /boot/efi    vfat    umask=0077    0    1# /home was on /dev/nvme0n1p2 during installationUUID=206e346f-51db-468c-bba6-2cb140efdded /home      ext4    defaults        0    2# /usr was on /dev/nvme0n1p1 during installationUUID=374aa537-c8d7-4ae-af53-4f0a1d7bada8 /usr        ext4    defaults        0    2/swapfile                                none        swap    SW              0    0root@ubuntu:~# sudo bikid/dev/nvme 1n1p2: UUID="69b38a28-4Cc5-43dc-988f-e704b253f4da" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="21470635-8f 1b-455b-8004-638db3f 1073b"/dev/nvme0n1p1: UUID="374aa537-c8d7-4a6e-af53-4f0a1d7bada8" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="a7983b28-ea2a-4fa8-9723-318ebf5c5f50"/dev/100p1: TYPE="squashfs"/dev/nvmeon1p2: UUID="206e346-51db-468c-bba6-2cb140efdded" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="d2921ab6-19f4-422a-857b-f8516f5fb066"/dev/loop17: TYPE="squashfs"/dev/loop8: TYPE="squashfs"/dev/1oop15: TYPE="squashfs"/dev/loop6: TYPE="squashfs"dev/loop4: TE guant &"/dev/loop11: TYPE="squashfs"/dev/loop2: TYPE="squashfs"/dev/loop0: TYPE="squashfs"/dev/loop18: TYPE="squashigs"/dev/loop9: TYPE="squashfs"/dev/1oop16: TYPE="'squashfs"/dev/loop7: TYPE="squashfs"/dev/nvme 1n1p1: UUID="F84C-8C81" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="1fc23977-7d89-4173-a66C-ed435b7d7ec3"/dev/sda1: UUID="524aeafa-6546-4452-9a0a-63c562dca4a3" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="49C7f407-0f35-449f-94e2-63047d801/dev/loop14: TYPE="squashfs"/dev/loop5: TYPE="'squashfs"/dev/loop12: TYPE="squashfs"/dev/loop3: TYPE="'squashfs"/dev/loop10: TYPE="squashfs"root@ubuntu:~#

Also, when I run ls in the ~ directory on the emergency mode screen, I can hardly see the directories I created when the system was booted normally.

Is there any way to solve this problem and have it start normally?I am using Ubuntu 22.04 Desktop.


Viewing all articles
Browse latest Browse all 4439

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>