On Sun, 08 May 2005 09:53, Robert Himmelmann wrote: > >If there is a bigger problem then the boot process gets interrupted - > >sometimes you get dropped into a read-only shell, somethings you get told > > to boot to a read-only shell, so you can run reiserfsck and fix the > > filesystem. > > That happens. There explanation is that the root filesystem could not be > mounted read/write.
That's good, because running a filesystem check on a read/write filesystem can be disastrous and is not recommended. At this point, log in as root and run "reiserfsck --check /dev/hdXX" where XX is your disk and partition specifics eg /dev/hda1 If this results in the message "corruption that can be fixed with --fix-fixable" then run "reiserfsck --fix-fixable /dev/hdXX" If it results in the message "Running with --rebuild-tree is required" then type "man reiserfsck" and read the directions under --rebuild-tree before running "reiserfsck --rebuild-tree /dev/hdXX" If it results in no error messages, then your filesystem is ok and there is something else wrong. > Something important might be that I do not have a seperate > /boot-partition. I am using the latest stable gentoo-sources (kernel). I > have compiled a monolitic kernel. But you've been booting happily on this kernel up to now, right? > Some of the messages I remember: > > Checking Journal. Filesystem is readonly, skipping > Remounting filesystem read/write > Could not mount filesystem read/write :( > Give root password or press Control-D for normal startup. Give root password and try reiserfsck --check > This all comes a short time after the framebuffer is initiated. Is there > anything specific I could look for before these messages come? I have > read/write access to the partition from SuSE and Knoppix, so I can > change anything in /etc or compile a new kernel. Try not to mount the filesystem read/write until after you've tried the reiserfsck --check - if it is scrambled you could scramble it worse. Cheers, Wayne
