After lots of head scratching and failed attempts I
came across the culprit... I made /dev/hdb2 ro
(read-only) in fstab. Curiously, I had not needed to
specifically make it ro on any other machines. Some
just said defaults (and I tried that unsuccesfully).
Maybe with 2 hard drives and the 2nd hard drive
containing / one has to be more specific.

--- SI Reasoning <[EMAIL PROTECTED]> wrote:
> I actually have this running at @expert but only had
> one response... pretty dead over there...
> 
> let me clarify things a bit...
> 
> I had two boxes previously running 7.2 with ext2
> box-x (broken box in question) and box-lt (laptop)
> 
> after upgrading to 8.1, I decided to also upgrade to
> ext3.  After recreating mkinird, box-lt worked
> without
> issue but box-x had this fsck problem. This is with
> the stock 8.1 kernel 2.4.8-26.
> 
> I was able to resolve box-x problem by re-ordering
> the"global" section at the top of lilo.conf and
> adding
> in read-only into this section (it already was on
> every individual kernel already... don't know why it
> also needed to be there).
> 
> This worked fine until I upgraded box-x to
> 2.4.8-36.1.
> I have not upgraded box-lt yet because it is running
> win4lin and they do not have an upgraded kernel for
> this yet. A new lilo.conf was automatically created
> during upgrade (which also did not have the
> read-only
> in the global section). I tried putting read-only on
> the new lilo.conf, I tried using the old lilo-conf
> only changing kernel versions, and I tried
> mkinitrd...
> all failed.
> 
> This is the status so far.
> 
> status of df -T on box-x:
> 
> [root@mom root]# df -T
> Filesystem    Type   1k-blocks      Used Available
> Use% Mounted on
> /dev/hdb2     ext3     3016176   2390920    472040 
> 84% /
> /dev/hda2     ext3       23393      3082     19103 
> 14% /boot
> none         tmpfs       63344         0     63344  
> 0% /dev/shm
> /dev/hda3     ext3      903052    746108    110980 
> 88% /home
> /dev/hda1     vfat     1625700   1098676    527024 
> 68% /mnt/windows
> si-mandrake.domain:/usr/lib/corel
>                nfs     9018696   6470592   2273224 
> 75% /usr/lib/corel
> si-mandrake.domain:/usr/doc/wpohelpfiles
>                nfs     9018696   6470592   2273224 
> 75% /usr/doc/wpohelpfiles
> si-mandrake.domain:/usr/include/wine-wpo2000
>                nfs     9018696   6470592   2273224 
> 75% /usr/include/wine-wpo2000
> si-mandrake.domain:/usr/share/fonts/wprequired
>                nfs     9018696   6470592   2273224 
> 75% /usr/share/fonts/wprequired
> si-mandrake.domain:/etc/fonttastic
>                nfs     9018696   6470592   2273224 
> 75%
>
/etc/fonttasticsi-mandrake.domain:/usr/share/fonts/userfonts
>                nfs     9018696   6470592   2273224 
> 75% /usr/share/fonts/userfonts
> si-mandrake.domain:/var/log/fonttastic
>                nfs     9018696   6470592   2273224 
> 75% /var/log/fonttastic
> si-mandrake.domain:/home/mom/.wpo2000
>                nfs     2530240   2243736    183688 
> 93% /home/mom/.wpo2000
> 
> 
> --- Vincent Danen <[EMAIL PROTECTED]> wrote:
> > On Thu Nov 29, 2001 at 09:13:04AM -0800, SI
> > Reasoning wrote:
> > 
> > (Let's move this over to expert@ where it belongs)
> > 
> > > That maybe the case...but I upgraded two systems
> > from
> > > 7.2 to 8.1 but only had problems with one of
> > them... I
> > > was able to resolve it with the old kernel by
> > mkinitrd
> > > and placing read-only in the global section at
> the
> > > beginning of lilo.conf. That does not seem to
> work
> > > with the new kernel.
> > 
> > Ok... both systems use ext2?  But now that I've
> seen
> > your other
> > message (about problems with -26mdk), I'm now
> > confused on your
> > definition of "new kernel".  Exactly what kernel
> are
> > you using on
> > either machine, and what is the output of "df -T"?
> > 
> > > > > potential "uniqueness":
> > > > > - 2 disk system with /boot on hda2 and / on
> > hdb2
> > > > > - upgraded mdk7.2 to 8.1
> > > > > - migrated from ext2 to ext3 (previous
> kernel)
> > > > > - k6-2 400 cpu (in case it is an amd chipset
> > > > issue)
> > > > 
> > > > I suspect, and this is by no means concrete,
> > that
> > > > your problem may
> > > > lie with the ext2->ext3 conversion.  I
> installed
> > an
> > > > 8.1 system
> > > > recently using ext3, but it was formatted as
> > ext3. 
> > > > The two disk
> > > > system should make no difference, and I can't
> > see as
> > > > a 7.2->8.1 update
> > > > would be the cause of the problem.
> > > > 
> > > > When I have a chance, I'll try installing a
> 8.0
> > > > ext2-based system in
> > > > vmware and then upgrade to 8.1 and converting
> > the
> > > > ext2 partitions to
> > > > ext3.  But it may take some days before I am
> > able to
> > > > do this.
> > 
> > --
> > vdanen (at) mandrakesoft.com, OpenPGP key
> available
> > on www.keyserver.net
> > 1024D/FE6F2AFD   88D8 0D23 8D4B 3407 5BD7  66F9
> 2043
> > D0E5 FE6F 2AFD
> 
> > ATTACHMENT part 2 application/pgp-signature 
> 
> 
> 
> =====
> SI Reasoning
> [EMAIL PROTECTED]
> 
> "They that can give up essential liberty to obtain a
> little temporary safety deserve neither liberty nor
> safety." 
> Benjamin Franklin
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! GeoCities - quick and easy web site hosting,
> just $8.95/month.
> http://geocities.yahoo.com/ps/info1
> 

=====
SI Reasoning
[EMAIL PROTECTED]

"They that can give up essential liberty to obtain a little temporary safety deserve 
neither liberty nor safety." 
Benjamin Franklin

__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com

Reply via email to