<html><head><style>pre,code,address {
margin: 0px;
}
h1,h2,h3,h4,h5,h6 {
margin-top: 0.2em;
margin-bottom: 0.2em;
}
ol,ul {
margin-top: 0em;
margin-bottom: 0em;
}
blockquote {
margin-top: 0em;
margin-bottom: 0em;
}
</style></head><body><div>Hi,<br>You should also check dmesg --ctime to see it there may be some more information than the journalog. </div><div><br></div><div>I suspect however this time is spend in bios doing something and you would need a monitor to actually see this is it doing. </div><div><br></div><div>Good luck</div><div><br></div><div>On Mon, 2025-10-06 at 13:29 -0400, Khalid Baheyeldin wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="ltr"><div><div style="font-size:small" class="gmail_default">I am setting up a new Dell server for a client, so we can move the site to it.</div><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default">But I am bothered by the time it takes from shutdown to boot.</div><div style="font-size:small" class="gmail_default">It will not be a frequent event, but when it is happening, the site is down.</div><div style="font-size:small" class="gmail_default">So minimizing it is important ... </div><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default">Here is the logs from journalctl:</div><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default">Oct 06 16:27:48 foo systemd[1]: Reached target shutdown.target - System Shutdown.<br>Oct 06 16:27:48 foo systemd[1]: Reached target final.target - Late Shutdown Services.<br>Oct 06 16:27:48 foo systemd[1]: systemd-reboot.service: Deactivated successfully.<br>Oct 06 16:27:48 foo systemd[1]: Finished systemd-reboot.service - System Reboot.<br>Oct 06 16:27:48 foo systemd[1]: Reached target reboot.target - System Reboot.<br>Oct 06 16:27:48 foo systemd[1]: Shutting down.<br>Oct 06 16:27:48 foo systemd-shutdown[1]: Syncing filesystems and block devices.<br>Oct 06 16:27:48 foo systemd-shutdown[1]: Sending SIGTERM to remaining processes...<br>Oct 06 16:27:48 foo systemd-journald[1694]: Journal stopped<br><br>-- Boot 67974696049a495c86f01b56d2a150dd --<br><br>Oct 06 16:32:09 foo kernel: Linux version 6.8.0-85-generic (...) (x86_64-linux-gnu-gcc-13 ...<br>Oct 06 16:32:09 foo kernel: Command line: BOOT_IMAGE=/vmlinuz-6.8.0-85-generic root=UUID=foo ro<br>Oct 06 16:32:09 foo kernel: KERNEL supported cpus:<br>Oct 06 16:32:09 foo kernel: Intel GenuineIntel<br>Oct 06 16:32:09 foo kernel: AMD AuthenticAMD<br>...<br>Oct 06 16:32:09 foo kernel: BIOS-provided physical RAM map:</div><br clear="all"></div><div style="font-size:small" class="gmail_default">You can see it takes a full 4 minutes and 20 seconds to do ... nothing?</div><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default">Any ideas why it takes that long, or where to look?</div><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">Khalid M. Baheyeldin</div></div><div>_______________________________________________<br></div><div>kwlug-disc mailing list<br></div><div>To unsubscribe, send an email to <a href="mailto:kwlug-disc-leave@kwlug.org">kwlug-disc-leave@kwlug.org</a><br></div><div>with the subject "unsubscribe", or email<br></div><div><a href="mailto:kwlug-disc-owner@kwlug.org">kwlug-disc-owner@kwlug.org</a> to contact a human being.<br></div></blockquote><div><br></div><div><span></span></div></body></html>