.Hardly fair to blame Microsoft
That is only since the tables were reported as fixed and then the /nt60 command added the efisector to my system when it doesn't even have a EFI BIOS. One thing I do know is that any software program does not make things up on its own and only does what it is programmed to do. The way Windows id obviously designed is to assume there is EFI via the /nt60 when in fact there is nothing of the sort.
nothing on my system told it there was EFI. It took that assumption on its own.
.............is being pushed by the Unified UEFI Forum consisting mostly of hardware makers and BIOS developers, with representatives from Apple, Dell, IBM, the Linux community, with MS playing an advisory role.
Maybe I have read totally different info but my research suggests that the Linux community is almost unilaterally against UEIF and in particular, the oens who run the Ubuntu and Dabian repositories and development as id doesn't offer nearly as much of a benefit for Linus systems.
MS did not "push" for UEFI, though MS is on-board with it because it offers MUCH BETTER security over the traditional BIOS. But to that, MS did not jump fully on board with UEFI until Windows 8 - and that is only with factory built systems - not home or custom built.
What my research also produced was that MS was one of the biggest advocates in pushing manufacturing to unilaterally adopt UEIF across the board. I further don't understand what differentiation there would be between factory produced units or home build and why MS wouldn't want all of their Windows 8 systems installed on UEFI.
.
As some times happens, it appears your tables somehow became corrupt, and in attempting to fix them, they became more corrupt. That does not automatically point to the OS as the culprit, but rather it typically points to hardware failure due either to a hardware component failing, or power anomalies disrupting data transfers - or even malware ......
Not Power issues, Malware was cleaned by several cleaners, only possibility along these lines are 5 sectors being reallowcated I noticed a few weeks before. I don't know when the reallowcations happened. It could have happened many months before as far as I know as I didn't monitor smart on every drive I know on a daily or weekly basis . I kept an eye on this and and is generally accepted that reallowcated sectors in themselves are not necessarily a bad thing but rather if the number continues to grow week after week. So, the number was not increasing. Only thing I can surmise is that the 5 reallowcated ones were system or maybe table files that were reallowcated and caused an issue or corruption.
..... damage from malware, or collateral damage from malware removal.
Don't know what that could be as I have never read anything about it.
.
I note too a discrepancy in your first FS Label list that confuses me, and suggests other issues. You say this is a 1Tb drive but when I add the Gb+ sized partitions (80GB + 818GB + 160GB + 70GB + 260GB + 10GB), I get 1398Gb.
Really, Because my calculator tells me 80GB+818Gb=898 and the aftermath is 30GB+9.5GB+892GB=930GB
So you may need to get a new calculator or put fresh batteries in it.
.
Is there any way to remedy this? Or at least get all of my data back?
A remedy now? Outside of a full format and reinstall, probably not. As far as getting your data back, you don't have current backup of all your data? Why not? ................... (because just about everyone lacks backup discipline), I am just saying backing up your data BEFORE problems arise, or at least as soon as you noted problems instead of after trying to resolve them would have been prudent. You might be totally out of luck now!
Yeh, we all lack perfect discipline and get lasy. Nuf said. I don't think this thread is about the woulda, shoulda coulda, questions that are really irrelevant at this moment and is more about 'this is where I am now and what avenues are there from here.'
.
You might try
Recuva from the makers of CCleaner to see if any of your data files are recoverable, but I would not hold your breath.
Before I try thta or any data recovery, I want to somehow list and evaluate all options I have available at this point.
Never had this kind of issue in the easy days back with XP.
Then you were just lucky. Hard drives have become corrupted since the beginning of time - or at least since they were invented. And that potential has not changed - hence the reason EVERYONE should have a robust backup plan, and use it.
Actually this is not true as the potential for data curruption and hardware failure in HDD's has increased exponentially with the increase in the size of disks not to mention that added tech in firmware and hardware with add more possible failure points. there is an actual tech term for this (at least the data corruption increase issue) and I can't remember what it is at the moment. And this just adds to the argument of the need for backup, plan for backup and diligence in implementation.
.
Sorry I don't have better or cheerier advice to offer.
At least you wrote something of what you figured from your knowledge after over 30 views from other and nobody seams to have an idea.
I think there has to be some HDD or data specialist who knows exactly what to do or the best procedure from here. I think there is also a way of fixing tables and even tools to write them manually if need be as I remember reading some time ago but never had to do such.
