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.
I replaced the battery on the mother board and now I can only boot with a knoppix livecd!
When I try to boot normally, the system goes through the POST but instead of the grub splash screen, it displays the word "grub _" followed by an underscore.
Background: Very stable, Pentium 3, linux (2.6.8-1) All the linux installation files are on a separate harddisk - hda. It has a software raid raid1(md0) consisting of 2 mirrored scsi hard drives (sda1 and sdb1).
More background: Last week I had a "kernel panic loop 1" message and a bunch of icmpv6 errors which locked up the system console and all the pc's that used the samba share. I managed to quell the icmp problem by restarting networking services. Not sure what kernel panic means. I thought maybe it was related to the icmp errors. It worked another week until I lost a samba share again. Restarted samba and the console locked. Had to ssh into the pc to shutdown / restart. On restart, pc says that md0 has a bad superblock and hangs waiting for me to do something with the superblocks. I don't know how to run e2fsck thought I'd just try at minimum to get the pc up since it handles samba for the network. I wanted to fix the raid later...when I have time to research it.
So... I went into fstab and changed columes 5 & 6 of md0 from 1 2 to 0 0 respectively. I did this so as to get around the superblock message. That notion worked and was able to restore all the services.
I have to power off in order to move the pc back into production and thought I'd take the opportunity to vacuum and reseated all the cables, memory sticks. After that boot goes directly to the bios - the system says that my motherboard cpu clock and the bus frequency don't match. I'm wondering why these settings are being reported as a problem - they haven't changed. I hoped it is something simple so I replaced the battery and things go from bad to worse.
Now pc doesn't even get to the grub splash screen it just sits there blinking "grub _" .
I used knoppix to confirm that the boot directory is still intact and the grub.conf is there too.
The grub problem is probably caused by your bios setting reverting to default when you removed the battery and replaced it with a new one. Check the boot order priority in your bios setup and try putting your hda hard drive first in the boot order. That assumes that assumes that your kernel and initrd lines in grub.conf are listing (hd0,*) with the "*" being the partition where root resides. Grub enumerates hard drives based upon their boot order priority in the bios setup. The first listed hard drive is given the hd0 designation. If hda got moved in the hard drive boot priority in the bios setup upon the bios resetting to default, it could result in the type of grub error you are experiencing.
Thank you. It was not the boot order but it was the bios. After you said that I found western digital hard drive installation guide and the mother board instructions. The wd guide said I should disable LBA and manually enter the values. The mother board said I should specify "use existing partitions" if I was reinstalled existing hd with os. Both those options, together or separately failed. I finally used autodetect and lba together. This caused the the bios to report that I have 255 heads. Weird becasue WD install guide I have 16 heads. Maybe the guide is wrong. or maybe I have the wrong guide. I will pull the hd out later to confirm the heads. In the meantime - all is well in the neighborhood with the exception of the badsuperblock on md0. I'll fix that this weekend. Thanks again for pointing me in the right direction.