Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Multi-BOOT Partition Anomaly
#11
(Yesterday, 02:42 AM)Froggie Wrote: @al3x, you may be right.


Same as above, this time with a single change to the Win11 OS partition prior to the above process.  No CHKDSK issues prior to the restore, no CHKDSK issues after the restore (only the Win10 disk ERROR msg like before).  reBOOT the System for ordered repair operation, no repair done.  This was different from yesterday as Win10 always did the repair scan during the reBOOT (never found any errors though).

As @al3x has suggested, the "no repair scan" following the reBOOT may have been caused by my CHKDSK scan (none of this was done yesterday), which found nothing... may have cleared the dirty bit prior to the reBOOT so no repair scan done this time.

Who knows... Win10's DIRTY may not be the same as everybody else's "dirty"  Rolleyes
Reply
#12
(Yesterday, 02:49 AM)Froggie Wrote:
(Yesterday, 02:42 AM)Froggie Wrote: @al3x, you may be right.


Same as above, this time with a single change to the Win11 OS partition prior to the above process.  No CHKDSK issues prior to the restore, no CHKDSK issues after the restore (only the Win10 disk ERROR msg like before).  reBOOT the System for ordered repair operation, no repair done.  This was different from yesterday as Win10 always did the repair scan during the reBOOT (never found any errors though).

As @al3x has suggested, the "no repair scan" following the reBOOT may have been caused by my CHKDSK scan (none of this was done yesterday), which found nothing... may have cleared the dirty bit prior to the reBOOT so no repair scan done this time.

Who knows... Win10's DIRTY may not be the same as everybody else's "dirty"  Rolleyes

Indeed I always create the required reBOOT repair process if I don't run CHKDSK prior to the reBOOT.  Something's "dirty" but I have no idea what since I don't know what Win10 uses for its "dirty" criteria... and HBS definitely tweaks it whatever it is.
Reply
#13
@Froggie,

Strangely, I wasn't able to reproduce the issue. Do I need specific steps, or special restore options, like the Delta restore option? 

I checked the dirty bit, and it doesn't seem to be problematic.

Thanks.

Best regards,
Reply
#14
No special sequence other than my description above.  Yes, I used Delta Restore but I believe it wouldn't make any difference either way.

Let's chalk this up to a personal System Win10 anomaly (the results are always good so it's not critical in any way), no more effort on your part until you hear more from this end on exactly what may be going on.

Thank you for your effort up until now!  Onward & upward (v6...?)...  Big Grin
Reply
#15
@Froggie,

I wonder if this issue is related to specific Windows 10/11 build versions. I've already tried both with and without the Delta Restore feature, but still couldn't reproduce the problem on my end.

Although this anomaly doesn't have any real impact on the restore functionality itself, it would still be great to identify the root cause if possible. Otherwise, some users might mistakenly assume it's entirely an issue with Hasleo Backup Suite, which could lead to a loss of trust in the software.

Also, just wanted to say - thanks for your continued attention to V6!

Have a nice day!

Best regards,
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)