A while ago I had an Intel Matrix RAID-1 pair of drives that got broken. One of them turned “red” and – since both drives were only a few serial numbers apart – the other was giving issues the moment I tried fiddling with it.
These actions failed:
- Windows image backup – would end up with a “blue” screen indicating Windows 10 had a problem and was trying to collect data
- Paragon HDM
- Migrating the OS to a brand new RAID-1 set
- P2V
- Disk2vhd would hang at the 100% completion mark
What had succeeded was a regular Windows backup (a non-image one).
This is what I finally did to get it working again:
- Kill disk2vhd after it hung a few hours at the 100% completion mark
- Verify with
- Mark the VHD file as online using diskpart (first atach the vdisk, select disk, then mark it online)
- Verify with chkdsk that the image was in fact without problems
- Detach the VHD file using diskpart
- Copy the VHD file to a HDD that Paragon HDM would recognise
- Use Paragon HDM to perform a V2P copy
- Paragon expects a .VD file, but if you ask it to use all file types, it does recognise that VHD files contain disk images
–jeroen
References:
- [WayBack] recovery – How to recover data and partition after diskpart clean – Super User
- [WayBack] TestDisk – Partition Recovery and File Undelete
- [Archive.is] Paragon Hard Disk Manager Suite – Overview
- [WayBack] DiskPart Command-Line Options
- [WayBack] DiskPart.exe and managing Virtual Hard Disks (VHDs) in Windows 7 – GES on Windows 7
- [WayBack] Disk2VHD will not end properly – Sysinternals Forums – Page 1
- [WayBack] Disk2vhd
