I'm trying to set up a laptop running Kali rolling to act as if it was running 'DeepFreeze". My goal is to be able to do the following:
- Set up sda1
- clone it to sda3 with Clonezilla as a "clean version" of sda1
- use sda1 with a client
- "revert" it by cloneing sda3 back over sda1 with Clonezilla.
Before Cloning The Partition:
- sda1 main partition to be "used"
- sda2 extended partition
--- sda5 swap partition
- sda3 backup partition ("clean" version of sda1, to be written over sda1 as needed)
- sda4 Clonezilla Live partition (used to copy sda3 over sda1 as needed)
After Cloning The Partition:
I imagine this is caused by clonezilla copying the entire partition, including whatever is inside of sda1 that tells grub to boot from it.
My issue is, I have no idea how to stop this from happening.
root@kali:~# cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda1 during installation UUID=20d4493c-5934-4633-998e-0c6dd970d4ad / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=3f0d9a95-a494-4ffa-a071-aefcf3d377ed none swap sw 0 0 /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
root@kali:~# blkid /dev/sda1: UUID="20d4493c-5934-4633-998e-0c6dd970d4ad" TYPE="ext4" PARTUUID="f69a4b07-01" /dev/sda3: UUID="20d4493c-5934-4633-998e-0c6dd970d4ad" TYPE="ext4" PARTUUID="f69a4b07-03" /dev/sda4: LABEL="Clonezilla" UUID="26bc43b4-b906-45e0-be27-eab166704de5" TYPE="ext4" PARTUUID="f69a4b07-04" /dev/sda5: UUID="3f0d9a95-a494-4ffa-a071-aefcf3d377ed" TYPE="swap" PARTUUID="f69a4b07-05"