Unallocated space resulting in I/O device error?

DriveJunky_95

Honorable
Jul 19, 2013
22
0
10,510
I think a bad cut/paste has somehow resulted in 1MB of unallocated space at the beginning of a storage drive preventing it from being accessed correctly.

"The request could not be performed because of an "I/O" device error."

Last night I went to cut/paste a movie file and ended up cancelling the operation because it took abnormally long and couldn't hear the drive spinning up.....

In computer management there's a new 1MB of unallocated space. The rest of the drive is all there, reading healthy and with the correct partitions.

I can open the drive in My Computer and see the file structure, but opening a folder results in the error.

In elevated CMD I can't run CHKDSK /F /R. It results in "The type of the file system is RAW."

/sfc scannow tells me that there is corrupted data, but it can't be recovered. If it's directly related to the 1MB of space is unknown as of right now.

Have tried assigning a new simple volume, but the action doesn't follow through - the process can't be started and the option can't be clicked (although it is highlighted).

HOW in the world do I remove/combine the 1MB of space so I can access the rest of the drive? Preferably without moving all 931GB of files and cleaning the drive completely.
 

DriveJunky_95

Honorable
Jul 19, 2013
22
0
10,510


Logging this for any future readers. Solution found.

I/O would suggest a problem with the cord (Input/Output) and/or a drive table that's out of sync, corrupted data would suggest a failing drive. Since I could access the file structure but not any actual files, it couldn't be determined that the files are actually corrupt. Slow spin ups are just slow spin ups and marketing gimmicks *cough*. Upon unplugging/plugging the SATA cable the 1MB of space is gone (beyond me) and the drive is back to operating normally. It helps to use your head and not jump the gun - saved me $100. Woot!