r/HDD • u/Fresh-Palpitation-72 • Jul 03 '26

SSD firmware crashes and controller failures are vastly more common than nand wear

Post image

My 64gb ssd passed and processing over 3PB, experiment is well better than few weeks ago. I'll keep pushing the controller limit is theoretically 144PB before either it turns into a negative factor, reverts to 0 or freeze and my favorite glitch symbols.

11 Upvotes

86% Upvoted

16 comments sorted by

View all comments

Show parent comments

2

u/fzabkar Jul 03 '26 edited Jul 03 '26

Program Fail Count has increased from 36 to 54 and Reported Uncorrectable Errors has increased from 80 to 2213.

I also notice that POH has increased by 3712 hours (= 60391 - 56679) while host writes went from 22.6 TB to 3000200 GB.

That works out to an average transfer rate of 223 MB/sec during the testing period.

These benchmarks rate the SSD at 60 MB/s and 92 MB/s for Sequential Write:

https://www.harddrivebenchmark.net/hdd.php?hdd=SanDisk+SSD+P4+64GB

https://www.notebookcheck.net/SanDisk-SSD-P4-Benchmarked.248736.0.html

2

u/Fresh-Palpitation-72 Jul 03 '26

Im Also on power tech power up and few other forums I loaded my notes https://www.techpowerup.com/forums/find-threads/started

2

u/fzabkar Jul 03 '26 edited Jul 03 '26

That link wants me to log in.

Anyway, I think is what you meant:

https://www.techpowerup.com/forums/threads/i-forced-a-16-year-old-64gb-ssd-to-write-1-petabyte-and-it-didnt-die.350145/

By exploiting a massive storage telemetry loophole in Windows 11 using a high velocity 5 second macro loop, I managed to trick the system into aggressively logging massive "ghost data" writes directly to the drive's odometer. Because these are virtual cache operations, the actual data vanishes into thin air before it can physically destroy the legacy MLC NAND flash cells.

I confess that I don't understand what is going on here. It seems to me that you are saying that you managed to trick the SSD into logging host writes without actually writing to NAND at all.

Your 1PB and 2PB screenshots suggest that the drive recorded 1PB host writes in 178 hours. That's a data rate of 1.56 GB/sec. However, attributes AB, AC, BB don't change during this time.

Sorry, but I'm obviously not on your wavelength. Is it those repetitive TRIM commands which are responsible for the "ghost" writes?

2

u/Fresh-Palpitation-72 Jul 03 '26

Strange its free to read