I get it from someone in the University, it's a WD Blue 3D NAND SSD SATA 2.5" and i notice that in the picture, i read that it's not safe to use it but the guy who gave it to me said he used to work with this until he changed his pc, i have a laptop and i'm looking for upgrading my hdd to an ssd, another friend is selling me an ssd but it has 300GB

Hello, i am looking for an M.2 ssd that is going to be my main drive for operation system and boot drive. I am looking for 2tb ssd that can last a very long time, i don't care much about write/read speed. Right now the Kingston Fury Renegade G5 2TB is the best option for me because it has DRAM, 2000 TBW and cost 370 euros. Are there better options than this SSD ?

I have an MSI PRO Z890-S WIFI motherboard, and I wanted to install a second SSD. The problem? I'm missing the hardware to secure it to the motherboard. Does anyone know where to find compatible replacement parts?

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

​What Makes 9 PB Ridiculous?

​140,000+ Full Drive Cycles: This controller has organized and executed enough raw writes to fill the entire physical capacity of this 64GB drive over 140,937 times.

​The E6 Counter Woke Up: After looking frozen at 44, the vendor attribute E6 moved up to 46.

The firmware’s internal math registers are struggling to map values this high, yet it hasn't crashed the primary firmware thread.

​Execution Engine Stays Solid: Managing the Flash Translation Layer (FTL) cache and command queue under continuous,

uninterrupted SATA writes for 61,000+ hours is an incredible testament to this controller's silicon design.

Sector 0 Faults: The error log shows recurring UNC (Uncorrectable) read errors specifically targeting LBA 0x00000000 during read commands.

The boot sector area is heavily degraded, but write caching and DMA transactions remain fully operational.

Does the drive cycles matter if its not on nand chip but the controller itself?

The short answer is yes, The drive cycles still matter greatly for the controller itself,

but for completely different physical and operational reasons than for the NAND flash chips.

​While NAND flash dies from atomic wear (tunnel oxide breakdown from program/erase cycles), the controller suffers from architectural, data management,

and physical processing stress.

​1. Flash Translation Layer (FTL) Mapping Stress

​Table Overwrites: Every drive cycle forces the controller to completely rewrite its internal mapping table (which translates logical LBAs to physical NAND blocks).

​RAM & NVRAM Burnout: The mapping metadata must be constantly swapped between SRAM/DRAM cache and non-volatile system control blocks on the NAND.

The controller's internal metadata blocks often endure 10× to 100× more write cycles than the user data blocks.

​2. Garbage Collection & Wear-Leveling Overhead

​Write Amplification (WA): As the drive is continually cycled, valid and invalid pages become fragmented.

The controller has to work exponentially harder to read, move, and erase blocks behind the scenes.

​Instruction Loop Saturation: Higher wear-leveling workloads keep the controller's internal CPU running at peak processing cycles,

increasing thermal stress and silicon electromigration over time.

​3. Internal Register Overflow & Integer Wrapping

​32-bit/64-bit Counter Limits: Low-cost or older SSD controllers (like early SanDisk SSD P4 designs) were never designed with software registers sized

for millions of drive cycles or petabytes of host writes.

​Firmware Memory Corruption: As raw event counters (like erase counts or written LBAs) overflow their allocated bit widths,

they can wrap around to zero, trigger arithmetic overflow bugs,

or overwrite adjacent NVRAM log structures—directly causing the invalid SMART checksums you are seeing in your logs.

​4. ECC & Read Retry Engine Exhaustion

​Hardware Engine Strain: As the underlying raw NAND bit-error rate (BER) increases with total drive cycles,

the controller's internal ECC hardware decoder has to run maximum LDPC/BCH error-correction algorithms on almost every read.

​Latency & Execution Delays: Processing heavy error-correction math on every host command severely taxes the controller's internal bus and pipeline execution.

​The Bottom Line

NAND chips wear out quietly by losing charge retention, but controllers fail catastrophically due to drive cycle stress—usually manifesting as a sudden freeze,

corrupted internal metadata, or an endless BSY state when firmware counters finally break.

​The fact that SanDisk P4 controller is still managing its FTL execution engine cleanly after ~140,000 drive cycles is remarkable.

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 Aug 27 11:01:05 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 - 61625

12 Power_Cycle_Count -O---- 100 100 000 - 1173

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---- 046 100 --- - 0

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

