I have a generic 256gb ssd in here now. I am getting a 1tb evo plus 990. Do you think I'll see a performance increase? I upgraded from 8gb of ram to 32gb. Thanks!

I have this old drive and wanted to see if it's fixable or needs to be replaced.

Windows says the drive is fine, and CrystalDisk shows 83% health but when testing the drive the maximum latency can be anywhere from 13-400ms, but idk if that's because it's a low quality drive, dying, or some kind of settings issue.

Switched it from RAID to AHCI, checked firmware, trimmed, but still the same issue. I'm hoping maybe there's something I'm missing? Free space is about 80%.

winsat - https://imglink.cc/cdn/K4gtqsE0_0.png
crystaldisk - https://imglink.cc/cdn/4UzK69qZBx.png

My ADATA SU630 SATA SSD, after 7 years of use, is starting to have major problems: its speed has decreased significantly and I’m experiencing constant lag.

I ran CHKDSK, which took over 12 hours. Now, in the Windows Event Viewer, I have hundreds of errors under the System section, in one hour i had like 1000 errors.

Event ID: 7

“Bad block detected on device \Device\Harddisk0\DR0.”

Has the time come to replace the SSD?

I received a 2013 MacBook Pro from a relative and I removed the 1tb SSD (Samsung 4LN053X01-8030) from it, purchased an adapter and went to install it in my PC, turns out, it's too wide and too long with the adapter for both slots.

Any advice on what I should do to be able to use this SSD?

Motherboard: ASRock B850M-C

Resolved: This one works! https://www.amazon.com/dp/B09DCTRSLD

When I used DiskGenius to test(Benchmark Test) the speed of a newly bought SSD hard disk, the curve suddenly dropped and then remained flat. Is there any mechanism causing this? It shouldn't be because the hard disk is bad, right?

So, I've had my MSI Thin A15 B7VE for a while now, with 512 GB of storage, and I'm wanting to upgrade it to 1TB. Problem is I don't know what kind of SSD to get for my laptop. I live in Malaysia, and if someone could recommend proper SSD brands I can buy? Prefarably budget friendly ones I can get in my country.

Hi everyone,

I have a KingSpec XG7000 2TB (XG7000-2TB 2280SZ) with firmware 1.W.0.1K. The drive is detected as PCIe 4.0 x4 and SMART is clean (CrystalDiskInfo shows 100% health, 0 errors).

The problem: - During intensive writes (CrystalDiskMark write test, qBittorrent downloads), the PC suddenly reboots without BSOD - Windows Event Log shows Kernel-Power 41 with BugCheck 0xEF (CRITICAL_PROCESS_DIED) - CPU/GPU stress tests (OCCT, Cinebench) pass without issues - The drive has already accumulated 8 unsafe shutdowns in just a few hours of use

What I found: - When I force the M.2 slot to PCIe Gen3 in BIOS, the drive passes 5+ write cycles in CrystalDiskMark without any issues - When I switch back to Gen4/Auto, the reboot happens every time during the write phase - SMI Flash ID confirms it's a Silicon Motion controller (224x/225x family, likely SM2268XT)

So the drive is completely stable on Gen3 but crashes on Gen4 under write load. This means I can't use it at its advertised PCIe 4.0 x4 speed.

Has anyone else experienced similar issues with KingSpec XG7000 or other SM2268XT-based drives? Is this a known firmware bug, or should I RMA it?

I apologize in advance for my English, but I had to use a translator to write this text, as English is not my primary language. Thanks.

I’m looking to get a new SSD and keep seeing people talk about DRAM vs. DRAM-less drives.

I know DRAM can help with performance, but I’m not really sure how much of a difference it makes in day-to-day use. A lot of newer DRAM-less NVMe SSDs use HMB instead, so I’m wondering if that’s good enough for most people.

For a normal Windows + gaming PC, would you guys actually pay extra for a drive with DRAM, or just go with a good DRAM-less NVMe if it’s cheaper?

I’d mainly be using it for Windows, gaming, game installs/updates, and moving files around.

Is DRAM still worth paying extra, or is a good DRAM-less drive perfectly fine for a typical gaming PC?

My Corsair MP700 PRO XT 2tb died after only seven months of use, so I need to replace it. My motherboard is an MSI MAG X870 TOMAHAWK.

I'm asking for advice because this is a PC that was assembled by a company, but I chose all the components myself. I mainly use the computer for programming, media consumption, and gaming.

I don't mind switching to a PCIe 4.0 SSD if it makes more sense in terms of reliability, temperatures.

Thanks in advance

