Aller au contenu principal

restore image with snap deploy to a different drive letter

Thread needs solution

Hi,

I have a image XP-Pro with 3 partition (c,d,e) to be restore with Snap Deploy on a other computer.
The new one already have Win7 (c,d), XP-Pro-64 (f) and data disk to I,G. When I restore the image it give the folowing drive letter to the new partition on an other disk (e,h,j).

When I try to boot on the new image, it do'nt boot. Get an error message about ntoskrnl.exe missing. However he file is there. I notice that in the drive E (suppose the system drive) I got the drive
letter F in the shortcut for some (may be all) of the application.

The F disk is define has (Boot) not the E disk.

Any solution that one might think to be eble to boot on the e: drive?

Regards,

André

0 Users found this helpful

Hello André,

Thank you for using Acronis Corporate Products

Please unplug the old hard drives from the new system. You should leave a single hard drive you want to deploy the image to. After that deploy the image and boot into Windows.

After that you can connect the old hard drives back. Please note that you should specify the first hard drive to boot the system from in BIOS.

Thank you.

Hi oleg,

Thank's for the responce. Some more point,

doing this will it change the drive letter of the old system? If so the system W7 may not start, and
the XP-64 in F to. Will I keep my dual boot?

Regards,

André

Hello André,

Thank you for your response.

If you return the old hard drives back (I suppose it was set as the first HD in BIOS), the drive letters shouldn't be changed. The dual boot system will be functional.

Thank you.

Hello Oleg,

I do return the 3 olds hards drives, and it is set to the first HD in the bios. Remember that HD have
Win-7 (c:,d:) and xp-64 (f:). the result is that the old hd return back to the same drive letters and
the new one go to e:,h:,j;. And unable to boot on the new one, same error, even if I put the new
disk in the boot sequence of the dual boot (this was install automaticaly when I install xp-64 before).

Regards,

andré

Hello André,

Let me clarify some information regarding this particular file:

ntoskrnl.exe is the kernel image for the family of Microsoft Windows operating systems. It provides the Kernel and Executive layers of the Windows NT kernel space, and is responsible for various system services such as hardware virtualization, process and memory management, etc., thus making it a fundamental part of the system. It contains the Cache Manager, the Executive, the Kernel, the Security Reference Monitor, the Memory Manager, and the Scheduler, among other things.

Here is the list of possible causes:

  1. Keyboard issue
  2. Miscellaneous corruption
  3. Corrupt boot.ini file.
  4. Missing boot.ini file.
  5. Missing or corrupt ntoskrnl.exe file.

Most probable cause in this particular situation the cause is corrupt or missing boot.ini file. But I'd recommend you to exclude all causes one by one:

Keyboard issue

This issue has also been known to be caused by a short in the ground wire in the keyboard cable. Make sure this is not the cause of your error by replacing the keyboard with a different keyboard or simply just disconnecting the keyboard from the computer.

Before trying any of the below recommendations it's recommend that you attempt to load the last known good configuration.

Make sure the line pointing to the operating system and its drive and partition is properly configured in the [boot loader] and [operating systems] by opening boot.ini file with text editor (it's located in the root directory of your active partition, for example C:\boot.ini)

Also, you may try restoring boot.ini file with Windows CD, but in this case it will damage your dual boot (second system won't boot at all)...

If the ntoskrnl.exe file is corrupt or missing this can also generate the error. To restore this file follow the below steps.

  1. Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
  2. Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
  3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
  4. Select the operating system you wish to fix, and then enter the administrator password.
  5. Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
  6. You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file.
  7. Type exit to reboot the computer.

Please let us know the results!

We are looking forward to hearing back from you at your earliest convenience.

Thank you.

Hi,

I did all that before I did the post. ;-)

what I see is if your image you start with, in my case a previous XP with c,d,e drive letter, you
could not use other drive lettre on the new system (In my case, the new computer already have drive lettre c,d,e from other disk drive). And I thing that the reason for this is that in the 'old system' registery, all the software and the most important the system (OS) are hard coded to c:. I do not think that SD can chage that. Any how if it does, I do not know how to do it.

Regards,

André

Hello André,

Thank you very much for the clarification. Yes, if none of solutions don't help, it means that your letters were changed, while the values in registry are the same. Please create a backup of the following folder:

\Windows\System32\Config folder. The most important file is SYSTEM hive - its entries are boot-critical.

After that, you should import the registry with correct values to your system as follows:

  1. Click the Start menu and click Run.
  2. Type "regedit" and click OK.
  3. Click Registry in the Registry Editor toolbar.
  4. Click Import Registry File.
  5. Browse to the directory containing the file (with .reg extension) and select the file.
  6. Click OK to import the registry file.

After that, please change the following:

- Clean registry key HKLM\System\CurrentControlSet\Enum\Storage\Volume\
- Clean registry key HKLM\System\MountedDevices

You should clean up the contents of the above mentioned keys. If there are errors while deleting the keys then you'll need to adjust permissions for the keys. We strongly recommend you to create a backup of the system before applying the above changes as they may affect some of the installed software functionality.

Then perform the backup of this file and try restoring it to target PC, then check if the issue persists.

Thank you.