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.
Distribution: Ubuntu, Slack, Athena Linux (derivative of RedHat)
Posts: 35
Rep:
Oh where, oh where, did /etc/fstab go?
I installed Slackware 9.1, spent an hour and a half trying to get WinME to reboot in DOS (I'm setting up a dual-boot system), finally got loadlin and my boot menu to work together, and tried to use it to boot into Slackware. Unfortunately, /etc/fstab seems to be missing, giving me a screenful of various error messages; I think they're all probably caused by this (please see below.)
Warning: couldn't open /etc/fstab: No such file or directory
/sbin/e2fsck: Is a directory while trying to open /
The superblock coule not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext3 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>
(then a nice frame of askeriske surrounding the following error message)
An error occurred during the root filesystem check. You will noe be given a chance to log into the system in single-user more to fix the problem. If you are using the ext2 filesystem, running e2fsck -v -y <partition> might help.
IIRC (I would check, but I don't know how from outside Linux!), my disk is partitioned into /dev/hda1 (Windows), /dev/hda2 (extended), /dev/hda5 (swap), and /dev/hda6 (/).
What might have caused this, and how can I fix it? Thank you!
This might have caused due to the improper shutting down of the pc... using the reset button... which is the common case with with windows... but with linux if u do not shutdown the system properly these kind of messages would be quiete common.... so do shutdown the system using poweroff or shutdown -h now....
to solve the problem regarding the /etc/fstab it is that u should get a copy of fstab file and edit the file according to your configurations... if u want i can send a copy of the fstab file....
Distribution: Ubuntu, Slack, Athena Linux (derivative of RedHat)
Posts: 35
Original Poster
Rep:
Thank you, I would appreciate that greatly. Or perhaps you could post it here, so that others can refer to it if they run into the same problem?
So once I edit it, save it to a floppy...what do I do? I'm thinking that I should probably boot from the CD and
mv /dev/fd0/fstab /etc/fstab
...would that work?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.