Rescue Disc problem

Danny, welcome to the Acronis users Forum.

More information is needed before members of the Acronis community can assist you in resolving this issue.

Looking at the screenshot it appears that you are using optical media, is this correct? The error message suggests that Acronis cannot write to the media because the DVD drive is busy. Is this a blank disk? What sort of disk (-R, +R, +RW).

What build of ATI 2021 are you using, the latest build of ATI 2021 is 39216 24-March-21. What operating system and build, for example Windows 10 Pro, x64 20H2 build 19042.867.

Is the burner internal or is it attached to a USB port? If internal, is it SATA or IDE (I still have an IDE writer on one of my ancient PCs).

The relevant log files would assist in understanding what is going on. To access the log files you need do download the MVP Assistant which is discussed in this thread. Unfortunately I cannot remember the log file to look for - I am on my iPad at the moment. So you will have to await further advice on the relevant log file.

Ian

Edited: Seniors moment, edited to recognise that you are attempting to create a rescue media. 

OK.... THANKS for the reply and help. I think I got everything you wanted so here's what I've got;

Windows 10 Pro 20H2 build 19042.804

True Image 2021  build 39216

DVD is internal SATA drive with a formatted DVD-R 4.7Gb disc

Attached is the log file ( I THINK ), not really sure it was confusing for me. I unzip the file into a folder and ran the exe file.

Nothing in the file seems to be relevant. I decided to check if I could burn a DVD recovery disk (build information in my first post) and it did not work. Looks like the problem is with new build of ATI. Attached is the screenshot showing the error message. Only difference was I was using a DVD-RAM not DVD-R.

Not sure what the issue is. I was creating a WinRE recovery disk. Need to create a support request. I suggest you do so as well.

Update: I attempted to create Linux recovery media and got the error message immediately rather than at the end of the process.

Further update: I will try downloading the ISO from my account and see if it works.

Ian

Have support case number now: case 04874841

Ian

Ian, please update us on a solution,once you have one. Thank you so much.

Well that is a relief to me:) I'll see about starting a report.

THANKS

And here's mine.

THANKS again for the help and support.

new case
04875079 

I was abled to create a Acronis Rescue USB Disk. Installed the new 1Tb NVMe drive with no partitions (only formatted). Installed the 500Gb m.2 drive in an USB Enclosure. Booted the system on the rescue disk, selected to clone a disk. Source being the 500Gb drive in the enclosure, destination being the 1Tb NVMe drive. I asked if I was replace a drive in the same computer (I said yes), showed it had a partition and said all would be erased I proceeded and it took about 20 minutes. System shut down, I removed the USB devices and booted the system but got the message Inaccessible boot device. So now I did the reverse and swapped the dives and I'm back to operating on the 500Gb drive.
Any ides what to try now?
THYANKS for the help.
Danny

Danny, have you tried using Backup & Recovery here instead of using Clone?

This has been working for me perfectly fine without the need to use any external enclosures when migrating my own Samsung 970 EVO Plus NVMe M.2 SSD drives.

See topic: Steve migrate NVMe SSD where I documented the process that I used when upgrading my laptop NVMe SSD drive using Backup & Restore.

Steve Smith wrote:

Danny, have you tried using Backup & Recovery here instead of using Clone?

This has been working for me perfectly fine without the need to use any external enclosures when migrating my own Samsung 970 EVO Plus NVMe M.2 SSD drives.

See topic: Steve migrate NVMe SSD where I documented the process that I used when upgrading my laptop NVMe SSD drive using Backup & Restore.

Steve... You used the Win-Pe based rescue?, and what is the MVP you listed in you description? It was suggested  to me to use the Linux based rescue. Could that be my problem? I'm unable to create a Win-PE rescue disk on my USB (32Gb Sandisk)

Thanks for the help.

Danny

Getting back to the  problem of creating recovery disk. I did some more testing (which I have shared with Acronis technical support) and the creation a recovery disk is hit and miss; I was able to create a Windows PE recovery disk and a Linux one (in the latter case there was the immediate error reported above but this time retrying allowed the disk creation to complete). I still have to do some more testing (but other more pressing things are getting in the way).

Ian

IanL-S wrote:

