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.
Thank you for instant reply! When booting, my Linux just stuck in place where an error occurred during the file system check.
To check file system /dev/hdb2, I use #df to check my file sysytem:
There is no information about /dev/hdb2, I wonder if it is a disk in windows.
I tried e2fsck /dev/hdb2, but the system hinted that :
"Read-Only file system while trying to open /dev/hdb2
Disk write-protected; use the -n option to do a read-only check of the device. "
Then, I tried fsck-n, and the system replied:
"fsck .ext3: No medium found while try to open /dev/hdb2".
The superblock could not be read or does not describe a correct ext2 file system. If the device is valid and it really contains ext2 file system (and not swap or ufs or something else), then the super block is corrupt, and you might try runing e2fsck with an alternate superblock e2fsck-b 8193 <device>"
So I tried e2fsck -b 8193 /dev/hdb2, but it still prompted "read-only file system" information.
Thank you very much! Now I think I find the root of the problem.
I tried fdisk and mount to check the disk information: first disk(for windows) hda1, hda2... normally; second disk displayed hdd1, hdd2, hdd3(swap). Then I checked /etc/fstab as you indicate, I found linux use hdb3 for swap.
Then I use command "chmod 777 /etc/fstab", and it showed that "changing permissions of /etc/fstab: Read-only filesystem". I cannot use vi to change this read-only file.
There might be two ways to solve this problem, one change the identification of second disk from "hdd" to "hdb"; or change the /etc/fstab file which is read-only.
So again I need some more detail suggestions.