@kdfrawg It's laziness and poor design. Had to go umpteen levels deep in the F8 menu to enable safe mode. (Boots fine there), toggle disk check on next reboot, disk check has NO output other than a percentage. I am at 100 percent now and nothing is really happening.
NO OTHER OUTPUT
Power outage. Reboot to constant spinning wait cursor of death. Startup repair fails with absolutely no indication WHY. Restart in safe mode and set drive to be chkdsk'd on reboot. At 52 percent.
What is Microsoft's issue? Why can they not give diagnostics output? Helpful things like 'Bad or corrupted sector'?
@matigo This is the first time I have encountered a problem that I couldn't fix. It simply refused to push changes. Maddening.
Thank heavens for git diff and git apply.
git apply editsfromborkedlocalrepo.diff
git commit -a
git pushAnd I'm back in business. No damned idea what was wrong with the initial local repo but I don't have time to play detective.
Cloned repo all over again. Made meaningless change. Pushed back successfully. Cloned yet again to make sure it indeed record change.
Now copy over 200 changed files to the freshly checked out repo to commit and push.
I have no clue what is wrong with the repo copy I was working on.
So strange finding myself in a position where 16GB of RAM isn't enough. Since the motherboard can't be expanded beyond that, it's time for an upgrade.
Cars washed. Long circuitous journey with sidekick taken. Setting gvim up on the RHEL7 VM to my liking.