[EMAIL PROTECTED] wrote:
>
> > Okay, cool. Make sure that the /etc/lilo.conf line looks exactly like
> > this:
> >
> > append="mem=64M"
> >
> > Also, after you check that or make the changes, run /sbin/lilo to write
> > the boot block back out with the updates. Maybe that got missed after
> > the previous change?
>
> Okay, new problem.
>
> KDE seems to crash on me a lot (I was working with kpackage). After one
> crash, I was working with the PPP interface, when suddenly, the shell
> crashed on me with a big stack error.
>
> When I reboot, it checks the hard disks, then it says, "/dev/hd1:
> Duplicate/bad block(s) in inode 22600:/dev/hd1: and it lists off a lot
> of other blocks with a similar label.
>
> After a bunch of errors, it concludes with, "/dev/hd1: UNEXPECTED
> CONSISTENCY; RUN fsck MANUALLY. (i.e. without -a or -p options)
> In red, it concludes with, [FAILED].
>
> Basically, it's a corrupted filesystem, I think. So how do I run fsck
> and fix it?
> --
do the cntl-d thing when it gives you the option
then:
/sbin/fsck /hdx1
where x should be like a or b depending if its the master drive
or a secondary drive.
Point is you're missing a letter when you say /dev/hd1
it should be /dev/hda1 or something..
===============================================
[EMAIL PROTECTED] ( [EMAIL PROTECTED] )
Coming to you with Linux-Mandrake 6.0
