6/7/2023 0 Comments Gigabyte smart usb backupAll goes smoothly now, the new installation works fine, do the usual updates, reinstall a bunch of stuff, did all the windows updates. I figure I've got the suspect image and the bios versions if I want to play with it more and try and figure it out. So screw it, I wipe the drive again, flash the bios to the latest version again, and reinstall windows 10 from a fresh creation media. What is so confusing here is that at this point I'm back to the known to be working bios, and known to be working image of the drive, with the known to be working processor, I literally never even swapped the CPU out because I always incrementally test all changes to my systems.Īt this point I'm just frustrated. same thing, drive is fully intact, readable, passes all the tests, reports a 98% condition on its lifetime. So this time I do a full proper reformat with a wipe on the suspect drive, back to Macrium to restore the pre-flash image, and. I can 100% interact with, copy to/from and access the drive without issue. Everything performs as expected, no problems reported in SMART. Crystal disk finds no problems disc check finds nothing, SFC, WD Dashboard nada. So i boot from a rescue image i have set up via USB to check out the drive. So at this point I'm back to the original bios and the original image of the NVME disk just before flashing and its still dead. This is with an image that was literally just working hours before. It wont work, Macrium installs it just fine with no problem but even with formatting the drive it fails to boot, same error. ![]() So i pull down the image that i just created of the drive before flashing. I tried 3 times with disk part to fix the changes, but each time I set the changes, they appeared to stick, then on restart they are changed back, and the failure repeats. Removing all other drives and starting did not work (probably because its trying to boot to the wrong partition, not drive). Googling around and find a few posts about C changing to E under odd and sporadic/varied conditions and some potential workarounds/fixes. Somehow my old C drive has been changed to E, and the normally inactive rescue partition that typically does not even have a drive letter is now my C drive. So then i get into diskpart and start poking around. ![]() Attempt to backup/rebuild/edit the BCD with no luck, when I scanned for OS's for the repair function it finds no operating systems. ![]() flashing should not have messed with the drives at all right? So I roll back the flash to the previous stock 2019 version of the BIOS it was running, still wont boot, same problem. So to test i reboot after flashing and windows (WD Black 500gb NVME) wont load, I keep getting a missing or corrupted boot sector, the error specifically says the BCD is missing or contains errors. I flashed the BIOS on my Gigabyte Aorus B450 Gaming board to the latest version (64a). ![]() get prepped for the swap but I never got that far. So the new CPU arrived and i proceeded to run backups etc. Originally i had a Ryin it, and I wanted to upgrade to a Ryzen 7 5700x. So recently I wanted to do some upgrades, and hand down some older parts to a dedicated server.
0 Comments
Leave a Reply. |