On Mon, 28 Dec 2015 01:14:48 +1030
Tim wrote:
> Generally speaking, if you want to clone drives, you're much better off
> booting from some third thing, and copying from source to destination
> without any interference from an OS currently running from the drive
> you're copying.
Yep. I do that pretty frequently, using rsync to copy everything off
the inactive drives to new partitions on the new disk (which can be
much bigger than the old disk). It is also how I install fedora these
days - install in a virtual machine first, guestmount the image and
rsync to the partition I want it to live in (with no possibility
anaconda will do anything to overwrite other partitions :-).
You can then chroot into the copied disk and run grub2-install in
there to make it bootable.
Alternatively, you can make a grub2 "configfile" entry in the existing
bootable disk which you can then use to boot the new disk and run grub2-install
after booting it. A configfile entry looks like this:
menuentry "Boot Fedora 23 via configfile" {
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
configfile /boot/grub2/grub.cfg
}
You'll need to adjust the hd0,msdos2 appropriately to point to the
new disk (and probably make a unique file in the root of the new disk
so you can check and see it is there after booting and you really did
boot the new disk and not the old one :-).
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
