[TriLUG] filesystem error on upgrade to RH 7.2

Vestal, Roy L. rvestal at rti.org
Mon Apr 1 14:35:45 EST 2002


The thing I ran into was I had to make a /boot partition. I made mine 100MB,
then it allowed root to work. Dunno if this helps.

-----Original Message-----
From: Richard O. Hammer [mailto:ROHammer at earthlink.net]
Sent: Monday, April 01, 2002 10:49 AM
To: trilug at trilug.org
Subject: Re: [TriLUG] filesystem error on upgrade to RH 7.2


"Vestal, Roy L." wrote:
> 
> What are your partitions? Sounds like a problem I had with mine a while
> back...
> 

I have tried many arrangements of partitions, and I have now
reinstalled (with accompanying repartition) twice, or perhaps
three times, since posting my most recent question on Friday.

But, to give one specific answer, here I copy a section from
my 3/21 post to this list on the same question:

<block from 3/21 post>

In response to "fdisk -l" I get:

Disk /dev/hda: 255 heads, 63 sectors, 1027 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot  Start    End    Blocks  Id System
/dev/hda1   *       1    383   3076416   b Win95 FAT32
/dev/hda2         384    386     24097+ 83 Linux
/dev/hda3         387   1027   5148832+  5 Extended
/dev/hda5         387   1018   5076508+ 83 Linux

Disk /dev/hdb: 64 heads, 63 sectors, 824 cylinders
Units = cylinders of 4032 * 512 bytes

   Device Boot  Start    End    Blocks  Id System
/dev/hdb1   *       1     33     66496+ 82 Linux swap
/dev/hdb2          34    700   1344672  83 Linux
/dev/hdb3         701    821    243936  81 Minix / old Linux

</block from 3/21 post>

Generally, I am trying configurations with partitions for
boot, root, and swap.  On a few attempts I've had a partition
for usr.

I have tried a broad enough arrangement of partitions that I
do not believe partitions have anything to do with the
filesystem error I'm facing.  And remember that I am
installing and reinstalling RH 7.0 on the same machine,
without encountering such an error.

Thank you,
Rich Hammer


> On Fri, 29 Mar 2002, Richard O. Hammer wrote:
> 
> > 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>
> >
> >
> > On Saturday, Tanner wrote:
> > >Do you use initrd?
> >
> > I am afraid I do not know what initrd is, or if I am using
> > it.  I suppose I am using the default for a RH 7.2
> > installation.  I notice that I have a directory "/initrd"
> > which is empty.  And on booting I see:
> >       boot:
> >       Loading initrd.img .......
> >
> >
> >
> > What I can try with this installation, to diagnose and cure
> > its ailment?
> >
> > Is there a good book which deals with startup scripts and
> > filesystems at a level which would help me diagnose this? (I
> > have a half dozen books on Linux, which introduce it and teach
> > for certification, but they do not cover what I need for
> > this.)
_______________________________________________
TriLUG mailing list
    http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ:
    http://www.trilug.org/~lovelace/faq/TriLUG-faq.html



More information about the TriLUG mailing list