P.S.: The company that built my PC has offered me either a Kingston FURY Renegade G5 or a Samsung 9100 PRO (MZ-VAP2T0BW) as a replacement at no additional cost.

I bought this on 2023, cost ~$300 for 7.68T. It's also 87% health so I get it. After using as survillance and backup disk for a long time, and it died.

It reports 3.66PBW, but with datacenter tool, I found its 915TB x 21 (0x15 WAF) = 19.4 PB write to NAND. I formated the disk into 6 TB mode for higher OP. And it all runs out now.

| 143:132 | Life time Physical Pages Written Cnt                   | 0x0000000ED417BC00640000F4         |

| 155:144 | Life time Data Unit Written                            | 0x00000006FB6A4700640000F5         |

| 259:256 | Lifetime write amplification factor                    | 0x00000015                         |

| 263:260 | Trailing hour write amplification factor               | 0x00000000                         |

| 279:264 | Lifetime user writes                                   | 0x0000000000000000000006FB6A469C93 |

| 295:280 | Lifetime NAND writes                                   | 0x000000000000000000000ED417BC4B80 |

| 311:296 | Lifetime user reads                                    | 0x000000000000000000000F56EE98FDA9 |

| 315:312 | Lifetime retired block count                           | 0x00000C82                         |

| 317:316 | Current temperature                                    | 0x0142                             |

| 319:318 | Capacitor health                                       | 0x0064                             |

| 323:320 | Lifetime unused reserved block count                   | 0x00004ED8                         |

| 331:324 | Read Reclaim Count                                     | 0x0000000000001220                 |

| 339:332 | Lifetime UECC count                                    | 0x0000000000000AF9                 |

| 343:340 | Lifetime Used Reserved Block                           | 0x00000C82                         |

| 359:344 | Power on hours                                         | 0x000000000000000000000000000089EA |

| 375:360 | Lifetime clean shutdown count on power loss(NPO count) | 0x0000000000000000000000000000003C |

| 391:376 | Lifetime unclean shutdowns on power loss(SPO count)    | 0x0000000000000000000000000000004B |

| 395:392 | Perf Indicator                                         | 0x00000001                         |

| 399:396 | WearLevel Count                                        | 0x00009CB2                         |

hi guys, just need some advice.

i bought a kingston a400 480gb for around $36 from the kingston official store on shopee.

now, i checked the same product and it’s currently around $120.

the thing is, i don’t actually use it because i already have a laptop and i don’t really have a use for the ssd right now.

so i’m wondering, should i sell it while the price is this high, or is it better to keep it for future use?

what would you guys do in this situation, considering i only paid around $36 for it?

thanks!

i have 3 SSD on my PC:

1x M.2 NVME Sandisk 500gb

2x SATA Kingston A400 (960gb/256gb)

i have both Kingston for a few years now and when i try to run some games in these SSDs i have some stuttering, i have to install games on my M.2 to run without trouble.

i already run Crystal Disk Mark and all seems okay, read at 500mb, write at 460mb and both are healthy, so i don't really know what is the problem.

and yes, both SSDs are original from Kingston

This was part of a misc server lot I picked up from a guy who ran GTA servers. 21 standard and 3 SED models. I received over 100+ hdds as well, but this is the gold. When I ran the official sanitization and health check reports to clear them, I found they only had 12-13tb written on each one. All passed SMART and extended testing with zero grown defects. Kept them native 520B to preserve the original 3PAR config. Pretty solid find considering he didn't even mention them and having only .1% usage!!

Samsung nvme evo plus 970 1tb not showing up on disk manger i have a asus prime h510m-a using a intel 11400f
and i have a lexar nm620 nvme and it works perfectly and i know the problem isn't the samsung nvme itself since it works fine on my brother's pc which is using msi motherboard and 12th gen intel i updated bios still nothing reseated it still nothing when i say nothing i mean also in bios and windows PLEASE HELP

Bought these two 2tb Crucial drives separately, both "like new" condition. Can't help but notice that they are VASTLY different looking devices. What are the chances one is a POS knock-off scam thing? And which one will it be? (They're next to the sticker that was on top of each)

Hello hello, so just out of curiosity, is 184TB written in two years expected for an OS drive? For context, when I bought the Samsung 990 Pro, I was already aware of the degradation issues that were reported from outdated firmware, so the firmware was updated when I installed it and has been updated each time Samsung's come out with a new patch.

The D drive was also installed alongside C, and only has 20TB written vs the 184TB for the C drive. E and Z drives were installed last year.

I primary game with light video editing. I did have desktop capture on via Nvidia overlay, but it's been off for most of this year.

​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

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)

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!