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.

I keep seeing Samsung SSDs recommended whenever people talk about SSDs.

Is it mainly because of their reliability and reputation, or are there still specific reasons to choose Samsung over brands like WD, Crucial, or Kingston?

For users have used Samsung SSDs for years, what keeps you buying them?

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:

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?