On 27 Jul 2018 at 10:57, ToddAndMargo wrote:
Subject: Re: clone
To: users(a)lists.fedoraproject.org
From: ToddAndMargo <ToddAndMargo(a)zoho.com>
Date sent: Fri, 27 Jul 2018 10:57:46 -0700
Send reply to: Community support for Fedora users
<users(a)lists.fedoraproject.org>
On 07/26/2018 05:21 PM, Patrick Dupre wrote:
> Hello,
>
> I did this ton of times, but this time, it does not work.
> I even just did it last week on an EFI system without problem
> Before updating my system (now in fedora 26), I cloned by using another live
system.
> cp -a /root1 /root2 (after mke2fs)
> cp -a /boot1 /boot2
> The /home /tmp are on other partitions
> /root1 has the entire system
> and /boot is a boot partition
> I modified the fstab file properly
> and I run grub2-mkconfig
> The new system is detected properly (I can also edit grub.cfg to try to boot
> on the right partition)
>
> But, I cannot boot on /root2 (using the /boot1 or /boot2)
>
> Is is a relabeling issue?
>
> How can I relabel from grub2 ?
> It seems that using touch /root1/.autorelabel
> I can only relabel the partition /root1 (and not /root2)
>
> As I said, I did this tens of times.
>
> Thank.
>
Hi Patrick,
I don not know if this will help, but what the heck ...
I have tried manually doing clones with dd and had no success
whatsoever.
That being said, I use Clonezilla on weekly basis and it
works wonderfully.
https://clonezilla.org/downloads.php
Seen thread but on Vacation, so only have remote access to main systems.
I maintain the G4L disk imaging project, and its primary backup uses dd and
default lzop compression to make image files.
It does have a clone option that makes disk to disk clones, but one issue that
sometimes happens. If you do a disk clone the block ids of the disks are the
same, and if ones loader is using blkids to load partitions, it is confused,
since each disk is suppose to have different block ids.
In my classroom, I had 20 systems, and would broadcast using udpcast to
the other 19 systems, but since all machines were separate no issues on
boot.
Had a user do a clone in same machine to another disk, and did allow
booting from either disk. He could boot from either disk if he disconnected
the other.
He manually changed the block id on cloned disk, and modified the grub.cfg
and then it worked fine.
I generally make compressed images to an ftp server or external usb device.
G4L can be added to the boot options, and run from ram after loading from
/boot.
So, another 2 cents.
The iso cuts beautifully to a flash drive with dd
-T
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned: 19,471
Processing time: 32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)
BOINC@HOME CREDITS
ROSETTA 65618572.246315 | ABC 16613838.513356
SETI 109441642.939754 | EINSTEIN 141229339.499240