To be clear - are you suggesting that I uninstall the disk driver in the currently working system (the 2 disk RAID-0 setup) - then create the clone to the new single SSD? Once that's done I would shift click shutdown - detach the RAID array - reboot into BIOS switch from RAID to AHCI - then try restarting?
I'm reluctant to "damage" the original working RAID setup as this is my fallback if all else fails. I do have a current backup though.
Best wishes,
Jon
Dear Samuria,
Thanks for your thought provoking question - can I check something with you? When using the Intel Mobo RAID solution (as I am here) does this take care of all the nitty gritty i.e. it presents the array as a single disk to Windows - which doesn't need to "know" that it is actually a RAID-0 array underneath?
If so, then I think I was wrong about my guess where the problem lies, as Windows shouldn't need anything special other than the standard Intel SATA drivers to read from the disk.... so it shouldn't be "the case of the missing RAID driver".....?? And more likely that the drive letter is just set incorrectly (as per other suggestions)......?
Just trying to think my way around the next best steps....
Cheers, Jon
Update: I tried switching over to the single SSD drive, then once it hadn't booted (as per usual):
I went into the BIOS and switched the SATA mode from RAID -> AHCI (save&reboot)
I booted from a Reflect recovery USB, and selected the option to fix Windows boot problems....
It found the new SSD, which I selected and then clicked finish (it did all its bcdedit stuff)... I followed the prompt to reboot the system.
I then see the MSI boot screen and the revolving circle of dots - but there is never any drive activity.
Eventually I see a light blue Windows failed to load screen with a big QR code thingie. I think it said that it failed to find the boot device and would then reboot.
Is there anything I can do to check the status of the current (RAID-0) install to check that there isn't something wacky that is getting cloned across and then preventing the boot drive from being found? What should a "normal" Windows disk layout look like?
Sorry about all the questions
Jon
Try this:
- connect the 3rd ssd, retain two old ones connected
- go to bios, retain two old ssds as raid, set 3rd one as sata if needed, set boot from raid if needed
- boot from raid, let os to install sata drivers (3rd ssd must be visible in disk mgmt), or install them manually if needed
- clone all partitions from raid to 3rd ssd
- set boot from 3rd ssd, boot from it
if the case of problems, screenshot or exact error message is absolutely necessary
Angry,
Is your machine booted via UEFI? Your blue screen screenshot looks like what would be expected when the boot order is wrong in your bios. Boot the PC and enter the bios. Look for the Advanced tab or section. In the Advanced screens look for Boot. Select Boot and look for Boot order. In boot order if your computer boots via UEFI make sure that the first device in the boot order list is Windows Boot Manager. If your machine does not boot via UEFI then make sure that new disk is first in the boot order list.
Save and exit the bios and see if it boots normally.
Typically cloning of a raid array to a single disk is not the best way to do a migration.
I have done this procedure several times on my front desk workstation. It had been set up in RAID 0 so that I could use two older SSD that had been upgraded on other workstations.
Migrating back to single SSD was very simple using MR, To Begin with, RAID 0 is a simple volume array on two or more disks. Still, it is a simple volume.
Creating a Full Disk Image of that Volume will capture the RAID driver as part of the Image.
Restoring at least using MR is accomplished by restoring to a single Drive, Which will boot as a single volume on a single disk. At that point, if RAID 0 is required or wanted that 2nd disk is introduced and the RAID 0 is recreated onto both disk.
As I did was to keep the volume on one single SSD and it remains today in RAID mode. Single SSD no RAID array created. I have to state that all my workstations and notebooks are using UEFI/GPT, I don't think the procedure is any different for a BIOS/MBR system. This is all detailed in the Macrium Reflect User Manual. See post 6 in this thread Migrating OS from RAID 0 to a single SSD Solved - Windows 10 Forums
If you wish to change from RAID to AHCI that procedure would be a separate operation.
Yeah, restoring a backup image file works fine. Cloning is very different than restoring an image. Cloning is a bit for bit copy so a clone would work or should work raid 0 to raid 0. Raid 0 to single disk is questionable. The OP getting BSOD indicates that a boot device cannot be found or that the boot device found has no boot files.
With MR Cloning or Restoring an image is the same result with RAID 0, however, I wouldn't try to clone since having the image prevents any chance of losing any data or bootability. Since nothing is changed in the BIOS The OP can replace his 2 disk raid Array disk back in the computer and carry on. Should any issues develop with the Image Restore? As stated earlier the RAID 0 is set up by the motherboard prior to windows booting For MR to restore to a 2 disk Array that Array would have to be set up Prior to the Clone or Image Restore otherwise it going to restore to a single Disk/SSD
Yes, that is correct. I have experienced many time the issue of the bios not finding the boot record properly by either looking at the wrong device or skewing the boot order out of wack. It pays to look and make sure that the device you wish to boot is in fact the first bootable device in the boot order list. If it is then there are problems with the boot record. That can be the result of the clone operation or disk corruption.
Quote
