-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 06 December 2003 21:28, Leonard den Ottolander wrote: > Looking at the above messages it seems your problem is that / gets mounted > rw, which is why fsck can't check the file system. You need to mount it ro > on boot, so fsck can check it (or actually just establish it is an ext3 > file system and skip that step), and remount it rw. Hi Leonard - Yes, you were right about needing ro on the kernel commanline, thank you. I finally solved the ext3 boot problem a couple of days ago and am describing the resolution here for future searchers. The key thing was to never return from nash, instead to use the nash exec command to replace nash with /sbin/init from the mounted root partition. So the concept is you come up in nash from your initrd, load any modules you need, including jbd and ext3 from the initrd filesystem, then mount your root filesystem and pivot-root into it. THEN do not exit nash, but use the exec nash command to spawn init in place of nash. The boot then proceeds properly. In the struggle to find the above solution, I discovered that the real-root-dev stuff in the redhat initrd nash script is deprecated. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/31GejKeDCxMJCTIRAk9EAJoD+24ivV/ZU3F9hp+8Yx5QhDFTaACeIiaV HFCEHoF4gZ9aiBoeDoYu4OM= =eWHp -----END PGP SIGNATURE-----
