On 19/06/2020 03:07, John Carter wrote:
> T M Smith wrote in
> news:5df3fded54.Broadband@tmsmith36.plus.com:
>> Using Rasbian on a Pi is there a log kept of the data that scolls
>> past as the system boots?
>
> I was told early on that there was no log. It has something to do with
> the BOOT process starting in the GPU and there is a point where the
> filesystem is mounted such that it is too late to do any BOOT logging.
>
> Pleae correct me here if this is wrong.
If I'm checking a system for problems, after boot up I do a
dmesg -H
This prints out the kernel logs from boots, in a paginated form so it
doesn't just shoot paste. Look for any red lines which signify errors,
you'll normally only get a couple from brcmfmac which can normally be
ignored.
I then do a
systemctl --failed
Which will show any services which didn't start up. If any are shown,
for each name to a
systemctl status -l
I then also use vim to look at /var/log/messages (vim uses syntax
colouring to make spotting errors easier) to look for issues before
and/or after the reboot. If there are problems, more information will be
in /var/log/syslog You may need to look in /var/log/syslog.1 for
information from before the reboot.
---druck
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | FidoUsenet Gateway (3:770/3)
|