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.
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?
Sorry, I forgot. I'm using the sata.i kernel supplied with the Slackware CD. It has support for both ext3 and SATA so that's not the problem. Any more suggestions?
did you try the boot flag on the linux partition like you said ?
Where did you choose to install LILO during installation ?
Do you intend for LILO to be your bootloader for windows and linux ?
Yes, I tried the boot flag, but it doesn't work. I installed LILO with lilo -M /dev/sda. And yes, I intend LILO to be my bootloader for both Windows and Linux.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.