Getting back to the  problem of creating recovery disk. I did some more testing (which I have shared with Acronis technical support) and the creation a recovery disk is hit and miss; I was able to create a Windows PE recovery disk and a Linux one (in the latter case there was the immediate error reported above but this time retrying allowed the disk creation to complete). I still have to do some more testing (but other more pressing things are getting in the way).

Ian

Ian... Thanks for the reply. I've been working by email thru their support. I CAN NOT create a DVD rescue disk in either WIN-PE or Linux. However I was able to create a rescue usb disk with Linux but again NOT with the WIN-PE form.  I've had people over at the Western Digital forums tell me to use the Acronis s/w for WD. I've also had someone say it doesn't work well with Win10. so I uninstalled the Acronis 2021 and installed the WD version. I've been trying to clone the disk (several times now) with no luck.  I can boot into the usb rescue disk and perform the clone, but it will not boot that way. I'm puzzled by the option of selecting to make the clone for this machine (it says bootable os) or for installation in another computer (again bootable os) I've been installing the new 1Tb drive in the computer and the 500Gb in the usb enclosure to do the clone. Can't get it to work.  Some people have said to create an image of my hard drive, swap drives and do a restore. I'm not proficient in this method.

OEM versions of ATI invariably have limitations on the types of drives supported. If you are using a WD version it may not allow you to clone to a non-WD HDD/SSD.

In my experience, backup and restore is better than trying to do a clone. 

A bit more information may help: Is the new drive an M.2 drive (either NVMe or SATA), or is it a SATA drive (attaches to SATA port rater than M.2 port). Please confirm the size of both the new and the old drive (is the old drive an HDD or SSD). I assume you disconnected the old drive after completing the clone - if not that can cause all sort of problems.

You also need to ensure that when you boot using the recovery media you select the correct mode  - UEFI or BIOS/Legacy (to match the mode that the existing OS uses). If you get it wrong, Windows will not boot. There are several ways you can confirm the mode used, there are various ways you can find this out (see here). If the system use UEFI then you select Windows boot manager rather than particular drive as the boot device.

Ian

Hello Danny,

When a Windows system is installed, much like other operating systems, Windows OS installed firmware read/write I/O drivers into your system disk C:. This means that your 500GB SATA mechanical disk which you first installed Windows on has a different read and write technology than your NVMe solid state disk does. In order to come around this problem, you may use Backup / restore with Acronis in the boot disk menu instead of Clone disk. If you were to use the same technology, i.e. a 2TB mechnical SATA disk, you would be fine with a boot from cloned disk - most of the time.

Hope that made sense? and I hope I helped you too.

Sincerely,

Michael

If I were in your situation, I would install Win 10 x64 clean on the NVMe solid state, then Restore backup from 500GB SATA, and you'll be golden with your files.

Remember to install all drivers again on the new Windows system partition.

Just to clarify what Danny is doing here, see his post here - where he clearly states that he is attempting to upgrade his PC from a 500GB NVMe M.2 SSD to a 1TB NVMe M.2 SSD, so there should be no issues with incorrect or missing drivers for the SSD.

Installing Windows 10 first on the new SSD is basically a waste of effort as any disk restore from a backup will wipe that new install as the first step in preparing the target disk!

If using WD OEM version of ATI, then the target drive needs to be installed in the PC and be recognised as a WD drive due to limitations imposed by the OEM process.  The full ATI 2021 version does not have such limitations but there are recommendations if this is a laptop system and using cloning!

Please see KB 56634: Acronis True Image: how to clone a disk - and review the step by step guide given there.

Note: the first section of the above KB document directs laptop users to KB 2931: How to clone a laptop hard drive - and has the following paragraph:

It is recommended to put the new drive in the laptop first, and connect the old drive via USB. Otherwise you will may not be able to boot from the new cloned drive, as Acronis True Image will apply a bootability fix to the new disk and adjust the boot settings of the target drive to boot from USB. If the new disk is inside the laptop, the boot settings will be automatically adjusted to boot from internal disk. As such, hard disk bays cannot be used for target disks. For example, if you have a target hard disk (i.e. the new disk to which you clone, and from which you intend to boot the machine) in a bay, and not physically inside the laptop, the target hard disk will be unbootable after the cloning.

