Macrium Support Forum

Restore Image > Boots > Black Screen after OS Menu [via CBT = DAMAGED INDEX ENTRIES]

https://forum.macrium.com/Topic28629.aspx

By Zardoz2293 - 10 April 2019 6:02 PM

Reflect Home v7.4156. Created "System" Image with (three) Incremental parts with W10 Pro 64-Bit v10.1809.17763.379

System Media (Original Source) = Samsung SSD 860 PRO 4TB (most current firmware)



Event occurred requiring restore. Restore procedure appears to work correctly. Upon booting OS Menu appears select or allow for default (as usual) and expect login screen (usually appears instantly). However, screen goes BLACK and there is hard disk activity. Booting into "SAFE" mode results in same BLACK screen.

Dell Precision 7720 with Nvidia Quadro P5000 video (most current firmware and video drivers)

Please advise solution or procedures to resolve.

Thank you.
By JamieW - 11 April 2019 7:05 AM

Lars - 10 April 2019 6:02 PM
Reflect Home v7.4156. Created "System" Image with (three) Incremental​ parts with W10 Pro 64-Bit v10.1809.17763.379

System Media (Original Source) = Samsung SSD 860 PRO 4TB​ (most current firmware)

​​

Event occurred requiring restore​. Restore procedure appears to work correctly. Upon booting OS Menu appears select or allow for default (as usual) and expect login screen (usually appears instantly). However, screen goes BLACK and there is hard disk activity. Booting into "SAFE" mode results in same BLACK screen.

Dell Precision 7720 with Nvidia Quadro P5000 video (most current firmware and video drivers)

Please advise solution or procedures to resolve.

Thank you.​​​​​​
​​​

Hi Lars,

Please can you open a support ticket at http://www.macrium.com/support so that we can collect some more information.

Kind Regards,
Macrium Support​​​​​​​
By Zardoz2293 - 11 April 2019 4:56 PM

JamieW - 11 April 2019 7:05 AM
Please can you open a support ticket at http://www.macrium.com/support so that we can collect some more information.

Kind Regards,
Macrium Support

Jamie, Opened Ticket 130264: Restore Image > Boots > Black Screen after OS Menu

However, your automated system is saying I'm out of support, implying the ticket will either go into limbo or be closed.
By Zardoz2293 - 12 April 2019 5:43 PM

