Problem with restart FC5 after moving

aussie90 · 02-13-2007, 05:08 PM

Hi, all,

A quick question: I had used FC5 on a Dell Precision 350 in my office and it worked quite well. However, recently I moved the computer to home. Somehow FC can't start anymore. During the boot process, first of all there is problem with \etc\ISCSI but FC5 went through anyway. Then it freezes at sendmail. I tried interactive mode to ignore this, the screen turns blank after all went through. During the process the startup of CUPS was very slow as well.

Is there anyway I can check/revise the startup process? I know I should use rescue disck (haven't used it once, need to find it somewhere), but what do I need to do to start up again?

Thanks

wmakowski · 02-13-2007, 10:16 PM

Might be a good idea to try booting into run level 1 to see if you can get the box up and running. When your boot loader (grub) starts go into edit mode and get to the line that had the kernel command on it. It will look something like this

Code:

kernel /boot/vmlinuz-2.6.19-1.2895.fc6 ro root=LABEL=/ quiet

Enter a 1 after the kernel file and before the ro like this

Code:

kernel /boot/vmlinuz-2.6.19-1.2895.fc6 1 ro root=LABEL=/ quiet

Once it boots into run level 1 you can use chkconfig to turn off some of your services. sendmail or CUPS might be a good place to start. You can then change your run level at the command line using init 3 to go into run level 3 for example.

Just thought of something, did you change monitors when you brought the machine home? Could be a problem with your X windows config.

Bill

aussie90 · 02-14-2007, 12:09 AM

Thanks a lot Bill.

I did some search and saw the questions in the forum related to sendmail. So I boot to shell mode and turn off the sendmail. This time there is no problem to go through but it ended up again waiting a long time. Finally (after 3 min of blank screen) the login window appeared (it turned out last time I didn't wait long enough). It also takes a long time for me to log in.

No, I didn't change my machine.

Right now the problem is that I can't get online. One thing different from before is that at the office I had a fixed IP address and a host/domain like XXX.XXX.com.au, now at home I used a roater to connect two machines. I changed the network card setup to DHCP instead of fixed IP address and change the hostname to localhost.localdomain. But it doesn't work.

Still trying. Any expert advices?

Thanks in advance.

james.farrow · 02-14-2007, 03:14 AM

What is your /etc/reolv.conf
Type dig on the command line and it should return the name server that is resolving for your box.
It will be the ip of your router if all is correct.
If not then manually add

nameserver <router ip> to resolv.conf

try the above again.

wmakowski · 02-14-2007, 09:52 AM

I would have to agree, it sounds like networking is the heart of the problem. Since your system had a static ipaddress in the past you will most likely need to set up dhcp to get your ipaddress and nameservers from the router. Once that is resolved the individual services that require networking will start up much more smoothly.

Most of the configuration can be done using the gui system-config-network. The other part is setup your system to use DHCP on boot. I'm going to assume you are using an ethernet card to connect to the network. The file you want to edit is /etc/sysconfig/nework-scripts/ifcfg-eth0. The contents should end up looking like this.

Code:

#
# File: ifcfg-eth0
#
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes

With any luck that will resolve your problem. The /etc/resolv.conf file that james.farrow is talking about deals with what nameservers your system uses. If dhcp is working properly it should get this information from your router.

Bill

aussie90 · 02-14-2007, 04:47 PM

Thanks a lot, James and Bill.

I finally get the network working. As I said, I changed the ethernet setup to DHCP, but it didn't work. That puzzled me a lot. Finally I checked each tab on the system-config-network and found somehow there is something like 10.0.0.1 generated in DNS, O_O So I deleted that line, and voila, it works. But next I checked, it is still 10.0.0.1 O____O So I don't know why it works and, for that matter, why it didn't work before.

Now I am checking one program by one program to see whether those are affected as well. Some of the programs I installed were under the old network id if I remember correctly, I don't know if I need to reinstall them under the new network id.

By the way, there was this error term when booting saying something wrong about ISCSI. Because it doesn't affect me so far, I just ignore it. Is there potential problem there as well?

Again, appreciate the replies from Bill and James. Thanks a lot.