Danny, you asked about my reference to the MVP rescue media - this is an alternative method of creating rescue media that doesn't use the Acronis Bootable Rescue Media Builder tool, so would eliminate that as the cause of the issue here.

See my signature for a link to the MVP Custom PE Builder tool via the Acronis Community tools KB page.

Ian... MSinfo32 confirms the bios is uefi. I might be making that mistake. I'll have to try again. 

My old drive is a Western Digital M.2 2280 500Gb SSD.

New replacement drive is a WD NVMe 2280 1Tb SSD

I tried to clone the drive as the instructions for a laptop, thinking it was best. I must be missing something simple.

THANKS for the help.

Danny

Michael Stenlund wrote:

Hello Danny,

When a Windows system is installed, much like other operating systems, Windows OS installed firmware read/write I/O drivers into your system disk C:. This means that your 500GB SATA mechanical disk which you first installed Windows on has a different read and write technology than your NVMe solid state disk does. In order to come around this problem, you may use Backup / restore with Acronis in the boot disk menu instead of Clone disk. If you were to use the same technology, i.e. a 2TB mechnical SATA disk, you would be fine with a boot from cloned disk - most of the time.

 

Hope that made sense? and I hope I helped you too.

 

Sincerely,

Michael

Michael... Thanks for the reply.

My current drive is a Western Digital m.2 2280 500Gb SSD

Replacement drive is a WD NVMe 1Tb SSD.

I found that the old drive is operating under UEFI format. I might be making a mistake in my cloning process. I'm going to double check.

Thanks again

Danny

IanL-S wrote:

OEM versions of ATI invariably have limitations on the types of drives supported. If you are using a WD version it may not allow you to clone to a non-WD HDD/SSD.

In my experience, backup and restore is better than trying to do a clone. 

A bit more information may help: Is the new drive an M.2 drive (either NVMe or SATA), or is it a SATA drive (attaches to SATA port rater than M.2 port). Please confirm the size of both the new and the old drive (is the old drive an HDD or SSD). I assume you disconnected the old drive after completing the clone - if not that can cause all sort of problems.

You also need to ensure that when you boot using the recovery media you select the correct mode  - UEFI or BIOS/Legacy (to match the mode that the existing OS uses). If you get it wrong, Windows will not boot. There are several ways you can confirm the mode used, there are various ways you can find this out (see here). If the system use UEFI then you select Windows boot manager rather than particular drive as the boot device.

Ian

Ian....I just double checked my booting into rescue disk. It is listed as UEFI USB partition 1

When I look at ATI form the rescue disk and select BACKUP, it shows 2 options Dsik and partition backup or data backup. Is the disk and partition backup an image of the drive? It has been told to me that I should not try the cloning, but do an image and then a restore.  Your thought on this?

Thanks

Danny

 

Danny, thanks for the additional information.

Am I correct in assuming that the motherboard has two or more M.2 sockets? Or do you have a USB M.2 adapter - if the latter check that it supports NVMe M.2 drives, some only support SATA M.2 drives. If the motherboard has multiple M.2 sockets, check the user manual as I have a dim recollection of seeing a (rather old) motherboard where the second M.2 slot only supports SATA M.2 drives. Also, if you are using a PCIe M.2 add-in card, some do not support NVMe drives. (I am assuming that both drives are NVMe rather than SATA.)

At the moment I cannot think of anything else that may allow you to clone the drive, or for that matter creating a backup and restoring to the new drive.

Ian

IanL-S wrote:

Danny, thanks for the additional information.

Am I correct in assuming that the motherboard has two or more M.2 sockets? Or do you have a USB M.2 adapter - if the latter check that it supports NVMe M.2 drives, some only support SATA M.2 drives. If the motherboard has multiple M.2 sockets, check the user manual as I have a dim recollection of seeing a (rather old) motherboard where the second M.2 slot only supports SATA M.2 drives. Also, if you are using a PCIe M.2 add-in card, some do not support NVMe drives. (I am assuming that both drives are NVMe rather than SATA.)

At the moment I cannot think of anything else that may allow you to clone the drive, or for that matter creating a backup and restoring to the new drive.

Ian

Ian... Thanks for the reply.

My MB only has 1 M2 socket. The MB supports both M.2 SATA and NVMe drives. 

The USB Enclosure is supposed to support both SATA SSD and PCIe NVMe drives 

