Hello, today I blew away my Slack 9.0 system leaving only my /home partition in tact and installed 9.1 and I had everything was working okay.

Me being me I had to upgrade to 2.6.1, I compiled it using the 2.4.xx instructions on this site... WHOOPS!

Basically I don't think there's anyway to bring back to life my 2.6.1 but I should still be able to boot my 2.4.22 kernel as I renamed the old vmlinuz file and System.map to vmlinuz.old and System.map.old and in lilo.conf I put:

Image = /boot/vmlinuz.old
root = /dev/hda7
label = Slack.old
read-only

However when I try to boot it it complains about a bad ex2fs superblock in /dev/hda7 and asks for root pass to do maintenance or ^D to carry on, no matter what I do the system then reboots.

The thing is /dev/hda7 is reiserfs, not ex2fs and running resierfsck on it from knoppix works fine and it doesn't produce any errors... does anyone have any ideas as to what could be causing this? I need to be able to boot this kernel so I can recompile 2.6.1 the right way.

Thanks in advance,
BongFish

Uh, does /etc/fstab reflect the fact that /dev/hda7 is a reiserfs??
If you bought the Slack CD-set, if comes with an emergency bootable disk,
so you can fix things like this...........

Yeah try somehow to boot into linux without mount /dev/hda7, either with rescue disk or install disk/CD. Don't mount /dev/hda7 (safer), and do :

e2fsck -v -y /dev/hda7

That "-y" option answer yes to every question of e2fsck for repairing any corrupt block ..
"-v" is for verbose, and it should be better to run e2fsck on any partition without that it is mounted (safer), reboot ..

Okay, in rc.S (I think this was the startup file that was doing this) I changed fsck which was auto detecting wrong to fsck.reiserfs and it now works fine.

I've not checked my fstab but it could well have the wrong FS type in it because it's the fstab I kept from my old slack system. I'll check later.

Resolved!