Introducing AX64 Time Machine - hybrid imaging/snapshot software

No Isso, it was NOT "resolved". The WARNING still shows up in 1.3.0.7 like all the other "versions"... External volume modification detected.Backup will take LONGER... which basically equates to going through ANOTHER "Full Backup"



Am I to assume that ppl that "Dual Boot"(with Linux/Mac/Windows etc..) are SOL or are we working to resolve this. As I mentioned before, I have yet to experience this type of behavior from other back-up programs(I've tested quite a few) except this one.

 

I have to use the legacy boot loader because the standard one for Windows 8 simply won't load, I spam F8 and it just boots into normal Windows, I've also tried shift + F8 like some people suggest but still nothing (I've tried both well over 20 to 30 times, not kidding, spent a whole evening/night trying to get it to work) then changed it to legacy and now it works every time.. I'm not really too fussed over it, all I really need it for is safe mode.

 

Shift + Restart from Windows 8 works. But you have to be in Windows.

 

If I can get into Windows then I see no reason to need to get to the F8 menu thingy. Well unless some program needs me to run a cleaner in the safe mode in which case I consider legacy boot loader to be easier. But going off-topic here I think.

 

Hi Sanya,

If you change your settings for your Windows 8 or 8.1 to start after certain time (3 to 30 seconds), then at the bottom you will see an option for a boot menu called, "Change Default or Choose Other Options". When you enter this menu you will find lots of surprises, one of them being the old F8.

This will be shown to you during bootup as boot menu.

I will try to find some screen shots for you.

Best regards,

Mohamed

 

See the image for the menu called, ""Change Default or Choose Other Options".

You should get this menu at Windows startup.

Best regards,

Mohamed

 

Where does that option come from, Mohamed?

 

Just set your Windows to boot after certain seconds. Go to Advanced System Settings > Advanced > Settings. There you can choose the "default operating system" and then "time".

Best regards,

Mohamed

 

My Windows 8.1 is set to boot after 3 seconds.

Best regards,

Mohamed

 

Hi Stigg,

If you already dual booting with Windows 8.1 and Macrium Reflect, then this option should automatically show up at the very bottom of boot menu, along with Windows 8.1 and Macrium Reflect during bootup.

Best regards,

Mohamed

 

I too have had the "External Volume modification Panic!"

 

I do not believe that there is anything Isso can do about it. It's just the way AX64 works. It keeps track internally of all sector changes in order to be able to do hot restores. And if AX64 detects that the protected partition has been accessed externally then it has no choice but discard its tracking file and rebuild it from scratch. Otherwise all following snapshots might be corrupt.

Interestingly this even happens when I do a chkdsk on the system drive. Windows can only do it at the next reboot, it performs the chkdsk command and then reboots again. Doing a new snapshot right afterwards also results in this "External Volume Modification" message. And if you think about it, this is the correct behavior, because the chkdsk is performed before AX64 can load its driver.


So it's bad luck for dual boot machines, I guess...


Cheers
manolito

 

Hi Isso

Tried your method but F8 on this machine takes you to the BIOS drive select menu. Looked at Alladins method but time wise may not be relevant apart from being slightly different.

 

Hello all! I'm going to go out on a limb here and try and interpret Isso and his request and also comment on all the REPAIR OPTION problems that everyone seems to be having with trying Isso's timing test.

My Virtual Boss' suggestion was only a method to allow you to experience the timing involved with the new approach for HOT RESTORE. There are a myriad of reasons why the test may fail due to your system's inability to get to the REPAIR OPTION, some of which have already been discussed. Don't be dismayed... it doesn't mean the new HOT RESTORE won't work... it means you just can't get an idea on how long it will take to stage the new HOT RESTORE method. And for those who now cringe at the ability to not get access to WINDOWS REPAIR, you can always load the OS Installation CD and do the repair from there.

For those who don't have mouse/keyboard access once you reached the WINDOWS REPAIR environment... I know not what your various problems are but fret not. If your current AX64 TM RECOVERY CD/UFD works with your input devices, I'm sure the Isso solution will also work just as well. My guess... AX64 LLC will be building the "new" HOT RESTORE "media" (probably an executable ISO) in the same manner as the RECOVERY ISO/CD/UFD they currently produce.

My WINDOWS REPAIR environment doesn't work at all on my desktop (and I have the WinRE.wim file available)... it says it can't find a needed device (but doesn't tell me what it needs... way to go, WINDOWS), but the AX64 HOT RESTORE RECOVERY ENVIRONMENT will work just fine as my current recovery media does.

If we all wanna fix the WINDOWS REPAIR environment, it's probably best done in another thread... there are tons of reasons why this may not work just as there's tons of systems that can be built by manufacturers/users.

 

Hi Froggie

I have the same as you re. the Repair environment.

Away...so more profound words from 'The Pond'...thanks.

Regards, Balders

 

Balders, I haven't chased down my particular problem yet (don't need to waste the time) but I believe it to be a driver uissue, as others have found.

AX64 builds its RECOVERY CD using a standard WinRE driver set and tries to include any unusual local drivers it finds in the build... that's why the RECOVERY CD works on my system. A standard WinRE.wim does not include those drivers. My BOOT volume is an SSD located on a 3rd party, add-in PCiE SATA III controller... that's the device that I believe has the missing driver.

Sometime I'll corroborate this hypothesis... jsut not now

 

Baldrick,

Have a look at Post #2156

https://www.wilderssecurity.com/showthread.php?t=339999&page=87#2156

 

Hi Froggie

Thanks for the follow up. You are most probably right as I have an external using a non standard connection mechanism (for want of a better explanation) and I have experienced issues about inability to configure something when trying a full repair of Windows from a repair disc....Hmmmm!

Regards, Balders

 

Hi Brian

Thanks. Will do...but as Froggie so eloquently said earlier it is most probably best to get back on topic in this thread/open another if we want to follow up on this 'line of discussion'.

Regards, Balders

 

Hi Brian

Many, many thanks for bringing this post to my attention...brilliant. This has sorted out my "...can't find a needed device" message and I can now get into the Repair Windows option....which is great.

So many thanks again.

Regards


Baldrick

@TheRollbackFrog Take a look a the post...it may well sort out your issue too.

PS. Apologies all for continuing to be off topic a little while longer.

 

BrianK, you're quite right. I got confused between reading this (off Technet) Configure BIOS/MBR-Based Hard Drive Partitions and a recent reburbished Win7 machine I worked on: 1st partition was type 27h which was marked boot, hidden and system and contained the recovery image. After looking at the above link more closely, it's the "utility partition" that is, recovery, that's supposed to be hidden type 27h and recommended to be the last partition on the main drive.

I did a test by doing a clean install on a raw drive, and the System Reserved Partition was type 7h NTFS and only contains Boot folder, bootmrg & bootsect.bak.

I was sloppy. I should have said the option is there but doesn't work.

Winre.wim & bootsid were in C:\Recovery\{GUID} So, I tried using "reagentc /able". It reported "Successful" but I still got the device is inaccessible error.

I tried the procedures post 2156 and now the Repair option actually loads WinRE. Thanks

 

...and indeed it has. Balders, thanks for the reminder... Brian, thanks for being the official "pointer"... and to Carfal, an ol' RBrx friend, who published the tip.

All is well in RepairLand now...

 

No problems Froggie. Glad to hear it.

Indeed, many kudos to Brian AND Carfal.

Regards


Balders

 

HI

i want to know if i have 500 giga HD divide to c:\60 giga d:\440 giga , and i resize c: to 100 giga and d:\ will get 400....if i do a bare metal restore using AX64 (with bootcd ) will ax64 keep c:\ as 100 giga even i made the BACKUP ON C: WHEN HE WAS 60 GIGA?

 

DE, at this time in its development, if AX64 doesn't find its original 60gB partition to restore to... or find a blank HDD to start from, it will not restore anything. You will need another imager that can deal with partition changes in order to do this.