The long thread on 'kernel 23mdk panic' seems to be related to my problem. Has anyone made a summary of conclusions made so far? Which kernels are known to boot properly, with and without initrd?
On Tue, 2003-11-04 at 00:06, Svante Signell wrote: > Hi, > > I have been following the cooker development on and off for some years > now, and have not had any problems with the root partition as ext3 until > around half a year ago. The boot message displayed is: > > EXT2-fs warning (device ide0(3,65)): ext2_read_super: mounting ext3 > filesystem as ext2 > > This happens with e.g. kernels 2.4.18,2.4.20 and 2.4.22. Also, with an > initrd RAM disk no kernels boot at all, the boot halt with a kernel > panic, so I have to use the noinitrd option. The master boot record is > located on another physical disk (/dev/hda), and I'm using lilo as boot > loader. > > Checking the state with tune2fs -l /deb/hdb1 after boot shows that the > filesystem state is not clean. However, booting from a CD and mounting > the root partition either as ext3 or ext2, all is OK, the filesystem > state is OK. I did even remove all journal file information, checked the > partition, created a new journal file (and even tried the features > filetype, sparse_super), rechecked again, but same result as before :( > > What's going on here? > >
