You are not logged in.
Pages: 1
Hi fellas,
Tried to boot today. Emergency mode.
ran journalctl -p 3 -xb
Failed to Mount /dev/sda2 = my root partition
Grabbed an iso and chrooted in to fsck.
Disk check said cleaned but still boot into emergency mode after.
Was running fantastic before this.
Ideas ?
Last edited by HighValueWarrior (2021-11-03 01:15:03)
Offline
Make sure you're not actually using the '/dev/sda2' notation, you should be using labels/UUIDs/PARTUUIDs/etc. The 'sda' part can change depending on a number of conditions. There's a wiki page on persistent block naming.
Offline
Post (or link to) the actual journal contents rather than summarizing a single part of a single line of it.
Also tell us about your boot loader / manager and post it's config(s).
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Bootloader is systemd-boot
Nov 02 09:54:16 i7 systemd[1]: Failed to mount /dev/sda2.
Nov 02 09:54:17 i7 kernel: nvidia-gpu 0000:01:00.3: i2c timout error e0000000
Nov 02 09:54:17 i7 kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
Nov 02 09:54:17 i7 kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
Nov 02 09:54:28 i7 systemd[1]: Failed to mount /dev/sda2.
Subject: A start mob for unit dev-sda2.mount has failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/l … temd-devel
A start job tor unit dev-sda2.mount has finished with a failure.
The job identifier is 327 and the job result is failed.
Last edited by HighValueWarrior (2021-11-02 15:37:20)
Offline
Ok, so that still just a small excerpt without context. I suspect someone may be able to infer from that excerpt whether than is the initial mount triggered by the kernel line in the boot loader config or the remount as defined in fstab ... but it would be much more clear if we had the full output.
You've also not posted your boot loader configs.
In any case, Scimmia pointed you to the problem and the solution. Ideally UUIDs should be used in the boot loader configs and in fstab. So just fix them both.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Thank you.
There were just 22 lines. I typed out the relavant ones.
I have always used uuids in my configs.
Confirmed the uuid entry in my fstab matches output from blkid
At work. Will check /boot/loader/entries/ to make sure correct uuid is listed .... when I return home.
Offline
You clearly don't use UUIDs (everywhere). An incorrect UUID would not give this error message. Instead one of your configs clearly specifies /dev/sda2 - and I think that output would indicate this is in your fstab.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Thank you.
There were just 22 lines. I typed out the relavant ones.
Don't type. Use a pastebin service.
https://wiki.archlinux.org/title/List_o … n_services
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
I am always ready to learn ,,,, my fstab
# /dev/sda2
UUID=f986216b-8183-433b-a699-32e7cd24f388 / ext4 rw,relatime 0 1
# /dev/sda1
UUID=3824-1038 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
# /dev/sda4
UUID=c7e36da3-5780-4e41-995b-0c64a17d5a0a /home ext4 rw,relatime 0 2
# /dev/sda3
UUID=50534b13-5774-43a4-a2bd-4bf715a3eb01 none swap defaults 0 0
# automount file synology
192.168.2.2:/volume1/Diskstation /mnt/Diskstation nfs noauto,x-systemd.automount,x-systemd.device-timeout=10,user,noatime 0 0Last edited by HighValueWarrior (2021-11-02 23:23:31)
Offline
What is the contents of the systemd-boot loader config used for booting Arch?
Offline
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
options root=PARTUUID=a68f8c28-73dd-4e4f-946a-dcf0430c92b3 nvidia-drm.modeset=1 mitigations=offOffline
When you reach the emergency mode prompt what is the output of
cat /proc/cmdline
systemctl cat dev-sda2.mountOffline
cat /proc/cmdline
initrd=\intel-ucode.img initrd=\initramfs-linux.img root=PARTUUID=a68f8c28-73dd-4e4f-946a-dcf0430c92b3 nvidia-drm.modeset=1 mitigations=offsystemctl cat dev-sda2.mount
# /run/systemd/generator/dev-sda2.mount
# Automatically generated by systemd-fstab-generator
[Unit]
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
SourcePath=/etc/fstab
Before=local-fs.target
[Mount]
Where=/dev/sda2
What=#Offline
Did you type out the fstab in post #9 or was it exactly copy pasted?
Offline
exactly copy pasted. I pulled the file out with a live cd.
I have not had to touch these files since installation over a year ago.
Last edited by HighValueWarrior (2021-11-03 00:28:52)
Offline
Backup the current fstab then delete the first line and see if that fixes the issue.
Offline
The one that is commented out ??
Offline
Yes, systemd-fstab-generator is not treating it as a comment line.
Offline
Interesting. I tried to nano it and it said file unwriteable.
I will use a live cd to make the changes. Standby.
Offline
loqs
Your the Man.
send me your paypal
P.S why the F##k would it not respect the comment out ..... sigh
Offline
Possibly a None-printing character was inserted before #.
Offline
Thank you again sir, marking solved.
Offline
Pages: 1