SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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?
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.
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)
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.
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.
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
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.
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!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.