SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hi. I just installed Slackware 10.2 on my brand new SATA disk. Everything went smoothly, until I tried to boot into Slackware. During startup, e2fsck says bad superblock or superblock does not contain ext2 filesystem. I'm using ext3. And when I manually run e2fsck /dev/sda9 (my root device) it says the device is clean. Can anyone help me?
Root device on an extended partition? That can't be good. I'm not positive, but it sounds kind of dicey. I would stick to a primary for your root partition. (maybe someone can back this up, or refute it)
To narrow the problem down a bit, which kernel did you install, and how did you set up your partition table? Did you use the one in the Slackware installer, or a 3rd party utility?
Well, I set up the Linux partition using cfdisk. Ok, here's a complete picture of my hard disk organisation. I have one hard disk on hdc. My SATA disk is on sda. I have 4 partitions on my SATA disk. On the primary partition, I've installed Windows XP. On the first logical partition of my extended partition, I've installed Linux. What you say strikes true. Would setting the boot flag on my Linux parition solve the problem?
Well, I don't think that is actually what's causing your problem.
You still didn't say what kernel you're using. Do you have compiled in support for your root file system (ext3 in your case) as well as the hard disk type (SATA disk support)? If not, are you using an initrd to load the modules?
I'm afraid I can't since I deleted my Linux partition to see if reinstalling would do any good. I'll post them if this still doesn't solve the problem. One thing you people should know that might have a bearing on this is that I'm installing Linux on a Logical Partition. I have only one Primary Partition that contains Windows. All of the others are Logical Partitions.