Installed v7.2.4156 on FULL Image= without CBT (Test #A) and then with CBT (Test #B):
FULL Image Backup with CHKDSK on mounted backup image.
#A (without CBT) passed
#B (with CBT) passed

INCREMENTAL (CBT NOT INSTALLED) and then CHKDSK
#A (without CBT) passed
#B (with CBT) passed
DELETED INCREMENTAL file segments from both #A and #B

INCREMENTAL (CBT INSTALLED) and then CHKDSK
#A (without CBT) FAILED
#B (with CBT) FAILED
DELETED INCREMENTAL file segments from both #A and #B
By jphughan - 12 April 2019 7:18 PM

Not sure how to account for the failure above, but fyi you didn't need to create two separate Fulls.  CBT is never used for a Full even when it's installed because the point of CBT is to figure out the blocks that have changed since the most recent backup in the set, and a Full is always the first backup of a new set.  The test can be simplified to this:

- Install CBT, confirm it's monitoring your backup source
- Create Full (CBT will not be used)
- Create Incremental (confirm Reflect used CBT)
- Mount Incremental and run CHKDSK against it
- Delete Incremental, disable/uninstall CBT, create new Incremental
- Mount new Incremental and run CHKDSK against it
By Zardoz2293 - 12 April 2019 8:03 PM

jphughan - 12 April 2019 7:18 PM
Not sure how to account for the failure above, but fyi you didn't need to create two separate Fulls.  CBT is never used for a Full even when it's installed because the point of CBT is to figure out the blocks that have changed since the most recent backup in the set, and a Full is always the first backup of a new set.  The test can be simplified to this:

- Install CBT
- Create Full (CBT will not be used)
- Create Incremental (confirm Reflect used CBT)
- Run CHKDSK
- Delete Incremental, disable/uninstall CBT, create new Incremental
- Run CHKDSK

Good to know! Thanks!
By Zardoz2293 - 18 April 2019 10:46 PM

Any work being done to fix this? If you can't restore it isn't correctly backing up the image even when it reports it's 'valid'.


By JamieW - 19 April 2019 10:09 AM

Lars - 18 April 2019 10:46 PM
Any work being done to fix this? If you can't restore it isn't correctly backing up the image even when it reports it's 'valid'.



Hi Lars,

I've sent you an email via the support ticket.

Kind Regards,
Macrium Support​​​​​

​​​
By Keith Weisshar - 21 April 2019 6:58 AM

I’m having the same issue and I need to reinstall Windows. I’m out of support. I’m stuck in a reboot loop. I’m posting this from my iPad Pro 10.5 inch with Bluetooth keyboard since I don’t have another working PC. My Macrium license is still registered to this PC that can no longer boot and I can’t deactivate the license before reinstalling Windows because I can no longer boot into the desktop. This happened after restoring the synthetic full backup image after consolidating the full and incremental. I don’t have any other full backups to restore and I need to reformat and reinstall Windows. Can you please reply on this forum ASAP. My Macrium email support is already expired. I have CBT installed. When I ran chkdsk c: /f from Windows RE it found a lot of damaged index entries.  I had to completely reinstall Windows from scratch due to the file system corruption after restoring consolidated full backup which contains the incrementals with CBT enabled.  This is a critical data loss issue with CBT that needs to be fixed ASAP.   I have Macrium Reflect Home Edition v7.2.4156.
By JamieW - 21 April 2019 8:45 AM

Keith Weisshar - 21 April 2019 6:58 AM
I’m having the same issue and I need to reinstall Windows. I’m out of support. I’m stuck in a reboot loop. I’m posting this from my iPad Pro 10.5 inch with Bluetooth keyboard since I don’t have another working PC. My Macrium license is still registered to this PC that can no longer boot and I can’t deactivate the license before reinstalling Windows because I can no longer boot into the desktop. This happened after restoring the synthetic full backup image after consolidating the full and incremental. I don’t have any other full backups to restore and I need to reformat and reinstall Windows. Can you please reply on this forum ASAP. My Macrium email support is already expired. I have CBT installed. When I ran chkdsk c: /f from Windows RE it found a lot of damaged index entries.  I had to completely reinstall Windows from scratch due to the file system corruption after restoring consolidated full backup which contains the incrementals with CBT enabled.  This is a serious issue with CBT that needs to be fixed ASAP.

Hi Keith,

​Please can you ​​​open a support ticket at http://www.macrium.com/support

We understand that you are out of support, but we need to collect some more information and your ticket will not be rejected.

​Kind Regards,
Macrium Support​
By Keith Weisshar - 21 April 2019 10:04 AM

JamieW, Can you please reply to ticket #130598.
By Keith Weisshar - 21 April 2019 9:27 PM

This corruption problem occurs if the system was rebooted between a full backup and an incremental or differential backup unless I use reset CBT on reboot.  The following is a chkdsk scan of the mounted incremental image.
​​
The type of the file system is NTFS.

WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...
Progress: 0 of 199424 done; Stage: 0%; Total: 0%; ETA: 0:09:37  Progress: 44103 of 199424 done; Stage: 22%; Total: 8%; ETA: 0:08:51 . Progress: 89625 of 199424 done; Stage: 44%; Total: 17%; ETA: 0:07:58 .. Progress: 160513 of 199424 done; Stage: 80%; Total: 29%; ETA: 0:00:04 ...Progress: 199424 of 199424 done; Stage: 100%; Total: 35%; ETA: 0:00:03                                                             199424 file records processed.                  
File verification completed.
Progress: 6389 of 6389 done; Stage: 100%; Total: 23%; ETA: 0:00:04 .                                                            6389 large file records processed.           
Progress: 0 of 0 done; Stage: 99%; Total: 23%; ETA: 0:00:04 ..                                                            0 bad file records processed.            

Stage 2: Examining file name linkage ...
Progress: 49797 of 280926 done; Stage: 17%; Total: 29%; ETA: 0:00:04 ...Progress: 150444 of 280926 done; Stage: 53%; Total: 40%; ETA: 0:00:04  Progress: 150445 of 280926 done; Stage: 53%; Total: 40%; ETA: 0:00:04 . Progress: 366 of 366 done; Stage: 100%; Total: 45%; ETA: 0:00:03 ..                                                            366 reparse records processed.            
Progress: 200607 of 280926 done; Stage: 71%; Total: 46%; ETA: 0:00:03 ...Progress: 203860 of 280926 done; Stage: 72%; Total: 50%; ETA: 0:00:03  Progress: 206862 of 280926 done; Stage: 73%; Total: 55%; ETA: 0:00:03 . Progress: 210983 of 280926 done; Stage: 75%; Total: 57%; ETA: 0:00:03 .. Progress: 215121 of 280926 done; Stage: 76%; Total: 65%; ETA: 0:00:03 ...Progress: 220819 of 280926 done; Stage: 78%; Total: 66%; ETA: 0:00:03                               Index $I30 in file 16E9A is incorrectly sorted.
Index entry UP076F~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UP0CB7~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UP14AB~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UP16CC~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UP1E42~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UP2DAF~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UP3884~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UP38BA~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UP4198~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UP456E~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UP52FC~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UP597C~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UP7B54~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UP7D55~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UP8247~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UP8DEE~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UP96CC~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UP9D42~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UPA620~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UPA721~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UPAC79~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UPB13B~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UPB784~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UPB8BA~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UPBE04~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UPC098~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UPD2FC~1.ETL in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.001.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.002.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.003.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.004.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.005.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.006.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.007.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.008.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.009.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.010.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.011.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.012.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.013.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.014.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.015.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.016.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.017.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.018.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.019.etl in index $I30 of file 16E9A is incorrect.
Index entry UpdateSessionOrchestration.020.etl in index $I30 of file 16E9A is incorrect.
Index entry updatestore51b519d5-b6f5-4333-8df6-e74d7c9aead4.xml in index $I30 of file 16E9D is incorrect.
Index entry UPDATE~1.XML in index $I30 of file 16E9D is incorrect.
Index entry S-1-5-21-1097195503-1187525460-1112689983-1001_StartupInfo2.xml in index $I30 of file 16F2F is incorrect.
Index entry S-1-5-~3.XML in index $I30 of file 16F2F is incorrect.
Index entry WmiApRpl.h in index $I30 of file 1765E is incorrect.
Progress: 223109 of 280926 done; Stage: 79%; Total: 70%; ETA: 0:00:03 . Progress: 231735 of 280926 done; Stage: 82%; Total: 74%; ETA: 0:00:03 .. Progress: 235089 of 280926 done; Stage: 83%; Total: 77%; ETA: 0:00:03 ...Progress: 237466 of 280926 done; Stage: 84%; Total: 78%; ETA: 0:00:03  Progress: 239508 of 280926 done; Stage: 85%; Total: 80%; ETA: 0:00:03 . Progress: 280926 of 280926 done; Stage: 100%; Total: 79%; ETA: 0:00:03 ..                                                            280926 index entries processed.                  
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.
By Keith Weisshar - 21 April 2019 10:01 PM

After installing v7.2.4228, I deleted the old backup and created a new full backup, rebooted, created a new incremental backup and then mounted the most recent incremental backup and ran chkdsk f: and it reported no errors.  Restoring no longer renders the computer unbootable.  This is a critical update, if your still running v7.2.4156, please update immediately to v7.2.4228.