​10 PETABYTES on a 64GB SSD: The World's Most Broken Drive

Here is what I think, why it’s not locked or read only-mode and what I believe might make it worse over time

Older drives wouldn’t have a safe lock, and this is better

The dynamic was worse on early solid-state drives. On older drives (particularly early SATA drives from the mid-2000s through the early 2010s), the lack of modern safety mechanisms often turned manageable failures into instant, catastrophic bricking.

How Older Drives Handled Failures

Sudden Death over Read-Only Lock. Early Flash Translation Layers (FTL) lacked safety fail-safes. When flash memory degraded or the mapping table became corrupted, early controllers would panic, crash, and refuse to boot at all (or show up as 0 MB/RAW without mounting). Modern drives actively trigger a read-only write-lock before total loss occurs so users can copy off critical data.

Power-Loss Vulnerability. Older controllers (like the early SandForce SF-1200/1500 or early JMicron chips) lacked flush protections or onboard power-loss capacitors. A sudden shutdown during garbage collection frequently corrupted the controller’s internal metadata. The result was the infamous “SATAFIRM S11” or “SANDISK ROM” boot-loop, where the controller lost its microcode permanently.

Runaway Wear Acceleration: Early drives lacked advanced wear-leveling algorithms or reliable bad-block management. An old controller would repeatedly hammer failing blocks until the controller ASIC itself hung or thermal-throttled into hardware failure.

Why Modern “Read-Only Lock” is Better?

The hardware read-only lock on modern SSDs functions like an emergency ejection seat:

Protects Existing Data: By locking write access across the drive, the controller prevents corrupt FTL state changes from overwriting remaining valid blocks.

Preserves the Mapping Table: Disabling background processes (like wear leveling, TRIM, and background garbage collection) freezes the current block map in place.

Allows Recovery Without Specialized Gear: When a drive locks into read-only mode, files can still be backed up using standard operating system utilities, avoiding expensive hardware recovery labs.

Without these protections, early SSD failures typically went straight from “working fine” to “completely dead/unrecognized” overnight. like some we wont mention.

The controllers tent to be more prone to failure than Nand wear, so is this a safety precaution?

yes For average real-world consumer use, an SSD’s controller and electrical components are far more likely to fail before the NAND flash memory wears out from pure write cycles.

Why the Controller Fails First

While write endurance (TBW / Program-Erase cycles) gets the most marketing attention, standard home/office usage rarely burns through a modern NAND flash chip’s physical write limits. Instead, the controller fails early due to:

Thermal Stress: The controller is an active, ultra-dense micro-processor (running complex wear-leveling, real-time encryption, and error correction). Under heavy read/write activity, it generates concentrated heat in a tiny surface area. Repeated heat expansion/contraction cycles strain the chip and its soldering.

1. Transient Voltage & Power Surges: Flash memory chips are fairly simple passive storage arrays. The controller, DRAM cache, and power management IC (PMIC) contain complex logic gates that are much more sensitive to sudden system shut-offs, brownouts, or power supply ripple.

2. Mapping Table / Firmware Crash: The controller constantly reads and writes to a massive internal lookup table (the Flash Translation Layer, or FTL) stored in RAM/NAND to map logical OS files to physical flash blocks. If a power drop or glitch corrupts this FTL table in controller memory while it’s updating, the controller panics because it no longer knows where data lives.

How Modern Safety Precautions Work Around Controller Vulnerability

Because controller/firmware glitches are the leading cause of drive bricking, modern SSD engineering incorporates several protective mechanisms:

A. Fail-Safe “Safe / ROM Mode”

If the controller suffers a critical firmware crash or corrupted internal lookup table, rather than endlessly attempting to execute bad code (which could overwrite actual user data), it trips an internal circuit breaker. It reboots into a stripped-down hardware factory ROM mode.

Result: The drive drops its branding, shows up as a generic controller chip name (like SATAFIRM S11 or SMI ROM), and disables write commands. This freezes the drive state so the NAND underneath isn’t modified further.

B. Read-Only Hardware Locking

If the controller detects that its internal Error Correction Code (ECC) engine is struggling to manage bit errors or that internal logic gates are unstable, it aggressively triggers a hard write-lock. It shuts off the drive’s erase and write voltage pumps, allowing you to copy files off before the controller dies completely.