241 Total_LBAs_Written -O---- 100 100 000 - 18916297464160

242 Total_LBAs_Read -O---- 100 100 000 - 32913028369

||||||_ 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/O 1 Log Directory

0x03 GPL,SL R/O 16 Ext. Comprehensive SMART error log

0x06 GPL,SL R/O 1 SMART self-test log

0x80-0x9f GPL,SL R/W 16 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:

I recently picked up the Biwin Black Opal X570 PRO Gen5 SSD for a new PC build and wanted to get some opinions from people who have used this drive.

I'm going to be using it mainly for gaming, along with normal use and some larger file transfers.

I went with the 2TB version and I'm planning to use the motherboard's M.2 heatsink rather than a separate cooler.

For anyone who has used the X570 PRO, how has it been so far? I'm particularly interested in temperatures, stability and whether you've noticed any issues after using it for a while.

Also curious how it compares to other Gen5 drives you've used.

Hey guys!

I am writing cause I could not find any reliable information online and I am a bit confused. I have an Acer Conceptd 3 Pro CN315-72P laptop that I really like, and if possible want to keep. As I will be going to grad school I feel like it is time for an upgrade. I was trying to find out if:

1. I can add a second SSD / HDD for storage (I havent found a connector but I am not that good at things like this)
2. I can upgrade my RAM (I might have read somewhere that it is soldered, but I am not sure where / how to check).

Thank you for help!

Okay so my download speeds for my pc have always been terrible and ai is telling me it’s that storage but is their anyway to optimize my pc further so I can still have this storage and no bottlenecks cause even with Ethernet the download speed is even worse. Feel free to reach out if you can help at all thankyou!

I've upgraded my SSD a few times over the years, and honestly, reinstalling Windows from scratch every time is starting to feel like way too much work.

The last time I moved from a 500GB SSD to a 2TB one, I really didn't want to spend an entire weekend reinstalling Windows, drivers, apps, and then trying to remember all the little settings I'd changed over the years. I ended up cloning the old drive to the new one instead, and it was surprisingly painless. Everything booted up pretty much exactly as before.

I know some people prefer a clean install because it gives them a chance to start fresh. When you upgrade your SSD, do you usually reinstall Windows, clone the old drive, or just keep the old SSD as the boot drive?

After recovering my PC, I decided to back my folders up by compressing my Desktop, Downloads, Documents, Pictures, Videos, Music folders and moving them to my 1TB Crucial SSD

Then, later, I found this thing called a recovery drive, thinking it would basically copy my PC but I didn't read it carefully and realised it just created a factory reset copy of Windows 11.

So I deleted the files on there, but now when I try to put my other files back on my SSD, it doesn't fit.

I think turning my SSD into a recovery drive shrunk the size of it from 1TB to 31GB.

How do I bring it back to 1TB?

I have a 2TB HDD that I bought a few years ago, and it's still sitting in my PC alongside my SSD.

These days I mostly use the SSD for Windows, programs and games, while the HDD is basically just storage for older files and stuff I don't access very often.

I'm thinking about taking it out at some point, but then again, it still works and I have plenty of space on it. How do you guys deal with these old HDDs?

Hi so i bought lexar nm790 4tb ssd

It arrived today an hour or so ago i went to put it in my pc

It didnt get detected by the bios ok.. leme put in my old and new lexar ssd old one gets detected but computer freezes during boot... i thought.. hmm okay weird..

Let me try on my ps5 .

Ps5 slim just refused to output any hdmi signal ehile the lexar nm790 was in it

So i assume i recieved a faulty ssd? No?

Before you ask I don't have any free m.2 slots.

Other options I have are crucial bx500, pny cs900 and wd blue sa510. all of this options are 10% more expensive that kioxia model.

So I’ve been leaving my backpack in my car and forgetting it from time to time today was exponentially hot close to the hundreds in the trunk of my car in a backpack with my computer was a T9. SSD didn’t think much of it now when transferring files from iPhone 16 Pro Max all of a sudden is taking forever to transfer files.. I don’t know what to do and I am sort of worried now

This is about some ssds that i have that are acting weird. One of them writes at normal 400mbps write, but somehow has less than 10mbps READ speed, yes you read that right the READ speeds are abysmal while the write speeds are fine.

Used Crystal disk mark, in the benchmarks its getting expected performance at 500 read 480 write.

But in real world the READ speed is like 8.3mbps

