On Wed, Sep 4, 2019 at 4:21 PM stan via users
On Wed, 4 Sep 2019 15:05:36 -0400
murph nj <murphnj+fedora(a)gmail.com> wrote:
> I was able to mount the drives, and check them, no problems.
Did that include the boot partition, where the kernels and initramfs'
I had not, but on your suggestion, I did. And....
> I also took a look at the journals that were left, there was
> that seemed terribly indicative of the problem. It was all from the
> last time that it was running normally, nothing was getting written on
> the failed boot attempts, unfortunately.
Did you remove rhgb and quiet from the kernel boot parameters? That
should show you the stream of messages from systemd as the system
boots, and the error should be near the end of that stream, so it
should still be on screen when the crash happens. I think you hit
space or escape during boot to get the boot menu, and then you can edit
the line. I have a timeout, so I always see it.
I had not, but I edited from the grub menu, and eliminated them. I
was then able to see the messages. (I was able to see them previously
by hitting the escape key right after entering my password for the
Everything left on the screen after the kernel panic is (too much to type)
Does it drop to a dracut or grub prompt? If it does, it is also
possible to view the temporary boot logs from there (I think they are
under /tmp (/var/tmp?)). It's painful because the shell is very limited.
to see the available commands. I think less is there, as is vi.
Unfortunately, it goes right to a kernel panic, so no prompts at all
to work with. (I'd have chewed on it more before asking for help if I
had more to work with)