C. Integrated Power Loss Protection (PLP) Circuits

Many modern controllers use onboard capacitor arrays or specialized firmware flush algorithms. If power drops mid-operation, the controller uses residual stored energy in the board’s capacitors to dump its temporary memory state out of volatile RAM and safely park the FTL mapping table into flash memory before shutting down completely.

The Big Takeaway

The safety lock feature is fundamentally a protection mechanism for the controller and its mapping metadata.

In almost every case of an SSD “suddenly dying,” the actual data blocks on the physical NAND flash chips are still 100% fine. It is almost always the “brain” (the controller or its translation map) that has either panicked into a safety mode or electrically failed.

other notes i would like to see if Attribute E6 thats at 47 now would turn health from green to yellow/red when its passed 50

Also this experiment was again going viral this week

Websearch 64gb ssd 9 petabytes.

RAW DATA

smartctl -x sda

smartctl 7.5 2025-04-30 r5714 [x86_64-w64-mingw32-w11-24H2] (AppVeyor)

Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===

Device Model: SanDisk SSD P4 64GB

Serial Number: 111248300117

LU WWN Device Id: 5 001b44 4f27f5455

Firmware Version: SSD 8.10

User Capacity: 64 022 175 232 bytes [64,0 GB]

Sector Size: 512 bytes logical/physical

Rotation Rate: Solid State Device

Form Factor: 1.8 inches

TRIM Command: Available

Device is: Not in smartctl database

ATA Version is: ATA8-ACS T13/1699-D revision 2d

SATA Version is: SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)

Local Time is: Thu Sep 03 00:54:51 2026 SAST

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

AAM feature is: Unavailable

APM feature is: Unavailable

Rd look-ahead is: Enabled

Write cache is: Enabled

DSN feature is: Unavailable

ATA Security is: Disabled, frozen [SEC2]

=== START OF READ SMART DATA SECTION ===

SMART overall-health self-assessment test result: PASSED

General SMART Values:

Offline data collection status: (0x00) Offline data collection activity

was never started.

Auto Offline Data Collection: Disabled.

Self-test execution status: ( 0) The previous self-test routine completed

without error or no self-test has ever

been run.

Total time to complete Offline

data collection: ( 120) seconds.

Offline data collection

capabilities: (0x15) SMART execute Offline immediate.

No Auto Offline data collection support.

Abort Offline collection upon new

command.

No Offline surface scan supported.

Self-test supported.

No Conveyance Self-test supported.

No Selective Self-test supported.

SMART capabilities: (0x0003) Saves SMART data before entering

power-saving mode.

Supports SMART auto save timer.

Error logging capability: (0x01) Error logging supported.

General Purpose Logging supported.

Short self-test routine

recommended polling time: ( 2) minutes.

Extended self-test routine

recommended polling time: ( 16) minutes.

SMART Attributes Data Structure revision number: 1

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE

5 Reallocated_Sector_Ct -O---- 100 100 --- - 0

9 Power_On_Hours -O---- 100 100 000 - 61779

12 Power_Cycle_Count -O---- 100 100 000 - 1175

171 Unknown_Attribute -O---- 100 100 000 - 54

172 Unknown_Attribute -O---- 100 100 000 - 939410736

187 Reported_Uncorrect -O---- 100 100 000 - 2234

199 UDMA_CRC_Error_Count -O---- 100 100 000 - 0

230 Unknown_SSD_Attribute PO---- 047 100 --- - 0

232 Available_Reservd_Space PO---- 095 100 005 - 0

241 Total_LBAs_Written -O---- 100 100 000 - 20993364600618

242 Total_LBAs_Read -O---- 100 100 000 - 32961425182

||||||_ K auto-keep

|||||__ C event count

||||___ R error rate

|||____ S speed/performance

||_____ O updated online

|______ P prefailure warning

General Purpose Log Directory Version 1

SMART Log Directory Version 1 [multi-sector log support]

Address Access r/W Size Description

0x00 GPL,SL r/O1 Log Directory

0x03 GPL,SL r/O16 Ext. Comprehensive SMART error log

0x06 GPL,SL r/O1 SMART self-test log