My old drive is a SATA M.2 SSD, new drive is NVMe SSD. All the instructions I find in Acronis website says cloning is the way to move  from 1 drive to another and use an usb enclosure

Danny

Danny,

What mode is your Storage Controller set as?  AHCI or RAID are probably your choices.  You should research if your motherboard may need to have the storage controller set to RAID in order to boot the NVME disk.

Enchantech wrote:

Danny,

What mode is your Storage Controller set as?  AHCI or RAID are probably your choices.  You should research if your motherboard may need to have the storage controller set to RAID in order to boot the NVME disk.

 

Thanks for the reply. The MB is set for AHCI.

I apparently the WD version of Acronis doesn't play well with Win10. In trying to perform "Disk and Partition Backup" with an external hard drive for the image, the program locks up. Going back to the retail version od ATI and see what happens.

Danny

Danny we seem to be making progress of a sort. Should have asked about the type of M.2 drive earlier. Never used a SATA M.2 drive. Is the CPU an Intel or AMD, what chipset does the system have? It is possible that a bios upgrade could fix the problem, particularly if you have had the system for a while.

Ian

If you are migrating from a SATA M.2 drive to a NVMe M.2 drive then the earlier comments from Michael about needing drivers do apply but this is complicated if you only have a single M.2 slot (that can accept both types), as the simplest solution would be to have both drives installed so that Windows automatically finds / installs the drivers for new hardware discovered.

IanL-S wrote:

Danny we seem to be making progress of a sort. Should have asked about the type of M.2 drive earlier. Never used a SATA M.2 drive. Is the CPU an Intel or AMD, what chipset does the system have? It is possible that a bios upgrade could fix the problem, particularly if you have had the system for a while.

Ian

Ian... The MB is a Gigabyte B450DS3H, with AMD Ryzen 2600X. Some of the BIOS updates are related to usb. Yesterday I tried to make an "Disk and Partition Backup" but the software froze. I was told that the Western Digital version of ATI doesn't play well with Win 10. So today, I'm going to reinstalled the retail version of ATI and see what happens.

Thanks

Danny

Steve Smith wrote:

If you are migrating from a SATA M.2 drive to a NVMe M.2 drive then the earlier comments from Michael about needing drivers do apply but this is complicated if you only have a single M.2 slot (that can accept both types), as the simplest solution would be to have both drives installed so that Windows automatically finds / installs the drivers for new hardware discovered.

Steve .... Thanks for the reply. If I read the Acronis instructions correctly, it says to use an usb enclosure to perform the cloning. I was told that the Western Digital version of ATI doesn't play well with Win 10. So today, I'm going to reinstalled the retail version of ATI and see what happens.

Thanks again

Danny

 

Danny, USB enclosures can be a mixed blessing as they can introduce new controller hardware that then is involved and can cause OEM versions of ATI (such as WD) not to recognise their own make of drive being connected via the enclosure.

Danny, one of my systems has a Gigabyte AMD motherboard (see information in my signature). Much older than yours. Looking at the driver used for the 3 Samsung NVMe SSDs, they all use a generic Microsoft Driver. There is also a Samsung driver for the Storage Controller (I understand it works in conjunction with the device driver - it will work without the Samsung driver which apparently adds optimisation). Not sure what BIOS/UEFI setting I have set - but it is a much older chipset so may not help much.

Steve Smith could be correct about the USB enclosure confusing the issue (when using the WD OEM version of ATI).

Ian

Danny,

I looked up your Gigabyte board and I find that for Windows 10 there are 2 RAID drivers available, one is for the Storage controller on the board, the other is for USB thumb drive recognition.  If I were you I would download and install both of these and see if that improves your situation.  A link below to the download page

https://www.gigabyte.com/us/Motherboard/B450M-DS3H-V2-rev-10/support#su…

I also had a look at your manual and it sounds like your SATA controller set to AHCI should work with the NVME disk.

