Help: Suse Linux won't boot!

From: Chris Carlen (crcarle_at_BOGUS.sandia.gov)
Date: 01/28/05 

Date: Fri, 28 Jan 2005 08:34:22 -0800

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 -- NOTE: Remove "BOGUS" from email address to reply.

Relevant Pages

  • [SLE] Help: Suse 9.1 box wont boot!
    ... message that I need to check the filesystem, but as you will see, there ... fsck failed. ... bash# mount -n -o remount,rw / ... /dev/sda2 on / type reiserfs ...
    (SuSE)
  • cannot boot-up linux, unable to read superblock
    ... mount: error 22 mounting ext3 ... enable lvm and tried fsck for the volumes (one is empty volume? ... Attempt to read block from filesystem resulted in short read while trying to open /dev/VolGroup00/LogVol00 ...
    (RedHat)
  • Help: Suse Linux wont boot!
    ... message that I need to check the filesystem, but as you will see, there ... fsck failed. ... bash# mount -n -o remount,rw / ... /dev/sda2 on / type reiserfs ...
    (comp.os.linux.misc)
  • Re: Problem with multiple mounts
    ... make reiserfs and run fsstress test case on this partition. ... I mount this partition on the nbd server. ... ReiserFS: sda10: journal params: device sda10, size 8192, journal first ... Mounting a filesystem which is already mounted and replaying the journal. ...
    (Linux-Kernel)
  • Re: freebsd-security Digest, Vol 187, Issue 4
    ... I was so transfixed on Josh stating that the attacker could as well ... just mount a filesystem with suid root binaries and how that would be ... more useful than a buffer overflow in the filesystem driver. ... How about something to force a fsck ...
    (FreeBSD-Security)