How to Add Storage to a Server: Bays, Controller and Matching
Adding storage to a server sounds simple and stops for reasons people do not anticipate. This covers what to check before ordering, in the order that saves the most time.
First: are there free bays, and what kind?
Look at the front of the machine and count.
Bay count and size are fixed by the backplane and cannot be changed by adding drives. A 2U server with eight 3.5 inch bays has eight; it does not become sixteen. Some chassis support a rear bay kit or a second backplane, but those are specific parts for specific models.
Empty bays need carriers, generation-matched to the chassis, and blanks removed. Our caddies guide covers this, and it is the most common omission in a storage order.
If there are no free bays, the options are larger drives in existing bays, or external storage. Both are covered below.
Second: what will the controller accept?
Four checks.
Interface. SAS, SATA or NVMe, set by what the controller and backplane support. A SAS controller usually takes SATA drives; a SATA controller never takes SAS. Our interface guide covers the rules.
Capacity limit. Older controllers cannot address large drives, and the failure is either refusal or seeing only part of the capacity. Check the specification for your exact model and firmware. Our controller guide covers identification.
NVMe support is per-bay, not per-chassis. A bay that physically accepts an NVMe drive may have no PCIe lanes routed to it.
Firmware coding. Behind a vendor RAID controller, a non-coded drive may be flagged or refused during rebuild. Our OEM guide covers when it matters.
Third: match what is already there
If the new drives are joining an existing array, four things must match.
Capacity. An array uses the smallest member’s capacity on every drive, so a larger drive is wasted and a smaller one will be refused.
Speed class. An array runs at its slowest member. Our drive tier guide covers this.
Sector format. Mixing 512n, 512e and 4Kn in one group is refused or unpredictable, and it frequently surfaces during a rebuild. Our sector format guide covers this.
Recording technology. Never add an SMR drive to an array. Our SMR vs CMR guide covers why.
A new separate array has none of these constraints, only the controller’s.
Expanding vs adding a new array
Two different operations with different risks.
Expanding an existing array restripes data across the new drives. It works on most controllers, takes a long time, and the array is vulnerable throughout. Back up first — this is not optional. Our backup guide covers the principle.
Creating a new array from the new drives is faster, safer and leaves the existing data untouched. Where the use case allows a separate volume, this is usually the better choice.
If there are no free bays
Three options.
Replace with larger drives, one at a time. On most controllers, replacing each member with a larger drive and letting it rebuild, then expanding once all are replaced, works. It is slow, and each rebuild is a risk window, but it needs no new hardware.
Add an external enclosure. A JBOD on an external SAS HBA adds bays without touching the server. Our JBOD guide covers what that needs.
Move to shared storage, if more than one server needs the capacity. Our storage architecture guide covers the categories.
What to order alongside the drives
Four things people forget.
Carriers for every new drive, generation-matched.
Blanks for any bays still empty afterwards, for airflow.
A controller with enough ports, if the existing one is fully used.
Backplane cables, if enabling bays that were never cabled. Our cables guide covers the connector types.
Frequently asked questions
Can I add more drive bays to my server?
Not by adding drives. Bay count and size are fixed by the backplane. Some chassis support a rear bay kit or second backplane, but those are specific parts for specific models. Otherwise use larger drives or external storage.
Do I need carriers for the new drives?
Yes, for hot-swap bays, and they must be generation-matched to the chassis. Empty bays rarely come with them. This is the most common omission in a storage order.
Can I add a larger drive to an existing array?
It will work but the extra capacity is wasted, because an array uses the smallest member’s capacity on every drive. A smaller drive will be refused.
Should I expand my array or create a new one?
A new array is faster and safer and leaves existing data untouched. Expanding restripes data across the new drives, takes a long time and leaves the array vulnerable throughout, so back up first.
Will my controller support the drive capacity I want?
Not necessarily. Older controllers have capacity limits and will either refuse the drive or see only part of it. Check the specification for your exact model and firmware before ordering.
How do I add storage with no free bays?
Replace members with larger drives one at a time and expand once all are replaced, add an external JBOD on a SAS HBA, or move to shared storage if more than one server needs the capacity.
Send us your server model and a photo of the front, and we will confirm bay count, carrier generation and controller limits before you order.
