# rhgb umount2: Invalid argument umount: /initrd: not mounted umount2: Invalid argument umount: /initrd: not mounted Hmm, I'll remove rhgb and keep an open eye next time I reboot, it doesn't work anyway since I changed to init 3. On Sun, 2004-01-18 at 18:04, Christoph Wickert wrote: > Am So, den 18.01.2004 schrieb David Jackson um 23:02: > > This was posted a day or so ago, and I've run out of question and answers > > for poster. > > > > Any ideas the systems thinks /initrd is mount? His /etc/fstab didn't have > > it defined? > > > > > > David > > > > > > > > > # cat /etc/grub.conf > > > # grub.conf generated by anaconda > > > # > > > # Note that you do not have to rerun grub after making changes to this > > > file > > > # NOTICE: You have a /boot partition. This means that > > > # all kernel and initrd paths are relative to /boot/, eg. > > > # root (hd0,1) > > > # kernel /vmlinuz-version ro root=/dev/hda3 > > > # initrd /initrd-version.img > > > #boot=/dev/hda > > > default=0 > > > timeout=10 > > > splashimage=(hd0,1)/grub/splash.xpm.gz > > > title Fedora Core (2.4.22-1.2149.nptl) > > > root (hd0,1) > > > kernel /vmlinuz-2.4.22-1.2149.nptl ro root=LABEL=/ hdd=ide-scsi > > > rhgb > > > initrd /initrd-2.4.22-1.2149.nptl.img > > > title Windows XP > > > rootnoverify (hd0,0) > > > chainloader +1 > > > > > > > > > On Sat, 2004-01-17 at 13:21, Raghu Vadapalli wrote: > > >> post your /etc/grub/grub.conf or lilo.conf if you can > > >> > > >> On Sat, 2004-01-17 at 13:25, Y. Makki wrote: > > >> > Hello, > > >> > > > >> > These messages show up when the pc boots, been like that since I > > >> > installed, any ideas where I should look to figure this one out? > > >> > > > >> > Welcome to Fedora Core > > >> > Press 'I' to enter interactive startup. > > >> > umount2: Invalid argument > > >> > umount: /initrd: not mounted > > >> > umount2: Invalid argument > > >> > umount: /initrd: not mounted > > Actually I don't think this is a problem of initrd (at least I don't see > an error in the config) but of rhgb. Execute rhgb (as root) when the > system is running, you'll get this error message. > > Christoph
