| 1 |
Thanks for stepping in Dale. Yes, I was thinking /bar/log/messages or |
| 2 |
something similar. |
| 3 |
|
| 4 |
If the machine was completely hung then no disk activity probably means a |
| 5 |
big jump in the times logged and should make it somewhat easier to find the |
| 6 |
last stuff written. |
| 7 |
|
| 8 |
Please excuse the top posting. I'm on my phone with limited editing |
| 9 |
capabilities in GMail. |
| 10 |
|
| 11 |
Good luck |
| 12 |
|
| 13 |
On Wed, May 12, 2021, 7:50 PM Dale <rdalek1967@×××××.com> wrote: |
| 14 |
|
| 15 |
> Walter Dnes wrote: |
| 16 |
> > On Wed, May 12, 2021 at 11:16:56AM -0700, Mark Knecht wrote |
| 17 |
> >> Is there nothing in the system logs? What's near the end before whatever |
| 18 |
> >> you get from booting after this issue? |
| 19 |
> > Where would those logfiles be? "dmesg" starts off with... |
| 20 |
> > |
| 21 |
> |
| 22 |
> |
| 23 |
> Most likely in /var/log/messages. The bad thing about dmesg, I think it |
| 24 |
> resets when rebooting which erases previous info. |
| 25 |
> |
| 26 |
> As Mark pointed out, you need to go back to the time before it starts |
| 27 |
> adding the boot up process. |
| 28 |
> |
| 29 |
> Hope that helps. |
| 30 |
> |
| 31 |
> Dale |
| 32 |
> |
| 33 |
> :-) :-) |
| 34 |
> |
Archives