Windows 10: Lost access to drive - "Access is Denied"

I am not very Technical , but for my understanding, if there is a "Command Operation" going on , the Drive will not Spin Down.
So, how should that exactly go?!
I have a Seagate and it also happened, but I do not know if it has the same feature as WD green.
Well, seems that it is recognized that the problem has to do with "Power". That is a least a point.
I would like to hear from WD what they say about that explanation, for me it is not convincing.

EDIT: Also, should not forget, seems it also affects Internal Drives as well , although I do not if they were WD green.

 

I don't think the drives are spinning down during a write. I think they are literally dropping out like if I just physically yanked the drive out. I don't' know what would cause this but that's where Icy Dock suspects it's Intellipark. Of course this makes me wonder why this never happened in the years I've been using these drives in various enclosures on my old system.

I did have to return an older model Mediasonic enclosure a couple years ago that was USB 3. The USB 3 refused to work with my USB 3 card on my old PC. My PC just wouldn't see the drives. So I sent it back for their esata version which worked great with my esata card (the same one that is on my new Windows 10 PC). This is what I was running into last week before my corruption hit - my new PC wasn't seeing the drives over USB 3. It was seeing them over esata. But then I keep remembering how I had that freeze-up this week when I was trying to make a system backup, and that was over esata. So back to square one again.

I'm far from an expert, and it seems this issue is stumping the guys at Icy Dock too, so this is a tricky problem for sure. What makes this problem so bad is the potential for data loss, which has already happened.

 

"I had that freeze-up this week when I was trying to make a system backup.." exactly as in my case. Almost at the end of Backup, it stopped with an 0x??????? error and Drive was GONE!

EDIT: Drive was working well, was doing the Backup, and it should have been a "power drop" just in the middle ?!
The Drive itself is perfect, I put it in other enclosure, have been working with it and no issue.
There is something wrong, I hoppe people will find that out.

EDIT2: I also was upgrading from 8.1 to 10 and it just happened 12h after upgrade.

EDIT3: I do not know if it is related, but I had 2 Anti-Virus Drivers Leftover , I used their Removal Tools that are available on Internet. I had uninstalled the AV long time ago, but they have left some pieces back.
Now system is cleaned, i am using only Windows Defender.

 

Could I be missing a BIOS setting for my motherboard that affects how multiple drives are seen in enclosures over esata/USB? Just a guess because I have no idea if any settings int he BIOS could affect the was enclosure drives are seen.

I did get a BIG Windows update 2 weeks ago. It was an automatic Windows update. I think it was the Windows 10 anniversary update which updated my system from my clean-installed Windows 10 to the anniversary update. Just thought I'd mention it. I hadn't tried my enclosures on the new PC before that update so I have no idea if that played any part in my drive issues.

 

No, I do not think it has to do with BIOS, and I have never seen such a Setting in BIOS.
The Problem is around Enclosure - Power Supply or Windows itself or Other Software.
As it happens also with internal Drives, seems Enclosure will be not the main problem, although it could have been "our" problem.
Thinking back, my backup initialized and was running for over than 30 min., without issues and at a point there was an error.
There was no other Applications running, neither I was working in PC. It was only Backup running, I always do it like that.
I think it has to do with Migration of the OS, from W7 or W8 to W10.

 

I think you're misunderstanding me somewhere. It doesn't happen on my internal drives. Only external enclosures. I just meant currently I'm putting the drives that were previously in my enclosures in my PC (internally) to copy my data safely, since I can't trust my enclosures.

I have been copying using Teracopy all morning to a new internal drive. The only problem I'm having copying files internally is Teracopy keeps throwing up "out of memory" errors which is a known issue with Teracopy. It seems to hate some of my folders with thousands of tiny files inside. But I use Teracopy because it verifies the copy afterwards with CRC. I normally don't need to copy such large amounts of files all at once but I'm moving data around to clear some older drives for testing my enclosures without worrying about permanently losing my data if I continue to have corruption in my enclosures.

 

Rivre, I'm with Linw on this. One person in another thread/Forum had a problem similar to yours, but he only had one drive in his enclosure. It turned out to be a cable that caused his problems, so I'd start by replacing the cable first and have only one drive in the enclosure.

Then if that doesn't work, I'd follow Linw's suggestions.

 

Since this appears to be affecting multiple enclosures, all connected to a different port with different cables, I can safely rule out bad cables.

