![]() I've even tried restoring to a 'cleaned' disk - cleaned via diskpart or through disk mgmt. ![]() Whilst restoring intelligent or exact images back to the original SSD drive would be fine, trying to restore to another drive would always result in "Attempting to repair / diagnosing PC" loop. Might be worth mentioning that if I restored a boot image from 2 weeks ago, the files on the data drive (after running scan disk) may be slightly different to the more recent image (if that makes sense?). Running scan disk and fixing errors would usually restore those files, but I have also experienced instances of some files being corrupted when opened. Let's say I've saved some files this morning on the data SSD, then my boot drive messes up in the afternoon, I would restore my boot drive image from last week, but then notice those recent files are missing on the data drive. The reason for restoring a boot image is because the boot drive sometimes randomly goes into the "Attempting to repair / diagnosing PC" loop - start up repair or Macrium's own 'fix boot issues' don't work. I've recently noticed missing files on that drive when I restored an image for my boot drive. ![]() It appears that the bitmap image on the DATA drive is messed up. Something leads me to think that mentioning this is relevant, as I believe they affect one another? I also have a second SSD which is may DATA drive - also MBR. I currently boot from an SSD which is in MBR format booting from a UEFI compatible motherboard. I hope some of you might be able to shed some light on boot issues I'm experiencing with my cloned boot images.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |