...and I find the same hang happening with the RESTORE operation, although the system isn't fully hanging, only the restore process itself is hanging.
Scott, I just solved this problem by simply uninstalling MR (just the program, not the definition files, logs, etc.) and then reinstalling v6.1.871. Once I did that MR created the correct version of the Boot Recovery Menu (go figure)! Reflect seems to be working very well now. ...hopefully, this approach will also correct your issue.. Jo Ann
Hi Jo Ann, Doing that did the trick for me as well, thanks for the suggestion (but it shouldn't be necessary to uninstall-reinstall). Scott
You folks make me nervous - I don't seem to be having any problems, but feel somewhat insecure based on your posts - lol.
Hi Johnburns Don't feel bad. The latest versions are running trouble free for me also. But I don't every verify, as I personally consider it a waste of time. Pete
Personally I like to have verification on when making images (not restoring) since it can catch hardware issues, it was the only reason I caught my faulty RAM before it was way too late, sure it had caused some issues by the time I caught it but could have been way worse. But I mostly do Incrementals and they verify fairly quickly. I just like the peace of mind, knowing that at least Reflect thinks the image is OK. Edit: Also, my issues with verification when using delta index has been resolved with the update.
Well the funny thing is from all the beta testing I did with Shadowprotect, I learned the best way to check the image was have a pdf file with a video imbedded. If I can play that file from the image I've never had a problem. But I had one case where they were a tad premature on a version release, and I couldn't mount the image to play the file. I finally verifed it and it verified just fine. So I thought i'd try a restore. It failed. So I do question the value of verify.
I received a request for additional information, awaiting for a response. Doing some of my own due diligence in the way of analytical troubleshooting, I have come to the conclusion that the problem lies somewhere between the WinPE 10's disk I/O structure and my specific image holding disk... which is a 1st generation SSHD from Seagate (750gB). If I move the files around on the surface of the disk, the files in error change drastically depending on their surface position. The data's never wrong... it's the Windows I/O interface that's hanging, waiting for some sort of response. The problem never occurs with PE5 or PE3.1... only PE10. To prove this point I have moved the image set to both a standard HDD and an SSD and run the same set of tests... which run completely error free. This convinces me that, most likely, the SSHD's internal NAND/HDD interface is having an issue with how the PE10's disk I/O is happening (most likely a timing issue of some sort). For that reason I would say this is a non-issue for Reflect/PE10 and anyone using disks OTHER THAN Seagate SSHDs (most likely the older ones only... don't know for sure). I have passed this all on to Macrium Support. YMMV with this personal evaluation...
I do incrementals also and verify - haven't had any problems - just ran a backup to check and all is working fine. I'm just a "worrier".
...and FWIW (not very scientific), HDD Regenerator (using Win95 I/O) and SpinRite (using DOS I/O) find no delay/hang errors of any kind, and my LIVE Win7 system (on the test platform) never hangs either.
Hi JohnBurns I just did another of my favorite stress tests, with the latest build. Took a quick incremental. Then booted to my Shadowprotect recovery environment and started a restore. Let run to the 10% restored point and took out the USB key for SP and replace it with the MRv6 RE USB key. Did a power reset, and booted into the RE. All it showed was a local drive C that was empty. Did a restore and here I am. Worked like a champ. Pete
...and probably 2nd and 3rd generation Seagate SSHDs (those are the ones with 8gB of NAND cache... a new controller is used with them), but I don't know that for a fact.
I'm having issues booting from a win10pe USB recovery stick with version 6.1.871. Booting from it shows the blue window image & the spinning dots underneath, when the keyboard & mouse light up the screen goes off & then goes to a black screen & nothing else happens. If I create a windows 8.1pe USB recovery stick it boots fine & loads up the program.
They have all the info (and hardware) they need and are attempting to replicate the issue in their QA lab... kudos for their effort, if you ask me, for such an isolated problem.
Just curious why every one is jumping on the Win 10PE. Win Pe 8.1 works fine on my win 7 image and on my Win 10 image.
Well, when I click on"Add Recovery Boot Menu Option" Win Pe 8.1 is not offered. The only option I have is Win PE 5.0 and 10
Long shot maybe, but no chance it could be a power saving issue like this one you helped me with? Introducing AX64 Time Machine - hybrid imaging/snapshot software
O.K. Peter,thanks. I was confused because above you said "Win Pe 8.1" works fine with your win 7 image
