To investigate an unexpected Linux reboot, first establish when it happened, then inspect the preceding boot’s logs and correlate them with audit, hardware, or cloud-provider records. On a systemd system, start with who -b, last -x, and journalctl -b -1 -e. These records can point to an orderly reboot or a failure, but a log that ends abruptly does not by itself prove whether the cause was a crash, lockup, reset, or power loss.
1. Establish when the reboot happened
Start by narrowing the time window. This helps you compare Linux records with monitoring alerts, administrator activity, and platform events. Neither command below identifies the cause on its own.
who -b
last -x | head -30
who -breports the system’s last boot time.last -xdisplays recorded reboot, shutdown, and runlevel transitions. Uselast rebootif you want to focus on reboot records.
Compare the times with your system logs, authentication and audit records, scheduled jobs, and any external monitoring. Check time zones and clock changes before treating entries from different systems as simultaneous.
2. Inspect the previous boot’s journal
On a system using systemd’s journal, these commands show the end of the preceding boot and its kernel messages:
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
journalctl -b -1 -e
journalctl -b -1 -k
-b -1selects the boot before the current one.-emoves to the end of the selected journal.-klimits output to kernel messages.
To see which boots are available, run:
journalctl --list-boots
Do not rely only on the final surviving message. Inspect a wider time window around the end of the previous boot and search for relevant errors earlier in the session. A service’s last log entry may be incidental; its position at the end of the journal does not establish that it caused the reboot.
If the previous boot is missing
A missing boot in the journal does not establish that no relevant event occurred. Check how journald storage is configured and what your distribution retains. Journald may store records persistently under /var/log/journal or temporarily under /run/log/journal. Volatile records under /run are lost at reboot, so persistent logging must be configured before an incident to retain earlier journal entries.
3. Decide whether shutdown was orderly or abrupt
Look for a coherent systemd shutdown or reboot sequence, then correlate its time with records that can identify a person or automation:
- Authentication and audit logs, if audit rules and retention were configured.
- User sessions and command records.
- Cron jobs,
atjobs, and systemd timers. - Administrative activity or external monitoring around the same time.
An orderly sequence combined with an audit or authentication record may support an intentional reboot explanation. Shell history can offer a lead, but it is not a reliable audit trail: it may be absent, incomplete, or editable.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
If the journal simply stops without a clean shutdown, that is consistent with a crash, lockup, reset, or power interruption. It does not distinguish among them. Look for corroborating evidence before assigning a cause.
4. Look for kernel crash evidence
If a kernel panic or hang is plausible, inspect any crash dump and the crash-capture tooling configured for your distribution. Dumps can preserve details that ordinary logs do not, but the mechanism must be configured and have suitable storage before the incident.
Red Hat’s guidance is specific to RHEL: it recommends reviewing kdump output when investigating unexplained reboots and warns that, without kdump installed and configured beforehand, it may not be possible to determine the cause. Kdump also does not capture every trigger; Red Hat gives power outages and intentional reboots as examples it will not capture. See Red Hat’s RHEL reboot guidance.
5. Check watchdog and platform hardware records
A watchdog reset, overheating condition, fan failure, or power issue may leave evidence outside the ordinary guest journal. Some watchdog drivers expose status or boot-status information, but support depends on the device and driver; not every device supports the relevant status calls. The Linux watchdog API documentation describes these limitations.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
For suspected hardware resets, check platform firmware records, a management controller’s event log, or a serial-console capture if available. A serial console can retain boot diagnostics when a machine cannot provide a normal shell or its stored logs are insufficient. systemd documents boot-debugging parameters and serial-console approaches. Confirm that the machine exposes a compatible serial console and verify the connector, electrical levels, and platform documentation before purchasing an adapter.
6. For a cloud VM, check provider records
Guest logs cannot explain every host-side or control-plane event. On Google Compute Engine, correlate the guest timeline with Cloud Audit Logs and system-event records. Google documents events including host errors, automatic restart, guest termination, maintenance-related termination, and preemption; those event names and steps are GCP-specific. For audit records, examine the method and principalEmail fields where present.
Google’s documented query below uses a one-hour freshness window. Replace VM_NAME and adjust the time window to cover the incident:
gcloud logging read --freshness=1h 'resource.type="gce_instance" "VM_NAME" logName:("logs/cloudaudit.googleapis.com%2Fsystem_event" OR "logs/cloudaudit.googleapis.com%2Factivity")'
Use the Google Compute Engine reboot investigation guidance for the provider-specific procedure. A provider-side record can explain an event that the guest operating system could not observe.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
7. Match the evidence to likely causes
| Possible explanation | Evidence to check | What the evidence can establish |
|---|---|---|
| Intentional command or automation | Shutdown sequence, authentication or audit records, scheduled tasks, timers | May connect an orderly reboot to a user or job if records were retained. |
| Kernel panic or hang | Kernel journal, configured crash dump, serial-console capture | May reveal kernel failure details; availability depends on prior logging and crash-capture configuration. |
| Watchdog, thermal, or power reset | Watchdog status, firmware or management-controller event log | May identify a reset condition when the hardware and driver expose relevant status. |
| Cloud platform or control-plane event | Provider audit and system-event logs correlated with guest timestamps | May show an operator/API action or platform event; event types and procedures vary by provider. |
| Cause not confirmable from retained records | Missing or volatile journal, no preconfigured crash capture, abrupt power loss | Insufficient evidence is a valid result; do not present a guess as a confirmed cause. |
8. Preserve evidence for the next incident
When the current records are incomplete, improve retention before another reboot occurs:
- Enable persistent journal storage so earlier boot records are retained across restarts.
- If kernel failure is plausible, configure your distribution’s crash-dump mechanism and verify that adequate storage is available.
- For cloud systems, retain provider audit and system-event logs and correlate them with guest monitoring.
- For difficult hardware resets, consider an available serial console or an external monitoring source.
These steps increase the chance of retaining useful evidence; none guarantees that every power or hardware event will be recorded.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
For a reboot investigation, keep using the Linux logs, audit records, hardware evidence, and provider records above. If your incident workflow also needs a clean capture of a web-based dashboard or status page, ScreenshotNeo takes a screenshot with one GET request. Its API accepts consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, with the outcome indicated in response headers. Its MCP server provides screenshot tools for AI agents, and the free plan includes 1,000 shots per month without a card.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
See the ScreenshotNeo API documentation for request options. Paid plans start at $5 for 3,000 shots. Sign up for 1,000 free screenshots a month with no card.
Troubleshooting the investigation
journalctl -b -1 shows no entries
Check journalctl --list-boots and journald storage configuration. Earlier records may have been volatile and lost during the reboot. If persistent storage was not enabled beforehand, the missing journal may not be recoverable; configure retention for future incidents.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
The journal ends suddenly with no error
Do not treat the final message as a diagnosis. A crash, lockup, reset, or power interruption can all leave an incomplete journal. Correlate the time with crash dumps, watchdog and hardware records, cloud events, and external monitoring.
last does not show a useful reboot or shutdown record
Use the journal and any retained authentication, audit, and provider records as additional sources. A record that is absent cannot establish that a particular action did or did not occur.
No crash dump is available
Crash capture may not have been configured before the event, or the failure may not be one it records. Configure and verify the distribution’s crash-dump setup ahead of another incident; for an RHEL system, consult the RHEL-specific kdump guidance linked above.
The guest logs do not explain a cloud VM restart
Check the provider’s audit and system-event logs for the same time window. The guest cannot necessarily record host or control-plane actions; use the steps and event types documented for your specific cloud provider.
Frequently asked questions
Can Linux logs always tell me why the machine rebooted?
No. The answer depends on what the system retained before the reboot. A sudden power loss or reset can prevent a final explanation from being written, so related hardware or provider records may be needed.
Does an abrupt journal ending prove a power failure?
No. It is consistent with several failure modes and does not distinguish among them without corroborating evidence.
Can I recover a previous boot’s volatile journal after it was lost?
Not from journald’s volatile records once they have been lost at reboot. Persistent storage needs to be enabled in advance.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
