Jump to content

Photo

I/O Error (21) after doing a Data Migration

error file transfer help wanted

  • Please log in to reply
6 replies to this topic

#1
TheJayach

TheJayach

    Newbie

  • Supporter
  • 11 posts

I first received this error after I did a Data Migration to a new SSD using Samsungs Magician app

https://i.gyazo.com/...187b905e9c4.png

 

This is the Second Error, which I received on older version of Vortex by downgrading

https://i.gyazo.com/...2be5f2ca110.png

 

These are my Drives-  Vortex and my modded games are stored on my J: drive and my mods are stored on my G: drive

https://i.gyazo.com/...e2f63b1afe7.png

 

My question being how do I remove this error? Ive took a gander in Vortex settings, some Vortex files, and in regedit looking for records of vortex and the D: drive with no luck.

My games work fine so far, it seems to just be trying to read an incorrect path and giving a pesky error

 

Thanks in advance,

     -Jay


Edited by TheJayach, 01 June 2022 - 02:27 pm.


#2
rmm200

rmm200

    Resident poster

  • Members
  • PipPipPipPipPip
  • 2,939 posts

It is not clear from your description, but the following rules apply:

1) It does not matter where Vortex is installed

2) It does not matter where your Downloads archive directory is

3) Mod staging directory must be on the same drive as it's game.

 

I don't know how the Samsung Data Migration works, but if it does a Windows deep copy, all you hard links were converted to actual copies of the mods.

Always Purge from Vortex before moving a game directory. After the move, a simple Deploy fixes it all up.



#3
1ae0bfb8

1ae0bfb8

    Resident Hero

  • Supporter
  • 5,543 posts

what version of vortex did you have, then what version did you downgrade to, and why?

also what is error(21)?

 

ok google search revealed this; https://4ddig.tenors...in-windows.html

 

i'd suggest this isn't a vortex issue although downgrading vortex may give you other issues once you fix your disks.


Edited by 1ae0bfb8, 01 June 2022 - 03:37 pm.


#4
TheJayach

TheJayach

    Newbie

  • Supporter
  • 11 posts

I found an installer in my appdata (AppData\Roaming\Vortex\__update__\vortex-setup-0.18.6.exe) and ran it to see if it would "refresh" the drives it is trying to access, which it didnt, so I immediately updated back to most recent (which is also named vortex-setup-0.18.6.exe). I did not take note of which version was installed after "downgrading"

 

Im certain that this issue does not stem from just Vortex itself, but for some reason it decided to swap the drive letters I guess and its trying to look into my disk drive. 

I believe all I would have to do to fix this is change the D:\ to any of my other drives.

I just cant find out where to go to change it.


Edited by TheJayach, 01 June 2022 - 05:22 pm.


#5
Pickysaurus

Pickysaurus

    Community Manager

  • Admin
  • 21,526 posts

If I were to guess, if you did a copy of your D:\ drive onto a C:\ the registry is now completely borked for some apps.

 

That error appears to be trying to find your Steam install. I would suggest reinstalling Steam over the top of what you have now to try and repair the paths.



#6
1ae0bfb8

1ae0bfb8

    Resident Hero

  • Supporter
  • 5,543 posts

windows disk management may assist you - however, you're very light on detail about your "data migration" so at this point, that's just a wild-ass guess.



#7
TheJayach

TheJayach

    Newbie

  • Supporter
  • 11 posts

My bad, about not being so clear, The Acer B: drive was originally my C: Drive, I recently installed an 870 evo ssd and transferred everything from original C: drive to the new C: 870 evo ssd. Everything went okay with the transfer. I may have moved around my sata cables on my motherboard because I had to use the Disk management tool to re assign 2 of my external hdds. 

 

This is probably one of the most bizarre encounters ive had with windows trying to access files lol







Also tagged with one or more of these keywords: error, file transfer, help wanted

IPB skins by Skinbox
Page loaded in: 0.309 seconds