Of course the problem with this is how the filesystem is mounted. I used the same method and the following happens: masala:~ # mount /dev/sda5 on / type ext3 (rw) proc on /proc type proc (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/sda1 on /boot type ext2 (rw) /dev/sda7 on /home/local2 type ext3 (rw) /dev/sda6 on /usr type ext3 (rw) shmfs on /dev/shm type shm (rw) usbdevfs on /proc/bus/usb type usbdevfs (rw) masala:~ # cat /proc/mounts rootfs / rootfs rw 0 0 /dev/root / ext2 rw 0 0 proc /proc proc rw 0 0 devpts /dev/pts devpts rw 0 0 /dev/sda1 /boot ext2 rw 0 0 /dev/sda7 /home/local2 ext3 rw 0 0 /dev/sda6 /usr ext3 rw 0 0 shmfs /dev/shm shm rw 0 0 usbdevfs /proc/bus/usb usbdevfs rw 0 0 masala:~ # So your root filesystem is not ext3 anymore. It is ext2. Mark On Tue, 8 Apr 2003, Ralf Farke wrote:

Thanks a lot for this hint,

i had the same bootproblems (kernel panic) like the other's with a dual-pentium system and vortex scsi-raid. Just changing jbd - ext3 and the systems works fine again.

Thanks again to all,

Ralf Farke

Dirk Mueller schrieb:

...

On Mon, 31 Mär 2003, Stefan Proels wrote:

...

Root-Filesystem is ext3 INITRD_MODULES="aic7xxx usbcore jbd ext3"

swap ext3 and jbd

------------------------------------------------------------ Dr Mark O. Stitson, Senior Systems Programmer Yospace: Creating Value for Wireless 7 The Courtyard, High Street, Staines, UK, TW18 4DR Tel: +44 1784 466388 Fax: +44 1784 466387 http://www.yospace.com This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorised dissemination or copying of this email or its attachments, and any use or disclosure of any information contained in them, is strictly prohibited and may be illegal. If you have received the email in error please notify contracts@yospace.com and delete it from your system.

On 8 Apr 2003 at 13:54, Marc Wiesenhütter wrote:

Hi List,

well, this didn't work for me. I'm using SuSE 8.0 dual athlon 1GB ram. I installed the downloaded k_smp-2.4.18-243.i386.rpm kernel and proceeded like told in the announcement. rebootet, kernel panic. /etc/sysconfig/kernel: INITRD_MODULES="jbd ext3" new one: INITRD_MODULES="swap ext3 jbd" didn't change anything, so rechanged to

You were not told to write "swap ext3 jbd' into initrd but (from your old entry INITRD_MODULES="jbd ext3") just write INITRD_MODULES=" ext3 jbd". And don't forget to start lilo after that!

the old one. what helped was changing my lilo.conf to append = "noinitrd" what i'm wondering about is, mount shows me, all my partitions are mounted ext3 as it want them, but i thought noinitrd would change them to be mounted ext2. so, is there any problem changing my lilo.conf that way and what should i know? or did i miss any discussion? thanks and sorry if it's just stupid.

My explanation: If you do not use initrd that means: during bootup your root- filesystem can only be mounted with a filesystem type for which the support is in the kernel. That's ext2. You can boot, because it is possible to mount ext3 as ext2. Later (when the mount of the filesystems is done) the /etc/fstab ist there and also /lib/modules is available. So the ext3 module can be found and ... here we are. A problem might be that after a crash there will be _no_ journal recovery from your "journaled" root-filesystem (ext2 does not suppport journaling). You only have the "normal" fsck. So if you really need the benefits of a journaling filesystem for your root-filesystem you need to have the module loaded during startup! Andreas

Hi, this helped, thanks a lot for this hint and for the others, too! I couldn't reboot the computer before today because we had a project with a lot people working on it all time. thanks again. Marc Christoph Illnar wrote:

hi list,

may be of interest to you as since yesterday there is a new aaa_base online for updates of 8.0

File-Description: Fixes mk_initrd which created a broken initrd if ext3 is used as root filesystem together with newer kernels.

regards Christoph Illnar

...

-----Ursprungliche Nachricht----- Von: Mark O. Stitson [mailto:mark@yospace.com] Gesendet: Montag, 31. Marz 2003 16:46 An: Stefan Proels Cc: suse-security@suse.com Betreff: Re: [suse-security] Kernel Panic after Security Update

We have a SuSE 8.0 running on an Athlon system with a Symbios SCSI controller and the root filesystem on an ext3 partition and received the same error.

I have now compiled the patched kernel from scratch and it seems the kernel tries to mount the root file system before kjournald and ext3 is available, so it defaults to mounting it as ext2 instead. SCSI and ext3 are statically compiled into the kernel, so I am at a loss what is going wrong. Now I avoid the kernel panic, but my root filesystem is ext2.

Mark

On Mon, 31 Mar 2003, Stefan Proels wrote:

...

Hello,

after installing the latest kernel update for the ptrace

security issue on

...

a SuSE 8.0 system, the new kernels panics while booting with the message "VFS: unable to mount root fs". My possibilities to analyze this problem are very limited since the system in question is an important 24x7 production system to which I only have remote access and when the system fails to boot this can only be fixed with the help of a local engineer. This is why I'm asking this list if anyone has experienced this problem before and possibly even has a solution for it. As a note, the

new kernel

...

works fine on two SuSE 7.1 systems.

Some information on the system:

SuSE 8.0, SuSE SMP Kernel 2.4.18-64GB-SMP for 2 P-III CPUs, 1 GB RAM, 2 SCSI drives with Adaptec SCSI controller.

Root-Filesystem is ext3 INITRD_MODULES="aic7xxx usbcore jbd ext3" Bootloader lilo

mk_initrd und lilo after installation of the new kernel ran without any error messages.

After re-installing the old SuSE 2.4.18 Kernel with the

security leak the

...

systems boots up fine again.

Thanks in advance Stefan

-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here

------------------------------------------------------------ Dr Mark O. Stitson, Senior Systems Programmer Yospace: Creating Value for Wireless 7 The Courtyard, High Street, Staines, UK, TW18 4DR Tel: +44 1784 466388 Fax: +44 1784 466387 http://www.yospace.com

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorised dissemination or copying of this email or its attachments, and any use or disclosure of any information contained in them, is strictly prohibited and may be illegal. If you have received the email in error please notify contracts@yospace.com and delete it from your system.

-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here