Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory System crash and Disk erasure !!! Post 61303 by DGoubine on Wednesday 2nd of February 2005 06:41:20 AM
Old 02-02-2005
Thanks for the help !
Now I understand the cause of the problem. "\rm -r" was unfortunately not an option in this case Smilie

Thanks for the feedbacks !
I guess I will just restore the system from spare disc.
Regards,
Dennis
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Disk Crash

We have a Unix system with two hard drives. When we tried to access it this morning it had frozen, and when we rebooted it couldn't find one of the hard drives, and had quite a few bad data blocks on the other. Of course we fear the worst: that the drive is completely gone, but were not sure how... (1 Reply)
Discussion started by: Kgatliffe
1 Replies

2. UNIX for Dummies Questions & Answers

Tru64 system crash

Hello All We are using Tru64 Unix V4.0D on a Digital Alpha 1200 machine, which by coincidence, crashed last night! Completely out of the Blue!!! After rebooting the system and recovering the databases everything seemed to work ok. It is however, discomforting not to know how or why the system... (2 Replies)
Discussion started by: Ivo
2 Replies

3. HP-UX

HP-UX system crash help please!!!

Hi, First of all, thanks for your help. I have downloaded freeBSD to study unix I'm here again 'cause my HP-UX 10.x has "broken". It raise this error: ---------------------------------------------------- Diagnostic System warning: = 0x1f005000 is POWERFAILED The diagnostic logging... (1 Reply)
Discussion started by: efrenba
1 Replies

4. UNIX for Dummies Questions & Answers

how to handle system which become crash automatically

helo, suppose u have well build in product system which is build in linux o.s. now due to reason system automatically become crash(software crash),then how do u handle such crash. which is better way to handle such crash. amit (0 Replies)
Discussion started by: amitpansuria
0 Replies

5. Filesystems, Disks and Memory

HP-UX Disk crash?

Hi, First post. I am not to experienced in the Unix or HP-UX world but I'm learning. We have some problem with a HP rx4640 server. During boot it states the following: Checking for LVM volume groups and Activating (if any exist) Volume group "/dev/vg00" has been successfully changed. vgchange:... (7 Replies)
Discussion started by: hoff
7 Replies

6. AIX

System crash when update TL

Hello everyone I have a partition with the TL 5300-06-01-0000 and try to update to this TL 5300-09-03-0918 but suddenly the update dont work more. I get in to the HMC and I see this code error 888 102 700 0C5 I try to restart my partition but doesnt work. Theres someone who has this... (9 Replies)
Discussion started by: lo-lp-kl
9 Replies

7. Solaris

scconf crash: registering a Veritas local disk on Sun Cluster (localonly=true)

Hi all, I want to put a local disk on a Sun Cluster node but scconf command explodes :eek: My system: * two node cluster on two VMWare virtual machines * Solaris 10 SunOS 5.10 Generic_141415-05 i86pc i386 i86pc * Sun Cluster 3.2 u2 * Veritas Volume manager The situation... (2 Replies)
Discussion started by: gxmsgx
2 Replies

8. UNIX for Dummies Questions & Answers

System check after crash?

Hi all, First and foremost I would like to mention I am pretty new to Linux. I have some experience in Windows systems administration but nothing professionally. Expect some real newbie questions. For a small company I am trying to install a server so a development environment can be... (1 Reply)
Discussion started by: Crazy Harry
1 Replies

9. HP-UX

restore data after system crash

Hi all, I have a server running HP-UX 11i V1 (11.11). We had a problem with the system disk which cannot boot and the recovery with the CD failed too. the only solution was to re-install the system on a new disk. The problem now is to get access to the data which are on other disks, not... (2 Replies)
Discussion started by: aribault
2 Replies

10. Solaris

Boot disk crash with metadb config info

Hello all; We have a SunFire V240 with three disks that were part of a metadb. One of those disks, the boot disk, experienced a horrible death Monday night and we're now trying to recover from that. I know very little about metadb stuff, so please be gentle with me... I'm assuming... (3 Replies)
Discussion started by: Handon
3 Replies
psradm(1M)                                                System Administration Commands                                                psradm(1M)

