Sponsored Content
Special Forums Hardware StorageTek 2540 battery failed Post 302566210 by buyantugs on Wednesday 19th of October 2011 08:46:51 PM
Old 10-19-2011
Hi DukeNuke2

I understand the batter replace is safer way but performance lost is more important for me.
if no power outage during new battery order completion period, I should change above option on disk cache? Am i right?
 

10 More Discussions You Might Find Interesting

1. Solaris

Sun Sparc T2000 + StorageTek 2540 - Help, I'm lost

I have a Sun Sparc T2000 (Solaris 10 05-08) and have installed a PCI-X 4GB Single Port HBA card in it. I have one StorageTek 2540 array that I would like to connect to the T2000. For the moment it would be a single path connection, but I've ordered a 2nd HBA, so eventually it would be... (4 Replies)
Discussion started by: soliberus
4 Replies

2. Solaris

One StorageTek 6140 vs Two (2) 2540 's?

We're moving our production 3510FC to development, so we need to replace the production 3510FC. The 6140 is nice, but pricey. Here's the question: Would two 2540's (RAID 10) be 'faster' than one 3510? (RAID 10) and faster than one 6140 (RAID 10)? One StoregeTek 6140 (16x72GB 15k rpm fc-al... (12 Replies)
Discussion started by: buddhavelvet
12 Replies

3. Filesystems, Disks and Memory

Configure large volume on Sun StorageTek 2540 array

Hi, We have 12x1TB SATA disks in our array and I need to create 10TB volume. I defined new storage profile on array and when I tried to add volume, I faced with ~2TB limit for new volumes. I didn't find how to set another limit on my storage profile. Is there is a way to configure one large... (3 Replies)
Discussion started by: Sapfeer
3 Replies

4. Solaris

Sun StorageTek 2540 - shutdown matrix

Hi, I have a simple question on how to correctly disable the matrix? Looking for the Common Array Manager and I do not see this option... Thank for help (3 Replies)
Discussion started by: bieszczaders
3 Replies

5. Solaris

Storagetek 2540

Hi peeps, Was wondering if anyone can help me, got a couple of storagetek 2540's that I need to configure. Trouble is I think they were brought as second user as all that came with them was cables. Does anyone know how to configure them (i.e. create raid sets and map to Luns and present... (1 Reply)
Discussion started by: callmebob
1 Replies

6. Hardware

Storagetek 2540

Hello all ! I am a beginner about system and networking , and after some research on internet , i didn't find any relevant information , so i post here , if someone have an experience with this kind of material or if some documentation about how to connect my storage device on my server. I... (2 Replies)
Discussion started by: acorradi
2 Replies

7. Solaris

SUN 6540 Array with failed controller battery

Can someone point me to a procedure detailing the replacement of a failed battery in a SUN 6540 controller. Or describe the procedure. Thanks (1 Reply)
Discussion started by: USFE
1 Replies

8. Hardware

Storagetek 2540

Hi Guys and Gals, Wionder if you could help me, got a problem with a controller on a storagetek 2540, dead when fully powered up but if you reboot, it is ok for a couple of seconds (and you can ping it). Then once the array is fully up, it goes faulty and is un-pingable. Had anyone... (4 Replies)
Discussion started by: callmebob
4 Replies

9. Solaris

StorageTek 2540 SAN array

Bought a Sun StorageTek 2540 SAN array a few years ago from a company that was going out of business. When we first set it up, we were able to get all the software (Common Array Manager) and firmware directly from Sun. We just upgraded the drives, but the array is too large for the firmware. Now... (6 Replies)
Discussion started by: edison303
6 Replies

10. Solaris

Server M4000 server lost connectivity to storagetek 2540

Hi Guys, I have situation here ... server M4000 server lost connectivity to storagetek 2540 , storagetek 2540 unable to be ping.From DAS URL the storage is undetected. Any idea why this is happening. Please share. Thank you. Raj (1 Reply)
Discussion started by: muralirajah
1 Replies
APMD(8) 						    BSD System Manager's Manual 						   APMD(8)

NAME
apmd -- Advanced Power Management monitor daemon SYNOPSIS
apmd [-adlqsv] [-t rate] [-S sockname] [-m sockmode] [-o sockowner:sockgroup] [-f devname] DESCRIPTION
The apmd daemon monitors the Advanced Power Management (APM) pseudo-device, acting on signaled events and upon user requests as sent by the apm(8) utility. The apmd daemon is only installed on supported platforms. The apmd is largely deprecated. Modern systems supporting ACPI should rely on acpi(4), powerd(8), and the envsys(4) framework instead. For suspend and standby request events delivered by the BIOS, or via apm(8), apmd runs the appropriate configuration program (if one exists), syncs the buffer cache to disk and initiates the requested mode. When resuming after suspend or standby, apmd runs the appropriate configu- ration utility (if one exists). For power status change events, apmd fetches the current status and reports it via syslog(3) with logging facility LOG_DAEMON. apmd announces the transition to standby mode with a single high tone on the speaker (using the /dev/speaker device). Suspends are announced with two high tones. apmd periodically polls the APM driver for the current power state. If the battery charge level changes substantially or the external power status changes, the new status is logged. The polling rate defaults to once per 10 minutes, but this may be altered by using the -t command- line flag. apmd supports the following options: -a Any BIOS-initiated suspend or standby requests are ignored if the system is connected to line current and not running from bat- teries (user requests are still honored). -d Enter debug mode, log to facility LOG_LOCAL1 and stay in the foreground on the controlling terminal. -f devname Specify an alternate device file name. -l A low-battery event causes a suspend request to occur. -m sockmode Use sockmode instead of '0660' for the mode of /var/run/apmdev. -o sockowner:sockgroup Use sockowner:sockgroup instead of '`0:0'' for the owner/group of /var/run/apmdev. -q Do not announce suspend and standby requests on the speaker. -s The current battery statistics are reported via syslog(3) and exit without monitoring the APM status. -S sockname Specify an alternate socket name (used by apm(8) to communicate with apmd). -t rate Change the polling rate from 600 seconds to rate seconds. -v Periodically log the power status via syslog(3). When a client requests a suspend or stand-by mode, apmd does not wait for positive confirmation that the requested mode has been entered before replying to the client; to do so would mean the client does not get a reply until the system resumes from its sleep state. Rather, apmd replies with the intended state to the client and then places the system in the requested mode after running the configuration script and flushing the buffer cache. Actions can be configured for the five transitions: suspend, standby, resume, line or battery. The suspend and standby actions are run prior to apmd performing any other actions (such as disk syncs) and entering the new mode. The resume program is run after resuming from a stand- by or suspended state. The line and battery actions are run after switching power sources to AC (line) or battery, respectively. The appropriate line or battery action is also run upon the startup of apmd based on the current power source. FILES
/etc/apm/suspend /etc/apm/standby /etc/apm/resume /etc/apm/line /etc/apm/battery Contain the host's customized actions. Each file must be an executable binary or shell script suitable for execution by the execve(2) function. If you wish to have the same program or script control all transitions, it may determine which transition is in progress by examining its argv[0] which is set to one of suspend, standby, resume, line or battery. See /usr/share/examples/apm/script for such an example script. /var/run/apmdev The default UNIX-domain socket used for communication with apm(8). The socket is protected by default to mode 0660, UID 0, GID 0. /dev/apmctl The default device used to control the APM kernel driver. SEE ALSO
execve(2), syslog(3), apm(4), speaker(4), apm(8), syslogd(8) HISTORY
The apmd daemon appeared in NetBSD 1.3. BSD
March 20, 2010 BSD
All times are GMT -4. The time now is 09:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy