4Kn Hard Drives: OS, Hypervisor and RAID Support Checklist

4Kn hard drives need support at every layer: operating system, hypervisor, RAID controller and UEFI boot. A checklist of the maker rules, and what fails when one layer does not.

Topics: 4Kn, Advanced Format, Sector Size, UEFI, VMware, RAID

What a 4Kn drive needs, in one paragraph

A 4Kn (4K native) hard drive uses 4,096-byte sectors both on the platter and at its interface, with no emulation. Everything between the drive and the application has to accept 4,096-byte logical sectors: the operating system or hypervisor, the RAID controller or HBA, and, if you boot from the drive, UEFI firmware. Legacy BIOS boot does not work. When every layer supports it, a 4Kn drive behaves like any other disk. When one layer does not, the makers simply do not support that combination: controllers will not mix 4Kn with 512-byte drives in one array, and legacy BIOS cannot boot from it.

This is part of our series on drive formats. If you are still deciding between formats, start with the 512e vs 4Kn vs 512n overview.

Why 4Kn exists

A 512e drive already stores 4K physical sectors; it only pretends to be 512-byte at the interface. 4Kn drops that pretence. The drive no longer needs to translate, so a small or misaligned write can no longer trigger the read-modify-write cycle that Dell and Seagate describe for emulated drives. The cost moves upstream: every piece of software that talks to the disk must understand 4,096-byte logical blocks.

The checklist

Work down this list before ordering a 4Kn drive. Each item is a layer that can say no.

1. Operating system

Windows. Microsoft's support policy lists 4Kn support for "All Windows versions from Windows 8 and later versions. All Server versions from Server 2012 and later versions." From those releases Windows can also "install … to and boot from a 4K sector disk without emulation". Windows 7, Server 2008 R2 and earlier can support 512e (the oldest only with updates) but not 4Kn. Dell's engineering paper notes that Windows Server 2003 and 2003 R2 support neither.

Linux. Dell's table lists 4Kn support in RHEL 6.1, SLES 11 SP2 and Ubuntu 12.04.4. Its footnotes are the important part: Red Hat Enterprise Linux 6 supports 4K-sector devices as data disks, with 4K boot disks supported in UEFI mode only, and SUSE does not support a 4KB-sector drive as the boot drive on x86_64 systems booting with a legacy BIOS. For anything newer, check your distribution's own release notes.

Applications. Software that does its own disk I/O can care about sector size too. Dell's paper flagged Microsoft Exchange as untested on 4Kn at the time, and noted that Exchange advises against different sector sizes within one database availability group. If an application vendor publishes a sector-size statement, read it before moving its data.

2. Hypervisor

VMware vSphere. Broadcom's support statement says vSphere 6.7 and vSAN 6.7 and later support 4K native hard disk drives, that a VMFS 6 datastore is required, and that RDMs are not supported on 4Kn HDDs. The vSphere 8 storage documentation adds detail:

  • ESXi "supports only local 4Kn SAS and SATA HDDs", and does not support 4Kn SSD and NVMe devices, or 4Kn devices as RDMs.
  • ESXi emulates a 4Kn drive as 512e internally, and "the guest operating systems always see it as a 512n device." Guests therefore do not need 4Kn support of their own.
  • With vSAN, 4Kn drives can be used only as capacity HDDs in hybrid arrays.

Check the documentation for your exact vSphere release, because these rules have changed between versions. The controller must also be on the VMware Compatibility Guide.

3. RAID controller or HBA

The controller has to recognise a 4,096-byte logical sector, and it will not put 4Kn and 512-byte drives in the same array. Dell's PERC documentation states the rule for the PERC S130: mixing 512-byte native and 512-byte emulated drives in a virtual disk is allowed, "but mixing 512–byte and 4 KB native drives in a virtual disk is not allowed". The same guide asks you to configure 4Kn drives "only" with the controller's UEFI configuration utility during pre-boot.

So a 4Kn drive cannot replace a failed member of an array built from 512n or 512e drives, even if capacity, speed and interface all match. It belongs in a new array of 4Kn drives. For controllers by family, see enterprise RAID controllers, Dell PERC and HP Smart Array. Then confirm 4Kn support in the user guide for your exact model.

4. Boot mode

Booting from a 4Kn drive needs UEFI. VMware states that "ESXi can boot only from a 4Kn device with UEFI". Dell's Windows table lists 4K disks as boot disks "in UEFI mode". The RHEL and SUSE notes above say the same for Linux. If a server must stay in legacy BIOS mode, keep its boot volume on 512n or 512e and use 4Kn only for data.

5. File systems and pools

For ZFS, the OpenZFS documentation warns that "there can be sector alignment problems on ZFS when a drive misreports its sector size", and that this "can be manually corrected at vdev creation" (the ashift setting). Set it when you create the pool.

What happens when one layer says no

Layer without 4Kn supportWhat the makers say
Operating systemNot supported (for Windows, anything before Windows 8 / Server 2012). Dell warns that software which does not align I/O to the physical sector size "can result in unexpected failed I/Os".
HypervisorNot supported for that use; for example, ESXi 8 supports no 4Kn SSD or NVMe devices and no 4Kn RDMs
RAID controllerCannot join a virtual disk of 512n or 512e drives (Dell PERC S130 rule)
Boot firmware in legacy BIOS modeCannot boot from the drive; UEFI is required (VMware, Dell, RHEL and SUSE notes)

If any row applies to your system, use a 512e drive instead. It stores 4K physically but presents 512-byte sectors to everything above it.

Checking a drive's format

Drives that list both 512e and 4Kn. Some Seagate Exos models are sold as a single part that supports both formats. Seagate ships them configured as 512e by default and documents a FastFormat feature that converts the logical sector size between emulated 512-byte and 4K. Seagate also notes FastFormat cannot be used with 512-byte native drives. The steps are in the product manual for each model.

Related guides

  • 512e hard drives: the emulated format that works where 4Kn does not.
  • 512n drives: what older servers need, and what to check before replacing one.
  • CMR vs SMR: the recording method, which matters as much as sector format in a RAID or ZFS array.

Planning a new 4Kn array or not sure your controller supports it? Email sales@prodisknetwork.com with the server and controller model, and we will check the documentation with you before you order.

Parts referenced in this guide

Every part below is named in the article above.

Part of

Enterprise Storage Hub

View all 178 pages →

Enterprise HDDs, SSDs, NVMe, SAS, SATA, RAID controllers, drive caddies and storage array hardware.