If there are incomplete writes to the hard disk that are journaled then they normally get completed and a message to that effect gets printed in the boot messages, then the filesystem gets mounted read-write.The first time I tried to start after the crash there were incomplete transactions. I corrected this by mounting the partition with knoppix.
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.
Anything else you can tell us? You turn the computer on and it boots to what point? What's the last couple of things you see?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.
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.
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.
Happy Hacking, Robert Himmelmann
Only those who leisurely approach that which the masses are busy about can be busy about that which the masses take leisurely.
-- Lao Tsu
"Murphy's Law, that brash proletarian restatement of G�del's Theorem ..."
-- Thomas Pynchon, "Gravity's Rainbow"