Well I did that Disk and Partition Backup and restore to no success. Still get the inaccessible boot device.
I was following the instruction from the user's guide on the Acronis website.
I booted the system using the ATI USB Rescue Disk (made with WINRE based media-64 bit) Boot menu shows it as UEFI BOOT USB 1.
I did the backup to an external usb 1Tb drive. Selected shut down after completion.
Swapped SSDs and rebooted back with the same rescue disk as before and restored the back up image from the external drive. Shut down when completed.
Booted the system in BIOS, made sure that the new 1Tb was selected as 1st boot.The BIOS sees and is set to boot from Windows Boot Manager on the WD 1Tb drive saved and exited, reboot and got the error message.
The only thing I didn't do was pull the power connector from the DVD drive .

Danny

Danny,

Okay, try this,  download and install the RAID drivers from the Gigabyte website.  Install those on your old SATA disk. After install and a restart of the system make a backup of the SATA full disk all partitions.

Shutdown and swap out the old disk for the new and with your external disk holding the backup and the Rescue Media attached, start the PC and boot to the Rescue Media.  Now restore the backup image to the new NVME disk and shutdown.  Remove the external disk and the Recovery Media and start the PC.  Windows now having the raid driver available if needed to boot will find and load that driver and the PC should boot.

Steve Smith wrote:

Danny, USB enclosures can be a mixed blessing as they can introduce new controller hardware that then is involved and can cause OEM versions of ATI (such as WD) not to recognise their own make of drive being connected via the enclosure.

Steve.... I had problems with the WD version locking up when trying to do an image. I uninstalled that version and reinstalled the retail version of ATI. I had no lock ups, but still couldn't get it to work.

THAKS

Danny

Enchantech wrote:

Danny,

I looked up your Gigabyte board and I find that for Windows 10 there are 2 RAID drivers available, one is for the Storage controller on the board, the other is for USB thumb drive recognition.  If I were you I would download and install both of these and see if that improves your situation.  A link below to the download page

https://www.gigabyte.com/us/Motherboard/B450M-DS3H-V2-rev-10/support#su…

I also had a look at your manual and it sounds like your SATA controller set to AHCI should work with the NVME disk.

Thanks for the reply 

My MB is not the V2 as referenced in your link.  This is mine;

https://www.gigabyte.com/us/Motherboard/B450M-DS3H-rev-1x#kf

Not sure what specific differences there is. Trying to compare makes my head hurt. :)

Danny

Danny,

Link to the driver is below, these drivers are the same for both boards by the way.

https://download.gigabyte.com/FileList/Driver/mb_driver_609_amd_raid_9…

I did a clean installed with not much problem. Here's a picture of the drive structure before the install. Does this make sense? To me, not that smart on the drive structure, it makes me think that why I could never get the clone or the restore to work.  Since I've NEVER had to "clone" a drive before to a bigger drive I thought this was strange. Meaning the number of partitions. I hadn't "cleaned" the drive before this install. All the other times I've been trying to clone it I would Clean the drive before starting. I did delete all of the partitions to start a new installed. For whatever reason after a couple of restarts, I now have 60Gb free, up from 30Gb. So for now, I'm staying with the old drive.
THANKS for all your help. I REALLY APPRECIATED it.
Danny

Name                                    Total Size                             Free Space                          Type

Disk0 Part1                         128.0mg                               128.0mg                               MSR (Reserved)

Disk0     Part2                     499mg                                   59mg                                     Recovery

Disk9 Part3                         99mg                                     68mg                                     System

Disk9 Part4                         465.2Gb                               52.6Gb                                  Primary

Unallocated                        465.6Gb                               465.6Gb

Danny, the picture does not seem to have come through.

Ian

IanL-S wrote:

Danny, the picture does not seem to have come through.

Ian

I added the TEXT

The original drive shows 2 partitions

Part 1 499mb Recovery Partition

Part2 99mb Healthy EFI System Partition

Drive C: 465.16Gb NTFS

THANKS

Danny

Danny,

What looks off to me are the Disk numbers.  These partitions look fine but all of them ought to be on Disk 0.  What you post shows the System and Primary partitions on Disk 9.  Can you run the commands below and post the results for us?

• From an admin command prompt type diskpart - press Enter - wait for the utility to start
• At the diskpart command prompt type list disk - press Enter  - post your result
• At the diskpart command prompt type list volume - press Enter - post this result
• At the diskpart command prompt type exit - press Enter - You can now close the command window

