I am seeing fixdisk report a lot of stuff but is apparently successful fixing it
Others are really in a better position to comment on this but - in case it's helpful - here's my experience of running
fixdisk on my failing original HDD whose LBA 0 was irrecoverable:
After "re-writing sector 0: succeeded"
fixdisk repeatedly ran the short disk self test, identifying errors at various blocks and asking if I wished to attempt repair of the bad block, to which I said yes and the re-writing succeeded. In order, the sectors were 558, 2174623, 2174610, 2174623 (again), 2174621, 2174621 (again), 2174617. When it again flagged an error at 2174621 I declined the repair attempt. It then checked the partition tables (MBR Status/GPT Status not present), then searched for partitions finding partitions 1, 2 and 3. It then asked if I'd like to attempt repair of the partition table, to which I said yes. It then re-read the partition table and said "New partition table has been created". It then reported further details before saying partition sda1 was an unrecognised partition type and
fixdisk aborted terminating the session with exit status 1.
On the clone I had to dig deeper and use
fsck on the individual partitions via the CLI option in CF Maintenance Mode. After this work I opted to create a new sda1* by formatting a spare HDD then copied that, sector-for-sector to the clone, then I had to edit the LBA 0 partition table to match reality. Result: no further demand to format the HDD from the Humax and job done.
*I'm not sure whether sda1 should have been recognised.