[CLOSED] Boot Screen Error Msg

Post Reply
xFaVuBee
Crewman
Posts: 6
Joined: Fri Oct 01, 2021 6:39 am

[CLOSED] Boot Screen Error Msg

Post by xFaVuBee »

Image: https://ibb.co/6Nfww8P

Im not sure if this is Arcolinux Specific but After a yay -Syu on 2021-10-14, i seemed to be having the error message displayed each time I log in.
Thankfully I can log into Arco just fine, and the laptop seems to be working fine aswell.

Debug Logs: https://ufile.io/f/q0186 (Journalctl, pacman.log grep upgrades, dmesg output)

Snippet for 2021-10-14 from:
grep upgrades /var/log/pacman.log

Code: Select all

[2021-10-14T02:21:05-0400] [ALPM] upgraded bluez (5.61-1 -> 5.62-1)
[2021-10-14T02:21:05-0400] [ALPM] upgraded bluez-libs (5.61-1 -> 5.62-1)
[2021-10-14T02:21:05-0400] [ALPM] upgraded bluez-utils (5.61-1 -> 5.62-1)
[2021-10-14T02:21:05-0400] [ALPM] upgraded electron13 (13.5.1-1 -> 13.5.2-1)
[2021-10-14T02:21:06-0400] [ALPM] upgraded flatpak (1.12.1-1 -> 1.12.2-1)
[2021-10-14T02:21:06-0400] [ALPM] upgraded qt5-declarative (5.15.2+kde+r32-1 -> 5.15.2+kde+r33-1)
[2021-10-14T16:35:39-0400] [ALPM] upgraded archiso (58-1 -> 58-2)
[2021-10-14T16:35:39-0400] [ALPM] upgraded arcolinux-logout-git (21.09-03 -> 21.10-01)
[2021-10-14T16:35:47-0400] [ALPM] upgraded linux (5.14.11.arch1-1 -> 5.14.12.arch1-1)
[2021-10-14T16:35:50-0400] [ALPM] upgraded linux-headers (5.14.11.arch1-1 -> 5.14.12.arch1-1)
[2021-10-14T16:35:50-0400] [ALPM] upgraded nvidia (470.74-7 -> 470.74-8)
[2021-10-14T16:35:50-0400] [ALPM] upgraded pamac-all (10.2.0-1 -> 10.2.1-1)
[2021-10-14T16:35:51-0400] [ALPM] upgraded qemu (6.1.0-2 -> 6.1.0-5)
[2021-10-14T16:35:51-0400] [ALPM] upgraded timeshift (21.09.1-2 -> 21.09.1-3)
[2021-10-14T20:21:53-0400] [ALPM] upgraded arcolinux-variety-git (21.09-02 -> 21.10-01)
[2021-10-14T20:21:53-0400] [ALPM] upgraded systemd-libs (249.4-2 -> 249.5-1)
[2021-10-14T20:21:53-0400] [ALPM] upgraded git (2.33.0-1 -> 2.33.1-1)
[2021-10-14T20:21:53-0400] [ALPM] upgraded systemd (249.4-2 -> 249.5-1)
[2021-10-14T20:21:54-0400] [ALPM] upgraded systemd-sysvcompat (249.4-2 -> 249.5-1)
[2021-10-14T20:21:54-0400] [ALPM] upgraded xfce4-whiskermenu-plugin (2.6.0-1 -> 2.6.1-1)
[2021-10-15T17:06:39-0400] [ALPM] upgraded gst-plugins-bad-libs (1.18.5-1 -> 1.18.5-2)
[2021-10-15T17:06:39-0400] [ALPM] upgraded gst-plugins-bad (1.18.5-1 -> 1.18.5-2)
[2021-10-15T17:06:39-0400] [ALPM] upgraded libpurple (2.14.7-1 -> 2.14.8-1)
[2021-10-15T17:06:39-0400] [ALPM] upgraded qt5-svg (5.15.2+kde+r7-1 -> 5.15.2+kde+r13-1)
[2021-10-15T17:06:39-0400] [ALPM] upgraded nomacs (1:3.17.2206-3 -> 1:3.17.2206-5)
[2021-10-15T17:06:48-0400] [ALPM] upgraded npm (8.0.0-1 -> 8.1.0-1)
[2021-10-15T17:06:48-0400] [ALPM] upgraded pidgin (2.14.7-1 -> 2.14.8-1)
[2021-10-15T17:06:48-0400] [ALPM] upgraded virt-install (3.2.0-1 -> 3.2.0-3)
[2021-10-15T17:06:48-0400] [ALPM] upgraded virt-manager (3.2.0-1 -> 3.2.0-3)
Snippets from Journalctl:
grep Debug Debug\ Logs/Journalctl-2021-10-15.txt

