Sponsored Content
Full Discussion: Reserve Failed error for HD
Operating Systems Solaris Reserve Failed error for HD Post 86046 by Perderabo on Monday 10th of October 2005 11:42:56 AM
Old 10-10-2005
Don't know really. Power cycle it for one thing...does that message go away. Try some other options in the format command. Try to use the disk without formatting.

When a disk goes bad, my boss takes it out of the system and smacks it on his hand a few times. Incredibly, that works about 60% of the time. He calls it "percussive maintainence". Smilie No, I am not making that up. But I will understand if you don't believe me. I have watched this ritual for eight years and I still don't believe it myself.
 

8 More Discussions You Might Find Interesting

1. Linux

proper way to reserve ports in linux

How do you debug a perl script non interactively, similar to bash -x? (1 Reply)
Discussion started by: marcpascual
1 Replies

2. Solaris

Reserve Memory for Global Zone

We have several containers on one machine and would like to reserve some memory for the global zone. capped-memory only allows max physical/swap and setting a max on each container isn't an option. The server has 32GB physical and 30GB swap. Currently there are ten containers on it. Normally... (6 Replies)
Discussion started by: kharjahn
6 Replies

3. Filesystems, Disks and Memory

Create file for space Reserve

Hi All, I want to make a 3GB of space reserve on Solaris. Let me know whether there is a way by creating empty file of 3GB so that i can delete that file in future to utilize that space. Or any other better ways for space reserve. -Vinodh' Kumar (4 Replies)
Discussion started by: vino_hymi
4 Replies

4. Shell Programming and Scripting

Reserve resources (memory and processes)

I have a shell script which sets some variables and then calls modules of a program in succession, one by one. Problem is that the script is executed on servers with many users, so sometimes the script starts running, runs for 10 minutes and then breaks due to lack of resources when other users run... (1 Reply)
Discussion started by: tetreb
1 Replies

5. Solaris

Cygwin X Server error: xdmcp fatal error session failed session 23 failed for display

Hi, i got the following error when i tried to access the cygwin x server from a windows XP PC. "xdmcp fatal error session failed session 23 failed for display" Alternatively, when i tried to access the same Cygwin X Server from another windows XP PC which is on a different LAN... (3 Replies)
Discussion started by: HarishKumarM
3 Replies

6. AIX

Reserve Ports

Hi I have a ticket to Reserve ports for SAS install in SAS servers. Does anyone knows the procedure how to do it. it will be helpful for me please Thanks in Advance (4 Replies)
Discussion started by: gulamibrahim
4 Replies

7. UNIX for Advanced & Expert Users

Reserve Ephemeral ports

my apps use port 40001; however, for example, firstly, I ftp to other server, it made a high port locally, remote is port 21, unfortunately, it hit my port 40001 and my apps is unable to startup. This chance is very very little, but I hit it. Can resevse my port 40001? otherwise command don't use it (5 Replies)
Discussion started by: goodbid
5 Replies

8. Solaris

Rpcinfo: can't contact portmapper: RPC: Authentication error; why = Failed (unspecified error)

I have two servers with a fresh install of Solaris 11, and having problems when doing rpcinfo between them. There is no firewall involved, so everything should theoretically be getting through. Does anyone have any ideas? I did a lot of Google searches, and haven't found a working solution yet. ... (2 Replies)
Discussion started by: christr
2 Replies
BOSSKILL(8)						      System Manager's Manual						       BOSSKILL(8)

NAME
bosskill - send a signal to your boss, or terminate your boss SYNOPSIS
bosskill [ -signal ] <bossname> DESCRIPTION
bosskill sends the TERM (terminate, 15) signal to the boss with the specified bossname. If a signal name or number preceded by `-' is given as the first argument, that signal is sent instead of terminate. The killed boss must be in the system administrator's supervisory chain. The following is a list of all signals with names as in the include file <signal.h>: SIGHUP 1 hangup. Forces bossname to re-read his/her job description and figure out that he/she knows squat about sysadmin work or life, in general. SIGINT 2 interrupt. Prevents the bossname from interrupting the sysadmin for one hour. SIGQUIT 3 quit. Causes the boss to quit his/her job with no explanation. SIGILL 4 illegal instruction. Makes the boss believe the last instruction he/she gave was illegal, so he/she withdraws it. SIGTRAP 5 trace trap. Display the exact location of the boss. SIGABRT 6 abort. Makes the boss go home and try again tomorrow. SIGKILL 9 kill. Game over. SIGBUS 10 bus error. Boss's transportation fails on the way to work. SIGSEGV 11 segmentation violation. Boss realizes he/she is trying to do something for which he/she is not quailified and stops. SIGSYS 12 bad argument. Boss loses. SIGPIPE 13 smoke pipe. Boss samples some green leafy substance and mellows out. SIGALRM 14 alarm. Boss is startled and falls over. Best used when boss is walking next to his/her boss. SIGTERM 15 termination signal. Boss is fired. BUGS
Sending a SIGABRT to a boss that is already home will cause him/her to walk aimlessly in circles for two hours. HISTORY
Written by Eric L. Pederson <eric@bofh.org.uk>. 27 September 1995 BOSSKILL(8)
All times are GMT -4. The time now is 12:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy