Boot failure after chkdsk /r No bootable image found

zbook · 01 Aug 2018

Hi Ztruker ,

Just started the verify per post #32.
What does it mean to verify if the C: drive that it made the backup image from is no longer available for comparison?
If it is unable to complete verification or if it fails what would that indicate?

Boot failure after chkdsk /r No bootable image found-macrium-verify-8-1-2018-15-percent.png

It just completed:

Boot failure after chkdsk /r No bootable image found-macrium-verify-8-1-2018-100-percent.png

titetanium · 01 Aug 2018

zbook said:

simrick,

Thank you for the information on Macrium.

For these what would happen?

a) In some threads it is suggested for Windows upgrade failure to clean install and then restore.
Is this a fix for partition problems only and not other problems as it restores everything except applications?
When restoring an image via Macrium, it restores everything down to the last file as is when the backup was made. In other words, if the backup was before the BSOD/crash, then you have it exactly like it was before the BSOD/crash. If it was taken after the crash, then you would restore the problems along with the crash that just happened. Think of an image like a snapshot you take with a camera, the picture you take before the crash (healthy) is what you get when you restore, and likewise the picture you take after (unhealthy) is what you get when you restore.

b) For a Windows upgrade failure that may be do problems with Users or problems with drivers would this restore method work but continue to have Windows upgrades fail as it restores the problematic Users folders and drivers?
See above

c) If a default Macrium update is done after a BSOD will the restore have the malfunctioning driver that may have caused the BSOD?
Yes
For the C: failure in this thread it performed the chkdsk /r /v and then rebooted to wallpaper and log on. After logon it BSOD.
If a different drive had a logon and later in the day a BSOD followed by a default Macrium backup would a Macrium restore have a problematic driver for another BSOD after restoration? Yes

d) Does the Macrium restore work well for corrupt operating system and registry, malware that has integrated into Windows, but could restore problems related to malware that is already in non-windows files? It works well if you have imaged the drives long before the problems started and saved those images for later restoration. It's not as good if you imaged it with the malware, faulty drivers, etc. If you fixed/removed the problem before you took the image, it would work, but why trust data that has been tampered with malware even though it was fixed and removed?

@zbook,
Answers provided inline in the quote from your last post.

EDIT: Your image is verified, meaning it is good for restoration per your latest post.

simrick · 01 Aug 2018

titetanium said:

@zbook,
Answers provided inline in the quote from your last post.

EDIT: Your image is verified, meaning it is good for restoration per your latest post.

Good to know.

I see titetanium has already provided very good answers to your questions to me, so I'll just add a few bits....

zbook said:

simrick,

Thank you for the information on Macrium.

For these what would happen?

a) In some threads it is suggested for Windows upgrade failure to clean install and then restore.
Is this a fix for partition problems only and not other problems as it restores everything except applications?

Correct.
If partition issues are causing upgrade failures, then a clean install fixes partition issues, and the C partition only image can then be restored to get back to the working OS as it was at the time of backup.

zbook said:

b) For a Windows upgrade failure that may be do problems with Users or problems with drivers would this restore method work but continue to have Windows upgrades fail as it restores the problematic Users folders and drivers?

Correct.
Keep in mind though, that this scenario can also assist in trouble-shooting: i.e. you have several possible solutions, you try the first and it borks the system; you know what went wrong and you need to start over, so you restore the image again, and try the second fix, knowing what you now know from the first trial, and so on...

zbook said:

c) If a default Macrium update is done after a BSOD will the restore have the malfunctioning driver that may have caused the BSOD?

Yes. It puts everything back to the way it was when the image was made - it's a snapshot in time.

zbook said:

For the C: failure in this thread it performed the chkdsk /r /v and then rebooted to wallpaper and log on. After logon it BSOD.
If a different drive had a logon and later in the day a BSOD followed by a default Macrium backup would a Macrium restore have a problematic driver for another BSOD after restoration?

The default Macrium image would have captured exactly where the system was at that time. So, if a BSOD was about to occur, it would occur after the restore, unless you were able to put fixes in place to avoid it. If a BSOD due a faulty driver had previously occurred, and then the image was made, the image restored would include the faulting driver.

zbook said:

d) Does the Macrium restore work well for corrupt operating system and registry, malware that has integrated into Windows, but could restore problems related to malware that is already in non-windows files?

The restore will put everything back the way it was. If the system was corrupt, you would get a corrupt system. If the system was infected, you would get an infected system. Whatever it was when the image was made, is what you will get when it is restored.

Saving a collection of images works well in the case of infection or bad drivers, as then you will be able to restore a "clean" image if you've saved them back far enough in time.

zbook · 02 Aug 2018

Some surprises:

Tonight I pulled the trigger and attempted to use the HP BIOS disk sanitizer.

It displayed that the system configuration had to be changed by opening device configuration and change the SATA device mode to either IDE or ACHI.

The SATA device mode was on RAID.

The ACHI was chosen.

The computer booted to the HP logo with rotating dots
The dots stopped rotating (frozen)

A power off and on displayed preparing automatic repair then diagnosing your PC with rotating dots.
Then a freeze of the rotating dots.

A power off and power on displayed automatic repair: your PC did not start correctly
Press restart to restart your PC which can sometimes fix the problems.

You can also press advanced options to try other options to repair your PC.

Restart was selected > it displayed the HP icon with rotating dots > diagnosing your PC

RESET was available but was not yet selected.

Start up repair was selected > attempting repairs > couldn't repair (it never offered srttrail.txt)

Exit and continue to Win 10 was selected.

It displayed the HP icon with rotating dots > the rotating dots froze again.

Power off and on displayed preparing automatic repair > diagnosing your PC with rotating dots > repairing disk errors.

This might take over an hour to complete. It took less than 15 minutes

