u/Fresh-Palpitation-72

SSD firmware crashes and controller failures are vastly more common than nand wear thats why im letting it scream,

Percent of Total Write/ Erase Count seemed to have gotten up, my findings that its odd and it should go down as you see older picture was down to 3 now its at 36, so I believe who had it before me ran it from 100% to 0, then it flipped and thats when I found it,

Also my notes is about EM interference (EMI) and so few things too...

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

Percent of Total Write/ Erase Count seems to go up that my findings that its odd and should go down as you see older picture was down to 3 now its at 36, so I believe who had it before me ran it from 100% to 0, then it flipped and thats when I found it,

Also my notes is about EM interference (EMI) and so few things

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

Percent of Total Write/ Erase Count seems to go up that my findings that its odd and should go down as you see older picture was down to 3 now its at 36, so I believe who had it before me ran it from 100% to 0, then it flipped and thats when I found it,

Also my notes is about EM interference (EMI) and so few things

Seems ok, no new BB, C3, 05 errors, wonder if this is good for boot drive though?

Video also has details on ssd and the odometer pushing passed 3pb

SSD firmware crashes and controller failures are vastly more common than nand wearMy 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

https://youtu.be/13btRWFCUv4?si=T2ZgYb\_H4EMUIZ4t

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.

I found this Marvelous drive in an pc being scrapped and updated the firmware, I am pleased to have updated the firmware before it got worse, and pleased to announce no further issues but to make sure, i am writing 10 extra Terabytes to make extremely sure its relaiable. Using anvil endurance to do it.

I am officially back with the SanDisk P4 and the madness just won't stop. After defying all logic and crossing the 1 Petabyte milestone, I kept the torture test screaming to see what it actually takes to kill a 64GB drive from 2010.

​In this timelapse, you’re watching the telemetry data climb all the way past the 2PB mark. This is where things get genuinely weird. Most consumer software and older hardware firmware from this era were never meant to see numbers this high. We are actively pushing the drive's 48-bit LBA firmware to its absolute limits, basically playing a game of chicken with the storage controller to see if the counter is going to roll over, glitch out, or just freeze.

​The secret? The drive isn't actually melting because a heavy system RAM cache and aggressive TRIM loops are absorbing the absolute brutal force of the writes before they can fry the physical NAND cells. In fact, during this exact run, the host Windows OS almost ran out of storage space and choked on its own temporary files, meaning the PC itself almost gave up before this ancient SSD even flinched.

​How much further can the drive go before the math or the hardware breaks? Are we hitting 5 Petabytes next, or is Windows going to crash first? Drop your bets in the comments

Been running an endurance loop on this old drive to see how far it can go. It’s hitting the telemetry cache and executing automated TRIM commands perfectly, so the physical silicon is still holding up fine despite the ridiculous milestone.

​Putting together a quick 1minute setup video for YouTube to show the bench rig and the macro loop in action, will drop it soon if anyone is interested.

Ancient SanDisk P4 SATA II drive with over 60,000 Power-On Hours that just smashed a milestone.

​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.

​

​my project completely de-bunks standard factory TBW limits as a hardware kill-switch and shows just how incredibly resilient legacy, over-engineered storage controllers really are.

​I officially obliterated the 32-bit integer limit weeks ago. Next Testing the limits of a 48-bit register!

​

Remember its a telemetry and firmware test, not a physical destruction test.

​

​The purpose isn't to burn the physical NAND to ashes; it's to see how a budget 2010 storage brain handles modern, enterprise-level digital stress under Windows 11. The fact that it crossed a Petabyte without a single firmware exception or interface crash is the real victory here!"

​

https://youtu.be/AZXOqvVEBHI?si=b8s5la2tX_M28-37

Ancient SanDisk P4 SATA II drive with over 60,000 Power-On Hours that just smashed a milestone.

​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.

​

​my project completely de-bunks standard factory TBW limits as a hardware kill switch and shows just how incredibly resilient legacy, over-engineered storage controllers really are.

​I officially obliterated the 32-bit integer limit weeks ago. Next Testing the limits of a 48-bit register!

​

Remember It’s a telemetry and firmware test, not a physical destruction test.

​

​

​The purpose isn't to burn the physical NAND to ashes; it's to see how a budget 2010 storage brain handles modern, enterprise-level digital stress under Windows 11. The fact that it crossed a Petabyte without a single firmware exception or interface crash is the real victory here!"

​

If u want to see the odometer hit 1pb link below

https://youtu.be/AZXOqvVEBHI?si=b8s5la2tX_M28-37

Research i do ghost writes on my ssd using trim Minutes in a day: 60 minutes multiplied by 24 hours equals 1 440 minutes.Total daily data: 216 GB per minute multiplied by 1 440 minutes equals 311 040 GB Note only windows 11 trim does the ghost writes and other software for trim does not work at ALL So proof of ghost writes that record writes but does not wear it down

​

​

Also I set a auto click for every 5 seconds to trim it, my research is found amazing things so far, but all I can say sata 2 technically is durable much so as today's ssds,

​

​

Place bets where it may roll back to 0 or max out, I'll let u know

​

​

​

Approx Max per trim is 18gb that every 5 seconds

​

Minutes in a day: 60 minutes multiplied by 24 hours equals 1 440 minutes.Total daily data: 216 GB per minute multiplied by 1 440 minutes equals 311 040 GB. That is if max is 18gb per trim.

Place bets

​

Video link, https://youtu.be/2GtvortiRHQ?si=79rbu07AZy5_JXLt

Research i do ghost writes on my ssd using trim Minutes in a day: 60 minutes multiplied by 24 hours equals 1 440 minutes.Total daily data: 216 GB per minute multiplied by 1 440 minutes equals 311 040 GB Note only windows 11 trim does the ghost writes and other software for trim does not work at ALL So proof of ghost writes that record writes but does not wear it down

​

​

Also I set a auto click for every 5 seconds to trim it, my research is found amazing things so far, but all I can say sata 2 technically is durable much so as today's ssds,

​

​

Place bets where it may roll back to 0 or max out, I'll let u know

​

​

​

Approx Max per trim is 18gb that every 5 seconds

​

Minutes in a day: 60 minutes multiplied by 24 hours equals 1 440 minutes.Total daily data: 216 GB per minute multiplied by 1 440 minutes equals 311 040 GB. That is if max is 18gb per trim.

​

Place ur bets

​

Link to video https://youtu.be/2GtvortiRHQ?si=79rbu07AZy5\_JXLt

​

​

​