Skip to main content

Rescue Media Builder just Corrupted 2 new Sandisk Flash drives

Thread solved

Hello,

I just tried making a bootable drive with 2 new Sandisk Flash drives.  32G (smallest I could get) 2.0 USB.  

I clicked on Rescue Media Builder, Clicked on Simple, Clicked on USB E (my drive) and clicked Proceed.

It started, the time bar got about 1/2 way and then stopped telling me it could not complete the job.  Now both disks say E drive not accessible, file or directory is corrupted and unreadable. 

I just reformated the 2 flash drives exFat.  They are both useable now.  

Now what?  What do I need to do to make a bootable flash drive?

 

Dan

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 488

Dear Daniel Becker,

Thank you for reaching out. In order to help you we have to ask what Acronis product and what version of the product you use?

Dan, how were the drives formatted when you ran the builder? I believe FAT16 or FAT32 is required.

If you cannot get the Acronis media builder to work, try the media builder in the MVP Assistant (link below in my signature).

BrunoC, 

I had not formated them.  I simply erased the Sandisk software and gave it a go.  I have gotten the drives working by reformating them but only had the option of exFat which I looked up and saw it is the new/current version of Fat32.

I just tried to make the boot drive again.  I made sure I check off Format and it worked this time. 

I don't recall seeing that option the first time.  So maybe reformating of the new drive before I used it was necessary.

Thank you all for your help. 

On to the next step.

One unrelated question: In my down load area there are Bootable Media and Universal Restore.  Do I need to install these with my Acronis Cyber Protect Home Office?  

Dan

The bootable media ISO is Linux and has limited driver support (cannot include proprietary drivers), so not the best option. Universal restore in only needed when moving to significantly different hardware - not needed as much as it used to be as Windows 10/11 have great driver support. I have never had the need to use it. Universal restore has not been updated since 8 August 2020 consistent with the decreasing need to use it.

You are much better off creating recovery media (either simple, or advanced [Windows PE], or use the media builder in the MVP Assistant as suggested by Bruno.

Ian

Ian,

Thank you for the information.  Why I'm into this is I am updating 3 older machines to SSD drives.  Two cloned with no issue.  The third twice as it started gave me a message after a while that the software was not responding.  Thus, I'm going to try the full backup recovery approach onto the new drive which requires the boot disk. 

It does get a bit confusing for someone like me with enough knowledge to get in trouble but not enough to really understand completely.  Example: Simple vs Windows PE.  I get simple, just click and go.  But what is Window PE and why would I choose that?  No clue.

With that, I have managed to produce a boot disk using the simple option.  I tested it on one of the machines that has the new SSD drive and it did boot.  It is a Lenovo B320.  It is my test machine as I have nothing of value on it.  I just use it to view stuff on the net.  The third machine I'm struggling with is also a Lenovo B320. 

I have to say, just like with fixing my vehicles, it appears computers can suffer from the mushroom event.  Fix or upgrade 1 thing and to get full benefit you have to update another thing.  In this case the ethernet/wifi hardware and router to get the speed so that backing up to the cloud does not take forever.  

Dan

Dan, please see the following about rescue media..

For the ATI 2018 & later version rescue media, there are 3 different versions available:
Simple:  created based on your Windows Recovery Environment for WinPE media.
Advanced: created based on Windows ADK (or AIK for earlier OS versions) - WinPE media.
Advanced: created based on a small Linux distro OS (BusyBox) or created from the .ISO CD image download from your Acronis Account page.

The Simple WinPE media should offer the best compatibility due to including device drivers from the Windows Recovery Environment whereas the Linux based media has a number of known limitations such as not supporting RAID or BitLocker which can include NVMe SSD's which can use RAID.

The other key important factor for all Acronis rescue media is to always use this to match the BIOS boot mode of the Windows OS on the PC where it is used.  Most modern PC's now use UEFI BIOS boot mode (for GPT drives) whereas older PC's may still use Legacy BIOS boot mode (for MBR drives).  This can normally be checked easily using the msinfo32 command in Windows then look at the BIOS mode value shown in the right panel.

KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media

Steve,

Thank you for this info.  I just checked and my machines are Legacy BIOS.  I would not have know to check this if you had not mentioned it. 

I can assume my boot disk I have made using the "Simple" should work on all 3 machines as they are Windows 10, Legacy BIOS?

 

Daniel, the rescue media should work fine for UEFI or Legacy BIOS. But... you must be sure to boot it in the right mode. For example, on my machine (ASUS M/B) when I use the F8 key to get a boot menu, it will list the rescue media drive twice, one with UEFI and one without.