Solved Image restore query!

[Alexey2912]

Hi,

While restoring an image, the restoration stalls after verification for at least 5 mins...

SSD target detected... Attempting Trim.

Though SSD trim is checked... Any ideas.

Never happened with earlier version, seen with version 6.2.1549.

Thanks.

 

[mjf]

Your description of the problem is not totally clear.
But as a start

Did you successfully perform a system image restore?
Afterwards is the SSD Trim enabled - use elevated command prompt:

fsutil behavior query disabledeletenotify
Results-
DisableDeleteNotify = 1 (Windows TRIM commands are disabled)
DisableDeleteNotify = 0 (Windows TRIM commands are enabled)

While you are at it do a file system check
> sfc /scannow

Another thing to check is can you mount the Macrium image in question and browse through the contents.

 

[Alexey2912]

Results:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\XPS>fsutil behavior query disabledeletenotify
DisableDeleteNotify = 0

C:\Users\XPS>> sfc /scannow
'/scannow' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\XPS>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log

C:\Users\XPS>



Thanks for replying.

Above the results of fsutil behavior query disabledeletenotify and sfcscan, as seen windows trim commands are enabled but sfc found corrupted files in CBS.log.

Now I'll try to make things clearer.....

1. Creating a full back along with verification takes approx 14 mins.

2. Restoring a backup, using boot Rescue media and usb external drive on which the image is stored, takes around 29 mins.

3. System reserved is restored in less than a min, while restoring Windows, verification is fine but after that it stalls for 10-15 mins, at SSD targeted, Trim starting, till Trim is successful take around 12-15 mins. Total time for verification and restoring is approx 29 mins with 10-15 mins of rescue media stuck.

4. Tried restoring the 2nd backup, same results.

5. Can install a AV, but windows action center wouldn't recognize, despite it's running, prompting to activate AV.

6. Do you feel that after this sfc repair this won't happen?

7. Do I need to create new backups, or is it possible to correct the 2 images?

Appreciate your expert assistance.

Kind regards!






Edit:

1. Just wanted to make it more clear, create backups on live, running windows, restoration using boot rescue media. (Cold imaging).

 

[mjf]

6. Do you feel that after this sfc repair this won't happen?

7. Do I need to create new backups, or is it possible to correct the 2 images?

It's hard to say what caused the system file corruption. On the positive side it was repairable - sometimes it can't be repaired.
Did this cause the Macrium problem or did your version of Macrium cause the problem? - I don't know.

Here is what I would do
1) Update to the latest V6 if this isn't the latest and make another restore pe disk.
2) Keep the old system images since they appear to eventually restore with a repairable system file error.
3) Make a new system image after the system file fix.

The acid test will be restoring the new system image using the latest restore pe disk and see if the problem persists. This is your call.
This sort of test is always less risky if you have a spare SSD/HDD lying around as the "new" restore OS drive.

 

[Alexey2912]

Thanks again for replying.

Shall do as suggested.

Its the latest Macrium reflect, updated.

Faced none such issues, using 6.1.

Created rescue media on multiple optical discs, but same.

I feel the issue is with the PE ...

Anyways shall keep you posted.

Kind regards.

 

[mjf]

Keep us informed Alex as many people use Macrium with a high level of confidence.

It would be useful if other members could comment on their experience with the latest version of Macrium including any issues with the rescue pe.

 

[Alexey2912]

Hi,

I shall keep you informed, once I create a new backup of the repaired W7, and perform a restore of it.

Thanks.

 

[Alexey2912]

Hi,

The sfc scan results, display that corrupted files have been repaired, but they reappear on re scan.......strange?

May be the fresh W7 install is a corrupted one....

I will only be sure only after have seen a non corrupted W7 install, create it's backup and restore using Macrium 6.2.......

Any methods, besides another clean install to repair them?:huh:

Thanks.



PS: The CBS log file is huge to post.....



Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\XPS>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log

C:\Users\XPS>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log

C:\Users\XPS>

 

[mjf]

