ShadowProtect Recovery Environment
- 
 Ok so I have a system I'm testing with, and I'm kind of stumped as to what is occurring. I can boot into the recovery environment without issue (liveCD), but when I go to launch the application, it opens and then immediately closes (it being the application within the environment). Any ideas? 
- 
 So attempting to run the recovery application manually (CLI) I get an output of segmentation fault. Of course there is nothing (that I've been able to find) that explains what this issue is.
- 
 Tried recreating the recovery media? 
- 
 @dafyre Yep. Also it's just an iso that you mount as a CD into the VM. 
- 
 @DustinB3403 said in ShadowProtect Recovery Environment: @dafyre Yep. Also it's just an iso that you mount as a CD into the VM. How much RAM in the VM? I know that some Recovery CD's need a gig or 2 of ram. 
- 
 @dafyre said in ShadowProtect Recovery Environment: @DustinB3403 said in ShadowProtect Recovery Environment: @dafyre Yep. Also it's just an iso that you mount as a CD into the VM. How much RAM in the VM? I know that some Recovery CD's need a gig or 2 of ram. 8GB. I'm re-restoring my backup and will test with it. As it doesn't really make any sense as to what is causing this. 
- 
  This is the live environment.... and clicking the ICON does nothing. 
- 
 Still same issue... I'm curious if there is something bugged with this VM, It was pulled out of HV, and imported into XS. .. . . 
- 
 @DustinB3403 said in ShadowProtect Recovery Environment: Still same issue... I'm curious if there is something bugged with this VM, It was pulled out of HV, and imported into XS. .. . . Possible, but that shouldn't stop the Application from running... at least I wouldn't think. 
- 
 @dafyre That's the same thing I'm thinking, unless something inside of the VM, isn't visible for some reason.... Like the NIC or local storage. I tested the recovery iso on a different VM (not pulled out of Hyper-V) and it works... 
- 
 @DustinB3403 said in ShadowProtect Recovery Environment: @dafyre That's the same thing I'm thinking, unless something inside of the VM, isn't visible for some reason.... Like the NIC or local storage. I tested the recovery iso on a different VM (not pulled out of Hyper-V) and it works... Make a New VM and restore into that? .... Edit: Or link it to the original HD image giving you the problem. 
- 
 @dafyre that is worth a shot. I'll give it a try. 
- 
 Same issue in a brand new VM, and with a different download of the recovery environment. 
- 
 @DustinB3403 said in ShadowProtect Recovery Environment: Same issue in a brand new VM, and with a different download of the recovery environment. Linked to original disk image, or created a new one? 
- 
 @dafyre said in ShadowProtect Recovery Environment: @DustinB3403 said in ShadowProtect Recovery Environment: Same issue in a brand new VM, and with a different download of the recovery environment. Linked to original disk image, or created a new one? fresh download. 
- 
 did you use the old VDI? 
- 
 @Dashrender said in ShadowProtect Recovery Environment: did you use the old VDI? Same results with old VM, brand new (empty VM) and new and old ISO. 
- 
 @DustinB3403 said in ShadowProtect Recovery Environment: @Dashrender said in ShadowProtect Recovery Environment: did you use the old VDI? Same results with old VM, brand new (empty VM) and new and old ISO. Try less RAM. 
- 
 @Dashrender Just tried that, same thing. Also tried this on different hosts (non-similar hardware) same results. 
- 
 so you have a different old VM that it does work on, but all the new ones don't work.. weird. I'd say bad ISO. 


