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.
I'm new to linux and i'm using Redhat-5 distribution.
when i install redhat from the CDs it works properly for a while,
but thereafter, when i restart or reboot the system it promtes following
error messages and wont bootup.
error message...
"modprobe warning /etc/modprobe.conf line 0 : ignoring bad line
check filesystem
unexpected inconsistency : run fsck manually
kernel panic - not syncing : attempted to kill init"
Do you mean Red Hat Enterprise Linux 5? Plain old Red Hat 5 is old as the hills...
Anyhow, it sounds like a corrupt filesystem. Have you tried booting off a rescue disk and running fsck on the root partition as suggested in the error message? If the filesystem is going bad you should also run badblocks on the drive to see if there are any bad sectors. If the hard drive has S.M.A.R.T. capabilities, you should probably also run smartctl and run some of the self tests.
Do you mean Red Hat Enterprise Linux 5? Plain old Red Hat 5 is old as the hills...
Anyhow, it sounds like a corrupt filesystem. Have you tried booting off a rescue disk and running fsck on the root partition as suggested in the error message?
hi btmiller,
yes i'm working on RHEL-5, of course i tried with rescue mode and i ran fsck, but stil the same...
mean while miller, i didnt found any bad sectors as well.
still i'm unable to figure-out the exact probelm which cause this inconsistency.....
In the e-mail I received there was apparently a star <*> in the beginning of the 1st line.
Is this a glitch or is it real?
If the said star <*> exists, remove it for it could cause effect similar to Yours
--edit--
Nope there isn't a star, it's a glitch for bold-code.
Double check if said module 8139too exist
Last edited by SCerovec; 08-14-2007 at 04:22 AM.
Reason: double check
In the e-mail I received there was apparently a star <*> in the beginning of the 1st line.
Is this a glitch or is it real?
If the said star <*> exists, remove it for it could cause effect similar to Yours
--edit--
Nope there isn't a star, it's a glitch for bold-code.
Double check if said module 8139too exist
ok SCerovec, let me try it and will tell you the deails
soon.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.