Hardware Compatibility Lists: Why Supported Matters
Hardware compatibility lists are ignored until something behaves strangely, at which point they become the first thing anyone asks about. They exist because "it installed" and "it is supported" are different statements.
What a compatibility list is
Operating system and hypervisor vendors publish lists of hardware they have tested and will support — servers, storage controllers, network adapters, and sometimes specific firmware versions.
Being on the list means the combination has been validated and problems will be investigated. Being off it does not mean it will not work; a great deal of unlisted hardware works perfectly well.
What it means is that if something goes wrong, you are on your own — and with storage and network drivers, "something goes wrong" can mean data corruption rather than an error message.
The list matters most for the components in the data path. A quirky USB controller is an annoyance; an unsupported storage controller driver is a different category of risk.
Firmware is part of the specification
The part most often missed.
Compatibility lists frequently specify firmware versions, not just hardware models, and the combination is what was tested. Running supported hardware on unlisted firmware is a partially untested configuration.
This matters in both directions. Firmware too old may lack fixes the driver expects. Firmware too new may have changed behaviour the driver has not caught up with — which is why blindly updating firmware on a working system is not always the safe choice people assume.
The practical rule: check the list before updating firmware, not only before buying hardware. On a virtualisation host in particular, storage controller firmware and driver versions are a matched pair.
Where problems actually appear
Three components account for most compatibility trouble.
Storage controllers. The highest-risk category. An unsupported controller may work in normal operation and behave unpredictably under load, during a rebuild, or when a drive fails — which is precisely when you need it to be correct. Our controller guide covers the RAID and HBA distinction, and note that software storage layers need direct drive access rather than an array.
Network adapters. Usually fail more visibly — poor throughput, dropped packets, features that do not work. Offload features in particular are a common source of subtle problems.
Drives. A separate compatibility question from the operating system, and one that sits at the controller rather than the OS. Enterprise controllers validate drive firmware, and a drive without vendor coding may be flagged unsupported or refused during a rebuild. Our compatibility guide lists this by platform.
Older hardware and newer operating systems
The situation that catches organisations running end-of-life platforms.
Operating system vendors drop support for older hardware over time. A server that runs its current OS perfectly may not be on the list for the next version, and that frequently forces hardware replacement before the hardware has failed.
Two things follow.
Check the compatibility list for the OS version you intend to run, not the one currently installed. This is easy to skip and is exactly where upgrade projects stall.
OS support frequently ends before the hardware does. Like mobile device fleets, the binding constraint is software support rather than physical condition. Plan around that rather than around hardware failure.
Buying refurbished with this in mind
Compatibility lists are a strong argument for a particular purchasing approach.
If a platform is on the list for the operating system you run, buying more of that platform — including refurbished — keeps you in a validated configuration. Introducing a different model means checking compatibility again for every component.
That is the same standardisation argument that applies to switches and POS hardware: matching what you already run is frequently worth more than being current.
When buying refurbished, two checks. Confirm the model and its controllers appear on the list for your OS version. And ask what firmware level the hardware is at, since that is part of the tested combination.
Practical approach
Before buying, check the compatibility list for the OS or hypervisor version you will run, paying particular attention to storage controllers and network adapters.
Before updating firmware, check the list again rather than assuming newer is safer.
Before an OS upgrade, check the existing hardware appears on the list for the target version — this is where upgrade projects most often discover a hardware dependency.
And record the firmware and driver versions you are running, so that when something behaves oddly you can establish whether you are in a tested configuration or not.
Send us the server model and the operating system you run, and we will confirm what we can before you order.
Common questions
Does unlisted hardware not work?
Frequently it works fine. Being off the list means the combination was not validated and problems will not be investigated — and with storage drivers, problems can mean data corruption rather than an error message.
Should I always update firmware to the latest version?
Not blindly. Compatibility lists specify firmware versions as part of the tested combination, and firmware newer than the driver expects can change behaviour. Check the list before updating, particularly for storage controllers on virtualisation hosts.
Which components cause the most compatibility trouble?
Storage controllers, by a distance. An unsupported controller may behave normally until load, a rebuild or a drive failure — exactly when correctness matters. Network adapters fail more visibly, usually as throughput or offload feature problems.
Why did my OS upgrade project stall on hardware?
Because compatibility lists were checked for the installed version rather than the target one. Vendors drop support for older hardware over time, so a server running its current OS perfectly may not be listed for the next.
How does this affect buying refurbished?
It argues for standardisation. If your platform is on the list for your OS, buying more of the same platform keeps you in a validated configuration, where a different model means rechecking every component.
Send us the server model and the operating system you run and we will confirm what we can before you order.
