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.
You're right, it isn't a terminal window. It's a terminal.
What filesystem did you use at install time? Was it ext2 or ext3? As far as I understand it, you will never see that error with ReiserFS.
in any event, what you need to do is run e2fsck or e3fsck (depending on your filesystem) on /dev/hda1. Usually, you're supposed to do this without it being mounted, so you might want to boot off the install disc and do it from there.
You could also try the windows fix: reboot and see if the problem is still there.
fsck -t ext3 /dev/hda1
The filesystem size according to the superblock is 14651279 blocks
The physical size of the device is 12048749 blocks
Either the superblock or the partition table is likely to be corupt!
Hmm... yeah, I'd abort at that point. Looks like your partition table is borked. If you had a windows bootdisk, I'd suggest running "fdisk /mbr", but unfortunately I don't think the unix version of fdisk supports that.
I know you can do the same with "lilo -m", but I'm not 100% sure it'll fix the problem. Doesn't hurt to try.
You might also try loading up cfdisk and then writing the partition table and quitting. That might also solve the problem.
Anti-virus control is turned off in the BIOS, right? If it's on, it can screw up c/fdisk and prevent them from being able to write the partition table.
Failing that, since you've just installed the system, you can also use cfdisk from the install CD to wipe out the partitions again, and reinstall. If you go that route, I'd suggest 10gb for /, 512mb for swap, and the rest of the hard drive for /home. cfdisk has a graphical user interface which can make the creation/deletion of partitions pretty easy. As much as I loathe the "Windows" solution, that might actually be your best bet.