Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Ok so here is the scoop. And just to let you know I am new at Linux, but no time is like the present to learn! Anyways so here is my problem. During the booting process, i get the following error message:
----------------------------------------------
Checking Root File System
iLABEL=/:
The superblock could not be read or or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock
e2fsck -b 8193 <device>
fsck.ext3: No such file or directory while trying to open iLABEL=/
***An error ocurred during the file system check.
-------------------------------------------------
It then allows me to either login with root password and try and fix the filesystem or reboot with Cntr-D. I've searched these forums and others for things like this and haven't found anything exactly like this. The other cases that are similar are solved by using fsck with various parameters. None of this seemed to help my case. Just talking to one of my friends, he said that it might just be taht the partition tables have been corrupted or not able to be read or something along those lines. ANyways, i'm at a loss for what to do, any help would be greatly appreciated. Thanks for your help!
thats actually what i'm trying to keep from having to do if at all possible, but i'll give it another day. I spent a day searching for the answer myself, and now i'll spend a day to see if others can help me
UPDATE:
Even though i didn't really get much help from here, i figured i would at least update considering i fixed it. Who knows, someone else may have this problem down the line.
It turned out that while editing /etc/fstab i had accidently placed an 'i' in front of 'LABEL=/'. This cause quite a considerable problem. The way i fixed was to boot from a rescue cd (such as the rh9 installation cd) and mounted my linux partition and edited fstab with a text editor to remove that 'i'. Anyways, thanks for at least look at my problem, and hopefully this might help someone down the line.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.