Enter "expert mode", and check "-fsck-src-part" when you save such an image. By doing this, Clonezilla will run fsck program on the partition you want to save to check and fix the integrity of the file system.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That error started occurring only on CloneZilla 1.2.5-17, if I image a machine with 1.2.3-27 works fine, if I image the same machine with 1.2.5-17 the error pops up and aborts the imaging process.
Done in "beginner's" mode by the way.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes I did, if I do it in "expert" mode and add the "-fsck-src-part" works if I do it in "beginner's" mode it fails, but this only happens in 1.2.5-17 as I stated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I believe the partclone in Clonezilla live 1.2.3-27 does not check the file system very well.
You can boot any rescue CD to run fsck the partition you want to save, and you can make sure if the file system integrity is OK or not.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes I figured 1.2.3-17 wasn't doing something right. I don't mind using the expert mode but using the "beginners" option saves time and keystrokes, plus, less experienced users might find this a little bit complicated.
CloneZilla rules by the way.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm running into the following problem trying to clone a 40GB disk with LVM:
Disk /dev/hda: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 4865 38973690 8e Linux LVM
-- Logical volume --
LV Name /dev/VolGroup01/LogVol00
VG Name VolGroup01
LV UUID zx8u3z-D0jn-DZrc-qh6t-8wMH-RcNO-hTEfZi
LV Write Access read/write
LV Status available
# open 1
LV Size 35.19 GB
Current LE 1126
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:0
-- Logical volume --
LV Name /dev/VolGroup01/LogVol01
VG Name VolGroup01
LV UUID qaWEDh-ZQgc-Ati6-SncJ-wkSJ-xsnk-1yAXwD
LV Write Access read/write
LV Status available
# open 1
LV Size 1.94 GB
Current LE 62
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:1
The error log:
Partclone v0.2.9 http://partclone.org
Starting to clone device (/dev/VolGroup01/LogVol00) to image (-)
Reading Super Block
Calculating bitmap…
extfsclone.c: bitmap free count err, free:1845582
Enter "expert mode", and check "-fsck-src-part" when you save such an image. By doing this, Clonezilla will run fsck program on the partition you want to save to check and fix the integrity of the file system.
Steven.
That error started occurring only on CloneZilla 1.2.5-17, if I image a machine with 1.2.3-27 works fine, if I image the same machine with 1.2.5-17 the error pops up and aborts the imaging process.
Done in "beginner's" mode by the way.
So did you try to check the option "-fsck-src-part" in the expert mode?
Steven.
Yes I did, if I do it in "expert" mode and add the "-fsck-src-part" works if I do it in "beginner's" mode it fails, but this only happens in 1.2.5-17 as I stated.
I believe the partclone in Clonezilla live 1.2.3-27 does not check the file system very well.
You can boot any rescue CD to run fsck the partition you want to save, and you can make sure if the file system integrity is OK or not.
Steven.
Yes I figured 1.2.3-17 wasn't doing something right. I don't mind using the expert mode but using the "beginners" option saves time and keystrokes, plus, less experienced users might find this a little bit complicated.
CloneZilla rules by the way.