F5F Stay Refreshed Hardware Desktop SSD issue arose following a power cut; reports it appears full and slows down the system.

SSD issue arose following a power cut; reports it appears full and slows down the system.

SSD issue arose following a power cut; reports it appears full and slows down the system.

A
Apel29
Member
192
01-10-2024, 05:34 PM
#1
Power failure occurred in the house yesterday. Surge protection was handled previously. The PC started slowly after booting, but everything appears normal except the SSD drive (DSmile which now reports full capacity. Any activity using it freezes for about ten minutes. Removing the SSD resolves the issue; the computer restarts normally and operates as expected. A friend suggests a file might have been written to the drive during the outage, making it seem infinitely large. This doesn’t affect performance whether the drive is plugged into the case or connected via USB adapter to a USB 3 port. Windows interprets D: correctly regardless of connection type. Running chkdsk shows accurate usage vs. free space; results at the end confirm this. Samsung utility offers limited help, but it still displays the drive as full. Windows can’t clean the disk or delete files, so I’m considering next steps or checking if it’s damaged. The system runs on Windows 10 Home version 22H2 with a Samsung B550M DS3H motherboard, AMD Ryzen 7 3700X, and NVIDIA GeForce RTX 3060 Ti. Storage includes a 980 GB Samsung SSD (CSmile and a 1 TB Samsung SSD (DSmile, which is currently problematic. EVGA power supply and chkdsk logs are also reviewed. The drive shows errors during scans, but no further action is needed at this time.
A
Apel29
01-10-2024, 05:34 PM #1

Power failure occurred in the house yesterday. Surge protection was handled previously. The PC started slowly after booting, but everything appears normal except the SSD drive (DSmile which now reports full capacity. Any activity using it freezes for about ten minutes. Removing the SSD resolves the issue; the computer restarts normally and operates as expected. A friend suggests a file might have been written to the drive during the outage, making it seem infinitely large. This doesn’t affect performance whether the drive is plugged into the case or connected via USB adapter to a USB 3 port. Windows interprets D: correctly regardless of connection type. Running chkdsk shows accurate usage vs. free space; results at the end confirm this. Samsung utility offers limited help, but it still displays the drive as full. Windows can’t clean the disk or delete files, so I’m considering next steps or checking if it’s damaged. The system runs on Windows 10 Home version 22H2 with a Samsung B550M DS3H motherboard, AMD Ryzen 7 3700X, and NVIDIA GeForce RTX 3060 Ti. Storage includes a 980 GB Samsung SSD (CSmile and a 1 TB Samsung SSD (DSmile, which is currently problematic. EVGA power supply and chkdsk logs are also reviewed. The drive shows errors during scans, but no further action is needed at this time.

I
209
01-10-2024, 05:34 PM
#2
Execute chkdsk d: in an admin window. The command checks D: for issues without making changes. In PowerShell it will scan the filesystem but won’t alter anything. To repair, use chkdsk d: /f
I
IninhaGamer_BR
01-10-2024, 05:34 PM #2

Execute chkdsk d: in an admin window. The command checks D: for issues without making changes. In PowerShell it will scan the filesystem but won’t alter anything. To repair, use chkdsk d: /f

T
tydall
Member
137
01-10-2024, 05:34 PM
#3
Executed as administrator with /f flag. System path: C:\Windows\system32. File system detected as NTFS, volume labeled TJH. Initial stage analyzed basic file structure. Processed 388,352 records, verified all files successfully. Stage duration for file verification: 2.92 seconds. Handled 57 large files, no orphan recovery needed. Checked bad records, found none. Bad record inspection took 0.26 milliseconds. No errors encountered during the process.
T
tydall
01-10-2024, 05:34 PM #3

Executed as administrator with /f flag. System path: C:\Windows\system32. File system detected as NTFS, volume labeled TJH. Initial stage analyzed basic file structure. Processed 388,352 records, verified all files successfully. Stage duration for file verification: 2.92 seconds. Handled 57 large files, no orphan recovery needed. Checked bad records, found none. Bad record inspection took 0.26 milliseconds. No errors encountered during the process.

A
AtaberkIncesu
Member
105
01-10-2024, 05:34 PM
#4
It looks like the system is stuck. Diskpart might help reset it, then you can reformat or repartition it. All your files are lost, so it’s risky—though it could work for a new drive later. Don’t rely on it for critical data.
A
AtaberkIncesu
01-10-2024, 05:34 PM #4

It looks like the system is stuck. Diskpart might help reset it, then you can reformat or repartition it. All your files are lost, so it’s risky—though it could work for a new drive later. Don’t rely on it for critical data.

N
NoobHacker
Junior Member
32
01-10-2024, 05:34 PM
#5
I believe I've fixed it—links inside memory blocks got broken when moving to the next block, so everything is now recoverable after reformatting. Thanks, all of you.
N
NoobHacker
01-10-2024, 05:34 PM #5

I believe I've fixed it—links inside memory blocks got broken when moving to the next block, so everything is now recoverable after reformatting. Thanks, all of you.