Hello Chris,
Thank for your help.
I did exactly like you said, but the result is the same as before.
I am sure that the issue is with the initramfs.
According to the tests that I made. it is probably due to the /boot
which is not found
However, how can I know exactly what is going on?
I try to uncompress the new img, but it does not work
cpio -i -d -H newc -F ../initramfs-3.12.5-200.fc19.i686.PAE.img --no-absolute-filenames
cpio: premature end of file
This the grub.cfg generated:
menuentry 'Fedora, with Linux 3.12.5-200.fc19.i686.PAE' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.12.5-200.fc19.i686.PAE-advanced-69ee06ed-3f6a-4b9f-9b86-6e24c1847cf6' {
(this UUID is correct: new /)
set gfxpayload=text
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos16'
(this is correct: new /boot)
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos16 --hint-efi=hd0,msdos16 --hint-baremetal=ahci0,msdos16 --hint='hd0,msdos16' c2010fed-5fcf-4c59-bca9-10922b131d8b
(this is the UUID of the new /boot)
else
search --no-floppy --fs-uuid --set=root c2010fed-5fcf-4c59-bca9-10922b131d8b
fi
linux /vmlinuz-3.12.5-200.fc19.i686.PAE root=/dev/mapper/VolGrpSys3-root ro vconsole.keymap=fr rd.dm=0 rd.md=0 rd.luks=0 vconsole.font=latarcyrheb-sun16 rd.lvm.lv=VolGrpSys2/root
(this is bizarre: it should be:
linux /vmlinuz-3.12.5-200.fc19.i686.PAE root=/dev/mapper/VolGrpSys3-root ro vconsole.keymap=fr rd.dm=0 rd.md=0 rd.luks=0 vconsole.font=latarcyrheb-sun16 rd.lvm.lv=VolGrpSys3/root
why? VolGrpSys2/root is the cloned /)
initrd /initramfs-3.12.5-200.fc19.i686.PAE.img
}
How can I check each step?
Thank.
> > Hello,
> >
> > I wanted to clone my distribution fedora 19, I used to do it with
> > previous release but I failed with fedora 19.
> >
> > I copy (-a) the partition / (lvm2) and /boot (ext4)
>
> You probably need to remake the initramfs. The easiest way to do all of this after the cp -a of everything is to put together the clone at /mnt such that you have /mnt as rootfs, then /mnt/boot, and then use mount -B to mount the faux file systems, /proc, /dev/, /sys at their respective locations, /mnt/proc, /mnt/dev, /mnt/sys. Then chroot /mnt.
>
> Now blkid to find the uuids for /boot and /, and change fstab so that it's mounting the right volumes. Use dracut -f to make a new initramfs. And then grub2-mkconfig -o /boot/grub2/grub.cfg to make a new grub.cfg.
>
> If you started out with a system with correct labels, the cp -a will preserve them as it implies -Z so fixfiles/restorecon isn't needed.
>
> Chris Murphy
> --
> 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
===========================================================================
Patrick DUPRÉ | | email: pdupre@xxxxxxx
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
--
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