NAME
psradm - change processor operational status SYNOPSIS
psradm -f | -i | -n | -s [-v] [-F] processor_id psradm -a -f | -i | -n | -s [-v] [-F] DESCRIPTION
The psradm utility changes the operational status of processors. The legal states for the processor are on-line, off-line, spare, faulted, and no-intr. An on-line processor processes LWPs (lightweight processes) and can be interrupted by I/O devices in the system. An off-line processor does not process any LWPs. Usually, an off-line processor is not interruptible by I/O devices in the system. On some processors or under certain conditions, it might not be possible to disable interrupts for an off-line processor. Thus, the actual effect of being off-line might vary from machine to machine. A spare processor does not process any LWPs. A spare processor can be brought on-line, off-line or to no-intr by a privileged user of the system or by the kernel in response to changes in the system state. A faulted processor is identified by the kernel, which monitors the behavior of processors over time. A privileged user can set the state of a faulted processor to be on-line, off-line, spare or no-intr, but must use the force option to do so. A no-intr processor processes LWPs but is not interruptible by I/O devices. A processor can not be taken off-line or made spare if there are LWPs that are bound to the processor unless the additional -F option is used. The -F option removes processor bindings of such LWPs before changing the processor's operational status. On some architectures, it might not be possible to take certain processors off-line or spare if, for example, the system depends on some resource provided by the processor. At least one processor in the system must be able to process LWPs. At least one processor must also be able to be interrupted. Since an off-line or spare processor can be interruptible, it is possible to have an operational system with one processor no-intr and all other processors off-line or spare but with one or more accepting interrupts. If any of the specified processors are powered off, psradm might power on one or more processors. Only superusers can use the psradm utility. OPTIONS
The following options are supported: -a Perform the action on all processors, or as many as possible. -f Take the specified processors off-line. -F Force the transition to the additional specified state. Required if one or more of the specified processors was in the faulted state. Set the specified processors to faulted, if no other transition option was specified. Forced transitions can only be made to faulted, spare, or off-line states. Administrators are encouraged to use the -Q option for pbind(1M) to find out which threads will be affected by forced a processor state transition. -i Set the specified processors no-intr. -n Bring the specified processors on-line. -s Make the specified processors spare. -v Output a message giving the results of each attempted operation. OPERANDS
The following operands are supported: processor_id The processor ID of the processor to be set on-line or off-line, spare, or no-intr. Specify processor_id as an individual processor number (for example, 3), multiple processor numbers separated by spaces (for example, 1 2 3), or a range of processor numbers (for example, 1-4). It is also possible to combine ranges and (indi- vidual or multiple) processor_ids (for example, 1-3 5 7-8 9). EXAMPLES
Example 1: Setting Processors to off-line The following example sets processors 2 and 3 off-line: % psradm -f 2 3 Example 2: Setting Processors to no-intr The following example sets processors 1 and 2 no-intr: % psradm -i 1 2 Example 3: Setting Processors to spare The following example sets processors 1 and 2 spare, even if either of the processors was in the faulted state: % psradm -F -s 1 2 Example 4: Setting All Processors on-line % psradm -a -n Example 5: Forcing Processors to off-line The following example sets processors 1 and 2 offline, and revokes the processor bindings from the processes bound to them: % psradm -F -f 1 2 EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. FILES
/etc/wtmpx Records logging processor status changes ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
pbind(1M), psrinfo(1M), psrset(1M), p_online(2), processor_bind(2), attributes(5) DIAGNOSTICS
psradm: processor 4: Invalid argument The specified processor does not exist in the configuration. psradm: processor 3: Device busy The specified processor could not be taken off-line because it either has LWPs bound to it, is the last on-line processor in the sys- tem, or is needed by the system because it provides some essential service. psradm: processor 3: Device busy The specified processor could not be set no-intr because it is the last interruptible processor in the system, or or it is the only processor in the system that can service interrupts needed by the system. psradm: processor 3: Device busy The specified processor is powered off, and it cannot be powered on because some platform-specific resource is unavailable. psradm: processor 0: Not owner The user does not have permission to change processor status. psradm: processor 2: Operation not supported The specified processor is powered off, and the platform does not support power on of individual processors. SunOS 5.10 17 Aug 2004 psradm(1M)
All times are GMT -4. The time now is 08:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy