Windows Server 2025 / How to Add a Data Disk and Choose NTFS or ReFS
Adding a server data disk requires identifying it, initializing it, creating a volume, and choosing a file system. Begin this general file-sharing lab with NTFS; choose Resilient File System (ReFS) only after checking workload and management support.
Separate the storage concepts
| Concept | Meaning |
|---|---|
| Disk | Physical device or a VM’s virtual disk |
| Partition | A division of disk space |
| Volume | Usable storage exposed through a letter or mount path |
| File system | The structure managing files, folders, and metadata |
Increasing a virtual disk and extending its guest volume are separate steps. A dynamically expanding VHDX does not provide unlimited host space. Monitor host capacity independently from what the guest sees.
Identify the new empty disk safely
Shut down FS1 and add a new 40 GB virtual data disk through the hypervisor. This is a lab size, not a production recommendation. Do not reuse the OS, backup, or another VM’s disk file.
- Boot FS1 and open elevated Disk Management, diskmgmt.msc.
- Check the new disk’s number, capacity, and online state.
- Compare OS queries with the hypervisor attachment, excluding boot, system, and existing data disks.
- Cancel initialization if partitions or capacity are unexpected.
Get-Disk | Select-Object Number,FriendlyName,SerialNumber,PartitionStyle,Size,IsBoot,IsSystem Get-Volume | Select-Object DriveLetter,FileSystemLabel,FileSystem,Size,SizeRemaining
Disk 1 is not guaranteed to be the new disk. Initialization and formatting can destroy data when the wrong device is selected; avoid a hardcoded disk-number batch command.
Create a GPT and NTFS data volume
Follow new-disk initialization guidance only for an identified disk with no data.
- Initialize only the confirmed new disk using GUID Partition Table (GPT), if necessary.
- Start New Simple Volume on its unallocated space.
- Choose capacity and an unused letter; subsequent course examples use D:.
- Select NTFS, the appropriate default allocation unit, and label LabData; verify the empty target before formatting.
- Check letter, label, capacity, and file system in Explorer and Get-Volume.
If D: belongs to a DVD drive or another volume, assess that device before adjusting anything, or choose another unused letter and consistently substitute it in later paths. Do not change a production application’s drive letter for this lab. Formatting is not a method of preserving data while extending a volume.
Compare NTFS and ReFS by required capabilities
Review the NTFS overview and ReFS feature comparison for the current OS. Newer does not mean preferable for every data volume.
| Requirement | Review |
|---|---|
| General file-server compatibility | Application, backup, and administration tool support |
| FSRM lab | Use NTFS for the course’s quotas and file screening |
| VM storage or integrity features | Check support for the exact ReFS capability and deployment |
| Boot or volume resizing operations | Compare current supported operations |
Resilience does not replace backup against deletion, mistaken permissions, or ransomware. Avoid applying an old version’s comparison uncritically to Server 2025.
Verify and document recovery boundaries
Create LabCheck and a test text file on the data volume, then read it back. Record letter, label, file system, and the attached VHDX path. A successful administrator write does not verify ordinary user permissions.
Before undoing the attachment, inspect shares, backups, and apps using the volume. Detaching a virtual disk differs from deleting its backing file. Once useful files exist, neither formatting nor deletion is a casual cleanup step.
