You are in emergency mode - after parted action

Hello OpenSUSEcomunity,

I caused probably this issue myself by trying to format an SD card using CLI (parted). I tried to ensure I I was modifying /dev/sdb, which appeared to be the SD card.

However after reboot, the system goes into an emergency mode. It starts to boot normally with last two lines:

 OK ] Finished Wait for udev To Complete Device Initialiyation.
   *  ] A start job is running for /dev/disk/by-uuid/A35D-1B32 (1 min 27s / 1 min 30s)

Then it goes into emergency mode (for a lack of better options, here are images):

https://k00.fr/1i1w6lvk

/etc/fstab:

https://k00.fr/e7wwwwzl

YaST partitioning module:

https://k00.fr/ej1awtuc

When logged in to tty and executing journalctl -xb, I get overwhelming amount of information, thousands of lines. Some relevant lines look like:

/usr/lib/udev/rules.d/50-libsigrok.rules:32 Unknown group 'plugdev', ignoring
(many lines)
Configuration file /etc/udev/rules.d/55-brother-brscan4-libsane-type1.rules is marked executable. Please remove executable permissions bit.

FAT-fs (nvme1n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fcsk.

[sdb] No Caching mode page found
[sdb] Assuming drive cache: write through

dev-disk-by\x2duuid-A35D\x2d1B32.device: Job dev-disk-by\x2duuid-A35D\x2d1B32.device/start timed out
Timed out waiting for device /dev/disk/by-uuid/A35D-1B32

I’m quite lost as for what to analyze and what to try to fix. Any help is appreciated.

Remove entry for this device from /etc/fstab.

Thank you for your suggestion. I guess you mean /dev/disk/by-uuid/A35D-1B32, but I have no such device in my /etc/fstab. I don’t know where this disk label is comming from.

Show output of

cat /etc/fstab
cat /proc/cmdline
blkid

Mamy here do not trust all sorts of image hosting sites.

You can go to https://susepaste.org/ and upload an image there (see the word Image at top-right).
After you did this, you can copy/paste the URL from the page as shown in the address bar of your browser (and not the URL of the image itself). Paste this using the Link button (the one with the globe) from the toolbar of the post editor.

/etcc/fstab is above (link to a screenshot in my personal cloud). The other two outputs are below as requested.

/proc/cmdline:

BOOT_IMAGE=/boot/vmlinuz-5.14.21-150400.22-default root=UUID=7c92bcb4-5703-4530-db69-62d820e9979d splash=silent quiet mitigations=auto

blkid (screenshot - too much to rewrite):

https://k00.fr/iulwfo0m

OK, thank zou for your tip, I can try susepaste thingy, if it gives trusted link. i didn’t know it exists, so I used my personal Koofr share.

The device with UUID A35D-1B32 is in your /etc/fstab. If it were text, I could quote it and show you the exact line.

You were right, it was on the last line, my bad. I removed the line

Now the system ends up in tty1, probably with unrelated error. Perhaps a mismatch of nvidia driver and a new 15.3 kernel.

nvidia-gpu 0000:07:00.3: i2c timeout error e0000000
ucsi_ccg 0-0008: i2c_transfer failed -110
ucsi_ccg 0-0008: ucsi_ccg_init failed -110

I’ve added a NVidia repository and then started YaST and performed update. It updated tons of stuff including NVidia drivers and after the restart all seems to work fine!

Resolved.

Thank you for your help!