Arch Linux

Newnux

Member

Registered: 2007-06-13

Posts: 59

Filesystem Check Failed -> Mounted

After having a little trouble getting XFCE to start automatically like KDE did, I played around with some settings using a SLAX LiveCD.  Since then, I'm unable to boot for a different reason: Filesystem Check Failed.

The only thing that seems to be the problem is that /dev/sdb1 is, as it says, "mounted".  When I am prompted to fix it myself, I find that the system is confused as to whether it is mounted.

Typing "mount" produces

/dev/sdb1 on /mnt/sto type ext3 (rw,noexec,nosuid,nodev)

Yet typing "umount /dev/sdb1" produces

umount: dev/sdb1: not found
umount /mnt/sto: not found
umount: dev/sdb1: not found
umount /mnt/sto: not found

cd to /mnt/sto and using dir or ls -a also shows me nothing.
The following is displayed upon "reboot"

shutdown: /dev/initctl: No such file or directory
init: /dev/initctl: No such file or directory

Finally, the files I remember having edited in SLAX and partially ARCH.  I'm not sure how correct these are, but I didn't think trying to fix up XFCE was going to create such a problem:
/etc/X11/xinit/xinit.rc

#!/bin/sh
# $Xorg: xinitrc.cpp,v 1.3 2000/08/17 19:54:30 cpqbld Exp $

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then
    xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi

if [ -f $userresources ]; then
    xrdb -merge $userresources
fi

if [ -f $usermodmap ]; then
    xmodmap $usermodmap
fi

# start some nice programs
#twm &
#xclock -geometry 50x50-1+1 &
#xterm -geometry 80x50+494+51 &
#xterm -geometry 80x20+494-0 &
#exec xterm -geometry 80x66+0+0 -name login
exec startxfce4

/etc/inittab

#
# /etc/inittab
#

#  Runlevels:
#    0    Halt
#    1(S)    Single-user
#    2    Not used
#    3    Multi-user
#    4    Not used
#    5    X11
#    6    Reboot

id:5:initdefault:xdm

rc::sysinit:/etc/rc.sysinit
rs:S1:wait:/etc/rc.single
rm:2345:wait:/etc/rc.multi
rh:06:wait:/etc/rc.shutdown
su:S:wait:/sbin/sulogin -p

c1:2345:respawn:/sbin/agetty 38400 vc/1 linux
c2:2345:respawn:/sbin/agetty 38400 vc/2 linux
c3:2345:respawn:/sbin/agetty 38400 vc/3 linux
c4:2345:respawn:/sbin/agetty 38400 vc/4 linux
c5:2345:respawn:/sbin/agetty 38400 vc/5 linux
c6:2345:respawn:/sbin/agetty 38400 vc/6 linux

ca::ctrlaltdel:/sbin/shutdown -t3 -r now

x:5:respawn:/opt/xfce4/bin/startxfce4

# End of file

Please let me know if I'm missing any information.  I'm currently running Windows, but luckily have full access to my root partition.

Thanks in advance.

P.S. /dev/sdb1 is no longer being shown in Windows OR SLAX.  I predicted Windows, but can't think why it won't show up in SLAX.

Last edited by Newnux (2007-06-30 20:54:08)

Newnux

Member

Registered: 2007-06-13

Posts: 59

Re: Filesystem Check Failed -> Mounted

I've now managed to boot into Xfce by removing /dev/sdb1's fstab entry.

Strangely, manually mounting the drive now works perfectly.  The problem is this:

fsck /dev/sdb1
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
Storage has been mounted 29 times without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes

It seems to get stuck.  Either nothing is happening, or this is going to take many hours.  I also tried this in the shell, with it responding exactly the same.  Is there anything a little more verbose?

smurnjiff

Member

Registered: 2007-06-25

Posts: 211

Re: Filesystem Check Failed -> Mounted

Can you post your /etc/fstab?

Newnux

Member

Registered: 2007-06-13

Posts: 59

Re: Filesystem Check Failed -> Mounted

Never mind, the fsck seemed to complete just fine .

fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
Storage has been mounted 29 times without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Storage: 23560/24903680 files (22.3% non-contiguous), 41462978/49785427 blocks

It didn't take that long, I just expected a progress bar, like with other drives.

Thanks anyway!  Time to see if Arch boots without problems.