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.
Well, I'm confused. The command it is running assumes a partition has been formatted as an "ext4" partition, and then says that it can't find the partition's "ext2" superblock.
No surprise there...
The first thing that I would do is to drop into the maintenance shell and run "less /etc/fstab". Hit "q" to exit less. (if less isn't installed, try "cat /etc/fstab"). See what it says (and post it here).
And as an experiment, I just ran "fsck.ext2 /dev/sda2" (sda2 has my ubuntu 13 on it, and was only installed to help get my next-to-useless Kodak printer working. So no big loss if I hose it).
BTW, running fsck on a mounted drive is a "Very Bad Idea", and shouldn't be done (my sda2 partition wasn't mounted). I intentionally ran the wrong version of fsck.ext? (the "?" being the version number of fsck, in my case, I should have used "4", but I ran fsck.ext2), and it didn't even phase the partition.
Apparently the linux deities are looking out for us mere mortals (BTW, it mounted just fine).
So the upshot of this is that while fsck.ext4 shouldn't be used on a ext2 partition (or vice-versa), it doesn't seem to hurt it either. So post the output of /ect/fstab so we can see what we are working with.
Not sure if this might be related to your problem, but 2.6.28 was the first kernel with ext4, but it did not include full 64 bit support for ext4. I think the unsupported aspects were mostly related to maximum filesystem size and maximum file size, but might be worth looking into.
Is your system a 64-bit machine?
And if you are using a pre-built kernel, it is possible that it was not built with ext4 support because it was a new feature at the time.