Bob, I agree that they normally should appear on Disk 0. However this appears to depend on the Bios/UEFI. For some reason my Gigabyte Aorus GA-AX370-Gaming 5 motherboard when assigning Disk numbers first assigns them to those connected to on-board SATA ports (of which there is 8), then to the on-board M.2 port (0ne) , then to the M.2 drives two PCIe add-in cards, then to drives on the 4-port add-in PCIe SATA controller, and lastly to those on USB controllers. This is a first generation AM4 motherboard so oddities are understandable.

The system has a lot of drives, presently 14 (including 1 6TB USB HDD).

Ian

Enchantech wrote:

Danny,

What looks off to me are the Disk numbers.  These partitions look fine but all of them ought to be on Disk 0.  What you post shows the System and Primary partitions on Disk 9.  Can you run the commands below and post the results for us?

• From an admin command prompt type diskpart - press Enter - wait for the utility to start
• At the diskpart command prompt type list disk - press Enter  - post your result
• At the diskpart command prompt type list volume - press Enter - post this result
• At the diskpart command prompt type exit - press Enter - You can now close the command window

My STUPID mistake. NOT 9 but 0. I guess I can't type.

SORRY guys

Danny

 

IanL-S wrote:

Have support case number now: case 04874841

Ian

In case you haven't heard

This the response I got from Tech Support, although it took a long time and several uploads of reports.

As I checked with the team, "Device is busy" Bootable Media builder fails to create WinPE media on DVD from application is an known issue.

So as a workaround the team suggested to download the ISO from your account and burn to the DVD.

Danny

So your DVD drive sounds to be in use by another application therefore preventing the Media Builder from burning the DVD disk.

When you insert a blank DVD in the drive what action does Windows take?  Open drive to view files possibly?  If this is the case then you might try to change what Windows does upon insertion of a DVD disk to the drive.

1. In Windows 10, right click on the Start button and select Settings
2. Next, click on Devices
3. Now click on AutoPlay

Look for your DVD drive and set the option to "Take no action"  Restart the computer

Now run the Media Builder again after inserting a writable DVD and see what happens.

Ian,

I was more interested in understanding the partition structure on the OP's drive 0 which he confirmed the e typed Disk9 in error.

Bob, I understand that. Just intrigued by the strange behaviour of my machine.

Ian

Ian,

Actually I find the same behavior on my machines.  It is caused by the pecking order of device enumeration.  SATA storage controller(s) are first in that order.

Here's a good one for you, I recently assembled a new build using an older Z270 ASRock board that has a secondary PCIe chip on board which supports an additional 32 PCIe lanes giving the board a total of 64 lanes.  So this board has a total of 4 PCIe x16 slots on board and is able to support a 4 by 16 graphics card arrangement.  The board also sports onboard Intel HD graphics.  Since I have no interest in gaming I am using the additional PCIe slots provided by this onboard chip to run 2 x M.2 PCIe NVMe drives on adapter cards.  One of them is for the OS.  All other SATA ports are filled with SSD's. and there are 10 ports starting with port 0.  So my OS drive is drive number 10.

Enchantech wrote:

So your DVD drive sounds to be in use by another application therefore preventing the Media Builder from burning the DVD disk.

When you insert a blank DVD in the drive what action does Windows take?  Open drive to view files possibly?  If this is the case then you might try to change what Windows does upon insertion of a DVD disk to the drive.

1. In Windows 10, right click on the Start button and select Settings
2. Next, click on Devices
3. Now click on AutoPlay

Look for your DVD drive and set the option to "Take no action"  Restart the computer

Now run the Media Builder again after inserting a writable DVD and see what happens.

 

 

Blank DVD in the drive does nothing, explorer does not open drive light comes and goes out, end.

I dloaded the ISO and burned it to the dvd disk. and what happened?, good disk and I can boot from it no problem in selecting the dvd drive from the boot menu. I'm good on that process.

Now if I can figure out how to clone the damn drive from M.2 to NVMe. I might try another program.

Danny

 

mis-post

PROBLEM SOLVED

I was able to clone my 500gb M.2 SSD to my new 1tb NVMe SSD using the software from EASEUS.

I then extended the drive volume to use all the remaining space.

I neglected to mentioned that I had use the USB Enclosure and I had tried many times before.  I truly believe it was an Acronis problem

THANKS to all for the help.

Danny