I'm guessing you had Intel Smart Response Technology installed. It pairs a small, fast SSD with a larger, slower HD to create drive acceleration through caching. Read about it here: Intel Smart Response Technology. Thus, you may find an article like this one (How To Fix An Inaccessible Smart Response Technology Cache) helpful in putting your environment back to rights.
HTH,
--Ed--
Last edited by EdTittel; 28 Jul 2018 at 09:45. Reason: Fix URL formatting
Ken,
The storage drive with the Macrium image is in the bay of another computer.
It displayed 7/18/2018.
The default settings gave it about a week for auto updates.
In this link I had skipped or don't remember performing these sections: (the default settings were used)
Backup and Restore with Macrium Reflect | Windows 10 Tutorials
Create rescue media
Create differential or incremental backups
Based on the image seen does it appear that the problematic drive can now be sanitized and then clean installed with windows 10?
Is there anything else to check or double check?
Approximately 7 days of data would be missing from files?
When viewing disk management it appears that somehow the system reserved got onto the storage drive?
Would this have caused the post chkdsk /r crash?
How does this get fixed?
This is good news.
You don't even need to clean install the drive beforehand, just use the image to restore the drive exactly as you see in the image. On the other hand, you can just restore just the one partition you want if you clean install beforehand so as to not mess with the efi or recovery partitions. Personally, I'd just restore the whole thing, having done this many times so far.
Based on the image seen does it appear that the problematic drive can now be sanitized and then clean installed with windows 10?
Is there anything else to check or double check?
Approximately 7 days of data would be missing from files?
That's a new one. Looks like the system reserved partition was made active?! No wonder the boot sequence was messed up. It was booting to the system reserved partition. This needs to be fixed, I think you can use Macrium to fix the boot files but I'd go into diskpart and remove the active bit from that partition.When viewing disk management it appears that somehow the system reserved got onto the storage drive?
Would this have caused the post chkdsk /r crash?
How does this get fixed?
I agree, its looks like you can restore that partition althoughthe only thing I would question is the Raid 0 and what if any impacts it might have.
Which partitions were in the RAID 0? That could have a bearing.
You mentioned specific data files you did not want to loose, what partition are they on. I assume C the 426GB drive shown in Macrium. You could explorer the macrium image and ensure those files are there although as you said seven days old.
Is it possible that the second disk with the 500MB reserved is an old boot disk and we are just looking at history. See if that drive is MBR.
For clarification where is your disk management shot from?
It shows a C: at 230GB but Macrium shows the C: at 400+GB?
Last edited by Caledon Ken; 29 Jul 2018 at 11:00.
Still thinking about this. Revised previous post.
That second partition shouldn't be red (correct me if I'm wrong) in Macrium image and that is where the systems get info for boot. (As I understand it)
I wonder if it is red as macrium realizes it is only backing up half (Raid 0 ) data.
I wonder if rebuilding EFI partition would solve.?
Still the two different size c:'s puzzles me.
Thoughts / comments those on thread.
(Still if the image has the data zbook is looking for in its c: image that would be very good news.)
I think @Calendon Ken is right about the EFI partition being in red. The fact that it's showing red means the partition is almost full, something must have been writing quite a bit of data in that partition. Then there's the flash cache @zbook mentioned. It is likely the flash cache have been paired with the EFI partition and somehow filled it with data and possibly corrupted it in the process.
The EFI partition can be rebuilt, I think, without having to reinstall or reimage Windows back onto the 750GB drive, if that's the correct drive that was imaged. My EFI partition has only 25MB of data on a clean install, is this a normal amount on a fresh install on your computer as well?
Went looking for how to rebuild EFI and of course found this from Kyhi.
Moving / recreating EFI partition
Still would like to understand what we were looking at with respect to the different sizes of C:
I'm going to re-read.
Excuse the questions of clarification.
zbook you said you had a 750 GB drive, which I will assume is the "Windows or Boot or system" drive.
Then in the disk management shot there are two disks. Believe you said you had connected disks to another machine? Shouldn't there be three disks, the system disk of the host computer, the 750GB and the 1000GB. (This would likely answer question as to the wide differences in the size of C: between Macrium and disk management.) It seems the 750GB disk is not shown.
Thanks
Last edited by Caledon Ken; 30 Jul 2018 at 10:34.
Earlier today images were not able to be attached and the post turned grey. This is the third attempt and this time it will be text only and then an edit to post the images.
When the problematic drive crashed the 32 GB flash cache (RAID 0) was removed.
The 1 TB storage drive was also removed.
The 1 TB hard drive has the Macrium image.
This storage drive was then placed in another computer that has a 250 GB SSD and two empty hard drive bays.
The computer was rebooted.
After reboot the step to restore was done to view the status of the Macrium image and this image was posted into the thread.
To see the storage drive disk management was opened.
It displayed a MSR that was active.
The BIOS of the problematic computer was opened and the setting is UEFI native (without CSM).
There was another computer at one time where I had used this drive to back up files.
How a MSR go onto the storage drive is a puzzle.
The point of no return is the disk sanitization of the crashed drive.
HP tech supports wants this drive to be sanitized as there were many chkdsk /r done to fix chkdsk /scan problems and the multiple drive tests ( HD Sentinel, Crystal Disk, Atto, Sea Tools for Windows, HP UEFI diagnostics) never found any hardware problems.
For the disk management MSR problem on the storage drive the right click options are: open, explore, change drive letter and paths, format, shrink volume, delete volume, properties, and help
If the active MSR is a potential problem for the Macrium restore then it can be fixed before the restore. If it is not a potential problem that it can be fixed afterwards.
Does everything look ready for Macrium restoration? If so the disk sanitization can be started. Then clean install windows then install HP drivers then Macrium restore? Or Macrium restore before installing HP drivers and HP software such as support assistant and softpaq download manager? These are used to find the best HP drivers for the configuration.
The Macrium knowledgebase/support links I have not yet viewed and was planning to follow the Ten Forums tutorial. If there are any potential pitfalls please post.
The Macrium image has been viewed a few times and it appears that it has assigned several drive letters: F and G. Is this a potential problem? If it needs to be fixed what are the steps? One file was clicked on and it indicated that I did not have permission. Is that another potential problem with the restoration? Do you check the box to enable access to restricted folders? Or check the box for make writeable? Any other choices in the menu when attempting the restore?
Quote
