Acronis doesn't backed up all Linux partitions
Hello
I'm donig entire hard drive backup for Linux computer using acronis cyber protect
I connect hard drive external to my laptop using usb adapter
Partitions as below:
FAT16
EXT3
EXT3
Linux swap, photo below
Backup created successfully
My problem with Recovery
In last step before processing Recovery in summary page I realized that two partitions excluded from Recovery without error, EXT3 and Linux swap
After some tests I could make the recovery by restore FAT16 partition alone in one operation then restore the other 3 partitions together to another hard drive and test it but computer failed to complete booting, photo below
Advice please
Regards
Rejjal


- Log in to post comments

Hello!
Welcome to the forum.
Please check the following options/solutions:
-
Verify that the backup was created correctly: Ensure that the backup image was created correctly by verifying the checksums of the backup files.
-
Check the partition information: Verify that the partition information of the target drive matches that of the source drive. This is particularly important if you are restoring the backup to a new hard drive.
-
Check the boot configuration: The error message you have shared indicates that there might be an issue with the boot configuration. Verify that the boot configuration of the target drive is correct and that the boot partition is active.
-
Check the file system: Verify that the file system of the target drive is compatible with the operating system you are trying to boot. For example, if the backup was created on a Linux system, ensure that the target drive is formatted with a Linux-compatible file system.
If the issue persists and there aren't issues or incompatibilities I suggest you raising a ticket with our support so we can troubleshoot the issue. https://kb.acronis.com/content/8153
Thanks!
- Log in to post comments

Rejjal, welcome to these public User Forums.
What Linux distro are you trying to backup here?
Acronis is capable of doing backups of Linux but it is not really designed for doing so as it has no actual native ability to recognise the content unless you go to the premium business products which are intended to work directly on Linux OS systems.
From your description above, you are taking a Linux disk and connecting this to your Windows laptop and running the backup from within Windows which will then try to impose some exclusions that only apply to Windows. In addition, if you were to try to restore that backup using the same method, you would convert the Linux disk to match the partition scheme using by Windows, i.e. to GPT if this is a UEFI BIOS Windows system.
I would recommend downloading a copy of the Clonezilla and burning this to optical media then booting your Linux PC directly from that distro to make a backup from a tool that fully understands Linux partitions etc.
- Log in to post comments

Rejjal, just to clarify my understanding here: Your laptop is running Debian and is being booted from Acronis bootable rescue media created as Linux media with an external USB drive being used to store the backup image? Is that correct.
What actual version of Acronis software was used to create the Linux rescue media? Was this the latest ACPHO or ATI 2021 per this forum, or an earlier version?
In my experience the Acronis Linux based rescue media should be able to backup the partition types you listed in the initial post for this topic. If you have any EXT4 partitions then the media needs to be from ATI 2020 to have Acronis recognise EXT4 correctly.
See forum topic here where this was discussed in detail.
- Log in to post comments

Rejjal, just to clarify my understanding here: Your laptop is running Debian and is being booted from Acronis bootable rescue media created as Linux media with an external USB drive being used to store the backup image? Is that correct.
What actual version of Acronis software was used to create the Linux rescue media? Was this the latest ACPHO or ATI 2021 per this forum, or an earlier version?
In my experience the Acronis Linux based rescue media should be able to backup the partition types you listed in the initial post for this topic. If you have any EXT4 partitions then the media needs to be from ATI 2020 to have Acronis recognise EXT4 correctly.
See forum topic here where this was discussed in detail.
- Log in to post comments

Rejjal, if your laptop is Windows then you need to be doing the backup and recovery using Acronis rescue media on the Linux PC, not trying to do this from the Windows laptop.
Acronis will always use the same BIOS boot mode as is used by that laptop and will convert the backup to use that boot mode on recovery.
Is your Linux PC running as 32-bit or 64-bit, and is it using Legacy / MBR or UEFI / GPT for booting from the BIOS?
The Linux version of Acronis rescue media is capable of booting both 32-bit / 64-bit and Legacy / UEFI boot modes.
- Log in to post comments

