When my box crashed (power failure) it fails to now boot because it cannot be mounted. and the initrd prompts me for mount options or a shell, fsck,jfs is NOT in the initrd so I can't fix it from there... Booting from the LiveCD (2004.3) and running "jfs_fsck /dev/hda3" fixes it and it then can be booted. but shouldn't this have happened on it's own? Reproducible: Always Steps to Reproduce: 1.install system with hda1 ext2, hda2 swap, hda3 jfs 2. install kernel using initrd (genkernel 2.6.9-gentoo-r4) 3.crash box (pull power) 4. Actual Results: won't boot now. prompts for mount options or a shell from the initrd. must reboot with livecd and run "fsck_jfs /dev/hda3" to repair. Expected Results: the initrd should have run fsck_jfs on the partition before mounting. emerge info Portage 2.0.51-r3 (default-linux/x86/2004.3, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.8-gentoo-r10 i686) ================================================================= System uname: 2.6.8-gentoo-r10 i686 AMD Athlon(tm) MP Gentoo Base System version 1.4.16 distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux26-headers-2.6.8.1 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-mcpu=athlon-mp -O2 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/NX/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/shar e/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipd fm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ / usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/bind /var/qmail/c ontrol" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-mcpu=athlon-mp -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig candy ccache distcc distlocks sandbox sfperms" GENTOO_MIRRORS="ftp://mirrors.tds.net/gentoo http://mirror.datapipe.net/gentoo h ttp://mir.zyrianes.net/gentoo/" MAKEOPTS=" -j5 " PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X aalib acl alsa apm arts avi berkdb bitmap-fonts bonobo cdr crypt cs cope cups curl dga directfb dvb dvd encode esd f77 fam flac foomaticdb fortran f reetype gdbm ggi gif gnome gphoto2 gpm gstreamer gtk gtk2 guile imagemagick imli b jack java joystick jpeg junit kde libg++ libwww mad mikmod mmx motif mozilla m peg mysql nas ncurses nls nptl oggvorbis openal opengl oss pam pdflib perl png p ython qt quicktime readline ruby samba scanner sdl slang snmp speex spell sse ss l svga tcltk tcpd tetex tiff truetype usb videos wmf x86 xft xml xml2 xmms xv zl ib"
uhh what initrd ? are you using genkernel or something ?
using genkernel.... initrd is the initial ramdisk that genkernel creates and is used when booting the system to do the hardware detection and whatnot.
has nothing to do with base-layout then
Ok, well I don't see how anything would happen on itself. If it can't mount the root filesystem that contains fsck.jfs, then it can't fix it and it needs manual user intervention anyway, genkernel or not...
well if fsck.jfs was in the initrd it could have ran it from there, fixed the fs, mounted and all would be well... It seems that if jfs corrupts the fs during a power failure, even when the system is idle, then it should be marked as unstable in the kernel and not marked as not recommended due to this major problem. I can see it being OK for a non root FS, as fsck would be ran as the system boots, but I see it now as completely unsuitable for the root FS.
JFS will only allow a read-only mount until the journal is replayed by fsck. Booting the kernel with the "ro" option should allow the system to boot normally.
