Scheduled Manual FULL Image after Disk Geometry Change

[Froggie]

Correct...

[Froggie]

My problem is it didn't do that with v5.4.2.3.  If you're saying it will do that with v5.4.2.3 I will be happy to test again, but the original DISK/PARTITION task definition did have those partitions selected... they disappeared from the image after the geometry change.  What you're saying is that's not supposed to happen with v5.4.2.3... or it won't happen after your suggested fix (I'm a bit confused here).  Pls explain...

In V5.4.2.3, we have only made improvements to the system backup feature, which will automatically select the new partition after changes occur in the operating system-related partitions (System, boot and recovery partition).

For Disk/Partition backups, starting from version V1 to V5.4.2.3, if the geometry of the partition changes, HBS will prompt an error indicating that the partition could not be found. If you did not receive this error message after changing the partition's geometry, please provide us with detailed steps to reproduce the issue.

Thanks.

OK, here's where I am with this (running v5.4.2.3)...


I currently have (2) tasks operating on the current System configuration, both are DISK/PARTITION tasks whose job is to save (5) of the (7) partitions on that disk.  The (5) include all partitions (4) needed to successfully restore the UEFI System and (1) additional personal support partition.  A geometry change was made to both the OS and Windows Recovery (RE) partitions with no other partitions being affected.  Following that change, a manual FULL was generated, using task #1, to capture the geometric partition changes.  When the FULL was examined under the RECOVER menu, it was shown to no longer contain the 2-partitions that were changed, only the 3-partitions that hadn't changed... no error of any kind was generated during the FULL manual image operation (scary).  This occurred no matter what type of image I tried to capture in manual or scheduled mode.

I then created the 2nd task (under the current release) with identical settings to the first task, using a different task name, then captured a new FULL image of the System with the geometry changes included.  After checking the image, all selected partitions (5 of them) were there.

The two tasks are now tracking the same System.  Using task #2 (the newest task created under v5.4.2.3), if I make another geometry change to a single partition and run either a manual or scheduled imaging operation, I get the error stating about the unfound partition (as I'm told is expected).  If I run the same operation using task #1, I get no errors whatsoever and all images are missing the original changed partitions.

I checked the task settings/specs and they are identical.  The only difference I can see is task #1 was created under a much older version of HBS (can't tell what version it was running at the time it was created) and task #2 was created under the current version.

Both of these tasks are tracking the current System image... task #1 never errors and always leaves out the (2) originally geometrically changed partitions, task #2 always errors accordingly.

I don't know how deep you want to go chasing this anomaly... I have protected myself, accordingly, using the newer task #2.  Sounds like from your description of possible upcoming changes, this will make this whole anomaly moot.

What else would you like me to do...?

[Froggie]

Finding more issues... let's try and simplify (all under v5.4.2.3).  I have a (7) partition System disk.  The last partition is not active and not even lettered on the System.  I take a full image of that disk, all partitions (Image op #1).  I then shrink the last partition by appx. 100mB from the end.  I then try to take an Incremental (Image op #2) and it fails with "Specified partition not found (0x23020036000000E9)"... an expected error.

I then recover (non-advanced mode) that last partition (Partition Mode) from the original FULL (Image #1) and try an Incremental (image op #3) and it fails with the above error msg... tried advanced mode, same result.

Using Minitool's Partition Wizard I delete that partition, then try both a non-advanced and advanced partition restoration (deleting partition between operations) with same error result as above.

The only way to correct the situation is to restore that single partition, using Macrium Reflect (my backup imaging method)... all works as expected after that.

What else can I do...?

[n8chavez]

I've been reading this thread for a while now, and said nothing. But I just can't anymore. This is all so unbelievably, undeniably, stupid. I mean, come one. Just recreate the damn task and create a new full baseline. Quite making thing too needlessly difficult. Stop acting like HBS owes us anything. They do not. Take what support they offer and be grateful. After all they are getting nothing from us.

Froggy, I expected you to be a calm voice of reason. I won't make that mistake again. You are not just finding bugs. You are spitting into the wind and wondering why it came back to hit you in the face. Quit doing stupid things to your partitions that are beyond what the average user would do, beyond what the free HBS is expected to manage.