[gentoo-user] See bootup/poweroff screen?

[gentoo-user] See bootup/poweroff screen?

[German]

I have a SSD in my laptop and the system boots really fast so I can't see the details of the warnings it displays. Are there any way to scroll the screen or see some system boot's logs? Thanks

-- 
German <gentgerman@gmail.com>

Re: [gentoo-user] See bootup/poweroff screen?

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 341 bytes --]

On Thu, Mar 5, 2015 at 1:58 PM, German <gentgerman@gmail.com> wrote:

> I have a SSD in my laptop and the system boots really fast so I can't see
> the details of the warnings it displays. Are there any way to scroll the
> screen or see some system boot's logs?


Try;
dmesg | less

And you may also find what you need in /var/log/messages.

[-- Attachment #2: Type: text/html, Size: 694 bytes --]

Re: [gentoo-user] See bootup/poweroff screen?

[Dale]

[-- Attachment #1: Type: text/plain, Size: 534 bytes --]

German wrote:
> I have a SSD in my laptop and the system boots really fast so I can't see the details of the warnings it displays. Are there any way to scroll the screen or see some system boot's logs? Thanks
>


You may want to read this post and try this method too.  I did this ages
ago and on occasion, it helps. 

http://forums.gentoo.org/viewtopic-p-7682938.html#7682938 

It should scroll to it but it's the second post that is made by PeGa!
that may help.  The messages go to this file:  /var/log/rc.log 

Dale

:-)  :-)  *
*

[-- Attachment #2: Type: text/html, Size: 1148 bytes --]

Re: [gentoo-user] See bootup/poweroff screen?

[German]

On Thu, 05 Mar 2015 00:17:34 -0600
Dale <rdalek1967@gmail.com> wrote:

> German wrote:
> > I have a SSD in my laptop and the system boots really fast so I can't see the details of the warnings it displays. Are there any way to scroll the screen or see some system boot's logs? Thanks
> >
> 
> 
> You may want to read this post and try this method too.  I did this ages
> ago and on occasion, it helps. 
> 
> http://forums.gentoo.org/viewtopic-p-7682938.html#7682938 
> 
> It should scroll to it but it's the second post that is made by PeGa!
> that may help.  The messages go to this file:  /var/log/rc.log 
> 
> Dale
> 
> :-)  :-)  *
> *

Thanks Dale, done it. Unfortunately it doesn't log everything. For instance "Warning: /lib64/rc/cache is not writable" wasn't written to /var/log/rc.log


-- 
German <gentgerman@gmail.com>

Re: [gentoo-user] See bootup/poweroff screen?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 381 bytes --]

On Thu, 5 Mar 2015 03:08:46 -0500, German wrote:

> Thanks Dale, done it. Unfortunately it doesn't log everything. For
> instance "Warning: /lib64/rc/cache is not writable" wasn't written
> to /var/log/rc.log

Of course it wasn't. Warnings about /var not being writeable are not going
to be written to /var.


-- 
Neil Bothwick

Why is bra singular and pants plural?

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] See bootup/poweroff screen?

[Dale]

[-- Attachment #1: Type: text/plain, Size: 778 bytes --]

Neil Bothwick wrote:
> On Thu, 5 Mar 2015 03:08:46 -0500, German wrote:
>
>> Thanks Dale, done it. Unfortunately it doesn't log everything. For
>> instance "Warning: /lib64/rc/cache is not writable" wasn't written
>> to /var/log/rc.log
>
> Of course it wasn't. Warnings about /var not being writeable are not going
> to be written to /var.
>
>

Yea, it won't catch everything.  This is sort of designed for that point
where one log stops and the other hasn't started yet.  This is usually
where dmesg stops and syslog and friends hasn't yet started.  Of course,
if /var isn't mounted, well, it has no where to go.

Isn't those init thingys supposed to fix this sort of thing tho?  Isn't
it supposed to store it in memory until /var is mounted and then dump it?

Dale

:-)  :-)


[-- Attachment #2: Type: text/html, Size: 1253 bytes --]

Re: [gentoo-user] See bootup/poweroff screen?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 978 bytes --]

On Thu, 05 Mar 2015 03:16:55 -0600, Dale wrote:

> > Of course it wasn't. Warnings about /var not being writeable are not
> > going to be written to /var.

> Yea, it won't catch everything.  This is sort of designed for that point
> where one log stops and the other hasn't started yet.  This is usually
> where dmesg stops and syslog and friends hasn't yet started.  Of course,
> if /var isn't mounted, well, it has no where to go.
> 
> Isn't those init thingys supposed to fix this sort of thing tho?  Isn't
> it supposed to store it in memory until /var is mounted and then dump
> it?

The combination of dracut and systemd means it all goes in the journal.
The journal is kept in memory and then flushed to disk later in the boot
process.

journalctl is rather neat, being able to search both dmesg and system
logs in one go, and apply various search criteria, is far more flexible
than the alternatives.


-- 
Neil Bothwick

WWW: World Wide Wait

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] See bootup/poweroff screen?

[covici]

Dale <rdalek1967@gmail.com> wrote:

> Neil Bothwick wrote:
> > On Thu, 5 Mar 2015 03:08:46 -0500, German wrote:
> >
> >> Thanks Dale, done it. Unfortunately it doesn't log everything. For
> >> instance "Warning: /lib64/rc/cache is not writable" wasn't written
> >> to /var/log/rc.log
> >
> > Of course it wasn't. Warnings about /var not being writeable are not going
> > to be written to /var.
> >
> >
> 
> Yea, it won't catch everything.  This is sort of designed for that point
> where one log stops and the other hasn't started yet.  This is usually
> where dmesg stops and syslog and friends hasn't yet started.  Of course,
> if /var isn't mounted, well, it has no where to go.
> 
> Isn't those init thingys supposed to fix this sort of thing tho?  Isn't
> it supposed to store it in memory until /var is mounted and then dump it?

