Hard drives keep locking on shut down

jfh596

Reputable
Jun 10, 2015
2
0
4,510
I have an Asus Essentio CM6870 that I purchased back in the fall of 2012. Not too long ago I got fed up with Windows 8 and purchased a copy of Win 7 from Amazon.

I had a hard time installing it until I found a setting in the BIOS that prevented legacy OS's. I changed the setting and installed 7 and it had been running fine until a few months ago.

In the interest of improving performance and clearing out all the garbage that had built up over time I ran WipeDrive 6 and attempted to reinstall Windows 7.

No problem with WipeDrive or Windows 7, but now every time I start my machine the hard drives display as locked and I get a message saying no bootable device has been found.

The only workaround I have found is to put the WipeDrive CD in, start it in text mode, and run one of their drive unlock commands. This gets me through to the next time I restart my machine, at which point I need to repeat the whole process.

My BIOS is American Megatrends Inc. 0606 and I strongly suspect the issue lies with one of the settings there. But I have tried to tweak them all with no luck.

Has anyone seen this before? Any help would be appreciated.
 
Hey there, jfh596.

I'd recommend that you take a look at the website of the software and check the knowledgebase. I think I've heard that it has a solution for this issue - hopefully a permanent one. If you have trouble finding it - try googling "hard drive locked" (without the quotes) along with the program's name.

Hope that helps.
Boogieman_WD
 

jfh596

Reputable
Jun 10, 2015
2
0
4,510


What software? WipeDrive? As far as I can tell they are not causing the issue since I haven't run that program on my machine in months.

I spoke to one of their reps and they said it wasn't them. I suspect it is something in the BIOS, although it is curious that the only workaround I have found does involve a WipeDrive unlock command...

 
Well you could still search for that, just to see what pops-up. Having in mind this solves the issue (even if it's not a permanent solution), then it might be connected somehow. on the other hand, if you suspect that the BIOS might be at fault here, I'd recommend that you reset it or try to update it if possible, to see if that fixes the problem.