Can't graceful shutdown the server

[Jun Yu]

Hello all,

We have a brand new server on remote site. The server was running MS windows server for 2 month and everything is fine. We decided to deploy SLES9 AMD64 SP3 + latest errata(via YOU) on this server to replace the original MS windows server.
The server's ACPI is enabled in it's BIOS(systemROM) and ACPI suspend mode was set to S3(STR).

The problem is we can't shutdown it gracefully. when invoke the command " shutdown -h now" , the screen shows normal shutdown process and finally stopped on "System is shutdown immediately..." so our administrator have to press the power button manually.

I've logined into the system and checked it by the following procedures:

1. cat /var/log/boot.msg|grep ACPI (No error, the ACPI is enabled during boot process)
2. cat /var/log/messages|grep ACPI ( No error, all the ACPI log message looks fine)
3. lsmod |grep power (powersave module is loaded)
4. chkconfig --list|grep powersave ( powersaved daemon is enabled and start when system boot, on level 3 5)
5. yast -> power management ( the power setting is all Ok)
6. powersave -S (invoke this command returned "ACPI" , means the powersaved detect the system and tell us now we are ACPI supported)
7. upgrade the server systemROM (BIOS) to latest stable version from the vendor.(ofcoz i also checked the changelog of BIOS history ensure there is no bug relate to this issue).
8. re-install microsoft windows server 2003 on this server, the system can be shutdown gracefully.(this means that the hardware and BIOS setting should be OK).

I just wonder if additonal steps or procedures can help to troubleshoot this problem?

We'll test RHEL on this server at the end although personally i don't like to do this because we are benefit from SLES9's strong administration features.

Regards,

JOe

[Vipulinux]

Hi

Can you pls try with the poweroff command, does it work or the result is same.

Cheers

[Jun Yu]

Hi,

I've tried poweroff, halt, init. All are same effect.

Regards,

JOe

[Manuel Wolfshant]

there are a few things to try.
- disable local apic (pass nolapic on the boot line)
- disable acpi (pass acpi=off on the boot line)
- try apmd instead of acpi

[Steven E. Protter]

Shalom,

At the console or via console login.

tail -f /var/log/messages (or equivalent logfile)

From a normal prompt:
shutdown -h now

Watch the logs.

This statement is wrong:
8. re-install microsoft windows server 2003 on this server, the system can be shutdown gracefully.(this means that the hardware and BIOS setting should be OK).

That means bios settings are okay for Windows. That does not mean they are right for Linux. Nor does it means that this bios will work with Linux.

You may well have a hardware/bios problem.

SEP

[Jun Yu]

thanks for the above response.

Finally i've installed RHEL4U3 on it and the shutdown procedure executs well.

Things turn to clear as my original opinion, the issue may exist in SLES9's power control modules.

I've post a ticket to novell support service but still want to understand why this happen on a brand new server.(and this server has been used for 2 month without problem under MS environment).

Thanks guys,

JOe

[Alan_152]

What model server is this? I have experienced some issues on mid and high-end machines that were installed with both MS and *nix, where we had to turn off acpi compliance in BIOS or the EFI to get the *nix part to work.