idea-cipher problems during upgrade 2.4.5 -> 2.4.13

idea-cipher problems during upgrade 2.4.5 -> 2.4.13

Post by Space Tu » Thu, 01 Nov 2001 20:52:00

Hi all,

I've compiled kernel 2.4.13 with the international patch,had to make
some changes to Makefile by hand, but no problems with that, and now,
with booting 2.4.13, I'm having problems with mounting my idea-ciphered
harddiskpartition through loop0.

The sizes of the modules used for ciphering differ from 2.4.5 and 2.4.13,
but I use the same international patch. I can imagine that's because of
the kernel.

Any (cipher)idea? ;)

PS. I Don't really Feel like decrypring the whole hd under 2.4.5 and
encrypting again under 2.4.13, as you can imagine! :)


1. Upgrading kernel 2.4.9 -> 2.4.13 causes ex2fsck-problems.

Hi folks,

I upgraded my kernel source from 2.4.9 to 2.4.13 and got some problems with

I have one IDE hard disk divided as follows:
/dev/hda1 -> ext2, mounted to /boot
/dev/hda2 -> swap
/dev/hda3 -> reiserfs, mounted to /

With 2.4.9 kernel everything works nicely, like you see here:
------------(from dmesg)----------
Partition check:
 hda: hda1 hda2 hda3
reiserfs: using 3.5.x disk format
ReiserFS version 3.6.25
VFS: Mounted root (reiserfs filesystem) readonly.
and so on.

When I compiled 2.4.13, I also upgraded the reiserfs progs into the latest
version, 3.x.0j, that was available on

After installing 2.4.13 kernel, I get this on boot:
<---------------------reiserfsck, 2001--------------------------->
reiserfsprogs 3.x.0j
fsck.ext2: No such file or directory while trying to open /dev/hda1
The superblock could not be read or does not describe a correct ext2
If the device is valid and it really contains an ext2 filesystem (and not
or ufs or something else), then the superblock is corrupt, and you might try
running e2fsck wuith an alternatte superblock
    e2fsck -b 8192 <device>

fsck.ext2 /dev/had1 failed ([status 8]! Fun it manually!
Loading keymap....

fsck failed. Please repair manually and reboot. The root file system
is currently mounted read-only. To remount it read-write do:

mount -n -o remount,rw /
--------------(sorry about typos, I typed this manually from screen)

Then I changed back into 2.4.9 and everything works nicely again. I tried
that first without upgrading the reiserfsprogs with the same result and I
thought that it might have been the problem, but upgrading them didn't help,
as you can see above.

So, why does upgrading kernel to 2.4.13 cause these problems? I can't
understand why the filesystem would be corrupt with 2.4.13 when it works
just fine with 2.4.9.

Any ideas?

- Petri

PS. My distribution is otherwise quite basic SuSE 7.2, except for the kernel
and reiserfsprogs upgrades.

2. Propagandist Chad Myers Lies About Linux 150 Times

3. Trying to upgrade to Linux kernel 2.4.13

4. Help !!

5. Deadlock in kernel > 2.4.13-pre6

6. Cannot find quota.conf file?! help!

7. Heavy IO in 2.4.13-ac4 with preempt patch -> kupdated hogs system

8. DAT Transfer

9. Deadlock on kernels > 2.4.13-pre6

10. Disk light on full time with kernels => 2.4.13

11. Problems with 2.4.13, kt133a, and IBM DLTA drives

12. Tulip driver problem with 2.4.13-ac8

13. Google's mm problem - not reproduced on 2.4.13