I bought one for my Dell T3500 workstation and i needed to update my RST because HDD Regenerator showed the disk as 1123mb. But in my computer it showed 9.09tb and in disk manager 9313,98tb. It also showed 9.09tb in my Asrock Z590 OC Formula were i partioned it in, the asrock which is from 2021 and it should handle disk like this. I formated in GPT. I checked the disk in H2testw that checks false ssd sizes, it can handle hard drives to. It took 22h. I got 3 years warranty from amazon. A old data center drive, Manufactured 2017 aug. In hard disk sentinel it shows to be one day old, that is not correct. I did not know about tebibytes. Does newer windows count in that? Smaller seems to be in terabytes. 9,313.226 gigibytes or 9.094947 tebibytes.

Warning: Only 9537036 of 9537517 MByte tested.
Test finished without errors.
You can now delete the test files *.h2w or verify them again.
Writing speed: 173 MByte/s
Reading speed: 170 MByte/s
H2testw v1.4

It first did not spin up in my T3500. It was the sata power from my old Cooler master 500w. I had to use a molex to sata adapter to make it spin. It first showed up as 1123mb in HDD Regenrator but after i updated the RTS it showed up as 9314. But in my computer it shows 9.09gb., taping the 3.3V tabs on the disk's power supply connector then after a certain SATA3.x version as voltage on this can cause the disk to become completely powerless via built-in MOS-FET pulleys on the disk controller card (a deliberate 'feature' on server disks for to be able to do 'Norwegian reset' - ie 'voltage off - voltage on' - remotely for backplanes that support this signalling). you have to search for yourself exactly which 3.3 V contact tongue turns off the disk and needs to be taped. I found that to diffecult so i used a molex to sata adapter.

I updated Intel RST but i guess (32-bit LBA addressing) can be tricky? https://www.dell.com/support/home/sv-se ... erid=rr3h4
RST Version 10.1.0.1008 and later (what I managed to google quickly) if you want 48-bit LBA addressing - now looks like it wraps on LBA32 and only sees the last 2TB block when it wants LBA48 - The OS can read out how big the disk is with the SATA ID but notices that it cannot talk to more than LBA32 which gives about 2TB addressable area with 512-byte sectors

if the disk had used 4K sectors, it would probably have been fine when you reach 16 TB with the 32-bit LBA addressing, either i train the motherboard to understand 48-bit addressing, or buy a 4k-native sector disk or have to use a sufficiently modern HBA that can handle LBA48. - had i been running with SAS disks i would have been able to reconfigure the sector size i wanted - including with T10 checksums.

Don't know if it is possible on some SATA disk models to reconfigure between emulated 512-byte sectors and native 4K sectors in their SATA protocol to the host. - all modern drives since like 10 years use 4K sector size internally - 512 byte sectors are just an 'artifact' from ancient times but it has been extremely difficult to get people to buy 4K native sector size on SATA drives.

10TB - 8TiB = 1203.9 GB
10TB - 8TiB = 1121.2 GiB
10TB = 9313.23 GiB
10TB = 9.095 TiB
10TB = 9537000 MiB

RAID mode may be limited to 32-bit LBAs in your setup.

_________________
A backup a day keeps DR away.

Thanks. I use ACHI without raid. Single drives. I doubt if it writes to the whole disk as it is LBA 48 or if it writes to 2tb LBA 32 and then rewrites it again.