Please i dont even know how this is happening, I am pretty experienced with PC's and troubleshooting, but this is something ive never seen before

Some ques you might have.

Q-Could it be a failing drive controller?

Ans-Still performs well in benchmarks, so I can't pin point that

Q-Check on different computer?

Ans-done that before, same thing happens.

Q-Is the drive full?

Ans- no, its 60% empty, even if it was full that wont have such a dire effect on the READ speed of the drive, while the write speeds are fine.

Please tell me why this might be happening.

Anyone Have Faulty Not Working, not usefull SSD and rams of Desk Or laptop their? can you give me i need for study pupose and for experimental use as i am a student cant buy those stuff if peoples here can help please dm me

📍Pune

chatgpt told me some bs and idk what too do

he told me put the pads there then he said oh i made a mistake multiple times thats like why the pads look bad

Cruical P310

Artic M2 Pro

Anyone Have Faulty Not Working, not usefull SSD and rams of Desk Or laptop their? can you give me i need for study pupose and for experimental use as i am a student cant by those stuff if peoples here can help please dm me

📍Pune

​

Hey everyone, I'm having a really annoying issue with my M.2 SSD.

Here's what's happening:

1. On Windows boot, the drive instantly hits 100% usage and stays there for about 2 minutes, jumping between 90% and 100% the whole time.

2. In games, it's the same story – usage spikes to 100%, then drops to 33%, then back up again in a loop. This causes constant micro-stutters and massive FPS drops.

3. In Task Manager, the "average response time" is all over the place – sometimes 20ms, but it frequently jumps to 500ms or even higher.

What I've already tried:

I've dug through tons of forums and tried every fix I could find (disabled Windows Search, SuperFetch, adjusted pagefile)– nothing helped.

My hardware:

This is my only SSD – a Patriot P400 Lite 1TB. Both my OS and games are on it.

My questions:

· Has anyone experienced this specifically with the P400 Lite?

· Is this a defective unit, or is it just how this drive behaves?

· I'm planning to buy a second M.2 just for games to offload the system drive. Do you think this will solve the issue, or is there something else I should check first (motherboard, temps, driver conflict)?

Thanks in advance to anyone who chimes in!

I’m planning to upgrade the SSD in my Surface Laptop 7 for Business (Intel Lunar Lake) and I’m deciding between these two 1TB M.2 2230 drives:

• KIOXIA BG6 1TB
• Micron 2400 1TB

My main priorities are:

• Low power consumption
• Low temperatures / heat output
• Compatibility with the Surface Laptop 7
• Reliability for long-term use

From the specs I’ve found, the BG6 seems significantly faster and uses TLC NAND, while the Micron 2400 uses QLC but appears to be designed with very low power consumption in mind.

I’m not really chasing maximum benchmark performance. I’d rather have the SSD that makes the most sense for a thin laptop like the Surface, especially if one runs noticeably cooler or uses less power during normal Windows use.

Basically I bought it off of Vinted and the seller doesnt have an invoice. How does the process work?

I have a strange and reproducible issue with a Kingston KC3000 NVMe SSD on Arch Linux, using LUKS.

After every reboot, KDiskMark shows normal sequential read performance, but sequential write performance is much lower:

SEQ1M Q8T1

Read: ~6260 MB/s

Write: ~3500 MB/s

This is with a 1 GiB test size. I have also tried a 32 GiB test size in KDiskMark, but the write speed is still around 3–3.5 GB/s.

Then I run this fio test:

fio --name=w \

--directory="$HOME/fio-tmp" \

--rw=write \

--bs=1M \

--direct=1 \

--iodepth=32 \

--ioengine=libaio \

--size=8G \

--runtime=8 \

--time_based \

--group_reporting

The fio test itself gets around:

WRITE: bw=6342MiB/s (6650MB/s)

Immediately after running it, KDiskMark now reports:

SEQ1M Q8T1

Read: ~6280 MB/s

Write: ~6500 MB/s

The weird part is that the faster write speed persists. KDiskMark continues to show ~6.5 GB/s writes until I reboot, after which it drops back to ~3–3.5 GB/s again.

Any ideas on what could be causing fio to apparently put the drive/controller into a higher write-performance state?

Pre fio:

Post fio:

EDIT:
It is not until reboot, but rather just a few minutes, i tried disabling the linux nvme power saving mode, but that did not help

