You are not logged in.
hello,
during my boot I received some errors/warnings.
I cant catch&read it, because it is flashing too fast.
I am not interested in dmesg or journalctl, because this error is related with LUKS partition and I need to check this particular error.
dmesg is showing nothing regarding LUKS.
how can I check all messages generated before login prompt (tty1) ?
these messages are appear after first seconds of my computer is turning on.
I checked /var/log and found nothing
any idea?
thanks for help
Last edited by collector1871 (2017-05-01 21:05:15)
Offline
You can edit
/usr/lib/systemd/system/getty@.serviceand set TTYVTDisallocate to "no" which will prevent your console being cleared by systemd. Altough I still think the error should also be logged in the journal. Have you actually looked at it or only at dmesg?
Last edited by FlowIt (2017-05-01 15:33:48)
Offline
You can edit
/usr/lib/systemd/system/getty@.serviceand set TTYVTDisallocate to "no" which will prevent your console being cleared by systemd. Altough I still think the error should also be logged in the journal. Have you actually looked at it or only at dmesg?
Problem is regarding that since last 2 weekend I am configuring mount/encryption
And something went little wrong and this error started flashing during boot.
I can`t read it, because it`s very fast.
And when I am trying to grep journalctl or dmesg, then found nothing regarding encryption.
(or meaby wrong search)
I am very careful of errors like this, because errors regarding mount/encryption are very dangerous for disk health. So I need to debug this and check this error.
any idea how to prevent clearing boot messages via editing /usr/lib/systemd/system/getty@.service ?
Last edited by collector1871 (2017-05-01 15:53:05)
Offline
Altering the service file in /usr/lib/systemd is not recommended as it will be overwritten on package update. systemd#Editing_provided_units
See also General_troubleshooting#Console_messages is you can not scroll back far enough.
Last edited by loqs (2017-05-01 16:04:30)
Offline
So you just grepped the journal for "encryption", found nothing, and your conclusion was that the journal does not contain the error message? Please find 10 minutes to read through the whole journal, I am pretty sure you will find something. There is no generic or easy way to filter the journal for an error you no nothing about.
Offline
type
journalctl -p 3 -xb
to Show only error, critical, and alert priority messages from last boot
Have you tried this?
more ways to filter journal here
https://wiki.archlinux.org/index.php/Systemd#Journal
Last edited by glyons (2017-05-01 23:09:31)
Offline