Loading...

access files on corrupt HDD

Windows RT 8.1

Asked
Asked by: god_0

i recently installed windows on a new HDD and had to access files from my old HDD to copy over, so i plugged my old HDD into my PC via an external docking bay.

after trying to access my files, it said i did not have permission, and i needed to click a pop up that would give me permission permanently. after clicking it and waiting several minutes, i just found the file online instead. so i went to eject the HDD via the system tray icon. however it told me a program was still using it, so i close all my programs and tried again, but it still said a program was using it, so i waited several more minutes, but no change. so i turned off the docking bay and undocked the HDD. my drive format is NTFS, so i shouldn't have unplugged it. i guess i should have shut my computer down?

but now it says my HDD is corrupt, when i plug it in. it shows me all my partitions, but they all says 0/0 bytes free, and i cannot even view the directories.

is there a way to fix this? without paying somebody hundreds of dollars?

why does windows make me get permission to a folder that i physically have the HDD to? If i have the HDD in hand, i should not need extra permissions, alternatively, i used the same copy of windows for each install, couldn't it have detected that?

could the docking bay have contributed to the corruption?

why am i still using windows?

Answered
Answered by:

For well over a decade, the Windows NT line (Windows NT, 2000, XP, 7, 8/8.1, 10 . . .) has natively used the NTFS format.  NTFS has file level permissions that prevent just ANYONE from accessing the files.  Such permissions are there to give you the protection beyond the physical protection of having to have access to the drive.  Same with things like encryption (which you did not mention, but if you were using any encryption, this could be much worse.)

 

With everything but encryption (in most cases) - physical access does mean you can get the data - but no one said it was supposed to be transparent.

 

What you did was take a drive from one system with one set of accounts and connected it to another system with another set of accounts.  You then STARTED the process of changing all the permissions/ownership on the partition/drive to the new accounts.  Then, before that completed, you forcefully removed the drive.

 

You would have similar issue with other operating systems/other file format and protection schemes (permissions, encryption, etc.) - so Windows, Linux, OS X - doesn't matter.  It's not what OS you are using, but whether or not you take the trouble to understand things before attempting them and have a fallback plan in place (backups, for example.)

 

What exactly happened is not 100% clear - but something like TestDisk might help you.

.-
Shenan Stanley
MVP 2005-2011 & 2013-2015
.-
Answered
Windows Store 26/11/2015 0 Comment 79 views
Loading...

Comments ( 0 )

Notice!
No comments yet. Be first to comment!

Leave a reply