Acronis SD5 with HP G8 with Linux Debian release Jessie
Hi,
Recently I've experienced a strange issue with our server HP DL380 G8 and Acronis SD5 using Linux Debian 8.0 (Jessie) release, an issue that I dont have experienced using Wheezy (7.8).
Actually, when I take an Acronis Image using the Acronis PXE Boot Client, the image takes 39GB for a fresh NetInstall taking about 580MB of disk space. Ok, the size of the RAID 1+0 is 123GB, but a Full install of Linux 7.8 Wheezy takes around 6GB, not 39GB. Linux Jessie use the version 2.25 of the fdisk tool. It is possible that could make a difference because they changed some features?
In our case, it is preferable to use the cfdisk tool than fdisk. Cfdisk automatically align partitions that fdisk does not.
The question is: What is the best practice to safely and correctly take an image of Linux partitions?
We have 1 Volume of 3 partitions: /boot (35Mb), swap(12GB) and / (111.4GB).
The df command report 1% of disk use, 622 MB. We are far far away than the 39GB of the tib file.
Thanks in advance
Best regards
Martin Leduc
Hi AlexanderK and many thanks for your help.
"It looks like ASD could not recognize file system on the disk and created an image using Sector-by-sector."
I'm not an Acronis expert, but in the ASD Operation Progress window I read:
1. Creating Image
Hard disk: 1
Drive letter: C: (dos compatibility enable)
File system: Ext4 (It see the FS Type)
Volume label:
Size: 118.4 GB
My disk used space is around 680 MB, Total progress: 1h39 Remaining....
"Please make sure that file system of the disk of the machine with Wheezy is supported by Snap Deploy"
We use Jessy, Debian 8.0 Jessy and each file system we use (ext4 and swap) seems to be supported. When I start the Master Image Creator I see the partitions with their type (ext4 and swap)
"Also, corrupted file system may cause sector-by-sector image creation."
This is an excellent point. So I've completely reset my RAID controler configuration and reinstall Linux Jessie (8.0) with all standards options (Next -> Next -> Full -> Next -> Next -> Install)
Same behavior.
I wondering if I can check a log about the detection, somewhere in the TTY2?
Hello,
It looks strange, because ext4 is supported file system. Probably, this is a hardware issue, for example, because of the RAID controller.
I think, the issue should be tested on our environment.
To get this issue resolved, contact our support team, please.
Hi AlexanderK,
I dont think this is a hardware problem. I mean, but I dont have your skills, ASD5 was working perfectly with the same hardware on Debian 7.8. Now, with Debian 8.0 (and the new release of the fdisk from util-linux 2.20.1 to util-linux 2.25.2
The RAID controler driver are up to date and, I mean, haven't apparent issue with Debian 8.0
Thanks and I will check with the Acronis support, but I maintain my idea: The problem is not hardware, it's too easy and working well with the previous release of Debian Linux ;)
Cheers
Martin