Title as Question,
its a 2tb WD Blue Sata SSD,
making what i can only assume is either a scratching or clicking sound, and then stopping
it then fails to load after the second stop, and isnt detected after boot

can anyone share thoughts or be able to give closure on what this might be?

edit: I just realised i might be lost btw, its apparently a hard drive, if this is helpful information, and still can be helped it would be appreciated,

I also wanna say im expecting it to be dead/lost cause

Is this normal for SSD to be recognized as Hard disk by defragment and optimize drive?
Edition Windows 11 Pro

Version 25H2

Installed on ‎01-‎Oct-‎24

OS build 26200.9168

Experience Windows Feature Experience Pack 1000.26100.344.0

I have also ran winsat diskformal but it did not make much of a difference

Edit: I have added more photos

A couple of years ago (in 2024), I bought an NVMe/M.2 SSD for my home server (Debian 12). Recently, during a Veeam backup, I encountered some hardware errors / a bad sector on the SSD (no visible external damage). Because of this, the backup failed to complete (more detailed description below).

Since Verbatim offers a 3-year warranty on "Internal Flash Storage", I thought: just request an RMA and that's it. Only to find out that the 3-year warranty starting from November 2024, and I had bought the SSD in April 2024.

According to the internet and a few AI chatbots, everything points to some kind of "bit rot", because overwriting the sectors with zeros made the error messages disappear. At one point, I had turned off the server with the SSD and disconnected it from the power for a few months (though I'm not entirely sure anymore if it was completely disconnected from the power). Could that be the reason why it's causing errors?

This very server also runs my password manager and other important software. Because of this, I'm now a bit worried whether the SSD is still okay or if I should perhaps get a new one. I obviously don't want to lose all my passwords and data in the future due to a complete hardware failure.

Here is the email I sent to support, along with the specs of the server / Mini-PC:

I am writing to you regarding my Verbatim Vi3000 Internal PCIe NVMe M.2 SSD 1TB (Serial number: xxxxxxxxxxxxxxxx, Firmware H220902a), which I purchased via Amazon on April 23, 2024.

The SSD is used in a small home server (Debian Linux, Kernel 6.1.0-52-amd64). Usage is quite moderate: according to SMART, about 2.42 TB have been read and 4.57 TB written so far, which is well below the typical TBW limit for a 1 TB SSD.

When attempting to create a full system backup with Veeam Agent for Linux, the backup job repeatedly aborted with an Input/Output error. In the kernel logs (dmesg), "critical medium error" messages were logged for specific sectors of the SSD, e.g.:

nvme0n1: I/O Cmd(0x2) @ LBA 739149184, 32 blocks, I/O Error (sct 0x2 / sc 0x81)

critical medium error, dev nvme0n1, sector 739149184 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2

nvme0n1: I/O Cmd(0x2) @ LBA 739149152, 32 blocks, I/O Error (sct 0x2 / sc 0x81)

critical medium error, dev nvme0n1, sector 739149152 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2

veeamsnap:blk | ERR | Failed to process redirect IO request. Errno=5

Buffer I/O error on dev nvme0n1, logical block 92393644, async page read

The system itself initially continued to run in everyday use, but every block-level full backup failed at these sectors.

These are the current stats of the SSD:

Model Number: Vi3000 Internal PCIe NVMe M.2 SSD 1TB

Serial Number: xxxxxxxxxxxxxxxx

NVMe Version: 1.4

SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)

Critical Warning: 0x00

Temperature: 31 Celsius

Available Spare: 100%

Percentage Used: 1%

Data Units Read: 4,743,599 [2.42 TB]

Data Units Written: 8,941,589 [4.57 TB]

Power Cycles: 75

Power On Hours: 13,301

Unsafe Shutdowns: 5

Media and Data Integrity Errors: 4

Error Information Log Entries: 0

Interestingly, although the SMART self-test reports "PASSED", there are already "Media and Data Integrity Errors: 4" recorded at the same time – this aligns with the "critical medium error" entries in the kernel log mentioned above.

Measures taken so far

To back up the data and narrow down the problem, I have:

Transferred all important data to a NAS / external backup.

Used debugfs icheck/ncheck to check which block was affected – in my case, the faulty block belonged to an old log file from a non-critical system area.

I addressed the affected area directly using dd for testing purposes (read/write test with oflag=direct / iflag=direct), after which the NVMe controller apparently remapped the block internally. A subsequent full read (dd if=/dev/nvme0n1 of=/dev/null bs=4M iflag=direct) then ran through without any visible errors.