Rejjal, I have tested using ATI 2021 Linux rescue media (on DVD) to backup a Debian 11.6 64-bit laptop and then restore the same from the backup image where all went successfully.
I collected the logs for both operations by saving these from the rescue environment before exiting from it.
Backup Log
<?xml version="1.0" encoding="UTF-8" ?>
<log build="39287" product="Acronis True Image" task_name="My Disk Drives Backup" uuid="0633584A-B6BE-022A-CADB-431A221AA717" version="25.10">
<event code="0" id="1" level="2" message="Operation "My Disk Drives Backup" started." module="100" time="1681577794" />
<event code="55" id="2" level="2" line_tag="0x8BA4FA0BAC28C294" message="Fast incremental/differential backup and file filters are not supported for this file system." module="7" time="1681578136">
<field name="volume" type="TString" />
<field name="fstype" type="TIdentifier">LINUXSWAP</field>
<field name="$module" type="TIdentifier">trueimg_home_media_glx_39287</field>
</event>
<event code="252" id="3" level="2" message="Backup operation succeeded." module="100" time="1681578137" />
</log>
Recovery Log
<?xml version="1.0" encoding="UTF-8" ?>
<log build="39287" product="Acronis True Image" task_name="Recover" uuid="0633584A-B6BE-022A-CADB-431A221AA717" version="25.10">
<event code="0" id="1" level="2" message="Operation "Recover" started." module="100" time="1681578249" />
<event code="0" id="2" level="2" message="Detected GRUB 2 loader on disk '\local\hd_sign(78E0B368)'. Activated on volume '\local\hd_sign(78E0B368)\part_sn(2F05C2279A4330FCF9993EA94E6A7E1E)start(2048)'." module="57" time="1681578475" />
<event code="0" id="3" level="2" message="Detected GRUB 2 loader on disk '\local\hd_sign(78E0B368)'. Activated on volume '\local\hd_sign(78E0B368)\part_sn(2F05C2279A4330FCF9993EA94E6A7E1E)start(2048)'." module="57" time="1681578475" />
<event code="0" id="4" level="2" message="Fixing operating system bootability." module="29" time="1681578475" />
<event code="0" id="5" level="2" message="Detected GRUB 2 loader on disk '\local\hd_sign(78E0B368)'. Activated on volume '\local\hd_sign(78E0B368)\part_sn(2F05C2279A4330FCF9993EA94E6A7E1E)start(2048)'." module="57" time="1681578475" />
<event code="0" id="6" level="2" message="Activating GRUB 2. Disk '\local\hd_sign(78E0B368)' Volume '\local\hd_sign(78E0B368)\part_sn(2F05C2279A4330FCF9993EA94E6A7E1E)start(2048)'" module="57" time="1681578475" />
<event code="0" id="7" level="2" message="Detected GRUB 2 loader on disk '\local\hd_sign(78E0B368)'. Activated on volume '\local\hd_sign(78E0B368)\part_sn(2F05C2279A4330FCF9993EA94E6A7E1E)start(2048)'." module="57" time="1681578475" />
<event code="0" id="8" level="2" message="Detected GRUB 2 loader on disk '\local\hd_sign(78E0B368)'. Activated on volume '\local\hd_sign(78E0B368)\part_sn(2F05C2279A4330FCF9993EA94E6A7E1E)start(2048)'." module="57" time="1681578475" />
<event code="0" id="9" level="2" message="Changing loader configuration." module="29" time="1681578475" />
<event code="0" id="10" level="2" message="Reconfiguring GRUB in the BIOS mode." module="29" time="1681578475" />
<event code="0" id="11" level="2" message="Processing boot loader entry 'Debian GNU/Linux'." module="29" time="1681578475" />
<event code="0" id="12" level="2" message="Processing boot loader entry 'Debian GNU/Linux, with Linux 5.10.0-21-amd64'." module="29" time="1681578475" />
<event code="0" id="13" level="2" message="Processing boot loader entry 'Debian GNU/Linux, with Linux 5.10.0-21-amd64 (recovery mode)'." module="29" time="1681578475" />
<event code="0" id="14" level="2" message="Processing boot loader entry 'Debian GNU/Linux, with Linux 5.10.0-20-amd64'." module="29" time="1681578475" />
<event code="0" id="15" level="2" message="Processing boot loader entry 'Debian GNU/Linux, with Linux 5.10.0-20-amd64 (recovery mode)'." module="29" time="1681578475" />
<event code="0" id="16" level="2" message="Detected GRUB 2 loader on disk '\local\hd_sign(78E0B368)'. Activated on volume '\local\hd_sign(78E0B368)\part_sn(2F05C2279A4330FCF9993EA94E6A7E1E)start(2048)'." module="57" time="1681578475" />
<event code="0" id="17" level="2" message="Processing the fstab file." module="29" time="1681578475" />
<event code="0" id="18" level="2" message="Changing device reference 'UUID=27c2052f-fc30-439a-a93e-99f91e7e6a4e' to 'UUID=27c2052f-fc30-439a-a93e-99f91e7e6a4e'." module="29" time="1681578475" />
<event code="0" id="19" level="2" message="Changing device reference 'UUID=0e90f941-f3ff-45f3-9267-97e44fa42bcb' to 'UUID=0e90f941-f3ff-45f3-9267-97e44fa42bcb'." module="29" time="1681578475" />
<event code="0" id="20" level="2" message="Cannot map device '/dev/sr0' to the target hardware because the original configuration of fstab does not contain the platform-independent device identifier." module="29" time="1681578475" />
<event code="0" id="21" level="2" message="The operating system bootability has been fixed." module="29" time="1681578475" />
<event code="0" id="22" level="2" message="Fixing operating system bootability." module="29" time="1681578475" />
<event code="0" id="23" level="2" message="Updating boot caches on volume '\local\hd_sign(78E0B368)\part_sn(2F05C2279A4330FCF9993EA94E6A7E1E)start(2048)'." module="29" time="1681578475" />
<event code="0" id="24" level="2" message="Updating boot caches on volume '\local\hd_sign(78E0B368)\part_sn(41F9900EF345FFF3E4976792CB2BA44F)start(310581248)'." module="29" time="1681578475" />
<event code="0" id="25" level="2" message="Updating boot caches on volume '\local\hd_sign(4F588B60)\part_sn(525B49A0)start(2048)'." module="29" time="1681578475" />
<event code="0" id="26" level="2" message="Updating boot caches on volume '\local\hd_sign(4F588B60)\part_sn(F019072001D5D536)start(14866432)'." module="29" time="1681578475" />
<event code="0" id="27" level="2" message="The operating system bootability has been fixed." module="29" time="1681578475" />
<event code="0" id="28" level="2" message="Detected GRUB 2 loader on disk '\local\hd_sign(78E0B368)'. Activated on volume '\local\hd_sign(78E0B368)\part_sn(2F05C2279A4330FCF9993EA94E6A7E1E)start(2048)'." module="57" time="1681578475" />
<event code="252" id="29" level="2" message="Recover operation succeeded." module="100" time="1681578476" />
</log>
Both operations took around 6 minutes each to complete after being launched from the rescue environment.
This was just a vanilla Debian 11.6 OS system installed earlier today for testing. Debian created just a single EXT4 main partition along with a Linux Swap partition, so no FAT16 or EXT3 partitions as you have listed previously.
The laptop booted successfully into the Debian desktop after the recovery and all looked to be working correctly as far as my limited testing went, i.e. launched web browser, weather app.
- Log in to post comments