Make sure your kernel log buffer is as high as it will go, I use 21 if
memory serves which is about a meg or so.  Also, I find with an init
thingy and using systemd (Yes I know, don't start a flame war), then I
see everything in its system journal -- much more even than rc.log used
to give me.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] See bootup/poweroff screen?

[Dale]

covici@ccs.covici.com wrote:
> Dale <rdalek1967@gmail.com> wrote:
>
>> Neil Bothwick wrote:
>>> On Thu, 5 Mar 2015 03:08:46 -0500, German wrote:
>>>
>>>> Thanks Dale, done it. Unfortunately it doesn't log everything. For
>>>> instance "Warning: /lib64/rc/cache is not writable" wasn't written
>>>> to /var/log/rc.log
>>> Of course it wasn't. Warnings about /var not being writeable are not going
>>> to be written to /var.
>>>
>>>
>> Yea, it won't catch everything.  This is sort of designed for that point
>> where one log stops and the other hasn't started yet.  This is usually
>> where dmesg stops and syslog and friends hasn't yet started.  Of course,
>> if /var isn't mounted, well, it has no where to go.
>>
>> Isn't those init thingys supposed to fix this sort of thing tho?  Isn't
>> it supposed to store it in memory until /var is mounted and then dump it?
> Make sure your kernel log buffer is as high as it will go, I use 21 if
> memory serves which is about a meg or so.  Also, I find with an init
> thingy and using systemd (Yes I know, don't start a flame war), then I
> see everything in its system journal -- much more even than rc.log used
> to give me.
>

I just recall reading somewhere, systemd or not, that that is how it is
supposed to work.  After all, it can't run fsck and such while mounted
rw from my understanding.   It's been to long ago since I read that
tho.  Add in that I'm kick boxing with the flu right now and things are
fuzzy at least.   That kernel log buffer does ring a bell somewhere out
there. 

Dale

:-)  :-) 

Re: [gentoo-user] See bootup/poweroff screen?

[Rich Freeman]

On Thu, Mar 5, 2015 at 8:19 AM, Dale <rdalek1967@gmail.com> wrote:
>
> I just recall reading somewhere, systemd or not, that that is how it is
> supposed to work.  After all, it can't run fsck and such while mounted
> rw from my understanding.

Keep in mind that an initramfs is nothing more than an archive file
containing some kind of init implementation (often just a shell
script) that the kernel unpacks and launches.  It does whatever it is
designed to do.  Some are more bare-boned than others.

I personally use dracut which has quite a few bells and whistles.  If
you're using systemd as has already been pointed out it runs the
journal during early boot and merges it into the system journal when
it pivots.  I believe that if you're not using systemd it captures
whatever it does to a log file in /run, but I don't think it
necessarily runs a full syslog listening to /dev/log and so on.  That
said, nothing is really running that early in boot so as long as it
logs its own work you're fine.  Often the level of logging is
configurable.

-- 
Rich

Re: [gentoo-user] See bootup/poweroff screen?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 577 bytes --]

On Thu, 5 Mar 2015 09:38:07 -0500, Rich Freeman wrote:

> I personally use dracut which has quite a few bells and whistles.  If
> you're using systemd as has already been pointed out it runs the
> journal during early boot and merges it into the system journal when
> it pivots.  I believe that if you're not using systemd it captures
> whatever it does to a log file in /run,

My understanding of the man page is that it only does that if you use the
rd.debug option.


-- 
Neil Bothwick

Gigabyte: (n.) more than you can comprehend and less than you'll need.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] See bootup/poweroff screen?

[Rich Freeman]

On Thu, Mar 5, 2015 at 12:08 PM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Thu, 5 Mar 2015 09:38:07 -0500, Rich Freeman wrote:
>
>> I personally use dracut which has quite a few bells and whistles.  If
>> you're using systemd as has already been pointed out it runs the
>> journal during early boot and merges it into the system journal when
>> it pivots.  I believe that if you're not using systemd it captures
>> whatever it does to a log file in /run,
>
> My understanding of the man page is that it only does that if you use the
> rd.debug option.

That wouldn't surprise me.  I tend to use that option since I run
stuff like root on btrfs, or root on nfs with kernel/initramfs over
PXE and such - so you can imagine I'm a bit more likely to run into
bugs than the typical root-on-ext4-sda1 sort.

-- 
Rich

Re: [gentoo-user] See bootup/poweroff screen?

[Fernando Rodriguez]

On Thursday, March 05, 2015 3:16:55 AM Dale wrote:
> Yea, it won't catch everything.  This is sort of designed for that point
> where one log stops and the other hasn't started yet.  This is usually
> where dmesg stops and syslog and friends hasn't yet started.  Of course,
> if /var isn't mounted, well, it has no where to go.
> 
> Isn't those init thingys supposed to fix this sort of thing tho?  Isn't
> it supposed to store it in memory until /var is mounted and then dump it?
> 
> Dale
> 
> :-)  :-)
> 

Even late on the boot process the OpenRC log won't catch everything. I think 
it only logs openrc messages, if it comes from some program it's probably on 
the system log (or nowhere at all).

-- 
Fernando Rodriguez