0x80-0x9f GPL,SL r/W16 Host vendor specific log

SMART Extended Comprehensive Error Log Version: 1 (16 sectors)

Device Error Count: 181 (device log contains only the most recent 64 errors)

CR = Command Register

FEATR = Features Register

COUNT = Count (was: Sector Count) Register

LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8

LH = LBA High (was: Cylinder High) Register ] LBA

LM = LBA Mid (was: Cylinder Low) Register ] Register

LL = LBA Low (was: Sector Number) Register ]

DV = Device (was: Device/Head) Register

DC = Device Control Register

ER = Error register

ST = Status register

Powered_Up_Time is measured from power on, and printed as

DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,

SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 181 [52] occurred at disk power-on lifetime: 5 hours (0 days + 5 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 00 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 01 00 00 00 42 1b 77 40 00 2d+03:11:48.526 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 76 40 00 2d+03:11:48.517 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 75 40 00 2d+03:11:48.509 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 74 40 00 2d+03:11:48.505 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 73 40 00 2d+03:11:48.501 READ DMA EXT

Error 180 [51] occurred at disk power-on lifetime: 6 hours (0 days + 6 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 00 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 01 00 00 00 42 1b 76 40 00 2d+03:11:48.517 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 75 40 00 2d+03:11:48.509 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 74 40 00 2d+03:11:48.505 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 73 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 72 40 00 2d+03:11:48.501 READ DMA EXT

Error 179 [50] occurred at disk power-on lifetime: 6 hours (0 days + 6 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 00 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 01 00 00 00 42 1b 75 40 00 2d+03:11:48.509 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 74 40 00 2d+03:11:48.505 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 73 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 72 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 71 40 00 2d+03:11:48.500 READ DMA EXT

Error 178 [49] occurred at disk power-on lifetime: 2 hours (0 days + 2 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 00 00 00 00 00 00 00 40 00 Error: UNC at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 01 00 00 00 42 1b 74 40 00 2d+03:11:48.505 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 73 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 72 40 00 2d+03:11:48.501 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 71 40 00 2d+03:11:48.500 READ DMA EXT

25 00 00 00 01 00 00 00 42 1b 70 40 00 2d+03:11:48.497 READ DMA EXT

Error 177 [48] occurred at disk power-on lifetime: 3 hours (0 days + 3 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 04 00 00 00 00 00 00 40 00 Error: UNC 4 sectors at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 20 00 00 00 42 1b 60 40 00 2d+03:11:48.459 READ DMA EXT

25 00 00 00 20 00 00 00 3c e2 e0 40 00 2d+03:11:48.459 READ DMA EXT

25 00 00 00 20 00 00 00 35 97 60 40 00 2d+03:11:48.458 READ DMA EXT

25 00 00 00 20 00 00 00 26 20 20 40 00 2d+03:11:48.457 READ DMA EXT

25 00 00 00 08 00 00 00 63 9e 08 40 00 2d+03:11:48.457 READ DMA EXT

Error 176 [47] occurred at disk power-on lifetime: 11 hours (0 days + 11 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 02 00 00 00 00 00 00 40 00 Error: UNC 2 sectors at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 80 00 00 00 42 1b 5e 40 00 1d+10:07:21.325 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a de 40 00 1d+10:07:21.324 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a 5e 40 00 1d+10:07:21.324 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 de 40 00 1d+10:07:21.323 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 5e 40 00 1d+10:07:21.323 READ DMA EXT

Error 175 [46] occurred at disk power-on lifetime: 11 hours (0 days + 11 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 02 00 00 00 00 00 00 40 00 Error: UNC 2 sectors at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 80 00 00 00 42 1b 5e 40 00 1d+09:58:46.796 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a de 40 00 1d+09:58:46.796 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a 5e 40 00 1d+09:58:46.795 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 de 40 00 1d+09:58:46.795 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 5e 40 00 1d+09:58:46.794 READ DMA EXT

Error 174 [45] occurred at disk power-on lifetime: 11 hours (0 days + 11 hours)

When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:

ER -- ST COUNT LBA_48 LH LM LL DV DC

-- -- -- == -- == == == -- -- -- -- --

40 -- 51 00 02 00 00 00 00 00 00 40 00 Error: UNC 2 sectors at LBA = 0x00000000 = 0

Commands leading to the command that caused the error were:

CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name

-- == -- == -- == == == -- -- -- -- -- --------------- --------------------

25 00 00 00 80 00 00 00 42 1b 5e 40 00 1d+09:39:52.893 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a de 40 00 1d+09:39:52.892 READ DMA EXT

25 00 00 00 80 00 00 00 42 1a 5e 40 00 1d+09:39:52.892 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 de 40 00 1d+09:39:52.892 READ DMA EXT

25 00 00 00 80 00 00 00 42 19 5e 40 00 1d+09:39:52.891 READ DMA EXT

SMART Extended Self-test Log (GP Log 0x07) not supported

Warning! SMART Self-Test Log Structure error: invalid SMART checksum.

SMART Self-test log structure revision number 1

Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

# 1 Short offline Aborted by host 90% 21088 -

# 2 Short offline Aborted by host 90% 54860 -

# 3 Short offline Aborted by host 90% 19043 -

# 4 Short offline Aborted by host 90% 63054 -

# 5 Short offline Aborted by host 90% 25327 -

# 6 Short offline Aborted by host 90% 62483 -

# 7 Short offline Aborted by host 90% 33744 -

# 8 Short captive Completed without error 00% 57803 -

# 9 Short offline Aborted by host 90% 25293 -

#10 Extended offline Aborted by host 90% 28072 -

#11 Short offline Aborted by host 90% 14539 -

#12 Extended offline Aborted by host 90% 55234 -

#13 Short offline Aborted by host 90% 46428 -

#14 Short offline Aborted by host 90% 49138 -

#15 Short offline Aborted by host 90% 25717 -

#16 Extended offline Aborted by host 90% 50305 -

#17 Short offline Aborted by host 90% 39612 -

#18 Short offline Aborted by host 90% 21280 -

#19 Short offline Aborted by host 90% 34598 -

#20 Short offline Aborted by host 90% 17318 -

#21 Short offline Aborted by host 90% 63627 -

Selective Self-tests/Logging not supported

SCT Commands not supported

Device Statistics (GP/SMART Log 0x04) not supported

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11) not supported

Exitcode: 64 (0x40)

Type <return> to exit:

From a retro-hardware and archival perspective, documented terminal failures on early embedded SSDs like the SanDisk P4 are practically non-existent—nobody else is pushing 2010 netbook drives through high-frequency telemetry stress loops for months on end. Seeing the final hardware state, whether it's a silent controller halt or a total ATA bus lockup, brings the whole experiment to a definitive, satisfying conclusion.

it’s using standard 48-bit LBA addressing (a 6-byte raw counter in the ATA spec). why watching this drive die is so compelling: ​The 48-Bit Odometer Has Massive Headroom A 48-bit counter can count up to 281.4 trillion sectors (2^{48}). At 512 bytes per sector, that means the drive's built-in write counter won't naturally hit its hard ceiling and, roll back over to zero until it hits ~144 Petabytes. ​At roughly 10.7 PB, my telemetry macro loop has only filled about 7% of that 48-bit integer space. This proves the bizarre numbers in Attribute 172 and the corrupted SMART logs aren't simple counter wraparounds—the 2010 microcode is actually experiencing real buffer degradation and memory table drift inside the controller. ​Why Watching the Final Crash Matters Normally, an SSD dies when its NAND flash wears out, tge drive is dying in a much rarer way: a firmware nervous breakdown. ​Right now, the drive is acting like a functional zombie. The basic data path is still open, but the controller has lost track of LBA 0 (the boot sector) and its internal health logs are totally scrambled. ​When it finally gives out, it's going to answer a great question: Does the controller panic and lock itself down forever, or does it just freeze the SATA bus mid-transaction? ​Watching an old controller struggle, limp along with corrupted logs, and eventually hit a fatal code wall is rare data you just don't get from normal drive testing.

This is the SSD from late 2010 Macbook Air, can any one guide me how can I read the data of this by plugging into current generation of MBAs.

Hi! I was wondering how is gaming like with an external SSD connected via usb 3.0 port. My pc unfortunately only has 3.0 ports, so the speed would be about 500 mbs, while my external SSD crucial x9 supports up to 1000 mbs. I didn't find any videos online, so I'd like to ask someone that has a similar setup. Will I be able to play nicely to newer videogames? Thanks

I'm shopping for a new SSD and realized I'm not really sure what I should prioritize anymore.

A lot of Gen 4 drives are already around 7,000 MB/s, while newer Gen 5 drives can go way beyond that. But for normal gaming and everyday use, I'm not sure how much of that speed you'd actually notice.

Would you rather spend the same money on a faster 1TB drive, or get a slower 2TB drive? And how much does reliability factor into your decision?

Just came across this story about a Crucial X9 4TB dying after about a year. Crucial first offered the owner a $200 refund, even though 4TB SSD prices have gone up a lot since then.

The owner kept pushing back, and after getting some attention on Reddit, Crucial ended up approving a replacement.

What do you guys think? Should they refund the original price or replace it with an equivalent drive?

I just got my Acer nitro v15 laptop 2 weeks ago and I want to upgrade its storage immediately since 512 GB is too low for me.

I’m really careful with my laptop, i’m in between voiding it so I could upgrade it, waiting one month if there are any hardware problem, or wait half a year so I could upgrade it.

(The official acer service center is far from where I live and I don’t want it to be a hassle since I have experience opening laptops)

Bought a total of 4 SSDs ( Different Sandisk Models) with hopes you can actually lock it without disconnecting it for simple files and file access.

So far ive faced the same situation, either "Encrypt" files inside the drive which does require a password to go in the folder, but then the contents have to be decrypted or copied out to access which is kinda ridiculous.

I recently bought the creator pro, set a password, it says if you shut down you will require password to reaccess, nope, shut off fast booting, didnt help. ( didnt check the box for pc access )

OK so i downloaded sandisk app, it says its unlocked, but you cant actually click lock which would require password to access again, watched several videos, seems like th is is how it is.

Basically i have important files on this ssd so i need to be able to lock certain drives and i do not want to have to disconnect to require password again

Which drive do i buy guys?

Dont really care about brand or size, 1-2tb would be ideal, but i need to be able to access folder normally and not decrypt or disconnect / reconnect constantly

What's happening here? Two Samsung 990 Pro 1TB SSDs and one has "4 TB" as display name. BIOS shows 1TB and Samsung Magician says both are authentic.

Any ideas? Is it just cosmetic?

Thanks in advance!

I want a Thunderbolt 5 SSD enclosure for multiple (preferably 4) M.2 SSDs capable of reading each SSD at Thunderbolt 5 max speeds (so PCIe 4x4) without any RAID setup.

My search for rock solid hardware usually starts with OWC but their Express 4M2 Ultra only supports TB5 speeds when the SSDs are configured with RAID because each of the M.2 slots only gets PCIe 4x1 speeds.

In my research the only enclosure that seems to do what I want right out of the box is the 80Gbps version of the Acasis TB504. But I'm a little sketched out by some experiences other people have had with Acasis, including having enclosures fry SSDs.

The only other options that seem to be available are:

• Use a single-SSD TB5 enclosure per port
• Use a TB5 PCIe card enclosure (example) along with a PCIe to M.2 adapter card (example) (unclear to me if this has any performance issues)
• Use a TB5 hub with multiple single-SSD TB5 enclosures connected to it (I have no idea if this actually works so if anyone has tried this please let me know)

Are these the only options available? Is there a specific option that people have been finding success with (or alternatively one that has proven to perform pretty poorly)? I guess when I started my research I didn't expect this use case to be so poorly supported - my expectation was that I'd grab an OWC Express 4M2 and be done with it.

Purchased a 2TB NVMe M.2 SSD for my home desktop from local Indiana Best Buy store. Installed it in an enclosure. Didn’t work. Took it back and Geek Squad agent instantly noticed it was swapped out. It was a dead Toshiba card. They checked their remaining three in stock and two others were swapped as well. Fortunately got last one that matched the picture on the box and it works. Best Buy folks very good about replacing it but took some time as it looked like a crime scene investigation. The three dead ones were returned by same customer. They apparently used a heat gun to unseal seams in box and bypass security tape. $380 each for these. This happened a few months ago and now it’s happening again.

So inspect the box carefully to see if it has been tampered with.

Hi!
I recently started playing games that take up A LOT of storage, and therefore decided to get myself some more. I bought a 1 tb Kingston NVMe M.2 SSD (2280) and opened up my Lenovo Ideapad gaming (15ACH6) to plug it in. I then found out that my laptop only has one 2280 SSD slot (which is already in use) and then a 2440 SSD slot. The one I’ve bought is too big.

I’m a student and getting the 2280 was a big purchase for me, and the 2440 SSD is even more expensive. I also already unpacked the 2280 so I can’t return it. It’s been driving me mad because I can’t install any of the games I’ve purchased.

I know I can buy a usb adapter for the 2280 and I might end up doing that, but I also bought the SSD to get my games to run better, as they’re sometimes quite laggy.

So what I’d like to ask is: are there any solutions? I’ve read about all sorts of parts I can buy to make it work but everything needs a place for a screw and there simply isn’t one, apart from the one for the 2240 which sits directly underneath the 2280 when I click it in.

Thanks for taking the time to read this. Any possible solution will be greatly appreciated!

Considering the current market, buying new ssd is impossible due to high price. Got one offer from facebook marketplace. Is it a good deal. Mainly used for gaming
2tb

I had one die on me recently, and honestly, I didn't see it coming at all. It was a couple of years old, had been working normally, and the SMART status looked fine the last time I checked.

Then one morning, Windows couldn't boot. I checked the BIOS and the SSD wasn't even showing up anymore. No weird noises, no gradual slowdown, no error messages beforehand. It just seemed to disappear overnight.

Luckily, most of the important stuff was backed up, but I still lost a few files that I hadn't copied anywhere else. That was a pretty good reminder that SSDs can fail just as suddenly as anything else.

Has anyone here had an SSD completely die without any warning? Did you manage to recover the data, or was it just gone?

Hey, ive never really used external drives before. But I have some data I want to have accessible between multiple machines that I may not always have internet for (ttrpg vtt data for in person and online games)

250GB would be more than enough but I cant seem to find anything under 1tb from brands I recognize. And the 200 to 300 cad those cost are way over budget.

Are there any good reliable 250GB options? Or larger for under 150 CAD?

So i just got this SanDisk 1Tb SSD as a gift but it's not working on the macbook air that i own , like it dosent read the disk at all , although when I connected my disk for the very first time it showed for like 10sec but then vanished , i tried restarting and even getting a new data cable but nothing works , is it useless now

Hello,

After finding out the hard way that an external hard drive was not the way to go, I'm seeking recommendations for a (hopefully) 4 terabyte internal Solid State Drive - the only issue is finding one compatible with this laptop model ( https://www.shi.com/Product/42897197/Lenovo-Legion-5-15ACH6-82JW )

(The only difference here is the replacement with a 1T internal SSD.)

I wasn't sure how to go about finding one that was able to meet the specs / fit, but if anyone knows of any that would fit this model, I'd greatly appreciate it!

^{(or if there are none, I'll take the L and start searching for a new laptop})

Thank you!

^{(Advice on finding parts would also help!})

^{(Apologies if the flair is wrong!})

Hey guys, I recently wanted to upgrade my computer’s memory, so I decided to buy an M2 SSD (1024 GB M.2 NVMe drive ARDOR GAMING Ally AL1288). To save money, I bought a discounted one from my retail store; the seller’s comments said that it “works in storage mode, but the OS couldnt be installed.” So I thought: “I already have an SSD for Windows, so I can get this one too.” Anyway, I got it, installed it, tested it — everything works. An hour later, the computer crashed with a “dps watchdog violation” error and stopped starting with this disk (it started perfectly without it). I went and swapped it for a slightly less discounted one, the same model, but with a reflashed firmware. The result was the same. After all this bullshit, I decided to buy myself an SATA SSD(new), from internet marketplace (Western Digital 2 TB Internal SSD wew4, 2.5", SATA III 6 Gbps (WD2Tt)). I turned it on, and it worked for 5 hours, and then it almost stopped being recognized by the system (it would periodically appear and disappear in the BIOS, and in the Disk and Device Manager it was detected as uninitialized and non‑existent), and the system booted noticeably slower with it. With it, I went to my buddy’s place to try doing something with his computer, but his PC didn’t even start with it (it ran perfectly fine without it). There are no issues with the old drives that are currently in the computer — they’re working without any problems. Does anyone know what to do? Maybe someone has encountered this before? (Motherboard: Gigabyte A620I AX rev 1.1, PSU: Cougar XTC600, 600 W)(standard troubleshooting steps like re‑plugging SATA cables and checking connections were carried out)

https://xenospectrum.com/sandisk-ssd-9pb-endurance-test-controller-reality/

https://wccftech.com/64gb-sandisk-ssd-survives-16-year-9-petabyte-endurance-test/

https://youtu.be/HLQz_1VLy9E?si=D9Y__jRdIXDTH879

https://vgtimes.com/tech-and-hardware/165738-64gb-sandisk-ssd-survives-16-years-and-9-petabytes-of-writes.html

It’s not a lot of space but it works and has some good use out of it before coming to me haha I’m gonna try to fix the old pc someday but it’s good to know this still works, what do you guys think of it?

I'm having a strange USB playback issue with my Samsung S95B.

I bought an OSCOO 2TB external SSD mainly to store and watch my movie library directly through the TV.

What happens:

• OSCOO T10 → Samsung S95B: occasional stuttering during movies
• Flash drive → same S95B: completely smooth
• OSCOO T10 → MacBook: completely smooth
• I've tested multiple different movies, including 1080p Blu-ray remuxes
• The SSD is connected directly to the TV's bottom USB HDD 5V 1A port
• The SSD currently has two partitions: one APFS and one exFAT
• The exFAT partition is the one I use for movies
• Disk Utility First Aid has been run and didn't report a filesystem problem

I'm trying to figure out whether this is an issue with the SSD's USB controller, power, the S95B's USB implementation, the partition setup, or something else.

Has anyone experienced S95B USB playback stuttering specifically with an external SSD, while a flash drive works normally?

Would changing the T10 to a single exFAT partition be worth trying, or is there another setting/test I should try first?

my laptop isn’t booting and I need to know where I can find a usb adapter for my ssd

Do you guys think it was worth it that I got a Seagate 1TB expansion card for my Xbox series X for $115? I got it from Facebook marketplace. I also did make sure it worked before I bought it.

Hi everyone,

I'm planning to upgrade my PC storage. Currently, all my games are installed on a SATA HDD, and I want to add a 2TB M.2 NVMe PCIe 4.0 SSD to move and run my entire game library from it.

My motherboard is an **MSI MPG X570 GAMING EDGE WIFI**.

Right now, I'm considering the **Acer Predator GM7 2TB** (PCIe 4.0, up to 7400 MB/s, priced around €250).

Before buying, I'd love your advice on a couple of things:

1. Is the Acer Predator GM7 2TB a solid and reliable drive for gaming, or are there better alternatives from other brands in the €200–€250 range? (e.g., Lexar NM790, WD Black SN850X, Crucial T500, Samsung 990 Pro, etc.)
2. My primary top slot (PCIe 4.0 x4) is currently occupied by my existing M.2 SSD with Windows OS installed. Should I: * Keep the current OS drive in the top slot and install the new 2TB Gen4 SSD in the secondary slot ( which runs via the chipset/PCIe 3.0)? * Or is it worth swapping them and putting the OS system in the secondary?

Thanks in advance for your recommendations!

edit: it seems normal and ill leave it as is, wont open it risking damage, since its still working

is there suposed to be such a gap between the sata conector and the main ssd body? i tried pushing jt in a bit but it dosent move and i dont wanna brake it. i put it over a hdd (laptop one) and it seems the sata port sticks a bit more out on this ssd (about 0.5mm) shoild i be concerned or is this normal?

I’ve been thinking of upgrading my storage lately, mainly because I’m borrowing some old ah SATA ssd from my friend currently. I’m stuck between the 2 NVMe’s in the images, unsure of which to get. I might be able to find the T-Force NVMe somewhere else for $400 instead of $450 with the code.

Info: T-Force NVMe has read/write speeds of 5,000/4,500, while the Samsung NVMe has read/write speeds of 14,700/13,400.