So, I replaced the disk that was ruining my system and got everything back to where I started. but…
… the new disk has the exact same symptoms… lots of data errors and seek errors, no bad sectors and 5 to 10 second average access times.
Now I need to do more sleuthing to find out if I’m just unlucky and got two drives with the same problem (which sounds really unlikely) or there’s some other problem going. The troubleshooting tool from the PC’s manufacturer didn’t find any problems which is a problem in itself. It’s really fishy.
I dusted off my Linux box that I hadn’t used for 5+ years. The goal with the Linux box is to not need to tackle Windows malware at the same time.
There’s some Linux bit rot going on because the display is stuck at 640 x 480. I’m fighting with the X configuration file but am not making a lot of headway. The auto-config dumps on me.
I’m finding clues that the Linux box had vmware installed on it. I can’t get it to launch. (It might be because of the screen resolution?) The old virtual machines I have scattered on backup discs are incompatible with modern vmware.
It would be awesome if I got vmware to work because I have antique versions of Windows (98 and Millennium edition) and antique versions of Microsoft Office (2000 and XP) that would be fun to play with again. I have a matching vmware install disk, but that’s for another day.
I needed to upgrade the main disk on my Windows 8 computer. I was fortunate that the old disk allowed me to make a system image. (Monty Python: “I’m not dead.”)
I followed the instructions on a very helpful blog post “Simple steps for replacing your Windows 8.1 system disk with a bigger drive”
Everything went as directed until I got to the error message “The system image restore failed. Windows cannot restore a system image to a computer that has different firmware. The system image was created on a computer using EFI and the computer is using BIOS.”
I did an investigation of the error message using my current research workflow. (Just started using that workflow, so I have to mention it. One of its greatest attributes is that it prevents me from jumping down rabbit holes when I’m trying to learn something specific.)
The short answer:
Recent PCs can boot in two ways. One uses the old technique from a BIOS and another uses a different method called UEFI. (Unified Extensible Firmware Interface) The solution was to boot the prepared USB drive the same way that the original hard drive boot used.
I found the keypress I needed to go into the boot menu, (For my computer it was F12. Other computers might use other keys.) I picked the option to boot my USB drive with EFI instead of BIOS and now the data is being restored successfully.
….It’s easy to find a long answer to solve the problem.