ara1
2 February 2024 11:25
1
Greetings,
I run Big Linux, a Manjaro based distro. I tried to get help from their forum but the majority of the content is Portuguese.
Can anybody give some guidance to solve this? See URL below for screen output text when I was sent to the emergency mode when booting the system unsuccessfully.
Much appreciated.
ben75
2 February 2024 12:53
3
You can paste preformatted text here. Pastebin is completely unnecessary.
In Firefox you can use this:
ara1
3 February 2024 01:07
5
Portuguese is NOT the language in the screen output URL enclosed. I only meant the downstream distro’s own forum is not useful to me. Thats why I am here on Manjaro forum.
Can anyone help check the info on Boot failure output - Pastebin.com (which is in English) and give some pointers on fixing the problem? This is the full boot screen output of my system when I was sent to the emergency mode.
Much appreciated.
cscs
3 February 2024 02:24
6
There something wrong with tlp and your scheduler
Theres also something wrong with your users/home/pam/systemd
Fstab or other mount/dependency problems
And theres some sort of problem occuring with plymouth, though it could just be a symptom of the other problems … but plymouth is nothing but a wasteful potention source of issues to me.
Theres also snaps trying to automount/autorun that are failing.
(this crappy ‘hello world’ snap and its fail logs are repated a number of times)
A bunch of scheduler and missing device/path errors
2月 01 16:51:38 bigLinux (udev-worker)[552]: nvme0: /etc/udev/rules.d/60-ioschedulers.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:02.4/0000:02:00.0/nvme/nvme0/queue/scheduler}, ignoring: No such file or directory
2月 01 16:51:38 bigLinux (udev-worker)[552]: nvme0n1p1: /etc/udev/rules.d/60-ioschedulers.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:02.4/0000:02:00.0/nvme/nvme0/nvme0n1/nvme0n1p1/queue/scheduler}, ignoring: No such file or directory
2月 01 16:51:38 bigLinux (udev-worker)[564]: nvme0n1p3: /etc/udev/rules.d/60-ioschedulers.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:02.4/0000:02:00.0/nvme/nvme0/nvme0n1/nvme0n1p3/queue/scheduler}, ignoring: No such file or directory
2月 01 16:51:38 bigLinux (udev-worker)[576]: nvme0n1p2: /etc/udev/rules.d/60-ioschedulers.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:02.4/0000:02:00.0/nvme/nvme0/nvme0n1/nvme0n1p2/queue/scheduler}, ignoring: No such file or directory
2月 01 16:51:38 bigLinux big-preload[438]: ldd: /usr/lib/kf5/start_kdeinit: No such file or directory
2月 01 16:51:38 bigLinux big-preload[438]: ldd: /usr/lib/kf5/klauncher: No such file or directory
2月 01 16:51:38 bigLinux systemd[1]: Found device YMTC PC300-1TB-B EFI\x20System\x20Partition.
░░ Subject: A start job for unit dev-disk-by\x2duuid-B2E7\x2d48A4.device has finished successfully
More missing paths/mounts
2月 01 16:51:38 bigLinux systemd[1]: var-cache.mount: Mount process exited, code=exited, status=32/n/a
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: Support - Manjaro Linux Forum
░░
░░ An n/a= process belonging to unit var-cache.mount has exited.
░░
░░ The process’ exit code is ‘exited’ and its exit status is 32.
2月 01 16:51:38 bigLinux kernel: mousedev: PS/2 mouse device common for all mice
2月 01 16:51:38 bigLinux systemd[1]: var-cache.mount: Failed with result ‘exit-code’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Support - Manjaro Linux Forum
░░
░░ The unit var-cache.mount has entered the ‘failed’ state with result ‘exit-code’.
2月 01 16:51:38 bigLinux systemd[1]: Failed to mount /var/cache.
░░ Subject: A start job for unit var-cache.mount has failed
Apparmor failing too
2月 01 16:51:38 bigLinux systemd[1]: Dependency failed for Load AppArmor profiles managed internally by snapd.
░░ Subject: A start job for unit snapd.apparmor.service has failed
░░ Support: Support - Manjaro Linux Forum
░░
░░ A start job for unit snapd.apparmor.service has finished with a failure.
░░
░░ The job identifier is 192 and the job result is dependency.
More problems with things not existing.
And more of things missing and not mounting
And more and more
2月 01 16:51:40 bigLinux sudo[1371]: pam_systemd_home(sudo:account): Failed to connect to system bus: No such file or directory
2月 01 16:51:40 bigLinux sudo[1371]: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/chmod -R 777 ‘/mnt/USB Drive/’
2月 01 16:51:40 bigLinux sudo[1371]: pam_systemd_home(sudo:session): Failed to connect to system bus: No such file or directory
2月 01 16:51:40 bigLinux sudo[1371]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
2月 01 16:51:40 bigLinux sudo[1371]: pam_unix(sudo:session): session closed for user root
2月 01 16:51:40 bigLinux sudo[1379]: pam_systemd_home(sudo:account): Failed to connect to system bus: No such file or directory
2月 01 16:51:40 bigLinux sudo[1379]: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/chmod -R 777 ‘/media/Misc use NTFS/’
2月 01 16:51:40 bigLinux sudo[1379]: pam_systemd_home(sudo:session): Failed to connect to system bus: No such file or directory
2月 01 16:51:40 bigLinux sudo[1379]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
2月 01 16:51:40 bigLinux biglinux-improve-compatibility[1383]: chmod: cannot access ‘/media/Misc use NTFS/’: No such file or directory
2月 01 16:51:40 bigLinux sudo[1379]: pam_unix(sudo:session): session closed for user root
2月 01 16:51:40 bigLinux sudo[1387]: pam_systemd_home(sudo:account): Failed to connect to system bus: No such file or directory
2月 01 16:51:40 bigLinux sudo[1387]: root : PWD=/ ; USER=root ; COMMAND=/usr/bin/chmod -R 777 /media/sde6-ata-WDC_WD2500BEVS-0/
2月 01 16:51:40 bigLinux sudo[1387]: pam_systemd_home(sudo:session): Failed to connect to system bus: No such file or directory
2月 01 16:51:40 bigLinux sudo[1387]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
2月 01 16:51:40 bigLinux biglinux-improve-compatibility[1391]: chmod: cannot access ‘/media/sde6-ata-WDC_WD2500BEVS-0/’: No such file or directory
…
Start by going over your /etc/fstab I guess.