On 2014-06-20 17:03, Markus Koßmann wrote:
Hallo; when I update a factory installation chrooted by running the following script I see grub2-mount processes hanging around with 100% CPU for some minutes. Am I doing something wrong ? Or is this a bug in grub2-mount ?
-------- Script--------- mount -t ext4 /dev/system2/root_factory /mnt mount -t ext4 /dev/disk/by-id/ata-SAMSUNG_SSD_830_Series_S0WKNYABB00183-part7 /mnt/boot
mv /mnt/etc/resolv.conf /mnt/etc/resolv.conf.orig cp /etc/resolv.conf /mnt/etc/resolv.conf mount --bind /dev /mnt/dev mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys chroot /mnt zypper dup -l --download-as-needed mv /mnt/etc/resolv.conf.orig /mnt/etc/resolv.conf umount /mnt/sys /mnt/proc /mnt/dev /mnt/boot /mnt
It is long since I did this the last time. You may have to copy over "/etc/mtab" and edit it yourself, manually, so that it matches the situation as seen from inside the chrooted environment. I also did "export PBL_SKIP_BOOT_TEST=1". And I think you should also configure grub2, in yast, not to seek for other operating systems. On some real situations I have seen it takes many minutes at full cpu: it tried to mount extended partitions (which is of course impossible), for instance. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)