Hi there @yash.
I see you marked my recommendation of RedoRescue as the solution. Did you test out making a backup image with it or did you simply take the live disk for a spin. Just curious, because I've recommended it a few times, but as yet I haven't gotten feedback on if it works well with the BTRFS file system.
Just ran it myself so I could answer for him and it doesn't seem to support Btrfs unfortunately.
Executing: partclone.fat --clone --force --UI-fresh 1 --logfile /tmp/sda1.log --source /dev/sda1 --no_block_detail | pigz --stdout | split --numeric-suffixes=1 --suffix-length=3 --additional-suffix=.img --bytes=4096M - /mnt/remote/20220322_sda1_
Partclone v0.3.13 http://partclone.org
Starting to clone device (/dev/sda1) to image (-)
Reading Super Block
Calculating bitmap... Please wait...
Elapsed: 00:00:01, Remaining: 00:01:39, Completed: 1.00%
Elapsed: 00:00:01, Remaining: 00:00:00, Completed: 100.00%
Total Time: 00:00:01, 100.00% completed!
done!
File system: FAT32
Device size: 314.6 MB = 614376 Blocks
Space in use: 29.9 MB = 58312 Blocks
Free Space: 284.7 MB = 556064 Blocks
Block size: 512 Byte
Elapsed: 00:00:01, Remaining: 00:01:39, Completed: 1.00%, 0.00byte/min,
Elapsed: 00:00:01, Remaining: 00:00:00, Completed: 100.00%, Rate: 1.79GB/min,
Total Time: 00:00:01, 100.00% completed!
Syncing... OK!
Partclone successfully cloned the device (/dev/sda1) to the image (-)
Cloned successfully.
Executing: partclone.btrfs --clone --force --UI-fresh 1 --logfile /tmp/sda2.log --source /dev/sda2 --no_block_detail | pigz --stdout | split --numeric-suffixes=1 --suffix-length=3 --additional-suffix=.img --bytes=4096M - /mnt/remote/20220322_sda2_
Partclone v0.3.13 http://partclone.org
Starting to clone device (/dev/sda2) to image (-)
Reading Super Block
couldn't open because of unsupported option features (10).
btrfsclone.c: Couldn't open file system
That's too bad, because it's simplicity itself to use.
Sadly, simplicity apparently comes at the cost of lesser features.
Thanks for testing and reporting.
Yeah no worries. Btw I just tried rescuezilla and it also doesn't work which I found strange. Seems to be related to btrfsclone.c not being able to open the file system and partclone failing too
Very strange that btrfs doesnât work as the program uses partclone.
From partcloneâs Debian manpage, (Debian based system on live boot disk):
Partclone supported file system include btrfs, ext2, ext3, ext4, reiserfs, reiser4, xfs and jfs for LINUX.
https://manpages.debian.org/stretch/partclone/partclone.8.en.html
I simply use dd to create a sector for sector image myself.
I write the image directly to a similar SSD.
Very interesting. Do you have maybe a guide of sorts you use for this stuff? I would love to have a proper backup solution that doesn't rely on rsync so I could have an image file or an ISO on an external SSD. And do you think it would be worth running the btrfs check repair command? I don't understand why partclone is not working for me
From RedoRescue Github page:
Changes to Redo Rescue
Version 4.0.1 (UNRELEASED)
Fix bug that prevented selecting a new disk once one is chosen
Add support for mounting and imaging BTRFS filesystems
Remove wireless non-free firmware packages
Apparently BTRFS support coning soon.
Good to know about redorescue at least. Afaik rescuezilla and clonezilla support it already though so I wonder what's happening there
I have read that the dd command can be problematic with BTRFS, but it seems to work fine when doing a direct imaging for me.
IIRC this is the command I use:
dd if=/dev/sda of=/dev/sdX bs=1M conv=noerror,sync status=progress
Where "X" is the letter of your destination drive.
Be very careful your destination is correct, or an unforgettable life lesson will occur.
man dd
Hm thank you. I've used dd a couple of times for flashing Windows images in the past for various reasons but not that familiar. What does this command do exactly? Format's the destination drive and makes a clone of the source like clonezilla? Thanks
Direct sector by sector cloning (identical copy) from one drive to another drive of equal or larger size. Best done from a live boot environment, but I have even done it from a running system (not recommended).
Okay sounds good thanks. What reason do you do this instead of using clonezilla though? And for example, what if you were to Clone from a 500gb SSD to a 2tb SSD? And then clone back from the backup to the source if you broke something beyond repair? Does this DD command allow for copying to bigger drives and then back to smaller ones or will it fill out the size?
I use hotswap SSD racks, so it is simpler to clone from one similarly sized SSD drive directly to another. Clone drive, shut down, swap drives, restart.
Identical drive copy now running, original drive becomes backup, just that simple.
Only works to copy to drives same size or larger.
Just FYI:
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.