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.
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.
I certainly know how to make problems that i cant fix. This is the third linux forum i've turned to, as i got no replies on the last one, and the one before was rather inactive. So i hope people here can help me.
I cant start fedora core 5 at all at the moment, it runs through the boot process, enters runlevel 3 and then sits on bringing up eth1, a spare network card which i want to get rid of. So i even tried taking it out, trying to start it again, still sits there, trying to start it, whether the card is even in there, or if there is a network cable in or not. I disabled eth1 before, and would remove it if i could even get in there to take it out completely.
I plugged a cable into which would it start it in init 5, but right now im in init 3, which doesnt just say Failed to start eth1 like 5 does, it just sits there doing nothing, and inittab is set to default 3, as when you type init 3 in root console, it pretty much becomes useless. It stops some things, and sits there doing nothing. So i had to use inittab to get to runlevel 3, to install some drivers.
But now im locked out of fedora essentially, as it wont start.
I know i have to do one of two things:
Disable network on boot/disable eth1
Edit inittab back to 5 in hope that it will start like it did before, and then trash eth1.
I've tried getting into the hard drive using DSL to modify inittab. mounting the hard drive doesnt work, it never has when ive tried in the past, it says you must specify the filesystem (ext2). So i popped open a terminal and tried to mount it. and it says special device hda2 doesnt exist.
I have no idea.
Im sure that just from having Fedora ive cut a year worth of my life just from stress. But oh well.
Last edited by stephen_wq; 09-21-2006 at 12:45 AM.
You can use a kernel parameter to boot into a specific run level. This parameter must be last, and consists of the run level number only. Just edit the kernel line in grub and add a 5 to boot into run level 5.
i'll hunt for failsafe to see if i can somehow stop networking. edit: Cant find it, anyone help in turning off networking?
There's got to be some kernel boot parameter to accomplish this, but I can't tell you what that would be off hand. I'm guessing it's either hanging on the probe for your NIC, or loading some inappropriate driver and then hanging when that driver goes to initialize your card or something. You might check out the Linux Ethernet HowTo:
I think there's something like a "noprobe" boot parameter, but that's probably a bit drastic. That would disable all hardware probing and you'd have to identify your hardware and specify which modules to load manually. Yeuch. I'm not sure if the "noapic" boot parameter would be helpful in your case. I guess it can't get much worse than it is now, so might as well try it if you're desperate.
That explains why you can't mount /dev/hda2 - it's an LVM partition.
What are the contents of your /etc/fstab file?
No idea. Whatever the default Fedora install is, i suppose. I formatted not too long ago.
Tried noapic, did nothing. Noprobe is excessive. I wouldnt know what to do.
edit: Well, after rebooting after noapic, its started. Im in init3 and can get root access.
Now, could anyone give me a command to completely remove eth1?
Last edited by stephen_wq; 09-23-2006 at 07:40 AM.
Oh great, it was working until i removed that file.
It used to say it had a different mac address than expected. Now its sitting there trying to start it again.
But once again, rebooting it after i tried noapic, it fails to start eth1, and ive got terminal access again. Typed init 5 and it started up. Ive removed the network card out of system-config-network and the device too.
Thanks for your help, i still wish i could read it in knoppix though.
Last edited by stephen_wq; 09-23-2006 at 04:42 PM.
The following will work in Knoppix 5 (which includes support for LVM2)
(1) boot Knoppix
(2) open a terminal window
(3) su to root
(4) run "vgscan"
(5) run "vgchange -a y"
(6) run "pvs; vgs; lvs" to see your LVM stuff. Note your specific VG and LV names.
(7) run "mkdir /mnt/tmp"
(8) run "mount /dev/vg0/usr /mnt/tmp"
(adjust the above command based on your specific VG and LV names and the filesystem you want access to)
(9) access your mounted stuff on /mnt/tmp
If you do not have Knoppix 5, and are using older version 4, you will need to install LVM2 manually first (before doing the above). Here's how:
(1) boot Knoppix
(2) open a terminal window
(3) su to root
(4) modprobe dm-mod
(5) apt-get update
(6) apt-get install lvm-common lvm2
(7) lndir /lib/lvm-200/ /usr/sbin/
(8) procede to step (4) (the "vgscan" step) up in the first listing