PartClone Error



  • Hi!

    I get this error:
    set block XXX out of boundary(XXXX)

    The Image: MultiDisk/Mulktipartition
    Disk1: ext4 (boot-disk)
    Disk2: btrfs (data-disk)
    partclone uncompressed

    I do clone lot of disks, even headless embedded devices (works great!!) but this Lenovo Laptop makes problems :(

    As you can see on the pic: error is even in debug-mode

    Any help is welcome!

    regards,
    Xibeaga
    0_1524994519474_fog_error.jpg



  • @tom-elliott
    Nice move! Thanks a lot!
    i give it a try!


  • Senior Developer

    I’ve rebuild the init’s with Partclone v0.3.11 which is in the unstable directory. I have tested a linux based image with ext4 partition and that appears to not work properly yet. This appears to be a version issue (meaning something changed for ext4 application as reverting back to 0.2.89 with the same image file works fine). I don’t have an OS with btrfs so I will request you test this? I say this because from what I gather btrfs support was fixed in 0.3.10 from this pull request.

    For the simple cause that ext4 imaging is broke, and I’m not sure on the status of XFS, NTFS, or BTRFS, I find it unlikely this new version will make it into 1.5.3. I don’t know when a new version of partclone will be available to test and build. Right now, 0.3.11 has no issues building, but ext filesystems are unable to be checked, like it’s putting the data on the wrong inodes. I don’t have a windows system to test with yet, so I’m not sure of the status of NTFS. I’m also unsure of XFS and BTRFS. Hopefully, however, at least capturing would work. As far as deploying, well that’s another issue.

    The files can be downloaded using the linked names:

    init.xz
    init_32.xz



  • @tom-elliott
    I think i will change the FS of the disk, so it will become cloneable.

    have a nice day and thanks a lot for your help!
    can you mark the thread solved?


  • Senior Developer

    @xibeaga partclone is built as a part of the inits. Last I got around to partclone 0.2.89 was the latest stable version. I can try updating it but if you said clonezilla had the same issue I suspect updating wouldn’t help anything.



  • @tom-elliott
    Hi!

    i just saw, that FOG uses partclone 0.2.89 but 0.3.10 is actual.
    BTRFS seems to be an issue with partclone.

    Is there a way to upgrade partclone to 0.3.10 in a debian installation of fog ?

    thx!



  • @tom-elliott
    Okay, clonezille (live) crashed too.
    it terminates without any error-message or exit-code.

    the only solution I came up at the moment is:
    running fog DEBUG and boot into a shell
    then mount the fog nfs share
    then dd both disks onto that share

    so, at least i have a backup ;)

    if you have any better idea, you are welcome!

    best regards,
    Xibeaga



  • @tom-elliott
    hey, no problem at all! :)))

    Okay, ic. I suspected partclone too.

    I never used clonezilla, I just know it exists. I use fog since 0.98 or so… ;)
    Ok, I will try clonezilla on this.
    Hm, maybe i should try fog with dd first?


  • Senior Developer

    @xibeaga as strange as it sounds is it likely a problem with partclonr, maybe even the version of partclone? Can you try clonezilla to see if it works out of the box. Note I’m not questioning your skills or anything, I just don’t see the full picture. That’s why I asked about fdisk. Otherwise it’s like saying I made a cake but it didn’t rise as expected. Why didn’t it rise? Probably no flour or not enough eggs, is yeast expected. But we don’t know because we only got a very small amount of information.



  • @tom-elliott

    Here you can see the mount and fdisk output:

    root@uhura:~# mount | grep “sd[a|b]”
    /dev/sdb1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
    /dev/sda1 on /harddisk type btrfs (rw,relatime,ssd,space_cache,subvolid=5,subvol=/)

    root@uhura:~# fdisk -l /dev/sdb /dev/sda
    Medium /dev/sdb: 14,9 GiB, 16013942784 Bytes, 31277232 Sektoren
    Einheiten: sectors von 1 * 512 = 512 Bytes
    Sektorengröße (logisch/physisch): 512 Bytes / 512 Bytes
    I/O Größe (minimal/optimal): 512 Bytes / 512 Bytes
    Typ der Medienbezeichnung: gpt
    Medienkennung: FBF13E8A-6828-4DF5-93D2-F3781739F721

    Gerät Start Ende Sektoren Größe Typ
    /dev/sdb1 2048 31277055 31275008 14,9G Linux filesystem

    Medium /dev/sda: 894,3 GiB, 960197124096 Bytes, 1875385008 Sektoren
    Einheiten: sectors von 1 * 512 = 512 Bytes
    Sektorengröße (logisch/physisch): 512 Bytes / 512 Bytes
    I/O Größe (minimal/optimal): 512 Bytes / 512 Bytes
    Typ der Medienbezeichnung: gpt
    Medienkennung: 945D3E9A-EC7B-4ECA-80E2-CED391F83CB7

    Gerät Start Ende Sektoren Größe Typ
    /dev/sda1 2048 1875384974 1875382927 894,3G Linux filesystem


  • Senior Developer

    @xibeaga how do you know this? What’s output of fdisk -l



  • Hi Tom!

    Ah, sdA is data, i boot from sdB:

    sdb = ext4 = boot disk ;)
    sda = btrfs = data

    so, the problem persists. Any idea about it?
    Maybe BTRFS is the problem?

    thx!
    Regards,
    Xibeaga


  • Senior Developer

    @xibeaga you said disk one is ext4, but your btrfs command is on disk 1. Assuming the layout is correct what happens if you change /dev/sda1 to /dev/sdb1


 

478
Online

5.4k
Users

12.6k
Topics

118.9k
Posts