Startup Problem

Hello,

I am relatively new to Linux, and have been spending the last couple of
days joining a new Red Hat Enterprise Linux server onto a windows
server 2003 ADS DC. I am 90% of the way there:

However, when I reboot the machine, it gets through to the start of the
GUI where it starts up the services and probes for new hardware (and
the progress bar is on screen), but once that part is complete, it
seems to hang.

The monitor reports "no signal" and the keyboard appears to have gone
dead. If i press the power button on the server, it does not start the
shutdown process. The only way to reboot is to hold it in until the
power goes off.

The strange thing is that this does not seem to happen every time
(probably 1 in 5 does not hang).

The only changes to the startup I have made are to make the Samba and
Winbindd services auto start, and I can see from watching the "show
details" that they both appear to start.

Can anyone suggest any reason for this problem? Or at least where I
can look for any logs which report what the error may be?

Thanks,

Andrew

milney_boy wrote:
> Hello,
>
> I am relatively new to Linux, and have been spending the last couple of
> days joining a new Red Hat Enterprise Linux server onto a windows
> server 2003 ADS DC. I am 90% of the way there:
>
> However, when I reboot the machine, it gets through to the start of the
> GUI where it starts up the services and probes for new hardware (and
> the progress bar is on screen), but once that part is complete, it
> seems to hang.
>
> The monitor reports "no signal" and the keyboard appears to have gone
> dead. If i press the power button on the server, it does not start the
> shutdown process. The only way to reboot is to hold it in until the
> power goes off.
>
> The strange thing is that this does not seem to happen every time
> (probably 1 in 5 does not hang).

I think you have a better chance getting an answer to this problem if
you address it to a Redhat NG... as there are many parameters which can
be passed to the startup process depending on the distro and some
harware configuration. Try
linux acpi=off.
It worked for me when I struggled to install Mandrake some time back.
The startup used to go part way through then just hang.

--
"You can't have everything. Where would you put it?"
-- Steven Wright

On Wed, 08 Mar 2006 08:01:31 -0800, milney_boy wrote:

> Hello,
>
> I am relatively new to Linux, and have been spending the last couple of
> days joining a new Red Hat Enterprise Linux server onto a windows server
> 2003 ADS DC. I am 90% of the way there:
>
> However, when I reboot the machine, it gets through to the start of the
> GUI where it starts up the services and probes for new hardware (and the
> progress bar is on screen), but once that part is complete, it seems to
> hang.
>
> The monitor reports "no signal" and the keyboard appears to have gone
> dead. If i press the power button on the server, it does not start the
> shutdown process. The only way to reboot is to hold it in until the power
> goes off.
>
> The strange thing is that this does not seem to happen every time
> (probably 1 in 5 does not hang).
>
> The only changes to the startup I have made are to make the Samba and
> Winbindd services auto start, and I can see from watching the "show
> details" that they both appear to start.
>
> Can anyone suggest any reason for this problem? Or at least where I can
> look for any logs which report what the error may be?
>
> Thanks,
>
> Andrew

Hi..

If the problem appear to be un-constant, I would test for two things :

1 ) Test the memory with the MemTest-86 bootable CD.

You can download a bootable ISO CD image at the following URL :

http://www.memtest86.com/

or the same test and quite a few more on a test suite boot CD called

Ultimate Boot CD which can be downloaded at :

http://www.ultimatebootcd.com/


Either CDs are a must in any tech personnel tool-chest.

2 ) Try to ping your "hung" server from another host
to see if it really is hung or if it's only the
keyboard/mouse and screen that seem frozen...
Be aware that ping signals can be intercepted and
denied/dropped by firewalls. Check for arping...



Hope it help...