Carlos E. R. wrote:
The Friday 2005-01-28 at 08:35 -0800, Christopher Carlen wrote:
So that's it. There appears to be nothing wrong. Furthermore, I can mount it from the rescue and all the directories appear to be their, and the files in a few of the dirs I browsed.
How to get Suse to stop getting stuck?
I'd guess there is something wrong in the fstab file. Probably you have listed some partition with the wrong filesystem, or it is no longer there.
Yes, I disconnected the drive with that partition.
And why does it say it's mounted ro when it is really rw?
On the contrary, it complains that it is mounted rw, and thus refuses to check it. You mounted it rw your self first thing - see:
Partition /dev/sda2 is mounted with write permissions, cannot check it
______________________________________^^^^^
_write_ permissions, ie, RW.
No, that was the ouput from fsck, which correctly says that the /dev/sda2 partition is mounted RW. What I was complaining about is the fact that the startup scripts reported that the partition was mounted RO, so that it could be checked. See: ... fsck failed. Please repair manually and reboot. The root filesystem is currently mounted read-only. To remount it read-write do: bash# mount -n -o remount,rw / Attention: Only CONTROL-D will reboot the system in this maintenance mode. Shutdown or reboot will not work. Give root password for login: This is normally what happens when a root filesystem is inconsistent when booting, and so the boot scripts correctly halt the system and request the user to manually run fsck, which must be done with the problem partition mounted RO. That is what I tried to do, thinking that there really was a problem, and that the problem partition was RO. But the / was actually mounted RW. *I* did not mount / RW. The *boot scripts* did, and then incorrectly reported that it was RO and needed checking.
fsck.reiserfs /dev/sda2 failed (status 0x10). Run manually! # mount /dev/sda2 on / type reiserfs (rw,acl,user_xattr) /dev/sda2 on / type reiserfs (rw,acl,user_xattr)
________________________________^^
It seems you have a double entry for sda2.
No, it was something else. See my other reply. Thanks for your input and interest. Good day! -- _____________________ Christopher R. Carlen crobc@sbcglobal.net SuSE 9.1 Linux 2.6.5