-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2008-10-29 at 13:11 +0100, Josef Reidinger wrote:

This is not kernel problem, it is problem during upgrade bootloader configuration. This is check which compare /etc/fstab and /etc/mtab (in next release it is changed to /proc/mounts ) so if you send here your /etc/fstab and mtab I can say you what is wrong.

Thanks. mtab: /dev/hdd14 / reiserfs rw,acl,user_xattr 0 0 /proc /proc proc rw 0 0 sysfs /sys sysfs rw 0 0 debugfs /sys/kernel/debug debugfs rw 0 0 udev /dev tmpfs rw 0 0 devpts /dev/pts devpts rw,mode=0620,gid=5 0 0 securityfs /sys/kernel/security securityfs rw 0 0 /dev/hdc /mnt/dvd iso9660 ro,nosuid,nodev 0 0 NOT_nimrodel:/ # mount /dev/hdd14 on / type reiserfs (rw,acl,user_xattr) /proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) securityfs on /sys/kernel/security type securityfs (rw) /dev/hdc on /mnt/dvd type iso9660 (ro,nosuid,nodev) fstab: LABEL=320_boot3 /boot ext2 acl,user_xattr 1 2 LABEL=160_test / reiserfs acl,user_xattr 1 1 /dev/disk/by-id/ata-ST3320620A_5QF2M56F-part5 swap swap pri=42 0 0 /dev/disk/by-id/ata-ST3160021A_5JS4VV1F-part7 swap swap pri=42 0 0 LABEL=320_Grande /data/Grande xfs noatime,nodiratime,noauto 1 2 LABEL=160_Big /data/biggy xfs noatime,nodiratime,noauto 1 2 LABEL=160_root /other/main ext3 acl,user_xattr,noatime,nodiratime,noauto 0 0 LABEL=320_usr_local /other/main/usr/local reiserfs noatime,nodiratime,acl,user_xattr,noauto 0 0 LABEL=320_home1 /other/main/home xfs noatime,nodiratime,noauto 0 0 LABEL=160_usr_src /other/main/usr/src reiserfs noatime,nodiratime,acl,user_xattr,noauto 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 # LABEL=Amon_Din /mnt/Amon_Din reiserfs noatime,user,noauto,acl,user_xattr 0 0 #LABEL=Eilenach /mnt/usb/Eilenach reiserfs noatime,user,noauto,acl,user_xattr 0 0 #/dev/mapper/mcr_mm_nardol /mnt/usb/Nardol reiserfs noatime,user,noauto,acl,user_xattr 0 0 /dev/mapper/mcr_mm_erelas /mnt/usb/Erelas reiserfs noatime,user,noauto,acl,user_xattr 0 0 /dev/mapper/luks_crypto_042a7ba2-8908-4255-be33-a9cb51580de4 /mnt/usb/Nardol reiserfs noatime,user,noauto,acl,user_xattr 0 0 /dev/dvd /mnt/dvd auto ro,noauto,user,exec 0 0 However: /proc/mounts contains way much more. Factory is in a chrooted shell, the /"host" is 11.0 and contains a lot more and different; examples: rootfs / rootfs rw 0 0 udev /dev tmpfs rw,mode=755 0 0 /dev/hdd6 / ext3 rw,noatime,nodiratime,errors=continue,user_xattr,acl,barrier=1,data=ordered 0 0 - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkkIZJMACgkQtTMYHG2NR9UHLwCdG4ixTaKG/4kjlgr1z5X4GO7g 2m8An0vo2nUWBeFaOQAxTFggv8V1jphr =8zUn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2008-10-30 at 08:13 +0100, Josef Reidinger wrote:

OK, so now it is quite clear what happen, you have in fstab this line: LABEL=320_boot3 /boot ext2 acl,user_xattr 1 2

but in mtab there is no line about mounted boot. So perl-Bootloader think, that you have separate root which is not mounted.

