Booting in emergency mode after external HDD partitioning

Hello to everybody,
yesterday I wanted to move some files to an old external HDD. Before moving the files, I deleted any existing partitions and changed the filesystem to btrfs using KDE Partition Manager. I formatted it by changing the drive name to Data_2 and mount point to / run / media / andrea / Data_2.
Everything seemed to work fine, so I repeated the whole operation with another external HDD, calling it Data_3 and mount point / run / media / andrea / Data_3.
No error message, the PC shutdown went smoothly.
Today, when I turn on my PC, I notice that the startup is particularly slow. After more than a minute and a half (usually it takes no more than 15 seconds) the system goes into emergency mode:

You are in emergency mode. After logging in, type “journal -xb” to view system logs, “systemctl reboot” to reboot, “systemctl default” or “exit” to boot into default mode.
Give root password for maintenance
(or press Control-D to continue):

Then I reboot the system, I try to use another kernel (linux-lts) but nothing changes. So I boot from a timeshift snapshop. This time, finally, the boot is successful.
I have made multiple booting attempts, checking the output of journalctl -b -1 each time.
This is an example of a suspicious error:

ago 11 21:55:15 andrea-vyper kernel: audit: type=1131 audit(1628711715.184:15): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
ago 11 21:56:39 andrea-vyper systemd[1]: dev-sda2.device: Job dev-sda2.device/start timed out.
ago 11 21:56:39 andrea-vyper systemd[1]: Timed out waiting for device /dev/sda2.
ago 11 21:56:39 andrea-vyper systemd[1]: Dependency failed for /run/media/andrea/New Volumentfs.
ago 11 21:56:39 andrea-vyper systemd[1]: Dependency failed for Local File Systems.
ago 11 21:56:39 andrea-vyper systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
ago 11 21:56:39 andrea-vyper systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
ago 11 21:56:39 andrea-vyper systemd[1]: run-media-andrea-New\x20Volumentfs.mount: Job run-media-andrea-New\x20Volumentfs.mount/start failed with result 'dependency'.
ago 11 21:56:39 andrea-vyper systemd[1]: dev-sda2.device: Job dev-sda2.device/start failed with result 'timeout'.

I am sure that, in previous boot attempts, the output of journalctl -b -1 contained the same type of error referring to the Data_2 and Data_3 drives.

Content of /etc/fstab:

UUID=59AE-85F1                            /boot/efi      vfat    umask=0077 0 2
UUID=4967c5d8-4aa7-40ae-a1a9-6ab7ceab2b77 /              btrfs   subvol=/@,defaults,noatime,space_cache,autodefrag,compress=zstd 0 1
UUID=4967c5d8-4aa7-40ae-a1a9-6ab7ceab2b77 /root          btrfs   subvol=/@root,defaults,noatime,space_cache,autodefrag,compress=zstd 0 2
UUID=4967c5d8-4aa7-40ae-a1a9-6ab7ceab2b77 /srv           btrfs   subvol=/@srv,defaults,noatime,space_cache,autodefrag,compress=zstd 0 2
UUID=4967c5d8-4aa7-40ae-a1a9-6ab7ceab2b77 /var/cache     btrfs   subvol=/@cache,defaults,noatime,space_cache,autodefrag,compress=zstd 0 2
UUID=4967c5d8-4aa7-40ae-a1a9-6ab7ceab2b77 /var/log       btrfs   subvol=/@log,defaults,noatime,space_cache,autodefrag,compress=zstd 0 2
UUID=4967c5d8-4aa7-40ae-a1a9-6ab7ceab2b77 /var/tmp       btrfs   subvol=/@tmp,defaults,noatime,space_cache,autodefrag,compress=zstd 0 2
UUID=1a453e0b-5ce4-411d-8fc0-5730f4b4d12c /home          btrfs   defaults,noatime,space_cache,autodefrag,compress=zstd 0 2
UUID=1460dc6b-7e5e-4150-8a3c-8a783f9edfb9 swap           swap    defaults,noatime 0 0

Output of blkid:

/dev/nvme0n1p3: UUID="1a453e0b-5ce4-411d-8fc0-5730f4b4d12c" UUID_SUB="fc39b122-e76f-45ab-8c6f-f62684e9e9d9" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="5d1e8d28-629c-c349-bd7c-382f8e94cec7"
/dev/nvme0n1p1: LABEL_FATBOOT="NO_LABEL" LABEL="NO_LABEL" UUID="59AE-85F1" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="1b84684d-a7f2-8148-8d00-c97c79f04cdd"
/dev/nvme0n1p4: UUID="1460dc6b-7e5e-4150-8a3c-8a783f9edfb9" TYPE="swap" PARTUUID="b5acb501-bd1b-2047-890e-51d4f73e1c99"
/dev/nvme0n1p2: UUID="4967c5d8-4aa7-40ae-a1a9-6ab7ceab2b77" UUID_SUB="6cebb0de-8d4a-4205-a98f-c3b515d2bb31" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="47087b88-e980-f147-a2c5-9d143e55b120"
/dev/sda1: LABEL="Data" UUID="e6419550-0cc6-4eb3-8dfb-8941ca1a00ac" UUID_SUB="64b7547a-bdef-4ec3-b7c8-6b8f2d9cb55a" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="761ebed0-7a95-3e46-a5a0-95739e7c628e"
/dev/zram0: LABEL="zram0" UUID="973e1e00-c771-4d3d-b625-7701217ca1f9" TYPE="swap"

Output of lsblk:

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0 931,5G  0 disk
└─sda1        8:1    0 931,5G  0 part /run/media/andrea/Data
zram0       254:0    0  31,2G  0 disk [SWAP]
nvme0n1     259:0    0 465,8G  0 disk
├─nvme0n1p1 259:1    0   513M  0 part /boot/efi
├─nvme0n1p2 259:2    0   100G  0 part /run/timeshift/backup
│                                     /var/tmp
│                                     /var/log
│                                     /var/cache
│                                     /srv
│                                     /root
│                                     /
├─nvme0n1p3 259:3    0 317,3G  0 part /home
└─nvme0n1p4 259:4    0    48G  0 part [SWAP]

Is booting into emergency mode caused by these errors? How can I go about solving?
Thank you in advance for your help!

Without any real information my best guess is you have permanent mounts in /etc/fstab or systemd units to the old locations in /run/media which isn't what you want. If that is the case, try removing those and see if your system boots.

1 Like

Wrong file. You are investigating your failed system, not your working snapshot :wink:
Find and browse your broken (old current) snapshot in Timeshift or in File Manager at /run/timeshift/backup/.

You haven’t even said what DE you run.
There is an intro message in each new topic 1st post. Do you read it, or just … delete (Nah! It’s not for me…)?

Is it the hot summer? :man_shrugging:

2 Likes