About this tag
Disk size discrepancy issues in Windows Server environments often arise when a secondary drive reports an incorrect capacity, such as a 1TB SSD showing as 1.62TB. This can occur after reconnecting a drive used in a previous installation, possibly due to leftover partition metadata or driver conflicts. Users may find the drive unusable for expanding backup pools. Troubleshooting steps include checking Disk Management for partition anomalies, cleaning the drive with diskpart, or verifying firmware and controller settings. The tag covers real-world cases where reported disk size does not match physical capacity, impacting storage allocation and backup functionality.
-
S
Windows Server Essentials 2016 problem adding second drive for client backups
I've been successfully using WSE2016 since 2023 only for personal use to back up several PCs. A couple of months ago it failed, possibly the result of multiple power outages here in Florida. After trying to recover I gave up and did a new install using the same two 1TM SSDs as before...- samsquared2
- Thread
- backup backup pool data recovery disk health disk management disk size discrepancy drive not recognised formatting partition power outage secondary drive solid state drive storage usb windows server essentials 2016
- Replies: 9
- Forum: Windows Server Forums