It then displayed the HP icon with rotating dots and froze.

The computer's Windows advanced troubleshooting menu (not using the iso yet) was reopened with command prompt.
bootrec /fixmbr was successful
bootrec /fixboot was successful
bootrec /scanos displayed 0 copies
bootrec /rebuildbcd displayed successful but with the 0 copies.

So planning to return to fix the rebuildbcd after the chkdsk

A reboot displayed the HP icon with rotating dots and then a freeze.

Command prompt was reopened.
bootrec /nt60 displayed:
bootsect {/help|/nt60|/nt52} {sys|all|,driveletter>:} [/force] [/mbr]

bootsect /nt60 all displayed:

Target volumes will be updated with BOOTMGR compatible bootcode.

C: (\\?\volume{00704c0d-3860-4dbf-9d6b-adcef9ed2178})
Successfully updated NTFS filesystem bootcode.

D: (\\?\volume{f53df534-0000-0000-0000-100000000000})
Successfully updated NTFS filesystem bootcode.

E: (\\?\volume{f53df534-0000-0000-0000-501f00000000})
Successfully updated NTFS filesystem bootcode.

F: (\\?\volume{2b29bca6-b4a5-41f8-81c8-2953d42f8de3})
Successfully updated NTFS filesystem bootcode

\\?\volume{c91e56f6-c570-4006-b709-78a6688e6546})
Could not open the volume root directory:
The parameter is incorrect.

\\?\volume{981c9357-660e45ee-9b2a-b7ee073de0bf})})
Successfully updated FAT32 filesystem bootcode.

Bootcode was not successfully updated on at least one volume.

chkdsk /r C:
run time ETA approximately 4 hours for the 750 GB HD...…..in progress

So there may be some options now to fix the C: drive with it being no longer in RAID and now in ACHI.

The 32 GB flash drive was not yet reinstalled as it is not in RAID 0.
The C: drive is GPT with an EFI partition.
The 1 TB storage drive with the puzzling active MBR was in the secondary bay.
The MBR was not yet deleted from the storage drive.
The BIOS is UEFI native without CSM.

zbook · 02 Aug 2018

chkdsk /r C: completed and displayed windows found no problems

The attrib commands failed:
attrib c:\boot\bcd -h -r -s
file not found bcd

cd boot
attrib bcd -s -h -r
file not found

regback completed but did not fix the underlying problem.

power on > HP icon > rotating dots > frozen rotating dots
power on > preparing automatic repair > diagnosing your PC with rotating dots

Opened this PC:
there are 5 drives:
local disk C: 260 Gb free of 698 GB
system reserved D: 463 MB free of 499 MB
new volume E: 74.2 GB free of 931 GB
recovery F: 101 MB free of 440 MB
boot x: 505 MB free of 508 MB

Inserted Windows 10 iso:

bcdedit | find "osdevice"
partition=C:

sfc /scannow /offbootdir=c:\ /offwindir=c:\windows
Beginning system scan. This process will take some time.

Windows resource protection found corrupt files but was unable to fix some of them.
Details are included in the cbs.log windir\logs\cbd\cbs.log.
For example X:\windows\logs\CBS\CBS.log.
Note that logging is currently not supported in offline servicing scenarios.

Diskpart displayed the Windows 10 iso on drive G:

dism /online /cleanup-image /restorehealth /source:esd:g:\sources\install.esd:1 /limitaccess
displayed: deployment servicing imaging and management tool (version 10.0.15063.0)
error 50
DISM does not support servicing windows PE with the /online option.
The DISM file can be found at X:\windows\logs\dism\dism.log

dism /Get-WimInfo /WimFile:g:\sources\install.esd
displayed:
windows 10 pro
windows 10 home
windows 10 home single language
windows 10 education

What are the options now?

Other dism commands?
Use a newer iso for the older OS?
Windows reset with save files if available?
Macrium options?
Kyhi boot rescue options?
Ubuntu/Linux options?
disk sanitizer?
format the EFI partition and install new boot partition files?

At this time it has moved from no bootable system found to a bootable system that does not boot and operating system corruption.

zbook · 02 Aug 2018

What are the pro and con of the above troubleshooting options for the next step?

Caledon Ken · 02 Aug 2018

Can I ask what data would be lost if you restored your PC. I know it is seven (now longer) days old but is it irreplaceable data?

Me, I would pull the trigger. Put device back together, boot from Macrium boot disk and restore.

zbook · 02 Aug 2018

The C: drive has irreplaceable data.
Also there is software that is difficult to reinstall.
(Even the Microsoft store had difficulty installing/activating the software)
For example an old edition of Microsoft office with the product key.

Will reset with save files have a similar result of restoring a Macrium backup image?
If not what would be the difference? Only the drivers?

Caledon Ken · 02 Aug 2018

No.

Reset with keep files keeps data but deletes apps (Old Office).

Reset Windows 10

Given C: is questionable I would be leary. HP wanted you to scratch.

If C: on the 750GB is good enough to communicate (file structures responds to dir etc) then create Kyhi's recovery disk, boot machine and copy data off.

Once the data is off you then can decide how important old programs are. Libre office does it all.

zbook · 02 Aug 2018

Won't Macrium restore files in a similar fashion as reset save files?
Both lose applications?
Macrium keeps drivers?
Both have a new operating system?
So the irrepairable windows 10 operating system is fixed by both?

If the reset save files is problematic then can still perform a Macrium restore?

If reset save files works then download and install Macrium and make a new backup image > HP disk sanitizer > clean install > restore Macrium image > reinstall applications

There is approximately 74 GB free space on the storage drive.
What is the method for the Macrium backup as the backup image will be different as the new backup may have different drivers, etc.
What do you think about the pro and con of this approach?