Rejjal, I have tested using ATI 2021 Linux rescue media (on DVD) to backup a Debian 11.6 64-bit laptop and then restore the same from the backup image where all went successfully.
I collected the logs for both operations by saving these from the rescue environment before exiting from it.
Backup Log
<?xml version="1.0" encoding="UTF-8" ?>
<log build="39287" product="Acronis True Image" task_name="My Disk Drives Backup" uuid="0633584A-B6BE-022A-CADB-431A221AA717" version="25.10">
<event code="0" id="1" level="2" message="Operation "My Disk Drives Backup" started." module="100" time="1681577794" />
<event code="55" id="2" level="2" line_tag="0x8BA4FA0BAC28C294" message="Fast incremental/differential backup and file filters are not supported for this file system." module="7" time="1681578136">
<field name="volume" type="TString" />
<field name="fstype" type="TIdentifier">LINUXSWAP</field>
<field name="$module" type="TIdentifier">trueimg_home_media_glx_39287</field>
</event>
<event code="252" id="3" level="2" message="Backup operation succeeded." module="100" time="1681578137" />
</log>Recovery Log
<?xml version="1.0" encoding="UTF-8" ?>
<log build="39287" product="Acronis True Image" task_name="Recover" uuid="0633584A-B6BE-022A-CADB-431A221AA717" version="25.10">
<event code="0" id="1" level="2" message="Operation "Recover" started." module="100" time="1681578249" />
<event code="0" id="2" level="2" message="Detected GRUB 2 loader on disk '\local\hd_sign(78E0B368)'. Activated on volume '\local\hd_sign(78E0B368)\part_sn(2F05C2279A4330FCF9993EA94E6A7E1E)start(2048)'." module="57" time="1681578475" />
<event code="0" id="3" level="2" message="Detected GRUB 2 loader on disk '\local\hd_sign(78E0B368)'. Activated on volume '\local\hd_sign(78E0B368)\part_sn(2F05C2279A4330FCF9993EA94E6A7E1E)start(2048)'." module="57" time="1681578475" />
<event code="0" id="4" level="2" message="Fixing operating system bootability." module="29" time="1681578475" />
<event code="0" id="5" level="2" message="Detected GRUB 2 loader on disk '\local\hd_sign(78E0B368)'. Activated on volume '\local\hd_sign(78E0B368)\part_sn(2F05C2279A4330FCF9993EA94E6A7E1E)start(2048)'." module="57" time="1681578475" />
<event code="0" id="6" level="2" message="Activating GRUB 2. Disk '\local\hd_sign(78E0B368)' Volume '\local\hd_sign(78E0B368)\part_sn(2F05C2279A4330FCF9993EA94E6A7E1E)start(2048)'" module="57" time="1681578475" />
<event code="0" id="7" level="2" message="Detected GRUB 2 loader on disk '\local\hd_sign(78E0B368)'. Activated on volume '\local\hd_sign(78E0B368)\part_sn(2F05C2279A4330FCF9993EA94E6A7E1E)start(2048)'." module="57" time="1681578475" />
<event code="0" id="8" level="2" message="Detected GRUB 2 loader on disk '\local\hd_sign(78E0B368)'. Activated on volume '\local\hd_sign(78E0B368)\part_sn(2F05C2279A4330FCF9993EA94E6A7E1E)start(2048)'." module="57" time="1681578475" />
<event code="0" id="9" level="2" message="Changing loader configuration." module="29" time="1681578475" />
<event code="0" id="10" level="2" message="Reconfiguring GRUB in the BIOS mode." module="29" time="1681578475" />
<event code="0" id="11" level="2" message="Processing boot loader entry 'Debian GNU/Linux'." module="29" time="1681578475" />
<event code="0" id="12" level="2" message="Processing boot loader entry 'Debian GNU/Linux, with Linux 5.10.0-21-amd64'." module="29" time="1681578475" />
<event code="0" id="13" level="2" message="Processing boot loader entry 'Debian GNU/Linux, with Linux 5.10.0-21-amd64 (recovery mode)'." module="29" time="1681578475" />
<event code="0" id="14" level="2" message="Processing boot loader entry 'Debian GNU/Linux, with Linux 5.10.0-20-amd64'." module="29" time="1681578475" />
<event code="0" id="15" level="2" message="Processing boot loader entry 'Debian GNU/Linux, with Linux 5.10.0-20-amd64 (recovery mode)'." module="29" time="1681578475" />
<event code="0" id="16" level="2" message="Detected GRUB 2 loader on disk '\local\hd_sign(78E0B368)'. Activated on volume '\local\hd_sign(78E0B368)\part_sn(2F05C2279A4330FCF9993EA94E6A7E1E)start(2048)'." module="57" time="1681578475" />
<event code="0" id="17" level="2" message="Processing the fstab file." module="29" time="1681578475" />
<event code="0" id="18" level="2" message="Changing device reference 'UUID=27c2052f-fc30-439a-a93e-99f91e7e6a4e' to 'UUID=27c2052f-fc30-439a-a93e-99f91e7e6a4e'." module="29" time="1681578475" />
<event code="0" id="19" level="2" message="Changing device reference 'UUID=0e90f941-f3ff-45f3-9267-97e44fa42bcb' to 'UUID=0e90f941-f3ff-45f3-9267-97e44fa42bcb'." module="29" time="1681578475" />
<event code="0" id="20" level="2" message="Cannot map device '/dev/sr0' to the target hardware because the original configuration of fstab does not contain the platform-independent device identifier." module="29" time="1681578475" />
<event code="0" id="21" level="2" message="The operating system bootability has been fixed." module="29" time="1681578475" />
<event code="0" id="22" level="2" message="Fixing operating system bootability." module="29" time="1681578475" />
<event code="0" id="23" level="2" message="Updating boot caches on volume '\local\hd_sign(78E0B368)\part_sn(2F05C2279A4330FCF9993EA94E6A7E1E)start(2048)'." module="29" time="1681578475" />
<event code="0" id="24" level="2" message="Updating boot caches on volume '\local\hd_sign(78E0B368)\part_sn(41F9900EF345FFF3E4976792CB2BA44F)start(310581248)'." module="29" time="1681578475" />
<event code="0" id="25" level="2" message="Updating boot caches on volume '\local\hd_sign(4F588B60)\part_sn(525B49A0)start(2048)'." module="29" time="1681578475" />
<event code="0" id="26" level="2" message="Updating boot caches on volume '\local\hd_sign(4F588B60)\part_sn(F019072001D5D536)start(14866432)'." module="29" time="1681578475" />
<event code="0" id="27" level="2" message="The operating system bootability has been fixed." module="29" time="1681578475" />
<event code="0" id="28" level="2" message="Detected GRUB 2 loader on disk '\local\hd_sign(78E0B368)'. Activated on volume '\local\hd_sign(78E0B368)\part_sn(2F05C2279A4330FCF9993EA94E6A7E1E)start(2048)'." module="57" time="1681578475" />
<event code="252" id="29" level="2" message="Recover operation succeeded." module="100" time="1681578476" />
</log>Both operations took around 6 minutes each to complete after being launched from the rescue environment.
This was just a vanilla Debian 11.6 OS system installed earlier today for testing. Debian created just a single EXT4 main partition along with a Linux Swap partition, so no FAT16 or EXT3 partitions as you have listed previously.
The laptop booted successfully into the Debian desktop after the recovery and all looked to be working correctly as far as my limited testing went, i.e. launched web browser, weather app.
- Log in to post comments

