[–] [S] 1 point 1 year ago (1 child)

I was able to track down what I believe are the correct storage controller drivers from the mobo manufacturer and install those during the recovery process, but no change.

The only other thing I can think of is to dig out an old >1Tb sata drive and try recovering to that.

And yes, lesson learned for next time about making and testing the recovery drive ahead of time. I mistakenly put my trust in MS that recovering from a full system image using their own utility would be a dead simple process...

  • source
  • parent
  • context
  • [–] [S] 1 point 1 year ago

    So I believe it was the Defender full scan crawling the Google Drives mapped drive letter and accessing every file it found causing every file to be downloaded and cached. So I'm rerunning the scan with all my cloud drive agents disabled.

  • source
  • parent
  • context
  • [–] 4 points 1 year ago*

    Many IDE cables used to come with 2-4+ daisy chained connectors allowing you to plug in multiple drives into a single cable on a single IDE bus.

    This meant that you had to ensure any downstream HDDs would be configured as slaves to show up properly to the system.

    You could either do this manually by setting the jumper to slave (usually just removing it) or setting the jumper to cable select which would automatically configure master slave drives for you.

    Example for a Seagate drive:

    In your case, you could either use the master select or cable select and it wouldn't matter since you only have one drive.

  • source
  • parent
  • context
  • view more: ‹ prev next ›