Clone problem: Disk cloning has failed. See log for details??
I have searched everywhere for a solution to my problem however cannot find one. I am trying to clone my hard drive to newly installed hard drive but getting error message.
Go to Clone Disk
*Automatic OK
SOURCE = Basic Disk 2 C: (NTFS)
DESTINATION = Basic Disk 1 E: (NTFS)
Confirmation: "the destination hard disk you have chosen contains some partitions that could contain useful data. Click OK to confirm deletion of all partitions on the destination hard disk."
*Click OK
*Click Proceed
"Disk cloning has failed. See log for details."
what is going wrong here anyone enlighten me?
Hi Colin,
Don't know where to find the log (I know idiot!). Trying to do it from within windows, recovery CD? Source disk does contain OS.
It is a NETWAY PC (Computer shop)
Intel(R) Core(TM) i7-2600 CPU @ 3.40 GHz, 8GB RAM
LOL found log (durrr!)
Error code 10 'File system error is found' with extended code 458, 776 MFT Bitmap currupted
Run chkdsk /r (the 'r' option is most important) on both your drives. Windows will need to reboot to run Checkdisk on your system, but it can run from within Windows for the new drive.
To chkdsk, hold the Windows Button down and press the 'r' button, type in cmd, you will get a black window pop up, type here chkdsk /r .
Got the following message:
Access Denied: You do not have sufficient privileges. You have to invoke this utility running in elevated mode.
OK,
Do:
Windows Start Button -> All Programs -> Accessories..... right click on Command Prompt and select 'Run as Administrator'. Then perofrm the above actions.
Sorry, I have my system set up to always open the command prompt in Admin mode, so I tend to forget sometimes that standard systems aren't.
thats ok.
I ran dick check on both C: and E: and got the following messages....
C:\> The type of file system is NTFS.
Cannot lock current drive
Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? Y/N
Y (hope that correct)
E:\> The type of file system is NTFS.
Cannot lock current drive
Chkdsk cannot run because the volume is in use by another process. Chkdsk may run if this volume is dismounted first. ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INALID. Would you like to force a dismount on this volume? Y/N
have not answered.
Thanks Colin
Also have not restarted yet to run C: disk check
Have restarted and now running disk check.
ok have run chkdsk on c: but not sure what that achieved or what to do next?
Did you run chkdsk /r ? Did it report fixing any errors?
No I left it running and walked away and when I got back it was restarted as normal. No screens telling me anything?!?!
That's the problem with these newer versions of chkdsk: you return to a normal screen without any obvious message as to whether tests passed or found errors.
Is e a log you can check or something?
Is there a log I can check or something? (is what I meant)
No, the information is not kept, assuming if it did find something it fixed it, perhaps you should try again and see if Windows still reports a problem. Other than that, run chkdsk /r again ( as you didn't state you used the 'r' parameter, I'll emphasise again that this is important) and see what it reports.
I'm not sure why it rebooted your system as I normally get a choice offered on completion.
All chkdsk logs are stored as Windows events, and the results can be viewed in event viewer.
All chkdsk logs are stored as Windows events, and the results can be viewed in event viewer.
I hadn't realised that James, which log do they appear in, the Windows-CorruptedFile one or DiskDiagnostics?
I did a chkdsk/r
Also I ran the chkdsk/r on the C: which it completed during a reboot however the E: says it will force a dismount on the volume (do I want the volume to get of his horse?)?
C:\> The type of file system is NTFS.
Cannot lock current drive
Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? Y/N
E:\> The type of file system is NTFS.
Cannot lock current drive
Chkdsk cannot run because the volume is in use by another process. Chkdsk may run if this volume is dismounted first. ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INALID. Would you like to force a dismount on this volume? Y/N
Errors that occurred that day (day I ran chkdsk/r):
APPLICATION
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
Activation context generation failed for "c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll" on line 3. The value "MAJOR_VERSION.MINOR_VERSION.BUILD_NUMBER_MAJOR.BUILD_NUMBER_MINOR" of attribute "version" in element "assemblyIdentity" is invalid.
Activation context generation failed for "c:\program files\R\r-2.15.2\Tcl\bin64\tk85.dll".Error in manifest or policy file "c:\program files\R\r-2.15.2\Tcl\bin64\tk85.dll" on line 9. The value "x64" of attribute "processorArchitecture" in element "assemblyIdentity" is invalid.
Activation context generation failed for "c:\program files\R\r-2.15.1\Tcl\bin64\tk85.dll".Error in manifest or policy file "c:\program files\R\r-2.15.1\Tcl\bin64\tk85.dll" on line 9. The value "x64" of attribute "processorArchitecture" in element "assemblyIdentity" is invalid.
Warnings that occurred that day:
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.
DETAIL -
1 user registry handles leaked from \Registry\User\S-1-5-21-3141636644-888800007-1615434674-1000_Classes:
Process 720 (\Device\HarddiskVolume2\Program Files (x86)\Kaspersky Lab\Kaspersky Internet Security 2012\avp.exe) has opened key \REGISTRY\USER\S-1-5-21-3141636644-888800007-1615434674-1000_CLASSES
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.
DETAIL -
1 user registry handles leaked from \Registry\User\S-1-5-21-3141636644-888800007-1615434674-1000:
Process 1040 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-3141636644-888800007-1615434674-1000
SYSTEM
Warning:
The driver \Driver\kbdhid failed to load for the device HID\VID_046D&PID_C52E&MI_00\8&23bb8eb2&0&0000.
ADMINISTRATIVE EVENTS
ERRORS:
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
The server could not bind to the transport \Device\NetBT_Tcpip_{F1CA21EE-88D2-4BCC-9498-00B6D4DA5613} because another computer on the network has the same name. The server could not start.
Activation context generation failed for "c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll" on line 3. The value "MAJOR_VERSION.MINOR_VERSION.BUILD_NUMBER_MAJOR.BUILD_NUMBER_MINOR" of attribute "version" in element "assemblyIdentity" is invalid.
Activation context generation failed for "c:\program files\R\r-2.15.2\Tcl\bin64\tk85.dll".Error in manifest or policy file "c:\program files\R\r-2.15.2\Tcl\bin64\tk85.dll" on line 9. The value "x64" of attribute "processorArchitecture" in element "assemblyIdentity" is invalid.
Activation context generation failed for "c:\program files\R\r-2.15.1\Tcl\bin64\tk85.dll".Error in manifest or policy file "c:\program files\R\r-2.15.1\Tcl\bin64\tk85.dll" on line 9. The value "x64" of attribute "processorArchitecture" in element "assemblyIdentity" is invalid.
WARNINGS:
The driver \Driver\kbdhid failed to load for the device HID\VID_046D&PID_C52E&MI_00\8&23bb8eb2&0&0000.
The driver \Driver\kbdhid failed to load for the device HID\VID_046D&PID_C52E&MI_00\8&23bb8eb2&0&0000.
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.
DETAIL -
1 user registry handles leaked from \Registry\User\S-1-5-21-3141636644-888800007-1615434674-1000:
Process 1040 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-3141636644-888800007-1615434674-1000
I'm afraid I've never seen Checkdisk report errors about registry or internal errors. I'm not sure at the moment where to go next.
You aren't running Bitlocker or some other form of encrypted drive such as Truecrypt?
Have you checked to make sure you have no virii or malware lurking on your PC? Ideally, Windows Restore needs to be disabled to be totally sure when running a file scan for virii etc, but switching this off will delete all your install points. Some types of virus an dmalware hide in the hidden restore folder and respawn everytime the system boots.
Running System File Checker (sfc /scannow) from a command prompt might be able to repair faulty files.
Colin,
The errors reported above are not related to running a chkdsk, just errors reported in event viewer.
The chkdsk logs are in the Windows Logs/Application section.
Highlight the first event entry and then do a search for chkdsk.
Both on demand (chkdsk) and scheduled pre-boot (wininit) chkdsk operations are recorded.
additional info: http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event…
As suggested by MVP James F,
open Event Viewer
Expand the Windows log into the Apllication listing
Look under
Source=WinInit
Event ID=1001
The date and time listing will be about the time chkdsk was run.
Appears to have been successful with no errors?
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
3 minutes later it logged the following
Windows (4168) Windows: The database engine has successfully completed recovery steps.
Then 5 minutes after that
The Windows Search Service started.
ran a sfc/scannow
windows resource protection did not find any integrity violations.
Maybe some back story might help put it in perspective...
The reason I am trying to transfer everything off the hard drive to a new one is because there is a corruption that is causing it to crash showing the blue screen. This appears to occur only when using Microsoft excel however reinstalling and repairing Microsoft excel did not fix the problem and so I am cloning the data from the hard drive to a new (un-corrupted) hard disk.
If you can think of something I might be missing that is causing the crash then if I can fix that there is no need to do the clone. I had considered that it could be an error that could be transferred to the new disk but thought "hmmm cloning isn't that hard maybe try that since I had a hard disk available". I think my thought were wrong
Just some thoughts. Not sure if they're applicable...
Is the system where recovery being attempted a company issued device? If so, companies usually use a third party or OS based encryption to protect sensitive information should it be stolen or otherwise compromised. My own company lap top has encountered this issue with Excel and Access dbs. For me cloning was not an option and hours of work were lost.
There may also be a ".bak" type file for Excel. It contains an image of the Excel document you were working. I understand that the disk may be corrupt or bad, however, a recovery is sometimes possible in Excel by opening the document, then saving in .csv format (if this is feasible for you). I have also successfully recovered Excel/Word/Powerpoint documents by just using the copy command from one part of the disk to another, or to another disk - though this is rare.
While cloning a drive though, if the corruption lies within the Excel document (and possibly on the disk itself); a clone usually results in a clone of the corruption. It is unlikely that the cloning product will be able to tell if the corruption is within the document; though Acronis is very good about their reactions to hardware issues.
Like I said, just some thoughts, and don't know if they're relevant.
Just some thoughts. Not sure if they're applicable...
Is the system where recovery being attempted a company issued device? If so, companies usually use a third party or OS based encryption to protect sensitive information should it be stolen or otherwise compromised. My own company lap top has encountered this issue with Excel and Access dbs. For me cloning was not an option and hours of work were lost.
There may also be a ".bak" type file for Excel. It contains an image of the Excel document you were working. I understand that the disk may be corrupt or bad, however, a recovery is sometimes possible in Excel by opening the document, then saving in .csv format (if this is feasible for you). I have also successfully recovered Excel/Word/Powerpoint documents by just using the copy command from one part of the disk to another, or to another disk - though this is rare.
While cloning a drive though, if the corruption lies within the Excel document (and possibly on the disk itself); a clone usually results in a clone of the corruption. It is unlikely that the cloning product will be able to tell if the corruption is within the document; though Acronis is very good about their reactions to hardware issues.
Like I said, just some thoughts, and don't know if they're relevant.
Hi Jim
No it is not a company issued computer so no protection on it.
Thanks for the advice on lost worksheets :) Yes I was worried that the corruption may be transferred to the new disk but I just can't think of other solutions