Here is what I am getting....

EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended

Ok so I boot my rescue cd leaving my hda1 root ro and run e2fsck -y
After it morks it magic Which it "fixed" supposedly, several inode probs and some block structure.

Got 'FILESYSTEM MODIFIED'....

Rebooted and stil get the dmegs tail warning...

I have not been able to find any info of value on this subject... Call GURU magic....

Please advise...

Note learned something new today.... If you build a new kernel with an EXTRAVERSION = <what-ever> in the Makefile... nothing compiled with the SAME pre-version ie 2.4.22 will work with the 2.4.22.what-ever extraversion even though it is a simple name addition and not a whole new kernel version... They must be complied with the 2.4.22.what-ever kernel.... I find this to be a bit on the stupido side as nothing changed but removing the unused clutter of the kernel and id-ing a name to keep the generic kernel safe... So I had to re-make the kernel only changeing the Makefile EXTRAVERSION = so I would no be hung out to recomplie most of the stuff for just a simple name change... That needs to be really fixed..... very dumb indeed.... The kernel should be able to relay that its' core is still the same and only the name has changed....

"Ok so I boot my rescue cd leaving my hda1 root ro and run e2fsck -y
After it morks it magic Which it "fixed" supposedly, several inode probs and some block structure."

You must run fsck against an unmounted file system. Before you run fsck do:
umount /dev/hda1

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

thanks, BUT been there and done that..

The dmesg tail is still there. booting the rescue disk and running fsck /dev/hda1 indicates the fs is 'clean'...

"The dmesg tail is still there. booting the rescue disk and running fsck /dev/hda1 indicates the fs is 'clean'..."

The portion of dmesg that you show does not give the partition number. Do you have other Linux partitions besides /dev/hda1? If so then run fsck against every linux partition except swap.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

AHHH
That would explain another issue I am having with my 3 partition usb harddrive....
3 in the tree and 3 partitions... I think you may have provided me with the correct path... I am sure of it...

The EXTRAVERSION thing is there for a reason. It causes a new /lib/modules directory to be made with the new modules.
This way you can have a /lib/modules/2.4.25 modules dir for the standard modules and a /lib/modules/2.4.25-custom dir for your own modules. when the kernel boots it will look for the correct module directory.
If you want to backup the Makefile just change the name adding a suffix.

Yes I understand what it EXTRAVERSION does.. When I used it i had both my 2.4.22 and my 2.4.22.<box name>. When I booted with the new kernel all went will except when it tried to load certain things. i.e. custom usb hard drive mods, alsa mods, video card mods.. When I checked to see what the problem was it listed "modules built with 2.4.22" and it would not load them.
As I stated I only took the floatsom and jetsom out of the kernel. I wished to retain the original kernel intact as I am prone to tearing down my boxes and rebuilding them on the fly. With a few generic kernel available I would have a fallback when I added or removed something.