I have a server Hp proliant DL160 G6 with CentOS 5.4 . When I do shutdown -h now it doesn't poweroff.
I try differents options for acpi in menu.lst file. acpi=force, acpi=noacpi,acpi=off,acpi=ht but there's the same problem.
This the stdout when I do shutdown: Halting system... md: stopping all md devices. Completed flushing cache on controller 0 ACPI: PCI interrupt for device 0000:05:00.1 disabled xenbr0: port 2(peth0) entering disabled state ACPI: PCI interrupt for device 0000:05:00.1 disabled Power down. acpi_power_off called
I show you any specific information about my server:
I just did a clean reinstall of Ubuntu (10.04 --> 10.10). After the install, any time I do CPU intensive work, my PC is suddenly shutting down like it's overheating.Everything was working fine for months, and started having problems immediately after the reinstall. so this is not a problem with my hardware, and it's not a problem with my fans needing cleaning -- it's a problem with software. So please don't tell me "that sounds like overheating, clean your fans". Something is different in software-land between 10.04 and 10.10 that is causing this to happen -- I assure you that the upgrade did not magically fill my fans with cat hair.
I have checked my log files, and can't find anything related to overheating -- searches for things related to lm_sensors, "temp", and "thermal" are not turning up anything in the system logs (syslog, kern.log, or messages). I also looked at the logs around the times of the sudden shutdown, and couldn't find anything unusual.How can I diagnose this? I'd like to file a bug report, but since I can't find anything in the logs, I honestly have no idea how to go about providing useful information.Is there anything besides overheating that might be causing my laptop to suddenly shut off?
Built new system and installed openSUSE 11.3 x86_64 with Gnome desktop about 6 weeks ago. Have never been able to get the system to shutdown or fully poweroff using the installed OS. If I use the Knoppix live CD - no problem. System boots up fine and shuts down and powers off correctly. With the installed OS, it originally crashed on shutdown and had to power off using the power button. After trying many things, the OS shuts down, powers off the fans etc, but the keyboard is still lit. I cannot restart the system without turning off power at the power supply. Starting my computer by turning off the power supply switch, waiting 10-12 seconds, turning on the power supply switch and then hitting the power button gets to be very annoying after a few weeks.
Installed KDE and switched to that to see what difference it might make. System does not shutdown, but reboots instead. Switched back to Gnome. Have tried sudo /sbin/shutdown -h now and poweroff. Identical behaviour. System is completely up-to-date. BIOS, kernel, video drivers.
I'm running V5.3 (newly installed) on an FJ E8020 laptop. The problem I have is when shutting down (*not* rebooting). NetworkManager fails to stop and after (during?) the postfix shutdown, the system seems to hang.I cannot access via another screen or remotely. I can't find any clues in the log files.
I haveing a big problem atm (just after to upgrade to 10.04). I have a simply and easy script that sent a halt command to every KVM virtual machine actually running into the server. this script is/and was) palced as a init-rc script in rc0/rc1 and rc6 lvls. Just after to upgrade, I have noticed that this script is executed but the system ignore the time that it require to finish (giving time to correctly stop a single virtual machine). Aftert 5 second it start sending SIG-TERM and SIGN-KILL to any currect process and then reboot/halt.
I have just done a new script using upstart and I got just the same result. What is happending? why is the waiting the init secuence for a valid/or_not termination of any init script. I am so sorry for this crap english I have never study this language so I try to do my best anytime I speak it (or try ti..).
Is there any way to grant access to non root users to use some commands like reboot and date and some other commands that root user can work with .I tried chmod on their binaries and added them to root group but nothing happened.
I'm using pm-hibernate, and would like to reboot the machine after it's done hibernating, rather than having the machine turn off.Is there a way to do this with pm-hibernate, or any other Linux hibernate thing?
Imagine i want to power off my "Lenny" at exactly 16:00 everiday. no mather what I suppose i showld write a script with the shutdown command and add it to the /etc/init.d . but i will listen to your tips first.
I recently upgraded the hard drive on my Fujitsu N3530 notebook to WD Scorpio Blue 500 MB, and created a dual-boot configuration with WinXP, installing 32-bit Slackware 13.1 from DVD. Grub 0.97 bootloader is installed on superblock of root partition. Running KDE. Using the generic kernel with appropriate initrd for ext4 filesystem on root partition.
Everything runs fine so far, except the computer won't power off the computer. I've tried using the KDE shutdown, and shutting down from command line - same result. Also same result if I use the huge kernel or the generic kernel.
The last message I see is: Remounting root filesystem read-only. /dev/sda3 on / type ext4 (ro) Power down.
... and then the shutdown process stalls and I have to turn off the computer by pressing and holding the power button.
This is the first time I've installed any Linux OS on this notebook. I have Slackware 13.0 running fine on a Thinkpad T61 with no poweroff issue.
From reading various posts, this looks to be related to ACPI. I tried adding "acpi=force" to the kernel line in menu.lst, but it made no difference.
/var/log/messages shows "acpid exiting" and then "exiting on signal 15" as last entries during shutdown.s.
Last night there was a rather large thunderstorm, and my computer was on at the time. The power went out while my computer was on, and now it won't boot up. After the GRUB screen, a white message at the bottom of the normal loading screen says somthing along the lines of "a partition listed in /etc/fstab cannot be mounted /dev/disk/by-uuid/6835blahblahblah". I chose recovery mode from the grub menu, which gave me a similar message.
One or more mounts listed in /etc/fstab cannot yet be mounted: (ESC for recovery shell) /home waiting for /dev/disk/by-uuid/8bl I've googled around a fair bit, but people who got the same message were mainly those upgrading to Karmic, so a different problem. I think my problem was the fact that my computer was turned off possibly while writing and definitely without being unmounted.
So far I have tried changing /etc/fstab to refer to /etc/sda5 instead of UUID=68blahblah, but that came up with the same error. I have looked inside the /dev/disk/by-uuid and the disk that is trying to be mounted is there (so it's not a problem with that).
Due to some reason not known to me at this moment, my regular shutdown doesn't work. It freezes on disabling the swap file and doesn't do anything. Now, until that problem is solved, I need a way to properly shutdown. I found one, which is poweroff -f, but it is hardly graceful, and would amount to 'flipping the switch' I guess. The other is hibernate, which is what I now use. This does work, but I rather completely shut down the system. For one, regular boot is quicker than resuming from hibernate.
My main question is: is there any way to make the poweroff -f command, e.g. combined with manually disabling the swap file or whatever,"safe?" as in, I can imagine a sudden power off meaning more chance of damage to the HD, which I don't want.
recently I'va bought PCI adapter for extending ATA devices [URL], connected disk (WDC WD1600JB-00REA0, ATA DISK drive). Everything is fine except switching off. Sometimes it freezes, sometimes it takes longer time (more than 30 sec). Everything goes well - except the last step (when appears "Rebooting", or "Switching off" on console). I didn't add any extra boot option into /boot/grub/menu.lst
I have installed a cluster computer with 10 nodes . The manufacturer is HP . All nodes and the master node have redhat enterprise linux installed in them . When I shutdown the nodes from the master terminal using "shutdown -h now" they get shutdown . But they dont get completely turned off . This issue bothers me when the power supply is given , all nodes boot up simultaneously generating a huge heat .
Thing to note : When we shutdown our PC they get completely turned off . When the power supply is given , a press on the Power On button is required to boot the system. But , why does it not happpen in the case of cluster? Is there any other way of completely turning off the nodes from the master terminal ?
I have working system with fedora 6,It is working fine, but it is not properly shut downIt is giving me messages like System halted but after that i need to press the power buttonIt is not shut down properly.My system details are given below.CPU: Intel(R) Pentium(R) 4 CPU 3.00GHzRAM: 512 DDRHDD: 80 GBKernel: 2.6.18-1.2869.fc6xen (32 bit)
I have checked the following for this issue.1) I have tried acpi=off in kernel in grub options too.2) I have tried to change the settings with BIOS which is related to acpi3) I have searched regarding this issue and found some what related to kernel issue, But the repository of FC6 is not working i think, SO I could not able to upgrade the kernel.
I installed Ubuntu 11.04 in my laptop (HP TM2 touchsmart) and everything was great, install perfect, it recognize every driver, but then it said that there was updates availables, so I installed them, but after that, the system halt at restart, nothing, just a black screen, and if I enter in recovery mode It stops in the line "registering wacom driver" So, what can I do in that case..? Can I restore the previus drivers..? Do I need to reinstall..? How do I avoid that it may happen again..?
Im not sure if this is serious, but yesterday, 2 out of 6 times i tryed to halt my debian box, it didnt.The closing process took place correctly apparently, but after the last message "WILL NOW HALT", it didnt. The server stood there for a good time until i manually rebooted it.I used the command halt via putty, and i was configuring shorewall, so i only wrote some scripts and ran some shorewall restart's
Recently I installed vncserver (tigervnc) on my desktop. Ever since my computer refuses to shutdown normally. At shutdown the following message pops up: Quote: System policy prevents stopping the system when other users are logged in Then I have to enter the root password to shutdown. If I stop vncserver before, the computer shuts down normally.
When i tranfer my files from my hdd to my external hdd debian seems to like to just completely freeze up and just sit there completely unresponsive. My hdd is a 7200rpm st320gb and the external is a 320(probably 5400rpm) toshiba usb 2.0 portable hdd. The system's Lenny with backports on iceweasel. Also this hasn't happened in Fedora, Ubuntu, or Windows. Thus far it seems to be a debian only related issue. Also i have no "safely remove/eject" option on my external so it's a bit like i'm just unplugging it as i hear it physically just stop spinning all at once instead of theother os' wherein i can slowly kill it off.
Anybody here know anything about grub4dos? I'm building myself a multiboot flash drive using grub4dos and one of my commands on the menu, obviously, is shutdown. This should be simply "halt" but every time I launch that command, or if I type it into the grub4dos command line, the computer locks up and I have to do a hard reboot.
I am trying to add an entry to grub2 to turn the computer off using the 'halt' command, but grub2 freezes and I have to manually reboot. I have tried both 'halt' and 'halt --no-apm', both with and without 'insmod halt' first. The 'reboot' command however works fine (even without 'insmod reboot') so it doesnt seem to be an acpi/apm issue. This was all tested at grub2's command line, so there isnt any problems with syntax in the config file. The laptop I am trying this on is an Acer Aspire One, I am using Ubuntu Netbook Edition 10.04 (Lucid), and a more or less default config for grub2 (GNU GRUB 1.98-1ubuntu6) as far as modules are concerned.
The other they my laptop totally halted in the middle of a luks-encrypted external-hd copy operation or such.After a hard poweroff and reboot, the linux procedure would halt at the
Code:(initramfs) line and couldn't be pushed further. I booted with a LiveCD, ran sudo fsck /dev/sda1 and answered yes to a bundh of filesystem-fixing prompts. Yesterday the it happened again: freeze then incomplete boot with same error message. Do you have an idea of what can be causing it? How can I diagnose this problem?