| * It takes a long time to boot past the firmware; generally 3-4 minutes to warm boot and 6-8 cold.
^^ why is that? is it just the firmware being buggy, or is there any legit reasons why they need to self-check _for minutes_?
^^ why is that? is it just the firmware being buggy, or is there any legit reasons why they need to self-check _for minutes_?
Beyond that, lots of servers will then enumerate all of the network interfaces and try to initiate a net boot, and only then fall back to the hard drive. Some tweaking in the bios can usually disable these features and gain a bunch of time, but again in a headless remote context this default behavior is incredibly useful for recovery purposes. We like to avoid actually running out with a physical crash cart if we can help it :)