Red Hat Bugzilla – Bug 136199
rhgb-0.11.2-8 complains bad umount
Last modified: 2007-11-30 17:07:13 EST
umount: invalid argument
umount: umount /initrd failed
during the boot on x86_64 with kernel 2.6.8-1.624. Machine seems to
work fine otherwise.
This code hasn't changed at all recently. Is something mounted on
/initrd after you boot? Did you boot with an initrd?
fil[hjl@gnu-20 tmp]$ file foo
foo: Linux rev 1.0 ext2 filesystem data
[hjl@gnu-64 tmp]$ file foo
foo: ASCII cpio archive (SVR4 with no CRC)
I am not sure if the new /initrd is mounted at all during the boot.
It doesn't look like it is. If it is true, umount /initrd will lead
to those messages.
No, it should be mounted.
Hm, the umount is wrapped in a check that it's actually mounted. So
presumably there is something mounted there.
It may come from mkinitrd-4.1.18-1. It puts
in init in initrd.
The problem is rhgb-0.11.2-8 in RHEL 4 B2:
[root@gnu-5 log]# rpm -q rhgb
[root@gnu-5 log]# /usr/bin/rhgb
umount2: Invalid argument
umount: /initrd: not mounted
/usr/bin/rhgb is used by /etc/rc.d/rc.sysinit.
An update rhgb-0.14.1-5 fixing the bug has been pushed to RHEL-4.
It should fix this problem,