Even though I have had many successful image backups using Macrium I won't be using the software anymore. This disk is in perfect health.īefore I take backups of systems and always make sure all software is up to date including BIOS as well as check hardware SATA cables, etc. Again I run a system disk check as well as AOMEI software to check hard drive bad sectors. I thought to myself there has to be an issue with this HDD. Again I ask myself WHY THE HELL Macrium would effect the source disk? I was able to rebuild the MBR using /FixMbr bootrec /FixBoot bootrec /RebuildBcd. I rebooted the computer and it said "operating system not found". On a perfectly healthy HDD I proceeded to start a basic clone from a 1TB HDD to a 1TB SSD. ![]() The business owner wanted a backup of his datacenter server hard drive. Situation 2 - Windows server 2016 - Macrium server plus edition - paid for and not cheap. So now I'm thinking: How and why did the macrium reflect software effect a source disk? I ended up just formatting the computer and installing a fresh OS. I installed a new SSD and ran the image macrium made and still BSOD. I ran the image I just took with macrium and it failed. ![]() I ran Windows 10 startup repair which failed. I rebooted the system and low and behold I get a blue screen of death. Macrium said the image completed successfully. In this situation I simply took an image from a perfectly working HDD. Situation 1 - Windows 10 Pro recovery at a small business - Macrium reflect free 8 After a multitude of problems using windows recovery and images I decided to use Macrium reflect. ![]() As a system administrator for many small businesses and larger corporations I frequently look for better ways to do system backups. I wanted to inform the community of a Macrium reflect issue that's happened to me twice.
0 Comments
Leave a Reply. |