I acquired several SATA SSDs labeled as 240GB, but Windows Disk Management shows only about 120GB available on each one. Updating the firmware did not change anything. The drives came from discarded Cisco server equipment, so I wondered whether they had been configured for RAID, mirroring, or some kind of enterprise capacity limit.
The main drive I am investigating is a Micron 5300 with model number MTFDDAV240TDS. Its label and model searches identify it as a 240GB drive, but CrystalDiskInfo reports a total capacity of only 128.0GB and 250,000,000 sectors. I also have drives identified as SSDSCKKB240G8. Is there a safe way to remove a hidden capacity limit or old server configuration and restore the full capacity?
3 Answers
For the Intel-branded SSDSCKKB240G8 drives, Intel's Memory and Storage Tool may provide enterprise erase or configuration options, depending on the exact model and firmware. It is not applicable to the Micron drive, though. Before using it, back up anything important and confirm the exact model and serial number.
A secure erase is still worth considering for discarded server drives, but treat it as a data-wiping step rather than a guaranteed capacity fix. If the drive continues to report only 120–128GB after erase and the native maximum LBA is reduced, there may be no supported way to recover the missing capacity.
The CrystalDiskInfo output is showing the drive's actual reported capacity, not merely a missing Windows partition. The Micron drive is currently exposing 250,000,000 sectors, which is roughly 128GB. That points to a reduced ATA capacity setting such as an HPA, a vendor-specific enterprise configuration, or a previously provisioned server drive—not duplicated data or RAID mirroring inside the SSD.
Check Disk Management or diskpart for unallocated space, but if the disk itself reports only 128GB, deleting partitions will not restore the rest. A secure erase may remove old data and partitions, but it normally does not change a host-protected capacity limit. Use a tool that can inspect and restore the native maximum LBA, and make sure the correct drive is selected because the process destroys all data. If the native maximum is also around 128GB, then the drive is genuinely limited or defective and cannot safely be upgraded to 240GB.
The diagnostic list contains several different devices, and they do not all match the capacities described. The Kingston drive is a 256GB NVMe SSD, the ADATA device is a 1TB hard disk, and the Micron drive is the one reporting 128GB. So the 120GB result is not being caused by Windows confusing two disks; it is coming from the Micron drive's own reported sector count.
Look in Disk Management for unallocated space first. If none exists, inspect the drive's current and native maximum LBA with a reputable ATA utility. Do not change random firmware settings or use a tool intended for a different controller, since an incompatible firmware or capacity command can permanently make the drive unusable.
The model number is important here: MTFDDAV240TDS is sold as a 240GB Micron 5300, while the diagnostic output clearly identifies the connected device as 128GB. I would verify the label and serial number before trying any firmware or capacity utility.