My Cloned SSD is no longer booting.

zbook said:

Which drive was booted to run the commands?
Which drive needs to become bootable?

Disk 0 :ST1000DM003-1SB10C
Disk 1 :ST500DM002-1BD142
Disk 2 :CT1000MX500SSD1

First scannow:

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

Second scannow:

Code:

Windows Resource Protection did not find any integrity violations.

Disk 0 = MBR
Disk 1 = GPT
Disk 2 = GPT


Please post an image of the current BIOS settings:
UEFI native (without CSM)
UEFI hybrid (with CSM)
Legacy

Disk 0 is the one that is running these batch commands.
Disk 2 is the one that is not booting.

How does one discover bios settings?

Each BIOS may have different menus.
The computer has booted a MBR drive.

List of PC brands with their corresponding hot-keys

So explore looking for these terms:
UEFI native (without CSM)
UEFI hybrid (with CSM)
Legacy



Please run: V2
BSOD - Posting Instructions
How to Upload and Post Screenshots and Files at Ten Forums


When drives fail to boot a Windows 10 iso flash drive can be used to troubleshoot by running commands using Windows Recovery Environment (RE).
https://www.microsoft.com/en-us/soft...load/windows10
Download Windows 10 ISO File
Create Bootable USB Flash Drive to Install Windows 10

zbook said:

Each BIOS may have different menus.
The computer has booted a MBR drive.

List of PC brands with their corresponding hot-keys

So explore looking for these terms:
UEFI native (without CSM)
UEFI hybrid (with CSM)
Legacy



Please run: V2
BSOD - Posting Instructions
How to Upload and Post Screenshots and Files at Ten Forums


When drives fail to boot a Windows 10 iso flash drive can be used to troubleshoot by running commands using Windows Recovery Environment (RE).
https://www.microsoft.com/en-us/soft...load/windows10
Download Windows 10 ISO File
Create Bootable USB Flash Drive to Install Windows 10

Hey @zbook
I've done the V2 log collector
I'm not clear on why this will help in my current circumstance, which is I cannot run this on the build that is having the issue. I am running it on the computer that is my diagnostic computer. All I can do is install the faulty boot drive in this one as a readable volume, which it does. The V2 output will show that configuration. Please let me know if and how this should be done differently.

Currently reading up on RE but not sure where to instigate the procedure. I have Win10 on a bootable flash drive now. I also have a version with Macrium Reflect on it. Can I set my diagnostic build to boot with one of these flash drives and start the RE from there?

Thanks in advance of course

For the computer in which V2 was ran: ASUS H110M-C

The BIOS: Version/Date American Megatrends Inc. 1803, 5/18/2016

1) Upgrade the BIOS: 1803 > 4212
H110M-C｜Motherboards｜ASUS Global

2) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10

3) Run HD Sentinel: (free or trial edition)
Hard Disk Sentinel - HDD health and temperature monitoring
Hard Disk Sentinel - HDD health and temperature monitoring
For each drive post images of these tabs into the thread:
Overview tab
Temperature
SMART
Disk performance

Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10


4) The firmware is set for BIOS
The bootable HD: ST1000DM003-1SB10C is MBR


Earlier CT1000MX500SSD1 was reported to be the non-bootable SSD drive:
Disk 2
PartitionStyle: GPT
Size: 931.51 GB
Partition 1 = System 100 MB
Partition 2 = Reserved 128 MB
Partition 3 = F: Basic 464.98 GB
Partition 4 = Recovery 567 MB not enabled
Partition 5 = G: Basic 465.75 GB

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 734.9 GB
Total Space: 953.2 GB
File System: NTFS
      Model: ST1000DM 003-1SB10C SCSI Disk Device

      Drive: E:
 Free Space: 476.8 GB
Total Space: 476.9 GB
File System: NTFS
      Model: ST500DM002-1BD142

      Drive: F:
 Free Space: 240.1 GB
Total Space: 476.1 GB
File System: NTFS
      Model: CT1000MX500SSD1

      Drive: G:
 Free Space: 476.8 GB
Total Space: 476.9 GB
File System: NTFS
      Model: CT1000MX500SSD1

glypto said:

How does one discover bios settings?

When you power up, depending on the type, but typically either hitting several times the Escape or F2 key, some computers F10 or F 12 I repeatedly will get you into the BIOS. Some systems will show you briefly a line of text as to which key[s] will allow you to enter the BIOS configuration.

There you can navigate around, some of them with a mouse pointer most of them with navigation keys and find the relevant section and settings.

Simplest way to take a picture is to whip out your smart phone take a screenshot and upload it.

CountMike said:

For BOOT problems, BOOT from rescue USB you hopefully created with MR and choose the fix for it.

Well this turns out to be the simplest and effective solution ¯\_("̷ )_/¯ Though there was a fair amount of uncertainty about *where* to initiate the procedure. As mentioned the drive in need of repair was removed and installed on a separate system for diagnosis. (Which happened to be 13 miles away in a place of work) So as I researched and fussed with how to interpret the problem I had to contend with having the right hardware/software together in the right machine for the correct procedure. Not being one who does this on a daily basis it's actually confounding to get clear on what the limiting factors are. So I created the USB rescue flash drive with MR installed from the work computer after signing up for the trial version. Taking that and defunct drive back to the home system and initiating the MR Rescue environment from the USB. Basic from there as the options are simply let the rescue wizard interpret the conditions and only one option was presented in the group of four potential rescue options. (reinstalled the INI library apparently). Click finish and off to the races.

Honestly, I was paralyzed over the prospect of trying some combination of suggestions based on the general misunderstanding of my circumstance. I do get that it's involved and these batch files that TENforum puts together I assume are helpful, but they needed to be run on the machine that wouldn't boot.

Anyway, thank you all for giving a damn and taking a shot.

How is everything booting now?

Were the computers tuned up?

zbook said:

How is everything booting now?

Were the computers tuned up?

Rebooted just now to test that and it's as fast and smooth as I remember it from 2 weeks ago when SSD made my system 10X faster. I can't recommend it enough.

Macrium Reflect to be commended here...

Nice.

Please update the progress with the steps in post #24.

And when applicable please mark the thread solved.