Code: Select all

Oct 15 06:10:19 Zeraph systemd[1]: Condition check resulted in Kernel Debug File System being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in Kernel Debug File System being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in Kernel Debug File System being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in Kernel Debug File System being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in Kernel Debug File System being skipped.
Oct 15 06:10:23 Zeraph systemd[1]: Failed to mount Kernel Debug File System.
grep havege ~/Debug\ Logs/Journalctl-2021-10-15.txt

Code: Select all

Oct 15 06:10:23 Zeraph systemd[1]: haveged.service: Start request repeated too quickly.
Oct 15 06:10:23 Zeraph systemd[1]: haveged.service: Failed with result 'start-limit-hit'.
Oct 15 06:35:20 Zeraph dbus-daemon[452]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.44' (uid=0 pid=3906 comm="sudo systemctl haveged ")
Oct 15 06:35:20 Zeraph sudo[3906]:     anon : TTY=pts/1 ; PWD=/home/anon ; USER=root ; COMMAND=/usr/bin/systemctl haveged
Oct 15 06:35:45 Zeraph dbus-daemon[452]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.49' (uid=0 pid=4014 comm="sudo systemctl status haveged.service ")
Oct 15 06:35:45 Zeraph sudo[4014]:     anon : TTY=pts/1 ; PWD=/home/anon ; USER=root ; COMMAND=/usr/bin/systemctl status haveged.service
grep Root Debug\ Logs/Journalctl-2021-10-15.txt

Code: Select all

Oct 15 06:10:19 Zeraph kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
Oct 15 06:10:19 Zeraph systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
Oct 15 06:10:19 Zeraph systemd[1]: Starting Remount Root and Kernel File Systems...
Oct 15 06:10:19 Zeraph systemd[1]: Condition check resulted in Repartition Root Disk being skipped.
Oct 15 06:10:19 Zeraph systemd[1]: Finished Remount Root and Kernel File Systems.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in Repartition Root Disk being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in Repartition Root Disk being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in Repartition Root Disk being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in Repartition Root Disk being skipped.
Oct 15 06:10:23 Zeraph systemd[1]: Failed to start Repartition Root Disk.
grep Boot Debug\ Logs/Journalctl-2021-10-15.txt

Code: Select all

Oct 15 06:10:19 Zeraph kernel: Booting paravirtualized kernel on bare hardware
Oct 15 06:10:19 Zeraph kernel: x86: Booting SMP configuration:
Oct 15 06:10:19 Zeraph kernel: ACPI: EC: Boot ECDT EC used to handle transactions
Oct 15 06:10:19 Zeraph kernel: ACPI: \_SB_.PCI0.LPCB.EC0_: Boot ECDT EC initialization complete
Oct 15 06:10:19 Zeraph systemd[1]: Condition check resulted in First Boot Wizard being skipped.
Oct 15 06:10:19 Zeraph systemd[1]: Condition check resulted in First Boot Complete being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in First Boot Wizard being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in First Boot Complete being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in First Boot Wizard being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in First Boot Complete being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in First Boot Wizard being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in First Boot Complete being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in First Boot Wizard being skipped.
Oct 15 06:10:22 Zeraph systemd[1]: Condition check resulted in First Boot Complete being skipped.
Oct 15 06:10:23 Zeraph systemd[1]: Failed to start First Boot Wizard.
Oct 15 06:10:23 Zeraph systemd[1]: Condition check resulted in First Boot Complete being skipped.
Oct 15 06:10:23 Zeraph systemd[1]: Starting Record System Boot/Shutdown in UTMP...
Oct 15 06:10:23 Zeraph systemd[1]: Finished Record System Boot/Shutdown in UTMP.
The rest of the grep examples Binary, Database, Users, all have the same "Condition check resulted in ... being skipped"
If there is any other info I need to post, ill do that aswell.

Thanks in Advance.
Last edited by xFaVuBee on Tue Oct 19, 2021 9:48 pm, edited 1 time in total.
FavuBeen :geek:

