Strange message at bootup

adityavpratap · 04-23-2006, 11:31 PM

Hi,
I am running Slackware 10.1 on my system. I had trouble booting up yesterday and the problem was resolved thanks to the help given by members of this forum.
Now I notice that during the boot up process the following output is generated -

Quote:

VFS: Mounted root (ext2 filesystem).
ext3: Unknown symbol journal_force_commit
ext3: Unknown symbol journal_dirty_data
ext3: Unknown symbol journal_force_commit_nested
ext3: Unknown symbol journal_init_dev
ext3: Unknown symbol journal_dirty_metadata
ext3: Unknown symbol journal_forget
ext3: Unknown symbol journal_wipe
ext3: Unknown symbol journal_blocks_per_page
ext3: Unknown symbol journal_errno
ext3: Unknown symbol journal_extend
ext3: Unknown symbol journal_invalidatepage
ext3: Unknown symbol journal_create
ext3: Unknown symbol journal_unlock_updates
ext3: Unknown symbol journal_revoke
ext3: Unknown symbol journal_lock_updates
ext3: Unknown symbol journal_start_commit
ext3: Unknown symbol journal_flush
ext3: Unknown symbol journal_load
ext3: Unknown symbol journal_try_to_free_buffers
ext3: Unknown symbol journal_update_format
ext3: Unknown symbol journal_get_write_access
ext3: Unknown symbol journal_get_undo_access
ext3: Unknown symbol journal_get_create_access
ext3: Unknown symbol journal_destroy
ext3: Unknown symbol journal_clear_err
ext3: Unknown symbol journal_stop
ext3: Unknown symbol journal_init_inode
ext3: Unknown symbol journal_start
ext3: Unknown symbol log_wait_commit
ext3: Unknown symbol journal_release_buffer
ext3: Unknown symbol journal_check_available_features
ext3: Unknown symbol journal_abort
ext3: Unknown symbol journal_restart
EXT2-fs warning (device hda5): ext2_fill_super: mounting ext3 filesystem as ext2

I fail to understand why my ext3 filesystem on /dev/hda5 i.e., the root file system is being mounted as ext2.
I hope that the learned members of this forum can help me unravel this mystery.

dennisk · 04-24-2006, 11:30 AM

It looks like the ext3 journal might be corrupt. Check the man pages for ext3 (man -k ext3) for several programs that should help you out.

Perhaps what you did the other day to restore the system cause the problem. From the messages you posted I'd guess that rebuilding the journal or just converting the, now, ext2 filesystem to ext3 would fix things.

Dennisk

adityavpratap · 05-02-2006, 08:51 AM

It seems to be related to the kernel. When I boot into 2.4.9 kernel, the message is not displayed. Only when I boot into 2.6.10, that I get the error messages.

egag · 05-02-2006, 09:36 AM

hi there,

did you compile that 2.6 kernel yourself ?
looks like it's missing support for the ext3 filesystem.
(...and mounts it as ext2 because of that).

egag

adityavpratap · 05-02-2006, 09:55 PM

No, this kernel is available in the testing folder of the Slackware 10.1 2nd CD.
I just installed it using installpkg like this -
$installpkg kernel-generic-2.6.10.......tgz
$installpkg kernel-modules..............tgz
then
$cd /boot
$mkinitrd -c -k 2.6.10 -m ext3
then made the relevant changes to lilo.conf and ran lilo.
So now do I have to compile the kernel again for ext3 support?

willysr · 05-02-2006, 11:49 PM

if i'm not mistaken, you must use -m jdb:ext3 or jbd:ext3 to support ext3 for your initrd (please see README in /boot for more information about the correct modules about jbd or jdb. It's described there clearly)