Help answer threads with 0 replies.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 01-11-2004, 12:34 PM   #1
Registered: Jun 2003
Location: England
Distribution: Slack 9
Posts: 141

Rep: Reputation: 15
Just upgraded to 2.6.1, all sorts of problems starting up.

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 to vmlinuz.old and and in lilo.conf I put:

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

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,
Old 01-17-2004, 07:11 AM   #2
Senior Member
Registered: Nov 2002
Location: pikes peak
Distribution: Slackware, LFS
Posts: 2,577

Rep: Reputation: 48
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...........
Old 01-17-2004, 07:50 AM   #3
Registered: Jan 2004
Posts: 67

Rep: Reputation: 15
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 ..

Last edited by dirstyGuy; 01-17-2004 at 07:52 AM.
Old 01-17-2004, 09:18 AM   #4
Registered: Jun 2003
Location: England
Distribution: Slack 9
Posts: 141

Original Poster
Rep: Reputation: 15
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.



Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
X11 Forwarding over SSH all sorts of problems lucastic Linux - Networking 10 08-31-2004 08:34 PM
xfree86 upgraded: problems mtb Debian 5 07-22-2004 02:54 PM
Upgraded to Slack 10 without problems. Tips.... Nichole_knc Slackware 7 06-27-2004 08:40 PM
upgraded glib but problems rafc Linux - Newbie 2 05-22-2004 10:11 AM
Problems with upgraded XFree86 packages pmehta1613 Linux - Software 1 11-18-2003 08:51 AM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:13 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration