[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?
Well, you're missing a letter in the partition name there, so I'll
"assume" it's /dev/hda1 and if it's not, you'll need to change the
letter to whatever drive it actually is.
To fix the filesystem when you get that error, run:
e2fsck /dev/hda1
If it asks you questions, answer 'y' until you get back to your prompt.
Type 'exit' and the machine should reboot and start normally.
--
Steve Philp
Network Administrator
Advance Packaging Corporation
[EMAIL PROTECTED]