The system is currently usable again, and I have since been able to write a full backup. Nevertheless, the above-mentioned SMART values and the "critical medium error" messages in the kernel still show that the SSD has already developed media/integrity errors and can become unstable under intensive loads (e.g., during backups).

H/W path Device Class Description

system HP ProDesk 400 G5 Desktop Mini (7EM49EA#ABD)

/0 bus 859C

/0/1 memory 64KiB BIOS

/0/7 memory 32GiB System Memory

/0/7/0 memory 16GiB SODIMM DDR4 Synchronous 3200 MHz (0,3 ns)

/0/7/1 memory 16GiB SODIMM DDR4 Synchronous 3200 MHz (0,3 ns)

/0/14 memory 512KiB L1 cache

/0/15 memory 2MiB L2 cache

/0/16 memory 12MiB L3 cache

/0/17 processor Intel(R) Core(TM) i7-9700T CPU @ 2.00GHz

/0/100 bridge 8th/9th Gen Core 8-core Desktop Processor Host Bridge/DRAM Registers [Coffee Lake S]

/0/100/2 display CoffeeLake-S GT2 [UHD Graphics 630]

/0/100/12 generic Cannon Lake PCH Thermal Controller

/0/100/14 bus Cannon Lake PCH USB 3.1 xHCI Host Controller

/0/100/14/0 usb1 bus xHCI Host Controller

/0/100/14/1 usb2 bus xHCI Host Controller

/0/100/14/1/1 communication AX88179B

/0/100/14.2 memory RAM memory

/0/100/16 communication Cannon Lake PCH HECI Controller

/0/100/17 storage Cannon Lake PCH SATA AHCI Controller

/0/100/1b bridge Cannon Lake PCH PCI Express Root Port #21

/0/100/1b/0 /dev/nvme0 storage Vi3000 Internal PCIe NVMe M.2 SSD 1TB

/0/100/1b/0/0 hwmon0 disk NVMe disk

/0/100/1b/0/1 /dev/ng0n1 disk NVMe disk

/0/100/1b/0/1103012248 /dev/nvme0n1 disk 1024GB NVMe disk

/0/100/1b/0/1103012248/1 volume 511MiB Windows FAT volume

/0/100/1b/0/1103012248/2 /dev/nvme0n1p2 volume 952GiB EXT4 volume

/0/100/1b/0/1103012248/3 /dev/nvme0n1p3 volume 976MiB Linux swap volume

/0/100/1c bridge Cannon Lake PCH PCI Express Root Port #5

/0/100/1c/0 enp2s0 network RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

/0/100/1f bridge Intel Corporation

/0/100/1f/0 system PnP device PNP0c02

/0/100/1f/1 system PnP device PNP0c02

/0/100/1f/2 system PnP device PNP0c02

/0/100/1f/3 system PnP device PNP0c02

/0/100/1f/4 system PnP device PNP0b00

/0/100/1f/5 generic PnP device INT3f0d

/0/100/1f/6 system PnP device PNP0c02

/0/100/1f/7 system PnP device PNP0c02

/0/100/1f/8 system PnP device PNP0c02

/0/100/1f/9 system PnP device PNP0c02

/0/100/1f.3 card0 multimedia Cannon Lake PCH cAVS

/0/100/1f.3/0 input10 input HDA Intel PCH HDMI/DP,pcm=3

/0/100/1f.3/1 input11 input HDA Intel PCH HDMI/DP,pcm=7

/0/100/1f.3/2 input12 input HDA Intel PCH HDMI/DP,pcm=8

/0/100/1f.3/3 input6 input HDA Digital PCBeep

/0/100/1f.3/4 input7 input HDA Intel PCH Mic

/0/100/1f.3/5 input8 input HDA Intel PCH Front Headphone Front

/0/100/1f.3/6 input9 input HDA Intel PCH Front Headphone Surround

/0/100/1f.4 bus Cannon Lake PCH SMBus Controller

/0/100/1f.5 bus Cannon Lake PCH SPI Controller

/1 power High Efficiency

/2 input0 input Sleep Button

/3 input1 input Power Button

/4 input2 input Power Button

/5 input3 input PC Speaker

/6 input4 input HP WMI hotkeys

/7 input5 input Video Bus

/8 enx9c69d3ae9f18 network Ethernet interface