Inaccessible_boot_device after cloning.
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
Hello!
My laptop has two NVMe drives. A couple of years ago, I successfully cloned the system NVMe to the secondary NVMe drive. Since then, my computer has been working fine with the OS on the secondary drive. Yesterday, I decided to reinstall my OS using the manufacturer's recovery solution. The problem is, this solution does not provide an option to choose the destination drive, so it restored the OS to the factory drive.
Since the secondary NVMe is better than the factory one, I decided to clone the OS to it again. Unfortunately, no matter which method I choose (disk-to-disk or disk-to-image), I cannot boot properly; I keep getting the INACCESSIBLE_BOOT_DEVICE BSOD, and it seems the OS drive is in offline mode. Additionally, after cloning, I completely wiped the factory NVMe. Two years ago, this exact cloning method worked flawlessly. Did I miss something this time? What did I do wrong?
Firstly, please backup important data.
Secondly, please give testing Clonezilla live a try.
You might have to use Windows installion disk to enter rescue mode and run bcdboot command. Please refer to this related discussion:
https://sourceforge.net/p/clonezilla/discussion/Clonezilla_live/thread/3daee68b8f/
Thank you for the reply. Fortunately, I made backup of all important data before cloning attempt. So, if I understand correctly, it has something to do with this change, right?
"Do 512B to 4kn fix for NTFS. This should be after NTFS file system is resized. Otherwise we have to enter MS Windows rescue mode, in the command prompt run: chkdsk c: /f"
Not very sure since I do not know if your disk is 4kn or 512e/n format.
However, still you can give it a try. Just remember to backup important data before you test it.