Group: Forum Members
The more I think about this, the more I call it a Reflect BUG. It isn't a hardware problem. It is a data problem (i.e. GPT/BPP is bad). Data problems should produce an error. They should not cause a hang, especially not by a program whose job is doing image backups! Worse, it is more than a simple hang, you can't kill Reflect, but have to boot. You have not one, but two KB articles about the problem (one that I found about Troubleshooting Startup problems; and another, how to exclude disks during startup.) This means that you have had probably quite a reasonable number of people waste a few hours each trying to figure out what is going on. (i.e. since it is a hard hang, first I look for hardware problems; second I tried repairing Reflect; third looked for KB article; fourth tried the KB article fixes... all of which could have been short-cutted.)
Since it is a data problem, seems to me that Reflect could be fixed to detect the problem. All it needs to do is give an error message pointing at a KB article, and then treat the disk as excluded, same as the registry entry. With that fix, I'd have cut a few hours off my time.
And please link the Troubleshooting Startup Problems KB article to the Excluding Disks During Startup KB article. Currently it says: ...there are two possible reasons... -- well no, there is a third, damaged GPT/BPP; so an extra sentence on the bottom which say that if you can't solve the problem, the disk can be excluded, see Excluding Disks KB article.
And with that, I will move on. I just ask you to please update the KB article; and hopefully post a bug.