Drives and RAID controllers for servers in Tashkent: price per terabyte, selection and ready-made sets
Updated
In brief. A terabyte of capacity on server drives in Tashkent costs from 294,000 UZS per terabyte on 22 TB SATA and 392,000 UZS on 22 TB SAS up to 2,246,000 UZS on NVMe (Servix catalog, November 2026). For databases and virtual machines, SSD and NVMe are used; for files and backups, high-capacity SAS. The controller is chosen to match the drive type: RAID 5 and 6 need a battery-backed cache, and NVMe needs a tri-mode controller such as MR416i-p or PERC H755. A ready-made set for a file server with 16 TB usable — 20,127,055 UZS.
Request drive and controller selection → — send us the server model and serial number, and we will check the drive cage, controller and drive trays and calculate a set for the task.
Quick links: price per terabyte · which drive for which task · RAID controllers · boot modules · ready-made sets · drive trays and compatibility
Price per terabyte: the main table
The cost per terabyte is the only fair way to compare drives of different capacities. The spread between spinning disks and flash here is sevenfold, and it is exactly what determines which data is stored where.
Drive | Type and capacity | Price | Per terabyte |
|---|---|---|---|
SATA 7.2k, 22 TB | 6,469,411 UZS | 294,000 UZS | |
SAS 7.2k, 16 TB | 5,031,764 UZS | 314,000 UZS | |
SAS 7.2k, 22 TB | 8,625,882 UZS | 392,000 UZS | |
SAS 7.2k, 8 TB | 3,234,705 UZS | 404,000 UZS | |
SAS 7.2k, 10 TB | 4,312,941 UZS | 431,000 UZS | |
SAS 7.2k, 6 TB | 2,875,294 UZS | 479,000 UZS | |
SSD SATA, 7.68 TB | 10,782,352 UZS | 1,404,000 UZS | |
SSD NVMe, 1.92 TB | 4,312,941 UZS | 2,246,000 UZS |
Two practical conclusions follow from the table. First: for spinning disks the price per terabyte barely depends on drive capacity — 8 and 22 TB come out close, so for archives the largest drives are used, saving bays. Second: the SATA version of the same drive is roughly a quarter cheaper than SAS, and paying extra for SAS is justified only where dual-port access is needed — that is, in fault-tolerant configurations and in storage systems.
Which drive for which task
- Databases, 1C, virtual machines. Flash only: Micron 7400 Pro NVMe (4,312,941 UZS) or SATA SSD where the interface is sufficient. Spinning disks lose by an order of magnitude on random writes, and no controller cache can compensate for that.
- File server and video surveillance. SAS 7.2k at 8–22 TB. The workload is sequential; what matters is the total terabytes: HC320 8 TB, HC550 16 TB, HC570 22 TB.
- Backup repository. The same high-capacity SAS drives, but always with RAID 6 and a hot spare: a 16–22 TB drive takes more than a day to rebuild, and a second failure within that window is likely.
- Warm data and file cache. 7.68 TB SATA SSD (10,782,352 UZS) — a compromise between the price of spinning disks and the speed of flash.
A separate note on NAS drives: WD Red Plus 10 TB (price on request) and WD Red Plus 4 TB (1,868,941 UZS) are designed for home and office storage with a workload of about 180 TB written per year. For a server under constant load, the Ultrastar line is used — it is designed for round-the-clock operation and many times higher annual writes.
RAID controllers: cache, battery and tri-mode
The controller determines which drives the server will see and how fast it will write. Three boundaries matter when choosing.
Controller | Cache and battery | Drives and modes | Price |
|---|---|---|---|
no | SAS, SATA; RAID 1 and 10 or HBA | 4,312,941 UZS | |
no | SAS, SATA; RAID 1 and 10 or HBA | 5,750,588 UZS | |
yes | SAS, SATA, all RAID levels | 5,750,588 UZS | |
yes | SAS 12G, SATA, all levels | 7,188,235 UZS | |
yes | 16 internal lanes for dense drive cages | price on request | |
yes | external ports for a disk shelf | 7,188,235 UZS | |
yes | SAS 12G, SATA | 7,188,235 UZS | |
yes | SAS, SATA and NVMe — tri-mode | 8,625,882 UZS | |
yes | NVMe and SAS 12G — tri-mode | 9,344,705 UZS | |
yes | tri-mode for Gen10 Plus | 8,625,882 UZS |
- Cache and battery. Models without cache are suitable for RAID 1 and 10 or for HBA mode. RAID 5 and 6 need a battery-protected cache; otherwise write performance collapses, and cached data is lost on power failure.
- Tri-mode. Only controllers that support it work with NVMe U.2 and U.3. A classic SAS controller simply will not see an NVMe drive.
- Internal or external. The suffix i means ports facing inside the chassis, e — outside, for a disk shelf. If there are more bays than controller lanes, a SAS expander (7,188,235 UZS) is installed — cheaper than a second controller, but the bandwidth is shared among all drives behind it.
- HBA for software-defined storage. Ceph, vSAN, ZFS and Proxmox require direct access to drives: hardware RAID underneath them is unnecessary and harmful. For such setups, models without cache are used or the controller is switched to HBA mode.
Boot modules: don't waste bays on the system
Giving two drive cage bays to the hypervisor is wasteful. For booting, modules with a mirrored pair of M.2 drives are used: Dell BOSS with two 480 GB NVMe drives (7,907,058 UZS) and HPE NS204i-p with two 480 GB NVMe drives (10,063,529 UZS). The module builds the mirror itself, the operating system sees a single drive, and all cage bays remain available for data. For ESXi, Proxmox and Hyper-V this is the standard setup.
Ready-made sets with prices
- File server, 16 TB usable — 20,127,055 UZS. Four WD Ultrastar 8 TB SAS in RAID 10 and HPE Smart Array P408i-a. Fits any 2U server with an LFF drive cage.
- Virtualization, about 5.7 TB usable — 35,222,351 UZS. Six Micron 7400 Pro 1.92 TB NVMe in RAID 10 and the tri-mode MR416i-p. For thirty to forty virtual machines with medium load.
- Backup repository, about 96 TB usable — 47,442,347 UZS. Eight WD Ultrastar 16 TB SAS in RAID 6 and P408i-a. Plus a hot spare if the bays allow.
The amounts are for the drive part; the server itself is priced separately — ready-made configurations are in the selections HPE ProLiant Gen11 and Dell PowerEdge. If data must be available to several servers at once, drives in the server do not solve the task — see HPE MSA storage and Dell PowerVault ME5.
Drive trays, drive cage and compatibility
- Drive trays. A drive is installed in a vendor drive tray; HPE and Dell each have their own, and they differ between generations. Without one, the drive is not secured in the bay and does not connect to the backplane — it is a separate line item in the order that is easy to forget.
- Drive cage. The cage type (LFF or SFF, SAS/SATA or NVMe) is chosen when ordering the chassis and can only be changed together with the backplane and cable kit. Converting a SAS configuration to NVMe after the fact costs more than planning for it from the start.
- Monitoring. Vendor drive firmware gives iLO and iDRAC the full picture: error counters, failure prediction, automatic support case creation. With a third-party drive this data is incomplete, and the configuration is considered modified.
- RAID level. RAID 5 is not used on drives of 8 TB and up: the rebuild takes more than a day. RAID levels are covered in the guide RAID 5, 6 or 10, and an engineering review of drives is in the article drives for a server.
The whole section — drives and RAID controllers. Selection for your server model is free: write to us.
Sources
- HPE Smart Array SR Controllers QuickSpecs — HPE
- Dell PowerEdge RAID Controller 11 User’s Guide (PERC H755, H750, H355, H350) — Dell
Other Servix collections
- Server configurations and prices
- Server for 1C: configurations and prices
- How to choose a Dell PowerEdge
- HPE ProLiant Gen11: configurations and prices
- FortiGate by number of employees
- Dell PowerVault ME5 storage systems
- HPE MSA 2060 and 2062 storage systems
- Aruba Instant On for the office
- Network adapters, transceivers and DAC
- Xeon and EPYC server processors
- Server for video surveillance
- Dell PowerVault reference guide
- RAID controller reference guide
- HPE MSA reference guide
- Server for virtualization
- File server and backup