Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #196391 > unrolled thread

Boot process related logs. What? Where?

Back to article view | Back to linux.debian.user

Contents

  Boot process related logs. What? Where? Richard Owlett <rowlett@cloud85.net> - 2018-06-04 11:30 +0200
    Re: Boot process related logs. What? Where? songbird <songbird@anthive.com> - 2018-06-04 14:00 +0200
    Re: Boot process related logs. What? Where? David Wright <deblis@lionunicorn.co.uk> - 2018-06-04 15:40 +0200

#196391 — Boot process related logs. What? Where?

My explicit question is:
    Does an annotated list of boot process related log files and
    their locations exist?

I did a reasonably typical install from DVD-1 of Debian 9.1.0 .
It is at least partly functional - I can log in as root.
The only error message during boot was that it could not find a device 
with a specific UUID. It didn't stick around long enough to manually 
copy the string.

What is odd is that the last 5 characters match the UUID of the 
partition it is booting from.
I need to know:
   1. the complete UUID string
   2. what was it looking for at the time

I know that many log files are under  /var/log/ .
I used an operable system to examine the files on the failed partition 
and could not find a useful readable file. One file had an interesting 
name, but was apparently a binary file.

[toc] | [next] | [standalone]

#196392

Richard Owlett wrote:
> My explicit question is:
>     Does an annotated list of boot process related log files and
>     their locations exist?

  /var/log/installer ?


> I did a reasonably typical install from DVD-1 of Debian 9.1.0 .
> It is at least partly functional - I can log in as root.
> The only error message during boot was that it could not find a device 
> with a specific UUID. It didn't stick around long enough to manually 
> copy the string.
>
> What is odd is that the last 5 characters match the UUID of the 
> partition it is booting from.
> I need to know:
>    1. the complete UUID string
>    2. what was it looking for at the time
>
> I know that many log files are under  /var/log/ .

  yes, and it helps to know what they all are...


> I used an operable system to examine the files on the failed partition 
> and could not find a useful readable file. One file had an interesting 
> name, but was apparently a binary file.

  is this system supposed to be running systemd?

  if so, create a /var/log/journal directory to get persistent
logs from systemd.

  then you can use journalctl to look at them.


  songbird

[toc] | [prev] | [next] | [standalone]

#196399

On Mon 04 Jun 2018 at 04:21:20 (-0500), Richard Owlett wrote:
> My explicit question is:
>    Does an annotated list of boot process related log files and
>    their locations exist?

Not AFAICT. But it's never to late to start writing a wiki.

> I did a reasonably typical install from DVD-1 of Debian 9.1.0 .

"reasonably typical". Not a lot of help.

> It is at least partly functional - I can log in as root.
> The only error message during boot was that it could not find a
> device with a specific UUID. It didn't stick around long enough to
> manually copy the string.
> 
> What is odd is that the last 5 characters match the UUID of the
> partition it is booting from.
> I need to know:
>   1. the complete UUID string
>   2. what was it looking for at the time

/var/log/kern.log and /var/log/messages will both normally
contain the kernel comand line that actually booted the system.
You could then reconcile that with the contents of /etc/fstab
and the /boot/grub/grub.cfg you think was used. (I am aware
that you typically mangle the installation of grub.)

ls -l /dev/disk/*uuid
will give you a list of potential UUIDs that the system might
be looking for. The probability is quite high that they are
all unique in as few as the last five characters.

> I know that many log files are under  /var/log/ .
> I used an operable system to examine the files on the failed
> partition and could not find a useful readable file. One file had an
> interesting name, but was apparently a binary file.

Yes, it would probably be an interesting name for the rest of us to
know, but I realise that it would not be typical for you to reveal it.

Cheers,
David.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web