Bootable rescue CD Issues
THe first thing I did after loading ATI 2016 was burn several copies of the bootable rescue cd. One of the cd failed so I decided to create a replacement copy. When I try to make one, it tells me it will take 723MB disk space which naturally doesn't fit on a cd. All of my others copies fit on a cd taking about 517mb. Now why would it change?
The only thing I can figure out is today I decide to download the Universal restore option. Am I let to believe that now when I request JUST to create a bootable rescue disk that somehow the Universla Restore is now being added to this disk?
Any ideas?
Ken

- Log in to post comments

Can't honestly say but it soulds like it. I can say this is the first report of this issue I have seen.
- Log in to post comments

AllI can tell you is that is exactly what is on this bootable disk. I check the files located on my initial boot disk before downloading the universal tool vs the new bootable disk which has more files on it. In fact when you boot to it the selection screen gives you the following options:
1 Acronis Universal restore
2 Acronis True Image 64 bit
3 Acronis True Image Report 64 bit
Ken
Ps Is there a way to get an answer from Acronis?
- Log in to post comments

Instead of using ATIH to make your bootable media, install universal restore media builder (if you haven't already - it's included in your download section) and make it with that instead. That one will still use the same installers, but allows you to pick just the items that you want.. universal restore 32 and/or 64 bit (or neither), Acronis True Image Home 32 and 64 bit (or neither), snap deploy 32 bit applications if you have them installed too, etc. Just selecting True Image Home (I have 2015 currently) is less than 300MB if you only select ATIH - I'd recommend leaving off Acronis System Report (I've never used it) if you want to keep the image even smaller.
FYI, if you really want to know what is on your recovery media, you have to dig a little deeper. There are 3 sections of the rescue media and depending upon which option your system is defaulting to at boot time, you may not be seeing all of the files that are actually on your recovery media. Also, when I use the recovery media builder in ATIH, it basically grabs all 32 and 64 bit versions of Acronis True Image Home, Universasl Restore and System Report and puts it on the disk - doesn't seem to be a way to pick and choose using this method. That's why I generally use the universal restore media builder as you can select just the items you want (for the most part).
Using a tool like Notepad, you can view the .xml files that explain what each version of the bootmedia has put on the disk.
1) Legacy/CSM... root of the CD >>>>bootmenu.xml. This will show you a list of the files that legacy mode calls upon. It is associated with bootwiz.cfg on the root of the rescue media - be careful if you modify anything in either of these files as legacy mode changes are finicky.
2) 32-bit UEFI... root of CD >>>> EFI >>>> boot32.xml. This will tell you the 32 bit UEFI .DAT files that are available that a 32-bit UEFI system would use (usually cheap tablets that only have 16 or 32GB of eMMC flash memory hard drives which may be 64-bit but only have a 32-bit bios). Most systems probably won't use these though (unless you have one of those 32-bit bios systems).
3) 64-bit UEFI.... root of CD >>>> EFI >>>> boot64.xml. This will tell you the 64 bit UEFI.DAT files that are available for a 64-bit UEFI system (the majority of new computers within the last few years will use this and/or legacy mode if the BIOS still supports legacy mode). Also, 64-bit UEFI fully supports 32-bit booting so you can copy all of the 32-bit UEFI entries and paste them into this .xml (just rename the numbers so that you don't have multiple entries for 3, 4, 5, etc). On a 64-bit system, both the 32-bit or 64-bit applications will work just fine and I actually find that the 32-bit ones often have better mouse and network drivers than the 64-bit ones.
On the root of your CD or USB drive, you will find several .DAT files. These are all of the LINUX ramdisks and kernels. The Ramdisks are the large files and relate to the actual applications that get loaded when you select an option. You can technically just delete the RAMDISK and KERNEL .dat files you don't want from the root of the CD or thumb drive and then manually update the corresponding .xml files so they don't show up as an option when you boot into the recovery media.... - I have not found a way to edit .ISO versions and still make them bootable - typically this can only be done on a bootable USB thumb drives. Be careful if you do though as some files are the same in legacy mode and in the EFI.xml's.
Attachment | Size |
---|---|
320356-124768.jpg | 58.98 KB |
- Log in to post comments

Robert
I already did what you said and built my bootable disk using Universal Restore media builder. Like you said you can define exactly what you
want on your bootable disk. What confused me is when your selected recovery media builder you get everything including the kitchen sink. It just seems to me odd, you would think you would get only what you need to make a bootable disk for recovery of your images.
Thanks
Ken
PS I have issues for some reason saving the images created when I use the bootable disk. I can make images and store them with system is running window 10
- Log in to post comments

Kenneth,
What issues do you have in saving backups with the boot media? Would elaborate on that.
- Log in to post comments

Enchantech,
I can make online images and store them on my local drive or a usb external drivebut when i try the make the same images off a bootable cd what happens is it goes through the procedure to make the images(in fact I know it is truly making the image) but it will not save the image to my target folder. Does not matter if I try to store it on my local drive or my usb external drives. I get no errors. I make images of my seperate partitions. When I boot back to my op system which is windows10 the images are not there. It isnt like they are invisible since no space is taken up on the drives. Weird thing is though once in a while they do appear. I am trying to narrow it down and it looks like it is link to how I boot to the disc (ie legacy vs uefi)
I am really baffled with this because it was working a month ago when I first created my first bootable cd
Ken
Ps the boot disk works on my system 7 machine along with the same usb external drives. Just got a gut feeling it has to do with legacy vs uefi.
- Log in to post comments

Interesting, someone else in a recent post had a similar issue that hasn't been resolved - try the suggestions in there if you have the opportunity - especially if you have a second system that you can monitor the .tib file creation from.
https://forum.acronis.com/forum/109756
Wondering if it is a problem with the .ISO recovery media? I only use USB recovery media, but have not had any issues creating full system images (offline) with it - EVER (well other than it can't see my eMMC hard drive in my 2-in-1 tablet, but PE media works fine as a work-a-round for that). Can you try a USB thumb drive recovery media and see if the behavior persists?
If it does, or if you want to keep trouble shooting the issue with your .ISO's, can you test by first creating a folder on the root of your external storage location and giving all users full access to that new root directory. Then, any subdirectories you create in that folder should automatically inherit those permissions - hopefully allowing Acronis to create any folders or files where it needs to as .TIBs are being created.
I'd also recommend (this is just my personal preference though), that you customize your .TIB output size to break at 3GB instead of letting it make one giant one. The 3GB size has been best for me since it allows me still be able to create images on FAT32 drives (if necessary). I also find that Acronis seems to work faster/better, when it can split the files into smaller chunks and move onto the next one. 3GB is kind of the sweet spot because of the FAT32 benefit.
- Log in to post comments

Your issue just started to show up here on the Forum recently. Not sure what to make of it at this point. I do think you are on to something with the Legacy vs. UEFI thought.
I would think it this way, if you are creating a backup of a UEFI machine then you must boot the boot media in UEIF mode. If you are backing up a Legacy system disk then you must boot the media in Legacy mode. The two will not mix and I believe have the potential to produce unpreditible results such as you describe.
Do some experimentation and psot back.
- Log in to post comments

Hello,
There is no possibility to select Acronis components in the Rescue Media Builder of Acronis True Image. This is by design. Rescue Media Builder creates a Bootable Media with all available Acronis components. If you need to create a Bootable Media with components you want, you can use Acronis Universal Restore media builder.
Best regards.
- Log in to post comments