I think at this point trial and error and testing is required. Which is why I'm trying to backup some data today to clear up a couple older drives to use for testing purposes. Hopefully Icy Dock follows through and sends me a replacement enclosure with their new firmware for testing. There's of course no guarantee their enclosure is even the issue. But maybe if their new firmware works with those green drives without further corruption, that would narrow it down greatly. I still doubt it, but obviously something is to blame so I have to start somewhere.

 

I understood you very well.
You are looking for an answer for the failure, me too. I already did that question and nobody answered me.
That with accessing Drives is not only happening with external Drives, so far I could read from posts in the Forum.
So far I can see, the problem is arising with people that was upgrading to W10 and had Drives where W7/W8 had Initialized it. So, that may be the center of the problem.
Concerning Ice Box or other enclosure, it just need to be a poor contact and you have a big problem.
That is a question of the Quality that products have, if they are passing a Q&A certification. Nowadays makes I have the feeling , some people around the world are avoiding it and filling the Markt with cheap and very poor products, while they making money, the "good ones" have no chance and WE, the ones that pay, have the trouble to solve.
cheers.

 

Agreed on the cables; for some reason, when I first opened this thread, there were only two pages, but now there are four, so it looks like I may be a little late to the party. *Smile

Good on freeing up a couple of hard drives; if I were doing it, I think I'd go for the newest one (mainly to rule out a [possibly] failing hard drive). Secondly, I would remove every device connected to my computer; all the way down to a flash drive, in order to rule out interference by anything else.

If I've read correctly, you're running Windows 10; however, I haven't seen which version. Are you running the Anniversary Update (Build 14393.xxx I think)?

When I see a company like your Icy guys doing the right thing, it makes me know they're one of the good guys, and in this instance, they seem to be the exceptional guys.

 

A couple of other comments, if I may . . .

Every computer I've upgraded from Windows 7 to Windows 10 has had some kind of problem, so now my standard operating procedure is to upgrade, then immediately do a clean install. Yes, it means having to reinstall all the programs on the computer, but the client is happy with his/her upgrade. Then there are those who have upgraded from Windows 7 and swear they've not had the first problem. So, YMMV.

Insiders who have updated to Build 14942 have had the experience of external hard drives not being seen. It may be important that we know exactly what version of Windows 10 is on your computer; that's why I asked the question above. Also, your system specs only say Windows 10 64 bit, so we can't tell which version you have.

 

You're doing what I would have done by reshuffling drive content using the internal SATA connections and then move to testing enclosures with drive(s) that can be sacrificed without pain!

But, sods law will come into play, and you won't get it to fault after that!!!!

Hope Icy Dock ship you a new enclosure quickly. They will want to see your problem sorted as much as anyone I've no doubt.

As always, best wishes and good luck.

 

Yup, the Anniversary update installed itself a couple weeks ago on it's own. Before that I had a clean install from my retail Windows 10 (64bit) thumb drive. Of course I have all my software installed as well. My PC updated again the other day so I would say it's fully up to date.

 

I talked to Gigabyte (my motherboard manufacturer) earlier over the phone to see if they had anything to suggest. He highly doubts it could be a Windows 10 fault. He said it could quite possibly be an incompatibility issue between my enclosures and the 100 chipset used by the motherboard. He said that chipset is standard now on all motherboards, but that the enclosures, especially being older, likely would not have been tested on them, so compatibility could be spotty. He thinks the idea of the green drives being at fault may be going down the wrong path, but didn't rule it out since he's unfamiliar with that particular issue. Icy Dock is strongly leaning in that direction. I'm going to mention the 100 chipset to Icy Dock and see if they can verify that their enclosures are tested and compatible. Maybe these enclosures just don't play nice with this chipset, though if that was the case I would have thought I'd be finding that out in these forums.

 

rivre, did you also changed the Motherboard? I think your enclosures were working fine in W7 and I was assuming it was the same Motherboard with the 100 Chipset.
Anyway, all my 5 external Drives were working fine in W8.1 and just 1 went bad in W10 ver 1511, no Hardware changes here, only OS was changed, and I have no 100 Chipset. From that 5 Drives , 2 of them are in Icy Box and 1 went bad.
All sort of issues with Drives was arising with W10.1607 update and I doubt all the people had a 100 Chipset and a Icy Box or a WD Green, many cases they were even internal Drives.
MS recognized there were a "small number" of people suffering from that problem with Drives. Well, 1% of 350 Million is still a huge number.

As I said before, just as a precaution measure, I put the Icy Box away. Background thought was If there is a bad soldering point, with time it will get worse until the day comes were the resistance will be so high that voltage will drop and that could lead to the failure of disconnecting Drive in middle of operation. The error I had was in middle of System Backup.