Stop scrolling through endless logs looking for a specific boot
Logging & Journald
Stop scrolling through endless logs looking for a specific boot
🧩 The Challenge
Trying to find the exact logs from the last time the server crashed and rebooted is a nightmare when you have to guess the timestamps. I have spent way too much time hunting for that one specific boot record while the rest of the team is waiting for an answer.
💡 The Fix
Use the offset flag to jump straight to a previous boot session without playing the guessing game with grep. It makes tracking down post-reboot panic entries a five-second job.
journalctl -b -1 -e
⚙️ Why It Works
Passing the minus one integer tells journald to go back exactly one boot cycle from the current one. It drops you right at the end of that log sequence so you can see what happened right before the system went down.
🚀 Pro-Tip: Use -b -2 if the first reboot didn’t actually clear the issue and you need to look even further back.
Linux Tips & Tricks | © ngelinux.com | 11/19/2026
