Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I was attempting to access the level editor in supertux when my system halted. I then re-booted and my filesystem got a little screwed up. so I ran e2fsck and got the following error:
The superblock could not be read or does not describe a correct ext2filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblockis corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
so duh, it doesnt appear as ext2 because I am running ext3 on Mandriva 2007.0. so how can I route it to ext3 if its even possible?
Yes, a journal. That is an advanced technique for keeping track of any changes that were made to the file system, on purpose or by accident. It makes things easier (and faster) when you're trying to recover after a power failure or similar incidents.
No need to add a journal. ext3 already has one, by definition.
The real cause of your issue is a damaged superblock. A superblock, btw, is a place that stores information about the file system as a whole. When it gets damaged, the system can't any longer read from the file system so it produces the sort of error message that you received .
Such damage can be extremely tricky but quite often it is possible to recover by having the system read one of the backups of the superblock, which are located all over the file system at 8192 block intervals. That is the whole point of the suggestion made by the system:
e2fsck -b 8193 <device>
i.e. read the backup located 8192 blocks from the (presumably damaged) original superblock. In order to recover from the damage, you'll have to boot up and issue the that command when the system requests it, replacing <device> with the proper reference (e.g. /dev/hda1 if we're talking about the first partition on an IDE disc). If you prefer a command that targets ext3 more specifically, you could use
e3fsck -b 8193 <device>
but as I said, it doesn't make all that much of a difference.
If you had a liveCD, that would even be better. You would then boot off that cd and run the fsck command from there.