LinuxQuestions.org
Help answer threads with 0 replies.
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 01-20-2008, 05:34 PM   #1
oddo
Member
 
Registered: Sep 2003
Location: Bucharest
Distribution: Slackware *.*
Posts: 34

Rep: Reputation: 15
Unhappy Update from Slack 10 to 12 failed


I had to update a Slackware 10.0 full install to Slackware 12.

First thing - I have comiled and succesfully installed 2.6.23.14 - rebooted - everything was fine on Slack 10 with 2.6 kernel.

Then i copyed files from slack 12 DVD on my harddisk - telinit 1 and followed steps from changes_and_hints. In the last step I have updated only rc.M and inittab.

After reboot - I got :

/sbin/e2fsck : No such file or directory while trying to open /dev/hda1 ( this is my / partition )
then

after I logint to sstem maintenance ;

/dev/hda1:
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem ( and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:

Did that with all 3 values - same result as above.

Rebooted from CD - I run e2fsck on /dev/hda1 - everything is fine ( once it told me that superblock was modified in the future- and answered yes to fix )

I can see all the files in place...but this machine doesn't boot..

On this console
fdisk /dev/hda gives "unable to open /dev/hda" but I can mount rw /dev/hda1....

Any idea ?

Last edited by oddo; 01-20-2008 at 05:50 PM.
 
Old 01-20-2008, 06:32 PM   #2
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,633

Rep: Reputation: 450Reputation: 450Reputation: 450Reputation: 450Reputation: 450
there's a lot of changes between 10 and 12.0
you should have look over the .new files all over /etc and tried to merge it with the current configuration files

btw, have you installed udev?
 
Old 01-20-2008, 06:41 PM   #3
oddo
Member
 
Registered: Sep 2003
Location: Bucharest
Distribution: Slackware *.*
Posts: 34

Original Poster
Rep: Reputation: 15
yes udev-111-i486-5

It's weird because I get correct results from fsdisk when booting from cd , and nothing when I boot from HDD. Also if I boot with hugesmp kernel from cd and root on /dev/hda1 it doesn't work...

I got an error from udev at line 47 :
/sbin/udevstart: No such file or directory

Last edited by oddo; 01-20-2008 at 06:57 PM.
 
Old 01-20-2008, 07:11 PM   #4
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 1,808

Rep: Reputation: 234Reputation: 234Reputation: 234
Willysr is right.

You probably need to replace some of your old config files with the ".new" ones. Especially the ones under /etc/rc.d.

Also, it probably would've been better to run a fresh installation instead of upgrading...
 
Old 01-20-2008, 07:12 PM   #5
oddo
Member
 
Registered: Sep 2003
Location: Bucharest
Distribution: Slackware *.*
Posts: 34

Original Poster
Rep: Reputation: 15
I'm a stupid cow...Thanks for the hint willysr - indeed the problem lied in old /etc/rc.d/rc.udev. Updated with right version - all in place..I should have RTFM till the end.

Thanks again
 
Old 01-21-2008, 09:30 AM   #6
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,633

Rep: Reputation: 450Reputation: 450Reputation: 450Reputation: 450Reputation: 450
check the other files as well
i find this command works on mine
Code:
find /etc -name "*.new"
there's some exception though, for example /etc/passwd, /etc/group and /etc/shadow (you might want to leave it or look through diff to find the difference)
 
Old 01-21-2008, 02:56 PM   #7
oddo
Member
 
Registered: Sep 2003
Location: Bucharest
Distribution: Slackware *.*
Posts: 34

Original Poster
Rep: Reputation: 15
If I exclude the fact that I haven't taken care of .new files everything went smoothly. I had a little problem with upgrading to mysql 5 ( a matter of permissions on /var/lib/mysql* ) but fixed quickly. So in my case upgrade from 10 to 12 worked well. Anyway I guess reistall could reduce the amount of time.
 
  


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
Latest Suse "YOU" update....Linux Kernel Update Failed Balarabay1 Suse/Novell 10 06-11-2006 10:07 PM
yum update failed piforever Linux - Security 2 12-26-2005 10:06 PM
yum update failed piforever Fedora 6 12-25-2005 12:48 AM
RPM update failed? lucky_luuk Fedora 2 11-04-2005 07:31 AM
Failed system update blindcyde Fedora 2 04-22-2004 04:50 AM


All times are GMT -5. The time now is 02:35 PM.

Main Menu
Advertisement
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