LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 12-13-2008, 09:12 PM   #1
Andersen
Member
 
Registered: Dec 2008
Distribution: Slackware
Posts: 89

Rep: Reputation: 35
Problem after upgrading to 12.2


First, sorry for my bad English, I hope you will understand at least part of this post
Thing is, after upgrading from SW 12.1 to SW 12.2 and rebooting, I've got a problem I can't solve. System starts booting, and then when he gets to the point when it usually checks the root filesystem, only thing I get is ugly error message that informs me e2fsck can't find the superblock, and booting stops. It wont see /dev/hda2 (swap partition), and /dev/hda3 (root partition). Kernel I used with 12.1 was huge.smp, no initrd, and I didnt made any changes after upgrading, so I think it should use huge.smp again.. or I am wrong. Anyway, vmlinuz shortcut points to smp-huge-2.6.27.7-smp.
Anybody had the same problem, or maybe just knows what is going on?
 
Old 12-13-2008, 10:47 PM   #2
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,441

Rep: Reputation: 70
Did you rerun lilo after your upgrade?
 
Old 12-14-2008, 12:10 AM   #3
Andersen
Member
 
Registered: Dec 2008
Distribution: Slackware
Posts: 89

Original Poster
Rep: Reputation: 35
Yep, all "by book" or by "UPGRADE.TXT", but..
I fixed the problem, I was too nervous to wait, so I just did a clean install, and everything is ok now. This was a first (and a very last) time for me to do an upgrade, best way to skip problems is clean install.
However, I still don't know what was the problem there.
 
Old 12-14-2008, 02:37 AM   #4
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,913

Rep: Reputation: Disabled
Are you *sure* you completely followed UPGRADE.TXT?
This sounds like you forgot to do this step:
mv /etc/rc.d/rc.udev.new /etc/rc.d/rc.udev
(along with moving/merging all the other .new files)
 
1 members found this post helpful.
Old 12-14-2008, 03:09 AM   #5
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,441

Rep: Reputation: 70
On some machines a simple kernel parameter can make hdd that were /dev/hda look like /dev/sda instead. You could have had some disk corruption or perhaps other numerous causes for your problem.

I just posted a new Upgrade Howto for this release. Even though you did a fresh install you might want to check it out.

edit:
Just saw this:
Quote:
Originally Posted by rworkman View Post
Are you *sure* you completely followed UPGRADE.TXT?
This sounds like you forgot to do this step:
mv /etc/rc.d/rc.udev.new /etc/rc.d/rc.udev
(along with moving/merging all the other .new files)
That probably was your issue

Last edited by shadowsnipes; 12-14-2008 at 03:22 AM.
 
1 members found this post helpful.
Old 12-14-2008, 07:00 AM   #6
Andersen
Member
 
Registered: Dec 2008
Distribution: Slackware
Posts: 89

Original Poster
Rep: Reputation: 35
Quote:
Originally Posted by rworkman View Post
Are you *sure* you completely followed UPGRADE.TXT?
This sounds like you forgot to do this step:
mv /etc/rc.d/rc.udev.new /etc/rc.d/rc.udev
(along with moving/merging all the other .new files)
Quote:
Originally Posted by shadowsnipes View Post
On some machines a simple kernel parameter can make hdd that were /dev/hda look like /dev/sda instead. You could have had some disk corruption or perhaps other numerous causes for your problem.

I just posted a new Upgrade Howto for this release. Even though you did a fresh install you might want to check it out.

edit:
Just saw this:

That probably was your issue

Yes, probably it was, as I can remember, I've fixed *some* .new config files, but I don't remember I did it with the udev configuration file.
My mistake. Thanx for answers guys!
 
Old 12-14-2008, 02:08 PM   #7
gegechris99
Member
 
Registered: Oct 2005
Location: France
Distribution: Slackware 14.1 64bit
Posts: 728
Blog Entries: 3

Rep: Reputation: 77
Hello Andersen,

Run the following command to check any remaining *.new configuration file:

Code:
find /etc -name *.new
 
1 members found this post helpful.
  


Reply


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
problem when upgrading to FC7 LuggerHouse Linux - Software 2 01-07-2008 07:26 PM
Problem with upgrading from 5.04 to 5.10 kuusma Ubuntu 3 06-02-2006 05:32 PM
Problem upgrading to 2.6.7 Corallis Slackware 3 07-05-2004 06:49 PM
alsa upgrading problem Nadim Slackware 2 05-17-2004 09:20 AM
problem upgrading kernel TravisB Linux - Software 9 03-20-2002 02:48 PM


All times are GMT -5. The time now is 08:01 PM.

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