|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PLUG] file system error on boot
|
On Sun, Mar 31, 2002 at 05:17:21AM -0500, Martin DiViaio wrote:
> Date: Sun, 31 Mar 2002 05:17:21 -0500 (EST)
> From: Martin DiViaio <scatterbrained@usermail.com>
> To: Plug List <plug@lists.phillylinux.org>
> Subject: Re: [PLUG] file system error on boot
>
>
>
> On the 30th day of March in the year 2002 you wrote:
>
> > Date: Sat, 30 Mar 2002 00:36:48 -0500 (EST)
> > From: Jon Galt <jongalt@pinn.net>
> > To: Plug List <plug@lists.phillylinux.org>
> > Subject: [PLUG] file system error on boot
> >
> > Greetings fellow PLUGgers, I have a friend with this problem:
> >
> > Being much less of an expert than I would like to be, I think it'll be
> > more productive to just ask if anybody here can help...
> >
> > So, what's a superblock, and what should I tell him to do?
> >
> > Thanks,
> > Wayne
> >
> > -------- Original Message --------
> > Subject: Re: [TriLUG] filesystem error on upgrade to RH 7.2
> >
> > I still cannot get RH 7.2 running on my machine (5-year-old
> > Intrex, pentium 120, 64 Megs ram, 2 IDE hard drives, Windows
> > 98 and Minix in other partitions).
> >
> > No matter how I vary the installation, whether as upgrade from
> > RH 7.0 (which works fine) or as fresh install on newly
> > partitioned space (which I've tried in about six different
> > configurations), I get a filesystem error on booting after the
> > installation.
> >
> > I have learned that this happens when checking the root
> > filesystem. When the rc.sysinit script is running this
> > command:
> > initlog -c "fsck -T -a $fsckoptions /"
> > that command returns 11
> > [ which I deduce (from man fsck) adds up from:
> > 1 file system errors corrected
> > 2 system should be rebooted
> > 8 operational error.
> >
> >
> > It complains
> > invalid operand: 0000
> > then it drops me to a "Repair filesystem" prompt, in a
> > situation where the root filesystem is still mounted
> > read-only. I can restart the installation in rescue mode and
> > then modify configuration files, but I am clueless as to what
> > to do.
> >
> > Here is one perhaps-enlightening exchange:
> > (Repair Filesystem) 8 # fsck.ext3 /
> > e2fsck 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09
> > fsck.ext3: Is a directory while trying to open /
> >
> > The superblock could not be read or does not describe a
> > correct ext2
> > filesystem. If the device is valid and it really contains
> > an
> > ext2 filesystem (and not swap or ufs or something else),
> > then
> > the superblock is corrupt, and you might try running e2fsck
> > with an alternate superblock:
> > e2fsck -b 8193 <device>
> >
> >
>
> An EXT3 filesystem IS EXT2 only with journaling turned on. In fact, you
> could mount an EXT3 filesystem as EXT2 and you would not notice the
> difference except that the journals would not be maintained.
>
> Your friend is running fsck.ext3 incorrectly. The fsck program wants a
> device not the mount point of a device. Since you did not say what
> drive/partition/interface the root partition (/) is on, I can't tell you
> what device you are looking for.
Blah, how embarassing, I need to brush up on my reading comprehension 8(
Regards,
Time
13
\
9 . 3 clockbot.net
/
6
______________________________________________________________________
Philadelphia Linux Users Group - http://www.phillylinux.org
Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce
General Discussion - http://lists.phillylinux.org/mail/listinfo/plug
|
|