Hello all,
I'm trying to clone a 500gb laptop drive to a new 750gb laptop drive (both Seagate Momentus drives) using DiscWizard v14,387, and running into an unmountable_boot_volume issue. My laptop is a Dell E6410. It's a pretty simple drive configuration (one 100mb SRP, and the rest is the Win 7 partition.)
I did a clone, and I followed the instructions provided with DiscWizard:
http://www.seagate.com/files/www-content/support-content/downloads/discw...
(Specifically, chapter 15 - transferring the system to a new disc)
Specifically:
1) I created a bootable media disc
2) I used diskpart to clear off the destination 750gb hd
3) I put my original source 500gb drive in an external enclosure, and my new destination 750gb in the laptop. (Both drives are Seagate Momentus - which is why I was using the DiscWizard program.)
4) I booted from my rescue media
5) I selected Tools & Utilities -> Clone Disc
6) I used Manual mode (as I wanted to make sure to keep the SRP the same size
7) I chose the appropriate source and destination disks (easy to tell by model and size; and the fact that the destination showed unallocated)
8) Chose the Manual move method. I clicked on edit, and it looked like everything was good; the SRP partition size was still 100mb, and the win7 partition was sized as the rest of the drive; and they were in the correct order. The correct drive was marked active too.
9) The summary screen looked good, and the clone completed successfully.
However, when I tried to boot into windows (using only the new destination drive, still in the laptop - I disconnected the external original source drive and removed the rescue media cd), I got what looked to be a windows recovery boot (black screen which says "Windows is loading files" with a white progress bar) instead of the usual windows splash screen; and then it went to a blue screen with "A problem has been detected", saying UNMOUNTABLE_BOOT_VOLUME and giving a STOP:0x000000ED at the bottom.
I did some research, and found several sources that said to run chkdsk /r to fix this. Here's one:
http://support.microsoft.com/kb/555302
So I booted to my Windows Recovery disc and both chkdsk /f and chkdsk /r ran fine on the new destination hd. (0kb bad sectors and not even one rogue index entry.)
I also tried the Windows Recovery repair option, and it came up saying that it could not be automatically repaired. The weird thing is that with the Windows Recovery disc in the drive, I missed hitting F12 to boot from CD one time (I was trying to do multiple repair attempts, with reboots in between as was recommended by other posts), and it loaded into Windows just fine. In Windows, I was able to look at Disk Manager, and everything looks fine. I was also able to run a ghost utility; diskpart - which shows that the SRP starts in the same spot and ends in the same spot as the original disk. (I'll attach the disk management screens; the original, and the new one.) Windows looked like it was working fine when I was in it; and it found a driver for the new HD. However, when I tried to reboot, it went back to the blue screen UNMOUNTABLE_BOOT_VOLUME message. (So I started with the unmountable errors, was trying system repairs - missed one boot from CD, and it worked; but all subsequent attemps are back to the unmountable errors. Weird.)
Has anyone seen this before, and/or know how to fix it?
Any info would be appreciated. I'm hoping I can just try to fix the image I have, as it seems to have worked correctly (as far as the image being successful, and the partition info being in the same place; and the fact that for some reason, I was able to get into windows once and everything looked fine...)
FYI, this is from the diskpart utility; for the new 750gb destination drive:
Volumes Reported by OS
==========================================================================================================================================
Volume Path (Volume GUID)
Disk # Offset in Bytes Size in Bytes Starting Sector Ending Sector Size
==========================================================================================================================================
No path name found (\\?\Volume{dc4978ee-bb84-11df-a59d-806e6f6e6963}\)
Disk # 0 1,048,576 104,857,600 2,048 206,847 100 MB
C:\ (\\?\Volume{dc4978ef-bb84-11df-a59d-806e6f6e6963}\)
Disk # 0 105,906,176 750,049,558,528 206,848 1,465,147,391 699 GB
Here's the one from the working original source 500gb:
Volumes Reported by OS
==========================================================================================================================================
Volume Path (Volume GUID)
Disk # Offset in Bytes Size in Bytes Starting Sector Ending Sector Size
==========================================================================================================================================
No path name found (\\?\Volume{dc4978ee-bb84-11df-a59d-806e6f6e6963}\)
Disk # 0 1,048,576 104,857,600 2,048 206,847 100 MB
C:\ (\\?\Volume{dc4978ef-bb84-11df-a59d-806e6f6e6963}\)
Disk # 0 105,906,176 500,000,882,688 206,848 976,771,071 466 GB
So, it looks like the SRP is in the exact same spot, and is the exact same size; only the C Drive has expanded...