Rejjal, is there a reason why you cannot boot your Debian Linux PC directly from the Acronis rescue media?
This is how most Linux distros are installed from optical media, i.e. booting the install media as either a live distro or simply to perform the install, which is how I installed Debian 11.6 on my test laptop, and then booted the laptop from my Acronis Linux rescue media to do both the Backup and Recovery, using an external USB HDD to store the backup image.
Introducing another different Windows laptop means that Acronis will look at the boot drive for Windows and try to make the Linux drive bootable for Windows.
- Log in to post comments

Rejjal, is there a reason why you cannot boot your Debian Linux PC directly from the Acronis rescue media?
This is how most Linux distros are installed from optical media, i.e. booting the install media as either a live distro or simply to perform the install, which is how I installed Debian 11.6 on my test laptop, and then booted the laptop from my Acronis Linux rescue media to do both the Backup and Recovery, using an external USB HDD to store the backup image.
Introducing another different Windows laptop means that Acronis will look at the boot drive for Windows and try to make the Linux drive bootable for Windows.
- Log in to post comments

Our Linux computer installed on Industrial machine, any mistake will break the machine down, I think most safe way is take out Linux hard drive and connect externally with my laptopIs all of Acronis products work as you said that makes the backup boot compatible with backup operated computer?Isn't there an option in acronis settings just make exactly image of target hard drive regardless of operated computer?
There should be no risk to the Industrial machine from doing the restore directly to it - if you have a spare disk drive, then that would be a safe method of testing.
Yes, unfortunately, Acronis is designed to be used in Windows PC's and as such the developers have adopted methods which are intended to ensure that Windows will boot, which has negative impacts when disk drives from other OS's are involved!
There is no option to make an exact image 'as is' without any changes of the target drive. This has been a complaint from Acronis users for years since more computers started to use UEFI but users wanted to clone or image Legacy drives!
You may be able to take the approach you want if you use a different backup application such as Macrium Reflect which does not make any changes for bootability during restore.
Note: I have tested using Macrium Reflect 8 Home edition and it successfully backed up and restored my Debian disk drive attached via USB to my Windows 11 laptop, and the drive booted successfully into Debian when replaced in the original laptop.
The following images show the recovery.
- Log in to post comments

