On 2018-01-15 10:49, David C. Rankin wrote:
On 01/14/2018 10:55 AM, Bernhard Voelker wrote:
There are a lot of possibilities to create an image of an (unmounted!) filesystem:
FILESSYTEM='/dev/sda3' IMAGEFILE="/mnt/backup/image"
cat "$FILESSYTEM" > "$IMAGE"
or cp --copy-contents "$FILESSYTEM" "$IMAGE"
or - I don't see anything wrong with it - the one which is made for this:
dd bs=32M iflag=fullblock < "$FILESYSTEM" > "$IMAGE"
Have a nice day, Berny
Yes, thanks Carlos, Dave, Per, Wols, Juan and Bernhard,
This is the check I wanted. No super-new magic best thing since sliced-bread imaging app. Just good old dd or clonezilla. (or parted, etc..)
All the data on the drive is backed up. The only reason I want to image, is if things go south with the upgrade, I want to simply roll 42.2 back over the update mess and restore the 42.2 system. Then I'll yank the drive and do a clean install.
I'm looking for the Carlo's method philosophy..
An image is faster for doing full recovery, and it also covers the booting. No thinking needed ;-)
(specifically, the "No thinking needed" part for the rollback :)
LOL. Just remember to unplug the backup disk soon after finishing it - having it connected would confuse YaST a lot. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)