You sometimes need to run sfc /scannow a number of times. See how you go.

If you do this and sfc still reports errors then a data backup and a clean install could be an option.

 

[Alexey2912]

I ran it 3 times and another on reboot, still the same....

Clean install again.....

Thanks anyways for trying to figure out, using you smart brains.

 

[Layback Bear]

Every time you run SFC /SCANNOW and find a problem you should reboot.
At times the problem or some of the problems
will be repaired on reboot.

 

[Alexey2912]

Thanks for the expert suggestion.

Hypothetically, during a clean W7 install, how often, at what steps should one do a sfc /scan....

 

[mjf]

I run sfc from time to time as part of routine maintenance. It almost always comes up good.
However, before installing Windows updates I always do the following:
1) Run sfc/scannow to make sure all is good.
2) Make a system image
3) Install the updates
4) Run sfc/scannow again

On a few occasions Windows updates have resulted in system file corruption (or at least the sfc /scannow operation believes so). On these occasions the system files have often not been repairable. I then perform a system image restore and attempt to track down the culprit update. Recently MS have adopted a rollup update procedure which makes it difficult to identify a specific problematic update. The best strategy here is to reimage, wait a couple of weeks and try again.

This sounds burdensome and it is! You can thank MS for that.

 

[Alexey2912]

Thanks mjf for the expert suggestion.....

1. Btw when you perform it, do you create a full backup?

2. You must be creating an image each month....?

3. If, each month and the created is fine, do you delete the old one or overwrite it, once checked?

 

[MTS52]

alexey

Just for future reference when you run sfc /scannow you can use the command below to just show relevant details from the cbs log.

Run from elevated command prompt and the file will appear on your desktop.

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

This makes it easer to see what SFC scan has done.
If there are any files it could not repair you will be able to see which files still need to be repaired.

 

[Alexey2912]

Thanks MTS52 for sharing, would keep in mind.




Edit:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt" to be run only if sfc /scannow displays an error...correct?

 

[Alexey2912]

Hi,

While restoring an image, the restoration stalls after verification for at least 5 mins...

SSD target detected... Attempting Trim.

Though SSD trim is checked... Any ideas.

Never happened with earlier version, seen with version 6.2.1549.

Thanks.

Hi,

This is still happening, while restoring an image, despite that have none sfc errors on the new install.

Image creation is swift as always, but restoration stalls for 5-7 mins after verification process of the backup is successfully completed.

Is it cause that I/O displays a slower Write vs Read....approx 900 Mb/s (read) and 200 Mb/s (write)?

Thanks.


OR is a normal Macrium Reflect behavior?

 

[Alexey2912]

fsutil behavior query disabledeletenotify
Results-

DisableDeleteNotify = 0 (Windows TRIM commands are enabled)


But results of trim check.exe, display....Trim appears not to be working.( or hasn't kicked in yet).

 

[Alexey2912]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\XPS>fsutil behavior query disabledeletenotify
DisableDeleteNotify = 0

C:\Users\XPS>
C:\Users\XPS>



TRIM check v0.7 - Written by Vladimir Panteleev
GitHub - CyberShadow/trimcheck: SSD TRIM check tool for Windows

Loading continuation data from C:\Users\XPS\Downloads\trimcheck-cont.json...
Drive path : \\.\C:
Offset : 20000452608
Random data : E4 A3 61 66 8F 1C D7 54 75 BA 35 69 81 06 28 FE...

Reading raw volume data...
Opening \\.\C:...
Seeking to position 20000452608...
Reading 16384 bytes...
First 16 bytes: E4 A3 61 66 8F 1C D7 54 75 BA 35 69 81 06 28 FE...
Data unchanged.

CONCLUSION: TRIM appears to be NOT WORKING (or has not kicked in yet).

You can re-run this program to test again with the same data block,
or delete trimcheck-cont.json to create a new test file.

Press Enter to exit...

 

[AddRAM]

What is Trim.exe and How to Fix It? Virus or Safe?