Dear Steve
I don't know how to appreciate you
You really deserve the best appreciating
I'll test and keep you informed
Best Regards
Rejjal
- Log in to post comments

Dear Steve
Problem solved with Macrium
I test the following options:
Acronis cyber protect home
Acronis true image 2014, 2019,2021
Acronis cyber protect for server
All Acronis products failed to recover the backup (as you said) even with sector by sector
Macrium recovery success without sector by sector , thanks for your advice
I hope Acronis developers to make Acronis able to backup and restore Linux systems externally like Macrium
Best regards
Rejjal
- Log in to post comments

There is no option to make an exact image 'as is' without any changes of the target drive. This has been a complaint from Acronis users for years since more computers started to use UEFI but users wanted to clone or image Legacy drives.
I have never understood why Acronis hasn't corrected this issue as it has caused people (myself included) to move over to competing products as they clone / restores image "as is", which I find it insane that Acronis still in 2023 cannot clone disks / create - restore images "as is", which such software shouldn't care what OS, data etc is on the disks.
I don't expect to end up with a non booting hard drive because Acronis developers decided to be a "nanny" and tamper with target disks.
I personally moved to Terabyte - Image for Windows on my computers (and family members computers) and it just works "as is". No tampering at all on target disks (unless you manually tell it to do so).
- Log in to post comments