#Arch crashing

44 messages · Page 1 of 1 (latest)

cloud stirrup
#

Most of the time as of recently gotten alot worse when I shut my system down i have to hold down the power button as it gets stuck. Now my system is freezing often. Any suggestions?

short totem
#

@cloud stirrup are you fully updated?

short totem
#

... reisub

#

... magickeys

#

@short totem qbot is down

#

https://forum.endeavouros.com/t/tip-enable-magic-sysrq-key-reisub/7576
[Tip] Enable Magic SysRq Key (REISUB) - EndeavourOS Forum

EndeavourOS
[Tip] Enable Magic SysRq Key (REISUB)

The Linux kernel authors have provided a very nice feature of issuing low-level commands to the kernel directly, regardless of the state the system is in. This is called the “Magic SysRq Key”, because these commands are issued by pressing the SysRq key on the keyboard (if you can’t find it, typically, it shares the same physical key as the...

#

Anyways this helps

#

I think a chroot will help to get logs off it

#

@cloud stirrup

cloud stirrup
#

Thanks, Ill have to check these out when I get home. I wonder if the crashes I've started to get are related to me doing force shutdowns. Probably are

short totem
cloud stirrup
cloud stirrup
#

Something is seriously wrong. Ran sudo pacman -Syu, got transport endpoint is not connected on upgrading systemd. Restarted update, took forever to issue command and forever to issue Sorry, try again. prompt for sudo pass

#

I think its a filesystem issue. Put a arch iso usb in to try to repair root filesystem, computer frozen entering bios. Gonna completely shut off power and try again later

short totem
cloud stirrup
# short totem Chroot and get logs

Is there something specific I need to do to get the logs from a freeze/crash and/or stuck-on-reboot?
I havent checked the system logs before. For chroot, do you mean to boot into a repair-environment and chroot to check logs and if so, why? Do you want me to try that after a crash?

short totem
cloud stirrup
short totem
#

... journalctl

verbal grailBOT
#

#10200 📣 ```js

To actively follow log (like tail -f):

journalctl -f

To display all errors since last boot:

journalctl -b -p err

To filter by time period:

journalctl --since=2012-10-15 --until="2011-10-16 23:59:59"

To show list of systemd units logged in journal:

journalctl -F _SYSTEMD_UNIT

To filter by specific unit:

journalctl -u dbus

To filter by executable name:

journalctl /usr/bin/dbus-daemon

To filter by PID:

journalctl _PID=123

To filter by Command, e.g., sshd:

journalctl _COMM=sshd

To filter by Command and time period:

journalctl _COMM=crond --since '10:00' --until '11:00'

To list all available boots:

journalctl --list-boots

To filter by specific User ID e.g., user id 1000:

journalctl _UID=1000

To filter by specific SYSLOG_INDENTIFIER:

journalctl -t systemd-resolved
tldr:journalctl

journalctl

Query the systemd journal.

More information: https://manned.org/journalctl.

Show all messages with priority level 3 (errors) from this [b]oot:

journalctl -b --priority=3

Show all messages from last [b]oot:

journalctl -b -1

Delete journal logs which are older than 2 days:

journalctl --vacuum-time=2d

[f]ollow new messages (like tail -f for traditional syslog):

journalctl -f

Show all messages by a specific [u]nit:

journalctl -u unit

Filter messages within a time range (either timestamp or placeholders like "yesterday"):

journalctl --since now|today|yesterday|tomorrow --until YYYY-MM-DD HH:MM:SS

Show all messages by a specific process:

journalctl _PID=pid

Show all messages by a specific executable:

journalctl path/to/executable
$```

cloud stirrup
#

still cant really find anything. I just had to force power off my PC because I cant turn it back on in any way when it suspends from inactivity and found nothing

#

I found this but I think it happened after rebooting and doesnt seem significant

image.png
short totem
#

... mandmesg

verbal grailBOT
#

#17423 📣 ```js
cheat.sheets:dmesg

dmesg

Print or control the kernel ring buffer

Print the ring buffer contents, then clear it.

dmesg -c

Display the local time and the delta in human-readable format. Conversion to

the local time could be inaccurate.

dmesg -e

Print human-readable timestamps.

dmesg -T

Human-readable output (color + reltime).

dmesg -H
tldr:dmesg

dmesg

Write the kernel messages to standard output.

More information: https://manned.org/dmesg.

Show kernel messages:

dmesg

Show kernel error messages:

dmesg --level err

Show kernel messages and keep reading new ones, similar to tail -f (available in kernels 3.5.0 and newer):

dmesg -w

Show how much physical memory is available on this system:

dmesg | grep -i memory

Show kernel messages 1 page at a time:

dmesg | less

Show kernel messages with a timestamp (available in kernels 3.5.0 and newer):

dmesg -T

Show kernel messages in human-readable form (available in kernels 3.5.0 and newer):

dmesg -H

Colorize output (available in kernels 3.5.0 and newer):

dmesg -L
$```

short totem
#

So you can gracefully reboot

#

... magickeys

verbal grailBOT
cloud stirrup
cloud stirrup
#

Its not in the manual for my keyboard, and ive tried the keyboards inbuilt prnt-scrn macro

short totem
#

then on next freeze, it should work and ask the kernel to reboot gracefully

cloud stirrup
#

enabled sysrq key in linux command line settings/grub -> rebooted -> tried key combination -> nothing happened

#

i also tried enabling it with the command

short totem
#

so you can know what went wrong

#

then, try to fix

cloud stirrup