VulcanTourist Posted October 20, 2020 Share Posted October 20, 2020 What happens if a power failure occurs while Vortex is in the midst of deployment, and has created some but not all of the necessary hardlinks? If another deployment is later started, how does Vortex deal with those existing hardlinks? Does it recognize them as its own creation and simply leave the ones still relevant? Is there a possibility that some could become orphaned and create problems? Link to comment Share on other sites More sharing options...
Pickysaurus Posted October 20, 2020 Share Posted October 20, 2020 Is there a vortex_deployment.json in the folder? If so you might be able to use purge to reverse the existing links and deploy to restore them. Link to comment Share on other sites More sharing options...
VulcanTourist Posted October 20, 2020 Author Share Posted October 20, 2020 Is there a vortex_deployment.json in the folder? If so you might be able to use purge to reverse the existing links and deploy to restore them. The question was hypothetical and not motivated by a personal disaster. Someone at Reddit shared a rather disastrous series of missteps he made with Vortex, beginning with some "backup and restore" dialog that I've never encountered, made progressively worse with each choice he made. I'm not confident that anything is recoverable now, but if I can't quickly assess the current state of things I'll be trying to drag him over to Vortex Support. Why people think r/Skyrimmods is a better resource for troubleshooting their mistakes with Vortex.... Link to comment Share on other sites More sharing options...
rmm200 Posted October 20, 2020 Share Posted October 20, 2020 Not contradicting Picky - but Deploy is completely non-destructive. Just run it again.I would be more concerned about damage Windows does, writing to a disk when power fails. Would not hurt to check your disk for errors. Link to comment Share on other sites More sharing options...
Tannin42 Posted October 20, 2020 Share Posted October 20, 2020 Power outage during deployment shouldn't matter much.What Vortex does is it looks at all links in the game directory that are links to the vortex staging folder. Then it looks at all the files that _should_ be deployed based on the enabled mods and their order. Then it deletes the links that were found but shouldn't be there and creates the ones that should be there and aren't.So if it got interrupted, the next time you deploy it basically just continues where it left off the last time. When Vortex is done deploying it creates a manifest file that says which files came from which mod, that manifest would be incorrect after the power outage until the deployment finishes successfully, but Vortex only requires the manifest if something "unusual" happens. E.g. if the user manually deletes or moves the staging folder outside vortex, the process I described above wouldn't work, in that Vortex can use the manifest can be consulted, but it's really more of a backup. Link to comment Share on other sites More sharing options...
VulcanTourist Posted October 20, 2020 Author Share Posted October 20, 2020 What sequence of events can trigger the "backup and restore" dialog that the person mentioned? He was reticent with details, and I've never even heard of it. Link to comment Share on other sites More sharing options...
HadToRegister Posted October 20, 2020 Share Posted October 20, 2020 What sequence of events can trigger the "backup and restore" dialog that the person mentioned? He was reticent with details, and I've never even heard of it. SETTIINGS-------->WORKAROUNDS------>RESTORE/CREATE BACKUP Link to comment Share on other sites More sharing options...
VulcanTourist Posted October 20, 2020 Author Share Posted October 20, 2020 What sequence of events can trigger the "backup and restore" dialog that the person mentioned? He was reticent with details, and I've never even heard of it.SETTIINGS-------->WORKAROUNDS------>RESTORE/CREATE BACKUPNo, you misunderstand: he described being "forced" to do it by a dialog that appeared when he started Vortex. He was not attempting to do it by choice. Link to comment Share on other sites More sharing options...
Tannin42 Posted October 21, 2020 Share Posted October 21, 2020 Vortex does a sanity check on its database (which stores things like settings, meta information about mods and so on) to find and repair well known corruptions.If that check finds anything off, it will tell the user that it can repair that and if the user proceeds, Vortex will create a backup of the "damaged" db and do its repair, the backup is just in case that the repair itself is overzealous. But what exactly it was that got corrupted I can't tell. The error dialog that shows up does tell the user what exactly it's going to do but you didn't post that (maybe the reddit user didn't) However: Vortex also does periodic backups of the db. If the repair fails but also the corrupted state is - well - actually corrupted, you can still go back to one of the periodic backups that were created before the damage happened, that is what HTR described. Link to comment Share on other sites More sharing options...
VulcanTourist Posted October 21, 2020 Author Share Posted October 21, 2020 This is the Reddit post that I'm referencing: https://www.reddit.com/r/skyrimmods/comments/jee3ed/vortex_suddenly_saying_all_of_my_mods_are/I opened Vortex today and it asked me if I wanted to backup and repair for absolutely no reason. So I proceeded with that. I deployed the mods I changed and it asked me if I wanted to delete 100354 files. So I did it assuming Vortex knows what it is doing. I was then given the option to restore my old vortex state. So I did that. Deployed again and now everything I have is redundant and I am missing masters and plugins like crazy. Apparantly Vortex doesnt have a clue what it is doing so I thought I would post here to get some further instructions before I break things more.It was a cascade of bad decisions made recklessly. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.