Upon booting error message about bad superblock on ext2 device
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!
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.
Upon booting error message about bad superblock on ext2 device
It tells me to either run e2fsck, which didn't seem to help, or use a diff superblock address. I tried e2fsck -b 8193 (I think this is the example number they gave me) but didn't help.
What causes this error and what can be done to fix it?
I tried e2fsck /dev/hda8 without options. Also tried e2fsck -b -31987 (the number was somewhere around this) which is I believe to restore a backup superblock for a filestystem whose blocks are 4096 (again not exact number). I'm not too sure what a superblock is, but upon reboot I get the same message.
I realize under /etc/fstab I have my root as /dev/hda10 instead of /dev/hda8. I tried editing by typing vi /etc/fstab, but It says no such session, or something like that.
I am not exactly sure what is going on. It is hard unless I can see the errors you are getting when you run fsck. I don't know if the fstab would affect it, but that is possible.
I am 99% sure fstab is the problem, because fsck is trying to run on a partition that isn't there. The only problem I have now is trying to edit it, do you know why it's saying "no such session" or something along those lines when I try and edit it in vi?
Have you defined $term? Vi has trouble opening without it... define it to something like cons25 (which is pretty generic). If that still doesn't work maybe `ed` will but that requires real good knowledge about that editor and unless you have used it it will just confuse you.
One of my favorite comments about the editor is that it, "Let's you know you made a mistake with the very explainatory '?' error. Based on the error you made you should know what to do to fix it." ;-) Not really user friendly. But that is what the command mode of vi is based on. Anyway, try defining term... or maybe it can't find /etc/fstab ???
I tried defining $term, but wasn't too sure of the syntax so tried ed. I couldn't even use this, it was saying it was a read only file system. I scrolled up to where I get the error message and it said I'm on /dev/console, which would explain why I couldn't write or why certain applications weren't available. I ran Knoppix and edited my /etc/fstab from there. All is well, thanks for the help.
Good to know all went well... even if I didn't have anything to do with it. :-) At least I gave it a shot. Yeah, I forgot that it would have to be r/o if it wasn't clean...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.