User avatar
erikdubois
Captain
Posts: 4578
Joined: Tue Nov 07, 2017 3:45 pm
Location: Belgium
Contact:

Re: [OPEN] Boot Screen Error Msg

Post by erikdubois »

we have stopped using haveged

arch linux stopped with it
we stopped with it

Code: Select all

sudo systemctl disable haveged

Code: Select all

sudo pacman -R haveged
reboot

and see if that is the issue
Learn, have fun and enjoy.
But first use the power of the Arch Wiki
use the tutorials on https://www.youtube.com/erikdubois
then use the power of google
then use the power of our moderators.

xFaVuBee
Crewman
Posts: 6
Joined: Fri Oct 01, 2021 6:39 am

Re: [OPEN] Boot Screen Error Msg

Post by xFaVuBee »

That seemed to fix only Haveged, the others are still showing each boot up.

EDIT: ok so i used sudo e2fsck -n /dev/sda and directed it into this file - https://ufile.io/apgq9pex

Here's a snippet from the bottom up

Code: Select all

Inode 6331 has INDEX_FL flag set but is not a directory.
Clear HTree index? no

HTREE directory inode 6331 has an invalid root node.
Clear HTree index? no

Inode 6331, i_size is 18446606432892584656, should be 0.  Fix? no

Inode 6331, i_blocks is 4294935248, should be 0.  Fix? no

Inode 6319 has INDEX_FL flag set but is not a directory.
Clear HTree index? no

HTREE directory inode 6319 has an invalid root node.
Clear HTree index? no

Inode 6319, i_size is 18446606432892584656, should be 0.  Fix? no

Inode 6319, i_blocks is 143834159743696, should be 0.  Fix? no

Inode 6320, i_size is 18446606428597649408, should be 0.  Fix? no

Inode 6320, i_blocks is 143834159743696, should be 0.  Fix? no

Inode 6233 has illegal block(s).  Clear? no

Illegal block #6 (2153849840) in inode 6233.  IGNORED.
Illegal block #7 (4294935248) in inode 6233.  IGNORED.
Illegal block #8 (2153849648) in inode 6233.  IGNORED.
Illegal block #9 (4294935248) in inode 6233.  IGNORED.
Illegal block #10 (2153849632) in inode 6233.  IGNORED.
Illegal block #11 (4294935248) in inode 6233.  IGNORED.
Illegal indirect block (2148767824) in inode 6233.  IGNORED.
Illegal double indirect block (4294935248) in inode 6233.  IGNORED.
Illegal triple indirect block (2148771504) in inode 6233.  IGNORED.
Error while iterating over blocks in inode 6233: Illegal triply indirect block found

boot: ********** WARNING: Filesystem still has errors **********


boot: ********** WARNING: Filesystem still has errors **********
Ill run sudo e2fsk /dev/sda and tell you what i get in a file and also after reboot.

EDIT 2: Actually im not sure if i would be safe making any of the decisions, seeing as im underqualified in assessing this output.

Should I be running this command in a chrooted live boot of arch?
FavuBeen :geek:

User avatar
erikdubois
Captain
Posts: 4578
Joined: Tue Nov 07, 2017 3:45 pm
Location: Belgium
Contact:

Re: [OPEN] Boot Screen Error Msg

Post by erikdubois »

Same here

not qualified to give an answer...

Is it already an old drive

Faulty drives do exist
Learn, have fun and enjoy.
But first use the power of the Arch Wiki
use the tutorials on https://www.youtube.com/erikdubois
then use the power of google
then use the power of our moderators.

xFaVuBee
Crewman
Posts: 6
Joined: Fri Oct 01, 2021 6:39 am

Re: [OPEN] Boot Screen Error Msg

Post by xFaVuBee »

The laptop HDD is about 5 years old, I've heard that they can last for about 10years but maybe this one is just failing.
Thanks for your time, I'll try to learn a lil more so I can problem solve this myself!
FavuBeen :geek:

User avatar
erikdubois
Captain
Posts: 4578
Joined: Tue Nov 07, 2017 3:45 pm
Location: Belgium
Contact:

Re: [OPEN] Boot Screen Error Msg

Post by erikdubois »

Good luck
Learn, have fun and enjoy.
But first use the power of the Arch Wiki
use the tutorials on https://www.youtube.com/erikdubois
then use the power of google
then use the power of our moderators.

Post Reply

Return to “BYOI ArcoLinuxB Qtile”