Boot failure after chkdsk /r No bootable image found

I'll bet some of those errors are because they were files being cached, stripped Raid 0. So the files are incomplete.

If the file names are too long for the copy command then you may have to purchase a copy of Macrium (see if you want a purchased copy for other machines as it is cheaper to buy in quantity) and restore the aaaaaa folder. This would give you everything as it was backed it up.

Then add the critical files from the 750GB from July 18, 2018 to crash.

When you start to copy to the 4TB is it empty? The fact that desktop.ini is dup just skip.

I know with the free version you can't backup at the file / folder level but You might be able to restore.

Here is their knowledge base on how to.

https://knowledgebase.macrium.com/di...g+and+browsing

I'm going to fire up a free copy and see if I can restore a folder.

It appears to restore files and folders they must be backed up as a file / folder and not an Image of a disk.

there are no file / folder options in free.

I'm experimenting with purchased but again it looks like you have to first do it as a file / folder.

Yes it looks like you have have backed up a file / folder in that format, ie not an image.

Still you should be able to use copy. You may have to give drive and folder much shorter names. Drive 4TBSea Target folder bbbbbb

There is no prompt for each file to change the name.
Instead it seems that each file name needs to be recorded when the interrupt message is seen and then move to the drive > find the file > change the file name. That would take months to accomplish with the number of files.

One of the other notebooks was hot on the left side top.
IPDT (Intel Processor Diagnostic Tool) was ran and displayed fail.
HP was contacted and at the same time the other computer was discussed.
The backup of the desktop was interrupted by a shutdown.

On power on the HP technician asked that the control + L key to be repetitively clicked to open a menu to turn off the Intel RST accelerator.
There was no option.
Prior to this I had clicked control + I key and it had displayed the identical menu for F keys.
There was no method found to turn off Intel RST accelerator.

The HP technician also mentioned LSI to turn off the raid controller.
I asked him what would happen if both the problematic drive and the 32 GB flash drive were both swapped on another G0 model and he said it would likely have a problem in that the raid controller could be different.

When the control + L did not work the return key was clicked and the computer attempted to boot windows.
preparing automatic repair > diagnosing your pc > the PC did not start correctly > press restart to restart your pc which can......fix the problem. You can also press advanced options to try other options to repair your pc.

The first advanced option was reset with save files > getting things ready with rotating dots > all ready to go. Make sure your pc is plugged in > resetting will remove apps and programs that didn't come with the pc, change settings back to defaults, reinstall windows without removing personal files > resetting this pc 2% > undoing changes > there was a problem resetting this pc no changes were made > cancel > troubleshoot > startup repair > checking disk for errors > This might take over an hour. > attempting repairs >

So this was a surprise that these advanced troubleshooting options were available at this time.

I'm expecting it to fail but it's worth the attempt.

The backup of the desktop folder will be restarted and likely run through the night and part of tomorrow.

In the windows advanced troubleshooting menu on the computer repair from an image was an option and was not tried.

The chkdsk attempting repairs failed > no bootable device found > power off.

HP called back and suggested power on with control + C
This method produced the identical result as control + L and control + I

So no progress made.

Then after the control + I, return was clicked, and the wall paper appeared: 5:43 Friday, September.

This is where clicking return had opened the logon and then it bsod before after running chkdsk /r.

So going to see what happens.