Persisting problems when updating to new 2.4.18 kernel on SuSE 7.3
Hi, yesterday I also spent some hours on that kernel issue. Now I tried the workaround swapping the ext3/jdb order in INITRD_MODULES. After reenabling ext3 for the root filesystem, my system actually boots again. It also reports that / is mounted as ext3 (according to the "mount" output). But there is still a warning during startup, because / acually seems to be still ext2. And after intentionally hard-resetting the system it did not replay the journal, it just ran the lengthy fsck... Any (further) ideas? Thanks, Jan
Jan Kiszka wrote:
Hi,
yesterday I also spent some hours on that kernel issue. Now I tried the workaround swapping the ext3/jdb order in INITRD_MODULES. After reenabling ext3 for the root filesystem, my system actually boots again. It also reports that / is mounted as ext3 (according to the "mount" output). But there is still a warning during startup, because / acually seems to be still ext2. And after intentionally hard-resetting the system it did not replay the journal, it just ran the lengthy fsck...
Any (further) ideas?
Thats already known @SuSE. afaik they work on it. I have the same problem here, so you're not alone :) Regards, Sven
participants (2)
-
Jan Kiszka
-
Sven 'Darkman' Michels