Hi: I have a Suse 9.1 box that has suddenly broke. It gets stuck with a message that I need to check the filesystem, but as you will see, there is apparently nothing wrong with the filesystem: The booting stops here and the following is a log of what I've done to fix it, without success: ... Loading console font lat9w-16.psfu -m trivial CK ... done 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: # mount /dev/sda2 on / type reiserfs (rw,acl,user_xattr) /dev/sda2 on / type reiserfs (rw,acl,user_xattr) # fsck /dev/sda2 fsck 1.34 (25-Jul-2003) reiserfsck 3.6.13 (2003 www.namesys.com) ... Partition /dev/sda2 is mounted with write permissions, cannot check it fsck.reiserfs /dev/sda2 failed (status 0x10). Run manually! # mount -n -o remount,ro / # fsck /dev/sda2 fsck 1.34 (25-Jul-2003) reiserfsck 3.6.13 (2003 www.namesys.com) ... Partition /dev/sda2 is mounted with write permissions, cannot check it 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) Ok, so we see that the system tells me it is RO and I should check, but it is really RW and I can't check. Nor can I remount it RO. And there is the strange fact that mount shows it mounted twice. So I run the rescue system from CD: Rescue login: root Rescue:~# fsck /dev/sda2 ... reiserfsck --check started ... Replaying journal.. Reiserfs journal '/dev/sda2' in blocks [18..8211]: 0 transactions replayed Checking internal tree..finished Comparing bitmaps..finished Checking semantics tree: finished No corruptions found There are on the filesystem: Leaves 78819 Internal nodes 522 Directories 22794 Other files 303921 Data block pointers 9007004 (1123 of them are zero) Safe link 0 ... Reiserfsck finished Rescue:~# 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? And why does it say it's mounted ro when it is really rw? Thanks for assistance. -- ____________________________________ Christopher R. Carlen Principal Laser/Optical Technologist Sandia National Laboratories CA USA crcarle@sandia.gov