--Boot 32 character value --

[compis2]

My Debian bookworm locks up and when I look at journalctl I find --boot xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx -- in the log, where x is an alphanumeric value that changes. Can anyone tell me how I can find out more on what this boot is ?

 

[osprey]

Perhaps have a look here:

https://linux.org/threads/linux-mint-21-2-xfce-freezes-constantly.47523

for an approach to "locks up" or freezes. It's best if you provide exact output of the logs, using code tags, for readers to inspect the text in it's pristine form to avoid misinterpretations.

 

[compis2]

That is not the same type of problem. My Debian running XFCE freezes and the journal shows the --boot message at the time of failure..This is a newly settup machine. I am suspecting XFCE but I have another machine which doesn't have the issue.

 

[wizardfromoz]

-boot xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Does that match your UUID for root / from

cat /etc/fstab

Wizard

 

[compis2]

Does that match your UUID for root / from

cat /etc/fstab

Wizard

No. The value changes with every freeze. examples
-- Boot c702f41dea664d44a6c8875ab87ceb92 --
-- Boot 4bd27d8bd88b43299b5cdd749547bcc5 --
But it is an encrypted LUKS drive. I watch the next.

 

[compis2]

It is strange I posted on Reddit this issue and got the following response. Also since I post the freeze has not occurred, where as it would occur once a day.

 

[wizardfromoz]

You could try removing the encryption condition and see if it functions without issues.

Is there any output from the following commands

sudo blkid | grep -i "c702f41d-ea66-4d44-a6c8-875ab87ceb92"

sudo blkid | grep -i "4bd27d8b-d88b-4329-9b5c-dd749547bcc5"

Wizard

 

[compis2]

The search does not return anything. Also a view of the fstab shows a different value which does not change.
It appears that the -- boot xxxx value represents something else.

 

[f33dm3bits]

Those are just the boot id's journald uses.

journalctl --list-boots

`journalctl -b -1` says no such boot ID, while `journalctl --list-boots` shows it · Issue #28981 · systemd/systemd

systemd version the issue has been seen with 251 Used distribution Fedora 37 / Qubes OS dom0 Linux kernel version used 6.1.43-1.qubes.fc37.x86_64 CPU architectures issue was seen on x86_64 Componen...

github.com

 

[compis2]

Those are just the boot id's journald uses.

journalctl --list-boots

`journalctl -b -1` says no such boot ID, while `journalctl --list-boots` shows it · Issue #28981 · systemd/systemd

systemd version the issue has been seen with 251 Used distribution Fedora 37 / Qubes OS dom0 Linux kernel version used 6.1.43-1.qubes.fc37.x86_64 CPU architectures issue was seen on x86_64 Componen...

github.com

What is the purpose of Boot id's ? Since the journctl shows the date and time.

 

[f33dm3bits]

What is the purpose of Boot id's ? Since the journctl shows the date and time.

Each time the system boot the boot gets a boot id, that way if you want to look something up from a specific boot you can just use the boot id or the or the pointer to view the logs from a specific boot. For example you run the following.

 journalctl --list-boots | head -6
IDX BOOT ID                          FIRST ENTRY                 LAST ENTRY
-26 27c5b1e726074052a6f00d2569d23710 Tue 2023-11-14 07:23:01 CET Tue 2023-11-14 21:48:46 CET
-25 00bf5be744ee4c68a0921573ae71d218 Wed 2023-11-15 07:28:34 CET Wed 2023-11-15 23:57:45 CET
-24 ea291177a21a400bbe716192424b8840 Thu 2023-11-16 07:45:13 CET Thu 2023-11-16 21:36:45 CET
-23 ec856be145b645baa2bd0bc4698edc8b Fri 2023-11-17 08:43:21 CET Sat 2023-11-18 01:33:18 CET
-22 787fd27f6b9e4078ae01326cf9ef5e4c Sat 2023-11-18 09:15:12 CET Sat 2023-11-18 23:01:23 CET

You can then just use the pointer which points to view that boot journal.

journalctl -b -26

Or you can use the boot id to view all the logs of that boot.

journalctl -b 27c5b1e726074052a6f00d2569d23710

How To Use Journalctl to View and Manipulate Systemd Logs | DigitalOcean

Some of the most compelling advantages of systemd are those involved with process and system logging. Using other systems, logs are usually dispersed through…

www.digitalocean.com

 

[compis2]

Each time the system boot the boot gets a boot id, that way if you want to look something up from a specific boot you can just use the boot id or the or the pointer to view the logs from a specific boot. For example you run the following.

 journalctl --list-boots | head -6
IDX BOOT ID                          FIRST ENTRY                 LAST ENTRY
-26 27c5b1e726074052a6f00d2569d23710 Tue 2023-11-14 07:23:01 CET Tue 2023-11-14 21:48:46 CET
-25 00bf5be744ee4c68a0921573ae71d218 Wed 2023-11-15 07:28:34 CET Wed 2023-11-15 23:57:45 CET
-24 ea291177a21a400bbe716192424b8840 Thu 2023-11-16 07:45:13 CET Thu 2023-11-16 21:36:45 CET
-23 ec856be145b645baa2bd0bc4698edc8b Fri 2023-11-17 08:43:21 CET Sat 2023-11-18 01:33:18 CET
-22 787fd27f6b9e4078ae01326cf9ef5e4c Sat 2023-11-18 09:15:12 CET Sat 2023-11-18 23:01:23 CET

You can then just use the pointer which points to view that boot journal.

journalctl -b -26

Or you can use the boot id to view all the logs of that boot.

journalctl -b 27c5b1e726074052a6f00d2569d23710

How To Use Journalctl to View and Manipulate Systemd Logs | DigitalOcean

Some of the most compelling advantages of systemd are those involved with process and system logging. Using other systems, logs are usually dispersed through…

www.digitalocean.com

Thanks