Carlos E. R. wrote:
Funny.
Ah.... perhaps... an idea.
On a second phase, it is the job of '/etc/init.d/boot.localfs' to check the rest of the partitions, and when it runs, "/" is already RW, I think - yes, it is:
case "$1" in start) # rootfs is mounted rw, lvm et al should be up now
Then it runs fsck, and if the error is greater than 3, it does this:
... echo "fsck failed. Please repair manually and reboot. The root" echo "file system is currently mounted read-only. To remount it" echo "read-write do:" echo echo " bash# mount -n -o remount,rw /"
That's the message you saw, isn't it? But at that point root is RW, and that matches what you saw.
This second script is wrong. There are two mistakes: one is to wrongly report the RO status (because the script is derived from the first one). The other is misleading you to think that the root filesystem is faulty, when it is some other partition.
Ah!
I see it clear, it happened to me as well when I deleted a partition and forgot to remove it from the fstab file. I got the same error as you did.
Carlos E. R., you are brilliant!!! Thanks for the reply. I had almost forgotten about this problem, since I got my system working again by putting fs_passno=0 for the extra HD. Once I put it back in the system I think it doesn't matter. I am very happy you thought about the script, and looked at it. I had suspected there was really a bug, since we agree it should not have behaved this way. So this is actually quite serious. It should be reported to Suse. I would say that responsibility should be mine. I will make a note of it. Unfortunately, now I am deep into experiments with DVD burning, for the first time. Hopefully I won't forget about this issue. Good day! -- ____________________________________ Christopher R. Carlen Principal Laser/Optical Technologist Sandia National Laboratories CA USA crcarle@sandia.gov