goldenferro.blogg.se - Clonezilla image restore

#CLONEZILLA IMAGE RESTORE HOW TO#
#CLONEZILLA IMAGE RESTORE SOFTWARE#
#CLONEZILLA IMAGE RESTORE TRIAL#
#CLONEZILLA IMAGE RESTORE ISO#

rw-r-r- 1 root root 194 Nov 14 03:05 Info-packages.txt rw-r-r- 1 root root 53K Nov 14 03:05 Info-lshw.txt rw-r-r- 1 root root 96K Nov 14 03:05 Info-dmi.txt We already have a Clonezilla image in sdb, the image name is called ls -lh /home/partimag/ĭrwxr-xr-x 2 root root 4.0K Nov 14 02:36 Docsĭrwxr-xr-x 2 root root 4.0K Nov 14 02:36 Photosĭrwxr-xr-x 2 root root 4.0K Nov 14 03:05 focal-mbr-20201114ĭrwx- 2 root root 16K Nov 14 01:39 ls -lh /home/partimag/focal-mbr-20201114/ Partition size was enough to store live Clonezilla image (200M?) and was set bootable.In this example, the machine has 2 disks, 1st disk's name is sda (device name in GNU/Linux), 2nd disk's device name is sdb. Set up FAT32 partition on sdb (the disk to restore to, 'target' one) using fdisk and mkvfat.Downloaded Clonezilla live as according to this doc, up to configuring GRUB (so, downloaded, unpacked, changed 'live' folder name).Mission accomplished, my disk is restored, and here is how: Hopefully will be helpful for someone, sometime.

#CLONEZILLA IMAGE RESTORE TRIAL#

I hope this sounds less chaotic than I feel about it :) Situation is quite complicated for me and my previous experiences I hope someone here can set me straight.Īfter quite a lot of trial and error I found a way.

#CLONEZILLA IMAGE RESTORE HOW TO#

Or, since I hope this would be one-time task, perhaps I can simplify something? Edit clonezilla image (can mount it normally, right?) to allow ssh by default, perhaps restricting IP access or changing default password?įinally, how would you go about running system from this image? Where could I store it, if it indeed needs separate partition? And in case the best answer would be a partition on clear 'target' disk, how to make the system go to RAM at boot? Remember I would only be able to ssh into it once it is fully alive (so, booted, with network up, etc). In this case, on which machine should clonezilla image be located? Right now I'm thinking about setting up PXE server on different machine and pointing my 'target' server to get boot info from it. This answer pointing to this doc sounds like a solution here, although requires PXE setup. again, there is remote access only and clonezilla has ssh disabled by default.So perhaps use sdb (target disk) and let it be overwritten once booted clonezilla goes to RAM? Or use sda4 anyways and restore it from backup later? I definitely won't touch sda1/3/4 (boot, swap and raid data I wouldn't like to lose) and I'm afraid to partition sda2 having system data on it.

this livehd tutorial says it is needed to prepare single FAT partition for clonezilla to run.

I downloaded such image and copied it to sda2

#CLONEZILLA IMAGE RESTORE ISO#

no way to insert live cd/usb for booting It is, however, possible to run clonezilla live from iso image on hard disk.

However, right now I can identify following obstacles: With physical access, this would be easy. I want to have said Clonezilla disk image restored to sdb.

#CLONEZILLA IMAGE RESTORE SOFTWARE#

Never used this software before, so I hope there is everything in place - it is a folder containing quite a lot of dd-img. On sda2 there is, among other files, rather huge disk image made with Clonezilla.

sdb is perfectly clear and freshly installed.

sda is partitioned for boot (sda1), root/user fs (sda2), swap (sda3) and raid (sda4).

There is a server, accessible remotely by ssh, with no physical access. Having little experience in the area, I'm asking about the best / most reasobable way to manage my tools and resources in this particular task.

There might be possibly more than one right answer.