AUR and ACPHO bootable media troubleshooting
Hi, I've been having trouble trying to prepare for a system upgrade (new motherboard and processor). I've been trying to create bootable media on a USB stick in ACPHO using the "Acronis Bootable Media Builder" by clicking on "Acronis Universal Restore" under the "Tools" tab. I've tried the default linux based media type. This boots fine, but I'm planning on restoring my backup or ideally cloning my drive to my new NVME boot drive. I've read that there tend to be issues with the linux media type and NVME drives.
I've also tried the WinPE option, after installing the Windows 10 ADK and add-on. When booting to the media created this way, I get the error "Cannot Connect to 'localhost'". I've tried multiple links to the MVP Tool to try a different WinPE setup. But, most links require access I don't have and the ones I can access seem to be outdated and don't detect or work with ACPHO. As far as AUR, it loads and under OS I get "Cannot find an operating system on the current machine". Not sure what to do from here, any help is appreciated. Will post pictures of the errors.
ACPHO Build 40173
Thanks, Steven!
I found a few older links to the MVP Tool on threads regarding WinPE media created using the AUR bootable media builder. Which I was looking into because I was having trouble with a black screen when booting into the linux media. I've since booted into the linux media by changing the default graphics to onboard and that solved the problem. Now I'm trying to figure out if the linux media will work to restore or clone to a PCIe NVME drive. As I'm planning on upgrading my boot drive from a sata SSD. If not, I might need some help with the WinPE media using the MVP Assistant. I did end up finding and downloading MVP Assistant 2.2.1 before I read your comment. It seemed to hang at a certain point in the process that I don't remember right now. I'll go through the instructions again and see what happens. If it fails I'll let you know at what point.
So I haven't tried using MVP Assistant again. This is a picture of the error codes I get when booting into the WinPE media created using bootable media builder in ACPHO. I've looked for "Acronis Managed Machine Service". What I found was "Acronis Managed Machine Service Mini". That service is running and is set to automatic. This is while windows is running. I believe the problem is the service needs to be running when booting from the Acronis WinPE bootable media. I'm not sure how to do that.
Sorry but the Acronis bootable media does not use any of the Windows Services as it is a purely stand-alone tool that will work in bare-metal environments, i.e. on PC's with no installed OS.
The image appears to show that you have created AUR bootable media and are trying to boot from that media, based on the Module name: ur_tool_bartpe_...
I would suggest just trying to create the 'Simple' WinPE / WinRE version of the normal Acronis rescue media first and test booting with that.
KB 69472: Acronis Cyber Protect Home Office: how to create bootable media
Just tried booting into the normal rescue media (WinPE) and got this error: "Windows could not start" "There Isn’t Enough Memory Available to Create a Ramdisk Device". That was in "legacy bios mode" I believe it's called. Not UEFI. I'll try it in UEFI mode.
The media boot mode should always match that of the host OS on the same system, so if Windows uses UEFI so should the media.
All bootable media loads into memory then runs from the same.
The host OS is installed in MBR legacy mode and that's the mode in which I tried to boot the WinPE rescue media made with the normal rescue media builder (not the universal restore). I've searched "Windows could not start" "There Isn’t Enough Memory Available to Create a Ramdisk Device" but can't find anything useful. Also I uploaded a picture showing the process in MVP Assistant, which gets stuck at mounting wim. I've let to run for hours with no progress, so I assume something is wrong. I follow all the instructions as they are in the doc, so I don't know what's wrong.
Blitz, I see in your picture that the MVP Assistant project you created is located in G:\WinPE\. What is drive G:? Is it an internal drive or a USB drive? How big is it?
I'm just wondering if you were creating the project on the destination boot drive.
BrunoC wrote:Blitz, I see in your picture that the MVP Assistant project you created is located in G:\WinPE\. What is drive G:? Is it an internal drive or a USB drive? How big is it?
I'm just wondering if you were creating the project on the destination boot drive.
It's a 32GB USB drive.
Blitz, the project must be created on the hard drive. A project in the MVP Assistant Media Builder is not the build itself. First, create a project on the hard drive and from the Build menu you select the USB drive to create the boot media.
I suggest reading through the Help for the media builder.
BrunoC wrote:Blitz, the project must be created on the hard drive. A project in the MVP Assistant Media Builder is not the build itself. First, create a project on the hard drive and from the Build menu you select the USB drive to create the boot media.
I suggest reading through the Help for the media builder.
Thanks, Bruno!
I did read through the powerpoint, but I guess I didn't read that part very carefully. I was able to create the media and boot from it no problem. One issue I have is an error about the source clone drive not being able to lock, and to use linux based media instead. I have linux based media available as well, which I can boot into. My new NVME drive is the destination for the cloning, but AFAIK if the drive is not in RAID it shouldn't be an issue. Not entirely sure. One last question I have is about the cloning process. I don't know whether to pick "To replace a disk on this machine" or "To use on another machine". I'm upgrading from Sata SSD to NVME as well as changing my motherboard and processor. So my first instinct is to treat it as a new machine, but I want as close to an exact clone of my original drive as possible.
One last question I have is about the cloning process. I don't know whether to pick "To replace a disk on this machine" or "To use on another machine". I'm upgrading from Sata SSD to NVME as well as changing my motherboard and processor. So my first instinct is to treat it as a new machine, but I want as close to an exact clone of my original drive as possible.
I would suggest trying to keep your planned actions as separate as possible if you can.
If you current machine supports the NVMe SSD then take on that challenge first before doing a full heart transplant with the new motherboard and CPU etc.
With NVMe, I would recommend installing this in the existing machine if possible while still using the original SATA SSD - this will allow any new device drivers to be identified and installed by Windows before you attempt to do the migration. You should recreate the rescue media after doing this.
The choice about replacing the disk on this machine or using on another one only applies to cloning and my personal recommendation / preference would be to use Backup & Recovery - Not cloning! B&R is a lot safer than cloning and avoids the scenario of having both drives in the machine and potentially seeing a disk signature clash if you try to boot into Windows after duplicating the drives.
A full backup of the source disk is always recommended before using cloning so you would be already half way there!
If your current machine doesn't support installing the NVMe SSD, i.e. has no provision for this type of drive, then I would suggest doing the motherboard & CPU change while keeping the existing working SATA SSD and ensure that this is working then take on the migration from SATA to NVMe after that.