• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Issues with Debian 3.1 upgrades

C

Crashsector

[H]ard|Gawd
Joined
Jul 10, 2001
Messages
1,125
Hey everyone. I have installed Debian 3.1 on my IBM T41 and it works relatively well. However, when I edit my sources.list and include the testing distribution, and run an 'apt-get dist-upgrade', the kernel panics on a reboot saying something about the superblock being written in the future.

I have run fsck and e2fsck several times and neither of these seem to help.

FWIW, I'm running the testing release on a server at my house so I'm pretty sure it's not a bug. Also, when Grub comes up (I'm dual-booting with Linux) it still shows the 2.4 kernel in the selection, not the 2.6 that should be used.

Any idea where I can start troubleshooting this? Thanks!
 
I don't think it's a problem with the apt-sources - everything downloads, unpacks, and installs just fine when i do the dist-upgrade. It's when I restart that I get the error about the superblock being written in the future.

Any idea?
 
I'd check the BIOS date and time. If they're saved wrong, then it could read the superblock and see a time that appears to be in the future. Set it forward a couple of years, reboot, set the date under Linux properly, and reboot and change it back, and that may fix it. Maybe ;)

 
unhappy_mage said:
I'd check the BIOS date and time. If they're saved wrong, then it could read the superblock and see a time that appears to be in the future. Set it forward a couple of years, reboot, set the date under Linux properly, and reboot and change it back, and that may fix it. Maybe ;)

Click to expand...

hi2u :) I'll try that when I get home. Thanks!
 
So that didn't seem to do much. But here's a question... if I've upgraded to a 2.6 kernel, should my grub entry still be pointing to a 2.4 boot image?

There's something fishy about this because when I install the system for the first time everything works great, but I get these errors after I reboot.
 
You have to be using the 2.6 kernel to be running 2.6. Try "uname -r" to see what's actually being used. In all likelihood, you haven't changed it over yet.

Make sure you've got the drivers for the filesystem you're using built into the kernel (not as modules). If it weren't built in, it could give weird errors.

 
It sounds to me like apt-get should have taken care of this stuff... lemme see what I come up with.
 
OK, so from what I can tell it looks like the system itself has been updated but it is still trying to use the 2.4 kernel. How can I tell the system to use the 2.6 kernel? For what it's worth, I can't find a 2.6 image on the system (at least not in /boot). Is it hiding somewhere or is there something really simple I'm missing?
 
My suggestion is that you build your own kernel. It's a learning experience, and not really applicable to other linux-ish things, but still good to know how to do. Grab one from kernel.org - 2.6.14.5 is the latest and should be fine. Click on the "F" to the right to get the "full" thing rather than a patch from an earlier version. Run "tar jxvf linux-2.6.14.5.tar.bz2", "cd linux-2.6.14.5", and then get a starting point. There's probably one in /boot (on my Debian box there's config-2.4.27-2-386), or in /proc/config.gz; copy (or gzip -d) it to .config (yeah, there's a dot in front). Then run "make oldconfig" to bring it up to date - new drivers and such will be enabled or disabled. Then "make menuconfig" or "make xconfig"; go through and make sure that all the hardware that's important is turned on. Build everything directly into the kernel; modules are nice for some things, but for now it's simpler to deal with the kernel as a chunk. When you've got what you need, run "make bzImage modules", and then as root, "make modules_install". To install the kernel image, "cp arch/i386/boot/bzImage /boot/newbzImage" and then edit the grub config files to point to that in addition. Reboot and hope. If it doesn't work, let me know what the error message is; I've managed to generate a lot of them over the years :rolleyes:

PS: I'm on msn.

 
You must log in or register to reply here.
Back
Top