Hello. I am using an HP S5-1260 with Windows 10 Pro. I have a Samsung Evo 860 2TB SSD which is not accessible with explorer. On this PC I attempted the command line "chkdsk G: /f /r /x" to fix it but it was taking a long time (18hours) so I shut it down and ran the command for this drive on another PC. It ran faster on the other PC but it was still inaccessible so I ran the command again to give it a second pass. It was still inaccessible after the second pass. But what I did notice was that on both PCs the drive's used space is shown when right clicking for properties via Disk Management.
SSD is not accessible. Access is denied.
- Thread starter Han Solo
- Start date
FreeBooter
Member
You don't need to use /r switch for SSD drives try /f switch.
It really doesn't matter. With a hard drive, I always recommend the /r switch because it implies or includes all the functions of /f, plus it will attempt to locate and recover/repair a bad sector, if possible.
On a SSD, any function that cannot be done will simply be ignored. So running with the /r switch is not detrimental. Whether it does any good is another issue. My point is, however, if you ran with /r, it does no good to run again with /f.
As for time, it is the /f switch which is consuming time. And it can take a very long time to run on a large drive. It typically is best not to interrupt checking and just let it run. While it can take many hours and appear to be hung, it will eventually finish.
Since you tried this SSD in two different computers and were unable to access it from both, it would appear the drive itself is faulty. Did it ever work properly? You could try formatting it but frankly, and especially if still under warranty, you might be best served by contacting Samsung.
See if you can run a less vigorous switch:
chkdsk /c
chkdsk /i
chkdsk
Run Crystal Disk standard edition:
CrystalDiskInfo
Post images into the thread.
Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools for Windows | Seagate
How to use SeaTools for Windows | Seagate Support US
Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan
Access is denied may be related to permission issues:
Disk D: is not accessible. Access is denied on Windows 10 - How to Fix?
chkdsk /c
chkdsk /i
chkdsk
Run Crystal Disk standard edition:
CrystalDiskInfo
Post images into the thread.
Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools for Windows | Seagate
How to use SeaTools for Windows | Seagate Support US
Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan
Access is denied may be related to permission issues:
Disk D: is not accessible. Access is denied on Windows 10 - How to Fix?
Last edited:
Again, this problem occurred on two different computers and now we know the drive was working a couple days ago. Not likely a permissions problem.
FreeBooter
Member
You should have executed /r switch and compare it with /f switch if you do you will notice checking disk for errors with /r switch takes way longer finish with SSD drives.
There is something else I forgot to mention and it may be important. I use the these SSD usually as external drives connected to docking stations (I think that is what they are called). I had trouble with another SSD. In the beginning when I use these drives everything works well and when I shut down the PC I would dismount the drives by right clicking the "Safely Remove Hardware and Eject Media" feature. But sometimes would get a message saying that I couldn't disconnect because the drive was being used by some software or something. I could never find what that drive was doing; if anything. I would search via task manager and I could never see what was going on. So I would just turn off the docking station. I guess something happened during those power downs.
My bad. Sorry. I should have been more clear. Yes, /r will take longer but that is because it is way more thorough and IMO, if the condition of the disk is in question, reason enough to be patient and let it run through completion.
You might want to make sure Quick Removal is enabled for those devices. When enabled, it can degrade performance a little, but it ensures the OS writes all the data to the drive before it moves on to other tasks instead of temporarily stuffing the data into a buffer or cache. When enabled, it (at least in theory) lets you disconnect the external drive almost immediately after you perform a save (or close) operation.
Not sure what to suggest at this point. Since the SSD had the same problem with two computers, it sure suggests the problem is with the SSD.
I have never been a fan of external drive enclosures simply because USB is not nearly as reliable or robust as it should be. If me, I might install it directly in computer and see if I can gain access that way.
I have never been a fan of external drive enclosures simply because USB is not nearly as reliable or robust as it should be. If me, I might install it directly in computer and see if I can gain access that way.
I forgot to mention that there was one particular folder in that I drive that I was frequently using. It did appear in quick access and when I double clicked it I had access to the folder. But still no access to the drive through "This PC". The folder's video and text files were functioning but not the image files. Actually the image files were not opening with d'peg but did with windows photo viewer. I did try to run the "chkdsk G: /f /r /x" command on the drive via externally and let it run. It did state that run time would be 18 hours but then dropped to 2 hours. That didn't work. So I manged to install the drive internally and run the same command on boot but that didn't fix the problem. I did incidentally run HD Tune and no errors were found. For some reason none of the seagate tools work on this pc except for Seatools SSD. Seatools SSD was not able to successfully run a self test (short or extended) to the drive when it was connected externally. It did however run these test when the drive was internal and again no problems were found. I think that's it.
Using EaseUS Data Recovery I found the files in the SSD, at least most of them. Under the Lost Files in the Advanced Scan I found that this drive had 4 partitions (2 NTFS, 1 ExFAT and 1 unknown). This reminds me that I did format this drive between NTFS and FAT32 in an attempt to hook it up to a Fire Stick. It didn't work and so I eventually format it to NTFS in order to view some files in an XBOX. I think that perhaps the reformatting of the drive in order to access files in 2 different devices may have done something? So before I recover the files should I reformat the SSD? Any suggestions?
No, if you format that will possibly erase what you are trying to recover or at least diminish it. You really don't want and writing to the drive at all. Go ahead and recover what you can, then you can reformat as long as you are sure you got everything off of it you need.
I haven't recovered the files yet but EaseUS has discovered is a 12GB Pagefile from a 2TB SSD. Why would a huge pagefile like that be created on a SSD for storage? I'm guessing it was created by xbox since its windows based. Also is there a better recovery tool than EaseUS? Some files have lost file names, is there a way to recover file names perhaps by using the pagefile?
A 12GB Pagefile is unremarkable on any HDD/SDD. Windows 10 does a great job at managing the pagefile. Some think you need to turn the pagefile off with a SSD, I think it needs to be left alone.
Your paging file size should be 1.5 times your physical memory at a minimum and up to 4 times the physical memory at most to ensure system stability. Again, Windows 10 manages this very well.
I have no experience with EaseUS but I have seen others I respect in the industry that suggest its use. I have used Piriforms free version of Recuva with some success in the past. I am also a fan of the minitools selection of software.
All the free versions will have limitations.
Your paging file size should be 1.5 times your physical memory at a minimum and up to 4 times the physical memory at most to ensure system stability. Again, Windows 10 manages this very well.
I have no experience with EaseUS but I have seen others I respect in the industry that suggest its use. I have used Piriforms free version of Recuva with some success in the past. I am also a fan of the minitools selection of software.
All the free versions will have limitations.
Last edited:
Has Sysnative Forums helped you? Please consider donating to help us support the site!