You are right! Then... chroot has a problem or a behaviour I didn't was aware about. See, I have a script: #!/bin/bash mount /otros/test_d/ mount /otros/test_d/boot/ mount --bind /proc /otros/test_d/proc mount --bind /sys /otros/test_d/sys mount --bind /dev /otros/test_d/dev cp -f /etc/resolv.conf /otros/test_d/etc/resolv.conf echo echo " Copy paste the next line to activate prompt change:" echo "export PS1=$'\\[\E[1m\E[31m\\]NOT_\\h:\\w # \\[\E(B\E[m\\]'" echo chroot /otros/test_d/ /bin/bash --login And verifying: nimrodel:~ # mount | grep otros/test_d /dev/hdd14 on /otros/test_d type reiserfs (rw,noatime,nodiratime,acl,user_xattr) /dev/hda8 on /otros/test_d/boot type ext2 (rw,noatime,nodiratime,acl,user_xattr) /proc on /otros/test_d/proc type none (rw,bind) /sys on /otros/test_d/sys type none (rw,bind) /dev on /otros/test_d/dev type none (rw,bind) So, boot is there, mounted. However, when I chroot, it dissapears: nimrodel:~ # chroot /otros/test_d/ /bin/bash --login nimrodel:/ # mount /dev/hdd14 on / type reiserfs (rw,acl,user_xattr) /proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) securityfs on /sys/kernel/security type securityfs (rw) What's happened? This worked before. :-? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkkJoZ0ACgkQtTMYHG2NR9XeuACeINMkFPeYZumPZaMnqkF1Yo8/ dG0AnAxqX8m2i6w/Frs62MfDN7bgYd8h =tozM -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2008-10-30 at 14:03 +0100, Christian Boltz wrote: ( forgot to post this email, after the test )

...

So, boot is there, mounted. However, when I chroot, it dissapears:

nimrodel:~ # chroot /otros/test_d/ /bin/bash --login nimrodel:/ # mount /dev/hdd14 on / type reiserfs (rw,acl,user_xattr) ... What's happened? This worked before. :-?

Mount basically does a "cat /etc/mtab" when listing the mounted devices. Therefore it's not really surprising that it gets things wrong inside the chroot. As a possible workaround, you can manually edit the chrooted /etc/mtab.

I'll try: echo "/dev/hda8 /boot ext2 rw,noatime,nodiratime,acl,user_xattr 0 0" >> /etc/mtab which is the line the non-chrooted host system has, except that for pathto/boot. if it works, I'll think how to add it to my prepare script. [...] Yes, it works. I think that the correct thing is to edit the mtab file (joe, mcedit, vi...), and remove / add / edit incorrect entries, because it will contains the same that was valid when halting the system. The god news is that ti should keep till a real reboot. It just has to be done and not automated easily. Not a fault of the installer: it worked before per chance, perhaps. I think :-) I did open a Bugzilla, but as far as I'm concerned I'm happy just knowing that I have to edit mtab. Unless somebody makes me happier by telling me it is a real bug ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkkQLpkACgkQtTMYHG2NR9UJbQCfed0E9FRQvXv00k4s8ezQ8kL/ SSkAnjrd9qZoAvwsbQklvlfGnZMMx4SO =FK65 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Dave Plater wrote:

Carlos E. R. wrote:

...

Hi,

I'm running a zyper dup of factory from a 11.0 chroot. I get this error:

.... .... Installing: kernel-pae-base-2.6.27.3-2.1 [error] Installation of kernel-pae-base-2.6.27.3-2.1 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Setting up /lib/modules/2.6.27.3-2-pae Scanning scripts ... Resolve dependencies ... Install symlinks in /lib/mkinitrd/setup ... Install symlinks in /lib/mkinitrd/boot ...

Kernel image: /boot/vmlinuz-2.6.27.3-2-pae Initrd image: /boot/initrd-2.6.27.3-2-pae Root device: /dev/disk/by-id/ata-ST3160021A_5JS4VV1F-part14 (/dev/hdd14) (mounted on / as reiserfs) Resume device: /dev/hda5 WARNING Cannot determine dependencies of kernel module 'pata_acpi'. Does it exist? If it does, try depmod -a. Continuing without pata_acpi. WARNING Cannot determine dependencies of kernel module 'ata_generic'. Does it exist? If it does, try depmod -a. Continuing without ata_generic. WARNING Cannot determine dependencies of kernel module 'ide_pci_generic'. Does it exist? If it does, try depmod -a. Continuing without ide_pci_generic. Kernel Modules: dock scsi_mod libata ata_piix edd usbcore ohci-hcd uhci-hcd ehci-hcd Features: block usb resume.userspace resume.kernel Bootsplash: openSUSE (1024x768) 22200 blocks /boot directory is not mounted error: %post(kernel-pae-base-2.6.27.3-2.1.i586) scriptlet failed, exit status 1

Abort, retry, ignore? [A/r/i]: a

Which is false, /boot is mounted.

A retry fails:

NOT_nimrodel:/ # nice zypper -n dup -l zypper: error while loading shared libraries: libboost_signals-mt.so: cannot open shared object file: No such file or directory NOT_nimrodel:/ # rpm -i --force /mnt/dvd/suse/i586/boost-1.34.1-45.37.i586.rpm NOT_nimrodel:/ #

and now I can retry zypper dup, which then fails on the kernel install as above.

-- Cheers, Carlos Robinson

Check out bug https://bugzilla.novell.com/show_bug.cgi?id=431703 which I thought was fixed but your errors look like it maybe isn't Regards Dave P

No this is different bug, in that bug fail mkinitrd, because missing some modules which needed, but here failed bootloader_entry script. JR -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org