On Tue, 2017-11-21 at 20:56 -0500, Sam Varshavchik wrote: > I do not remember if I initiated the reboot for some reason, or if it was a > Win10-initiated reboot. But the reboot went into some kind of a recovery > mode I have not seen before, in Windows. Instead of booting Windows 10, it > was some kind of recovery menu, giving me a few options to try. I do not > immediately recall which options tjeu were, but the the conclusion was the > same, no matter which recovery option I picked: an adamant claim that my > "hard drive" is fried. I've seen that a couple of times with Win10. Always thought it was PEBKAC so the first time I just reinstalled Windows. The second time I tried the options (vaguely remember it was the first one) and it worked. OT: What triggered the problem in the first place was my attempt to dual- boot the Win10 system (it lives on its own disk). The VM is configured with EFI (ovmf), that being the preferred option when doing VFIO passthrough, but my box is configured by default to try BIOS before trying EFI and I didn't use the magic incantation in my boot screen, so Windows decided there was something wrong and tried to "fix" it - in this case by downgrading the VM from EFI to BIOS. Anyway, having managed to correct that I can now dual-boot if required by proper magic in the (real) firmware. What I'd really prefer is to reinstall Fedora using EFI but that seems somewhat complicated to achieve. I asked about it here a while back and found the answers discouraging (not impossible, just a lot of work). I don't really need to dual-boot anyway at the moment. It was just a whim so I could check performance of my VM. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
