Re: relabel

[Patrick Dupre]

Hello Chris,

I am back with you.
Thinking about your suggestion.
I generate a file: /boot/grub2/grub.cfg
and
a file initramfs
but these files are on the clone.
If I understand (I guess) the point in generating a new initramfs, I do not
see the point in generating a new grub.cfg file since it is not seen 
during the grub2 precessing since the grub.cfg file used in on the
cloned partition until a make a new grub2-install /dev/sda
from the clone.
Anyway, in my opinion, the issue is when grub executes:

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' {
        set gfxpayload=text
        insmod gzio
        insmod part_msdos
        insmod ext2
        set root='hd0,msdos16'
        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
        else
          search --no-floppy --fs-uuid --set=root c2010fed-5fcf-4c59-bca9-10922b131d8b
        fi

because the clone partition is not correct.
Something is missing:
failed to start creat static device mode in /dev
failed to start journal
etc...

To me looks like that the services are not started!!!
how the /dev partition is created?

What do yo think?

Regards.
> On Dec 25, 2013, at 5:48 PM, Patrick Dupre  wrote:
> > 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
> [e-mail]
> 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: [e-mail]
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale           | |
 Tel.  (33)-(0)3 28 23 76 12                   | | Fax: [phone]
 189A, avenue Maurice Schumann                 | | 59140 Dunkerque, France
===========================================================================

relabel

[Chris Murphy]

On Dec 27, 2013, at 6:45 PM, "Patrick Dupre"  wrote:
> Hello Chris,
>
> I am back with you.
> Thinking about your suggestion.

How did you clone it? Did you use cp? Did you use rsync? What was the exact command?
> I generate a file: /boot/grub2/grub.cfg

Did you use chroot at all? That is, did you mount the clone's parts, bind the dev, proc, sys file system, and then chroot the clone, and then from within chroot did you grub2-install, grub2-mkconfig, and run dracut?
> If I understand (I guess) the point in generating a new initramfs, I do not
> see the point in generating a new grub.cfg file since it is not seen 
> during the grub2 precessing since the grub.cfg file used in on the
> cloned partition until a make a new grub2-install /dev/sda
> from the clone.

That's why you chroot the clone, then run all of these commands, otherwise they do not produce correct results for the clone.
> Anyway, in my opinion, the issue is when grub executes:
>
> 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' {
>        set gfxpayload=text
>        insmod gzio
>        insmod part_msdos
>        insmod ext2
>        set root='hd0,msdos16'
>        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
>        else
>          search --no-floppy --fs-uuid --set=root c2010fed-5fcf-4c59-bca9-10922b131d8b
>        fi
>
> because the clone partition is not correct.
> Something is missing:
> failed to start creat static device mode in /dev
> failed to start journal
> etc...
>
> To me looks like that the services are not started!!!
> how the /dev partition is created?

The clone is on another drive? And is that drive in the same computer or a different computer?

Chris Murphy