ext2_read_super: mounting ext3 filesystem as ext2

Jiggy · 11-15-2003, 11:13 PM

You can ignore this thread, i've installed 9.1

root@localhost:/var/log# cat syslog | grep warning
Nov 15 23:40:45 localhost kernel: EXT2-fs warning (device ide0(3,6)): ext2_read_super: mounting ext3 filesystem as ext2
root@localhost:/var/log# mount /mnt/c
mount: fs type vfat not supported by kernel
root@localhost:/var/log#

I just recompiled my kernel and got the errors above. I'm assuming if i recompiled it with fat support it will fix the last error but what about the first one? I'm using Slack9 with kernel 2.4.20

scott_R · 11-16-2003, 12:20 AM

You'll need vfat support compiled in for windows, but I'm assuming you meant that. As for the ext2 thing, you need to enable ext3 support in the kernel. Taken alone, these errors might be confusing, but I have a feeling that for some reason either you missed the fs portions of the configuration, or didn't save it once you configured it. Most likely, the first option. Go through it again, and see. Running ext3 as ext2 won't cause any problems, you simply get that warning so you know there's no journaling support. If you were to continue to run it, you'd want to set up e2fsck to check you disk every once in a while (the amount depends on how much you value your data versus time you want spent on those checks).

Jiggy · 11-16-2003, 01:54 AM

I just compiled it to support ext3 but am having problems... Its been a while since i've used this box and so i thought i was using ext2... But then given the error i figured you were right and i had to of been using ext3 so i recompiled the kerenel with ext3, fat, VIA82Cxxx chipset, Direct Rendering Manager, and Video mode selection. Now when i boot to my new kernel the screen is blank, and when i boot to my old kernel i get the following kernel panic:

EXT2 - fs: ide0(3.6) - couldn't mount because of unsupported optional features (4)
Kernel Panic: VFS : unable to mount root on fs on 03:06

So i guess i was using ext2. I can understand that the new kernel screwed up but i don't understand why the heck my old kernel is now giving me problems. It was supposed to be a backup right? How can i fix this? I've tried booting to the CD and can't get a console

Jiggy · 11-16-2003, 12:26 PM

I've booted to a Slackware Linux LiveCD and heres my lilo.conf and fstab

Code:

bash-2.05b# pwd
/mnt/hda6/etc
bash-2.05b# cat lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#compact        # faster, but won't work on all systems.
prompt
timeout = 50
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hda6
  label = Slackware
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
image = /boot/vmlinuz.old
  root = /dev/hda6
  label = slack.old
  read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# DOS bootable partition config begins
other = /dev/hda1
  label = Windows
  table = /dev/hda
# DOS bootable partition config ends

Code:

bash-2.05b# pwd
/mnt/hda6/etc
bash-2.05b# cat fstab
/dev/hda5        swap             swap        defaults         0   0
/dev/hda6        /                ext3        defaults         1   1
/dev/hda1        /mnt/c           vfat        defaults         1   0
/dev/hda7        /mnt/d           vfat        gid=500,umask=002,exec,dev,suid,rw 1   1
/dev/cdrom       /mnt/cdrom       iso9660     noauto,owner,ro  0   0
/dev/fd0         /mnt/floppy      auto        noauto,owner     0   0
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults         0   0
bash-2.05b#

Now if theres nothing wrong with the above, could i edit my /mnt/hda6/usr/src/linux/Makefile to have this line "export INSTALL_PATH=/boot" point to /mnt/hda6/boot and recompile my kernel from this slack LiveCD, then reboot?

qwijibow · 11-16-2003, 02:11 PM

My kernel used to do that....

when configureing the kernel i fixed it by compiling all the file system support i needed as modules.

when compiling there first few kernels a common mistake is to compile alot of things into the kernel rather than modular. modules are GOOD, plus, your distro will assume that certain things are compiled as modules, if you try to compile into the kernel, it will get upset when trying to insert these already in there modules.

Jiggy · 11-16-2003, 02:55 PM

Thanks, are there any other things i should compile as modules?

Anyone know of a way i can compile my kernel from a Linux LiveCD? I think thats the only way i'm going to be able to do it since both my old and new kernels won't boot.

qwijibow · 11-16-2003, 03:45 PM

look in the /boot/ directory for a Configure-2.4.versionnumber
that contains the options used to compile the running kernel from the straight installation (the kernel on the cd)

you can usually load that up for the different kernel and just go through changing what you want.

i assume you use make xconfig to configure the kernel ? you can load it by clocking load config from file.

in redhat it seems almost everything is compiled as a module, only things every user and pc will definatly use are compiled inot the kernel.

yeah, also compile all the ppp stuff as modules, plus the netfilter settings for iptables

Jiggy · 11-16-2003, 03:52 PM

I'm running Slack9 but have booted to a bootable Linux CD... Heres whats on my HD in /boot config-ide-2.4.20. So since i'm on the LiveCD with my Slackware installation mounted on /mnt/hda6 all i have to do is edit the /mnt/hda6/usr/src/linux/Makefile to put the new compiled kernel in /mnt/hda6/boot/, and then after that i can just go to the /mnt/hda6/usr/src/linux/ and make menuconfig and load up the /boot/config-ide-2.4.20 file and continue compiling the kernel?

Thanks, i'll be sure to make the file systems and iptables modules

zelgadis · 11-18-2003, 07:27 PM

To compile a new kernel from a livecd or floppy rescue i think you must use the "chroot" command, not sure about how to use it.