normal gentoo system, ~x86. I get a notice about a stale /etc/mtab~ whenever I reboot my pc or shut it down to later turn it on again. Resolving is not critical, it can still boot without mount problems. (?) Resolving this: When I boot from a default gentoo livecd, and try to mount this jfs, I am getting an error from mount telling me it fails to mount. After that I fsck jfs, and every time it runs (with -pfv-parameters) it's got some errors on it. After fscking, I can properly mount jfs and remove /etc/mtab~.
Can we please have :- 1) Kernel version [ 'uname -a' ]... 2) 'emerge info'... 3) 'emerge -p baselayout' and the resulting version...
> Can we please have :- > 1) Kernel version [ 'uname -a' ]... $ uname -a Linux serena 2.4.20-gentoo-r7 #1 Tue Nov 18 08:59:25 CET 2003 i686 AMD Athlon(tm) XP 1900+ AuthenticAMD GNU/Linux > 2) 'emerge info'... $ emerge info Portage 2.0.49-r15 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.4.20-gentoo-r7) ================================================================= System uname: 2.4.20-gentoo-r7 i686 AMD Athlon(tm) XP 1900+ Gentoo Base System version 1.4.3.12 distcc 2.11.2 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -O3 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=athlon-xp -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox autoaddcvs ccache" GENTOO_MIRRORS="http://ftp.snt.utwente.nl/pub/os/linux/gentoo ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo rsync://ftp.snt.utwente.nl/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 foomaticdb libg++ libwww mad mikmod png xml2 zlib gdbm berkdb slang svga tcltk 3dfx 3dnow aalib -acl -afs alsa apm arts avi cdr -cjk crypt -cups dga directfb -doc dvd encode -esd -evo fbcon flash gd gif -gnome -gphoto2 gpm gtk gtk2 -gtkhtml imlib innodb ipv6 java jikes jpeg kde -matrox mbox mmx motif mpeg ncurses nls oggvorbis opengl oss pam -pcmcia -pda pdflib perl pic python qt qtmt quicktime readline samba sdl ssl wmf tcpd tiff truetype X xmms xv xft -postgres -spell mozilla moznoirc -mozxmlterm -mozcalendar -mozaccess -mozcompose moznocompose mozp3p" > 3) 'emerge -p baselayout' and the resulting version... sys-apps/baselayout-1.8.6.12
Yet some more info: sometimes there is another problem with /etc/mtab~ which prevents mount from mounting file systems on boot. And, since data loss occurs, I just lost every e-mail on my system. Thus I am raising the severity of this bug.
If you get errors _every_ time you run fsck on a fs, that's very bad. That usually means something like hardware problems. You could have a hard drive going bad, you could have dma errors that are causing fs corruption. Do me a favor, can you attach any kind of dmesg log (preferrably not from the livecd)? Also can you attach the config you used to compile this kernel?
Created attachment 21224 [details] Kernel config
There are no hardware errors, I'm sure. It has to do with unclean unmounting, mtab problems or something like that I guess. I have commented out the "rm /forcefsck" and then touched /forcefsck so I could make sure the fs is clean before mounting. This makes mtab errors disappear. Could it have something to do with usb-fs perhaps?
~ files are removed right after / is mouted rw, so its not an issue with baselayout as far as I am conserned.
Martin, It seems like the problem occurs because, on halt or reboot, the fs's cannot be remounted read-only - I get that error. After that, I get a prompt "Enter root password for maintenance or press ctrl+d to continue booting" on *shutdown* or *restart*. This lasts for about 10 seconds, after which the system shuts down or restarts.
Please note again: there are !!'s *after* "umounting filesystems": "Remounting filesystems readonly" [!!] Please help me because I'd like to remove that /forcefsck-file in a safe way. Why can't these file systems be remounted readonly? because they are unmounted one step before? I'm clueless and don't know which init scripts are responsible for this.
Please also notice the following; Every time my system is "unmounting remaining filesystems read-only", it doesn't seem to work - [!!] is shown. This happens on both of my systems (well actually, one gets a Kernel o0Ops and halts...)
Please update to baselayout-1.8.6.12-r2, as the remount ro issue should be fixed with it.
Yes, it works for me now. However, on an unclean reboot, a jfs filesystem doesn't get fsck'ed. This seems to be because it is uncorrectly marked clean still. As I don't think that's a gentoo bug, I'll close this one :) Thanks Azarah!
