FileWave Alliance

The Official Community Forum
  • Page:
  • 1

TOPIC: Imaging Disk Read Error

Imaging Disk Read Error 01 Sep 2017 15:05 #2681

  • Paul Harlan
  • Paul Harlan's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 22
  • Thank you received: 0
After Imaging PC with a custom image of Windows 7 taken from the same exact hardware (Dell Optiplex 790) and booting into it the imaged PC gives an error of "A disk read error occurred." Is there something wrong with the image taken? Guide followed can be found here: www.filewave.com/support/kb/article/windows-network-imaging

Imaging Disk Read Error 01 Sep 2017 21:16 #2684

  • Bao Tran
  • Bao Tran's Avatar
  • Offline
  • FileWave Staff
  • FileWave Staff
  • Posts: 103
  • Karma: 4
  • Thank you received: 13
It's difficult for me to give you good advice on this as I have not run into this before but here are some things that I would try if it happened to me.

1. Restoring the disk image to the same computer it was captured from. If the system doesn't boot correctly then FileWave did not capture all the requisite info correctly. Please file a ticket with FileWave Support.
2. If that works and you restore it to a different physical computer but it's not able to boot then that likely means there's a difference in hardware, particularly the hard disk or hard disk controller. Even though the computers may be the same model there are sometimes revisions within the same model as the manufacturer had to source parts from different vendors for the same component. If this is the case you'll need to include the drivers for whatever piece of hardware is causing the issue in your driver fileset being assigned to the device so it's installed when the reimaged computer goes through the OOBE. Make sure you sysprep the system and check OOBE or enable it via a commandline parameter.
3. Restoring the disk image to an empty VM. VM's have really generic virtual hardware so if the VM is able to boot successfully after reimaging then there's obviously nothing wrong with your image and the problem more likely with your driver fileset.
  • Page:
  • 1