Windows can't detect disk (ssd)

Han Solo

Contributor
Joined
Feb 9, 2018
Posts
420
I did try the power cycle instructions to fix the ssd that are posted on this forum but it didn't work. It is a relatively new Samsung 860evo 1TB it was working fine until recently. Before having this problem it was telling me that there was something wrong with the recycle bin. Everyday when I turn on the PC 2 things I do first is run speedfox and TFC by OldTimer. I wonder if that had anything to do with it. Also I have detected issues with reparse points using "windows repair" by tweaking.com. I've used the program to fix it but it keeps coming up. http://speccy.piriform.com/results/1haSOn7kJBZnDXpICjki58y
 
I am using this drive externally using a dock. I made another scan and the reparse points seem fine now. I attempted a disk scan and fix with elevated command prompt and it did fix disk errors. It works now but should I place the files on another disk?
 
Sometimes we can overdo the "tweaks and maintenance" for sure. Unless someone directs you to use the Tweaking.com's Windows Repair, I would be careful with it as it is a powerful tool and can cause problems if one doesn't fully understand it's inner workings. I'm not suggesting you do not understand, I'm only imparting friendly advice from experience.

@softwaremaniac What is that tool you recommend to test drives?
 
I will be using Cleanmgr+ instead of TFC since it seems to be a good substitute. And I'll be backing up my files and maybe reformat the drive.
 
I will be using Cleanmgr+ instead of TFC since it seems to be a good substitute. And I'll be backing up my files and maybe reformat the drive.
Just stay away from the registry cleaning on any app. System Ninja is another good (safe) one to use.

Or, Windows own cleaner is the best bet. You can get to extra settings by doing this: Open an elevated command prompt and copy and paste this into it. %SystemRoot%\System32\Cmd.exe /c Cleanmgr /sageset:65535 & Cleanmgr /sagerun:65535
 
I have moved all my files to a 2TB SSD and then I formatted the 1TB SSD which is now empty. It seems to me that perhaps there are errors on the drives when the drive are too full. In other words when the drives turn red when you see them in "This PC". When I transferred the files the 2TB drive did turn red so I took out 20 gb then 10gb of files until it turned blue. After a while when I checked to see the files in the 2TB drive there were folders missing even though it indicated the same used space as before. I attempted another fix disk with an elevated cmd prompt and windows found a corrupt master file table which it couldn't recover twice.
 
If you are talking about in Windows Explorer, the red is an indicator the drive is full.

drive-space.jpg
 
That's correct. I was just moving files around in order to make sure it wouldn't be full. I ran TestDisk on the 1TB SSD and it stated that the structure is OK and after a deeper scan it revealed that a part of the disk was not recoverable. TestDisk provided an option to write, Should I do that?
 
I am not familiar enough with Testdisk to confidently answer that. Let me do some research and I'll get back with you.

Could you post some screenshots of your actions in Testdisk while I'm researching, please? What is it asking to write for instance, what it's recovered?
 
That partition could be the recovery partition. It's protected and probably why you are getting that message.

Could you open that in disk management and post a screenshot, please?
 
Does your SSD disk visible in BIOS?
If not, try to install new MB drivers, otherwise looks like your SSD is damaged
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top