Now ran the full balance again and this time it took about an hour to complete. Though his commands seemed complicated I thougth of something else I decreased my swap partition from 4 to 1 GB and this is pretty cool I could expand my root partition with those 3GB while running the system within seconds with Gparted. Been reading some more, this was interesting, explains you can just add space from a USB stick or whatever to the partition to temporarily expand it so you can run the balance. Sadly nothing changed for Clonezilla - still aborting the process with 'set block out of boundary ' - Of course I was suspicious of the short time it took to do the balance in the live environment. I think it was fast because I used the 'btrfs balance start -d /' - I read it doesn't matter if you run it with -d or not but I guess it does. Now after trying the full balance command and the system hanging in read-only mode (probably because of lack of space), I booted into a live environment, mounted sda1 and ran the full balancing command again - with success! It was actually very fast - and better yet doing the check with Gparted now completed without errors so it definitely fixed something. The reason why I'm so careful is that besides me there's only one other person I can find on the whole internet who also had that 'set block out of boundary ' error. The system is rock stable, with two things wrong:ġ) when I 'Check' the filesystem with Gparted it aborts with 'ERROR: errors found in fs roots'Ģ) Clonezilla refuses to clone the sda1 partition and aborts with 'set block out of boundary ' No, I started out with btrfs from the beginning. It is also included as part of the free operating system ReactOS. A reimplementation from scratch, it contains no code from the Linux kernel, and should work on any version from Windows XP onwards.

By any chance, did you convert the filesystem from ext4 to btrfs? WinBtrfs is a Windows driver for the next-generation Linux filesystem Btrfs.

Btrfs driver