Sponsored Content
Operating Systems AIX System can't boot up after power outage Post 302937840 by Mayank Shah on Tuesday 10th of March 2015 12:27:06 AM
Old 03-10-2015
Once again press Power button after you see code 110000AC.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

boot fails after power faliure

Hi, i was installing solaris 8 on sunfire v250 and the power fails :mad: , now it does not boot from cd rom and get the next msg: ð Sun Fire V120 (UltraSPARC-IIe 648MHz), No Keyboard OpenBoot 4.0, 512 MB memory installed, Serial #56338483. Ethernet address 0:3:ba:5b:a8:33, Host ID: 835ba833. ... (1 Reply)
Discussion started by: agustincm
1 Replies

2. Solaris

Booting up problem after power outage

hi guys, i'm new so don't bite too hard. having a problem booting up a V210 running sol9 on after a power outage... an init5 was done but not a init0 before the power cut... so now when booting up it gives the ff: SC Alert: Host System has Reset Probing system devices Probing memory... (2 Replies)
Discussion started by: lungsta
2 Replies

3. SCO

file system not getting mounted in read write mode after system power failure

After System power get failed File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies

4. AIX

AIX does not boot after power on

We have a RS6000, model B50, type 7046, where I installed AIX 4.3.3 But, if the power goes off, the operating system does not restart, and I have to go there and push the button to start AIX again. Is there any way this procedure to be avoided, this is, I want the AIX to start automatically... (9 Replies)
Discussion started by: sebastia.net
9 Replies

5. AIX

Role of sys admin during power outage in Data center

i am new to aix environment and all my servers are @ remote location just curious to know , what issues/tasks we will be facing when there is a power outage in a data centre, i heard outage's will be a challenging task for administrators.. any example of that sort will be a great help (2 Replies)
Discussion started by: rigin
2 Replies

6. Linux

Administrator responsibilities, in case of power outage?

Hi guys, I was wondering if you could share some of your knowledge, in the event of a power outage. Let presume you are on duty and you get a call at midnight because half of your cabinets have no power, air conditioning is down and you deal with a ton of 500 error messages on your boxes. ... (9 Replies)
Discussion started by: TECK
9 Replies

7. AIX

IBM Power Pseries Open Firmware boot / VIOS POWERVM VET CODE

Hello, I installed PowerVM IVM Virtual I/O on P-550 but later found out that the machine isn't activated for CoD VET code for virtualization. So when booted , it goes into OPEN Firmware I/O Hosting requires a hosting partition boot not permitted exit called > ok Panel shows > IO... (3 Replies)
Discussion started by: filosophizer
3 Replies

8. Solaris

Configure Power Settings on Boot

Hi all, this is my first question on this forum, so if it isn't in the correct location, please let me know where to post. We are using Solaris 8 and with the power setting enabled the monitor will not wake up. It can take anywhere from 5 to 30 minutes for the monitor to display. One of the... (3 Replies)
Discussion started by: Wrongway
3 Replies

9. AIX

Automatic Server bootup after power outage?

Hi everyone, We had a power outage few days ago, and I got the servers up and running but I was informed to look into, if there is a way to bring up the servers automatically/defaultly. I was told the windows admin has their server set up where the servers are up automatically if there is a... (11 Replies)
Discussion started by: Adnans2k
11 Replies

10. AIX

IBM Power 740 won't boot after firmware update

A team member installed the wrong version of License Code on a Power 740 system used in our Development environment. The system will no longer boot. Does anyone have IBM documentation or experience to share on recovering a system that currently reports "Unsupported License Code version... (1 Reply)
Discussion started by: kevinedailey
1 Replies
POWERD(8)						      System Manager's Manual							 POWERD(8)

NAME
powerd - UPS monitoring daemon SYNOPSIS
/sbin/powerd [tty] DESCRIPTION
powerd monitors the serial port connected to an UPS device and will perform an unattended shutdown of the system if the UPS is on battery longer than a specified number of minutes. powerd needs to watch a tty with modem control properties. Please refer to the powerd documen- tation for further information. powerd also has the capabilities of notifying other clients on the network that may have a UPS but not be connected to the serial line that there is a power outage, and id configured through the powerd.conf file CONFIGURATION FILE
Here is the configuration format: Lines beginning with '#' are ignored. MODE <mode> specifies the mode the UPS should be in. Valid arguements are MONITOR and PEER MONITOR being the mode to actually watch a UPS serial port, and PEER being to listen for a connection from a machine in MONITOR mode MONITOR <device> Specifies which device to monitor while in MONITOR mode. Specify an actual device file. Example: /dev/ttyS0 POWERFAIL <line> <high|low> Specifies which lines on the serial ports indicate that the power is out. Valid arguements are DCD, CAR, CTS, and RNG. Also specify if the line being HIGH or LOW indicates a power failure. Since most people may not know this arguement, Please use the enclosed upsdetect program to automatically find this line. NOTIFY <hostname[:port]> <password> Specified in MONITOR mode to notify a client running in PEER mode. Specify the hostname of the machine, and optional port the daemon is running on, And the password as specified by their LISTEN command. See below for more details. LISTEN <hostname> <password> Specified in PEER mode, specifies a hostname that is allowed to notify us of when the power is out, and the password they shall give us to authenticate themselves. The 2 passwords should match on the MONITOR mode machines NOTIFY password, and the PEER modes LISTEN password. LISTENPORT <port> Specified in PEER mode, specifies the port that powerd should listen on. If you use this arguement, powerd shall not default to using port 532, and the machine in MONITOR mode must specify the port you use in their NOTIFY command. DELAY <delayinseconds> Specifies how many seconds before notifying init of a power outage. Note that this doesnt mean that the system will shut down in that many seconds, as it depends on how init is configured. Init usually issues a 2 min shutdown. USER <username> Specifies which username to drop to from root. The program will reobtain root access only when it needs to, Like when notifying init that the power is out. This is simply a security feature, and not needed for powerd to operate. Note: powerd must still be run ini- tially as root. It will then drop to the user if, and only if, a username is specified. ARGUMENTS
None: Please use the configuration file /etc/powerd.conf which can be generated with detectups. See detectups(8) for more information FILES
/etc/powerd.conf powerd configuration file /etc/powerstatus indicates line power status /etc/inittab init is what actually issues the shutdown SEE ALSO
powerd(8), shutdown(8), wall(1), init(8), inittab(5). AUTHOR
James Brents <James@nistix.com> (with parts of this man page borrowed from all over the Linux community) POWERD(8)
All times are GMT -4. The time now is 10:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy