512e Hard Drives: What 512e Means and Where It Works
512e drives store 4K physical sectors but present 512-byte logical sectors. What that emulation costs, where 512e is supported, and mixing 512e with 512n in one array.
What 512e means, in one paragraph
A 512e drive stores data in 4,096-byte physical sectors but tells the host its sectors are 512 bytes. The "e" stands for emulation: the drive's firmware translates between the two. That makes it work with software and controllers that only understand 512-byte sectors, at the cost of extra work inside the drive whenever a write is smaller than 4K or does not line up with a 4K boundary. Many current enterprise drives ship as 512e; Seagate, for example, ships its dual-format Exos models set to 512e by default.
This page is one of a series on drive formats. The 512e vs 4Kn vs 512n overview compares all three side by side; this guide goes deeper on 512e alone.
Logical and physical sectors
Every drive reports two sizes:
| Format | Logical sector (what the host addresses) | Physical sector (what the platter stores) |
|---|---|---|
| 512n | 512 bytes | 512 bytes |
| 512e | 512 bytes | 4,096 bytes |
| 4Kn | 4,096 bytes | 4,096 bytes |
Microsoft's support policy uses exactly this split. The logical size is the unit the operating system uses to address the disk. The physical size is the unit the drive actually reads and writes in one operation. A 512e drive is the only one of the three where they differ, and that difference is the whole story.
Why make that trade at all? Moving to 4K physical sectors lets the drive spend proportionally less space on the gaps and sync marks between sectors and more on error correction. Dell's engineering white paper on the transition puts the result at a format efficiency of about 97 percent, "almost a 10 percent improvement" over 512-byte sectors. Emulation lets drive makers take that gain without breaking hosts that still assume 512 bytes.
Reads cost nothing extra; small writes do
Reading from a 512e drive costs nothing extra. The drive reads the whole 4K sector into its cache and hands back the 512-byte piece that was asked for. Dell's paper notes this happens in the drive's DRAM and "does not measurably impact performance."
Writing is different. If the host writes less than a full 4K sector, the drive cannot write just part of it. It must read the whole physical sector, merge in the new 512 bytes, and write the full 4K back. That is a read-modify-write cycle, and both Dell and Seagate describe it as the main performance cost of emulation. Dell lists three causes:
- writes that are misaligned because the partition does not start on a 4K boundary;
- writes smaller than 4K;
- writes that are not a multiple of 4K.
The first cause is the one that bites in practice, and it is decided once, when the partition is created.
Alignment: the setting that decides performance
A partition that starts on a 4K boundary lines each 4K block of the file system up with one physical sector. Ordinary writes then map cleanly onto whole sectors and the drive never has to read before it writes. A partition that starts at an odd 512-byte offset shifts every block across two physical sectors, so almost every write becomes a read-modify-write.
Older Windows is the classic trap. Microsoft notes that on systems built before Windows Vista SP1, including all versions of Windows XP, "the default partitions will be unaligned", and that all I/O to such a volume "will by nature be unaligned". Dell's advice is simply to create partitions with a 4K-aware operating system, which avoids the problem. Its paper lists Linux kernel support for Advanced Format drives from version 2.6.31, with GNU Parted 2.1 and later handling alignment.
If you move an old disk image onto a 512e drive, check the partition start offset first. A sector-by-sector clone carries the old misalignment with it.
Where 512e works
Windows. Microsoft supports 512e on all Windows versions from Windows 7 SP1 and Windows Server 2008 R2 SP1. Earlier Windows 7, Vista and Server 2008 releases need specific updates (KB 982018 or KB 2553708). Hyper-V is excepted on those older rows. Dell's paper adds that Windows Server 2003 and 2003 R2 do not support 512e or 4Kn media.
VMware. Broadcom's support statement says vSphere and vSAN support 512e drives as direct-attached disks from version 6.5, and that earlier versions do not. VMFS 6 is required for 512e from 6.5 onward; the vSphere 8 documentation adds that local 512e devices do not support VMFS 5. The RAID controller must also be on the VMware Compatibility Guide.
Linux. Dell's table lists 512e support from RHEL 6.1, SLES 11 SP2 and Ubuntu 12.04.4.
Hardware RAID. A 512e drive reports 512-byte logical sectors, so controllers such as Dell's PERC S130 group it with 512n drives (see the next section).
Mixing 512e and 512n in one array
This is the most common real-world question, usually asked when a failed 512n drive is no longer made and the replacement on offer is 512e.
Controllers group drives by logical sector size, and 512n and 512e share the same logical size (512 bytes). Dell's PERC documentation states it plainly 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."
So a 512e drive can normally replace a 512n member of the same capacity and interface. Two cautions:
- Check your own controller's documentation. The rule above is Dell's wording for the S130; the manual for your controller model is the authority.
- Small writes cost the 512e member more. It does read-modify-write on sub-4K writes that the 512n members do not. Dell notes that with aligned partitions, larger writes map onto whole 4K sectors without that penalty.
What you cannot do is mix either of them with a 4Kn drive in the same virtual disk. A 4Kn drive reports a 4,096-byte logical sector, and that is a different group. See 4Kn hard drives for what has to support it.
How to check whether a drive is 512e
- Windows: run
fsutil fsinfo sectorinfo C:(replace C: with the volume). LogicalBytesPerSector of 512 with a physical value of 4096 means 512e. - Linux:
lsblk -tshows PHY-SEC and LOG-SEC columns. The same values are in/sys/block/<disk>/queue/physical_block_sizeandlogical_block_size. - Before you buy: many enterprise listings print the format in the product name. On our site, for example, the Toshiba MG07ACA14TE 14 TB and the Dell 223X4 8 TB SAS both state 512e in their names. Some Seagate Exos listings name both 512e and 4Kn. Seagate builds those to ship as 512e and lets the host switch them to 4Kn with its FastFormat feature (see the 4Kn guide).
Where to go next
- Replacing a member of an older array that still runs 512n? Read 512n drives.
- Building a NAS or ZFS pool? Sector format is only half of it. Check the recording method in CMR vs SMR.
- Shopping by platform: Dell PowerEdge SAS drives, HP ProLiant SAS drives, or all SAS and SATA hard drives.
If you are matching a drive to an existing array, email sales@prodisknetwork.com with the controller model and the part number of a current member. We will check the format before you order.