Sponsored Content
Operating Systems Solaris Sun-Fire V440 boot disk issue Post 302821339 by samnyc on Friday 14th of June 2013 11:49:37 AM
Old 06-14-2013
Sun-Fire V440 boot disk issue

Hi,

I have Sun Fire V440. Boot disks are mirrored. system crashed and it's not coming up. Error message is
Code:
 
Insufficient metadevice database replicas located. Use Metadb to delete databases which are broken.

Boot disks are mirrored and other disks are ZFS configuration. Please help.

Thank you so much.
 

10 More Discussions You Might Find Interesting

1. Solaris

Sun Fire V440 and Patch 109147-39

Got an curious issue. I applied 109147-39 to, oh 15 or so various systems all running Jumpstarted Solaris 8. When I hit the first two V440s, they both failed with Return code 139. All non shell commands segfaulted from then on. The patch modified mainly the linker libraries and commands. ... (2 Replies)
Discussion started by: BOFH
2 Replies

2. Solaris

Sun Fire v440 keeps shutting down

Hello, I hope you can help me. I am new to Sun servers and we have a Sun Fire v440 server in which one power supply failed, we are waiting for new one. But now our server is shutting down constantly. Is there any setting with which we can prevent this behaviour? (1 Reply)
Discussion started by: Tibor
1 Replies

3. Solaris

Sun Fire won't boot anymore

Hi all - I have an issue with our (way old) single processor SunFire 280R, running Solaris 9.0.4. It won't boot even after multiple power cycles. There was a power outage last week end in the computer room, so this might have to do. In normal boot mode, the screen shows a single line : ... (5 Replies)
Discussion started by: bostella
5 Replies

4. Solaris

Sun Fire v440 hardware problem (can't get ok>)

First of all it's shut down 60 second after power on and write on console : SC Alert: Correct SCC not replaced - shutting managed system down! This is cured by moving out battery from ALOM card. Now server start to loop during the testing. That's on the console: >@(#) Sun Fire V440,Netra... (14 Replies)
Discussion started by: Alisher
14 Replies

5. Solaris

error messages in Sun Fire V440

Hello, I am seeing error messages in V440 (OS = solaris 8). I have copied here : The system does not reboot constantly and it is up for last 67 days. One more interesting thing I found, I see errors start appearing at 4:52AM last until 6am and again start at 16:52am on same day.. I... (5 Replies)
Discussion started by: upengan78
5 Replies

6. Solaris

ALOM wont work when KVM connected to Sun Fire V440 server

Hi, I was asked to connect a KVM screen to a Sun Fire V440 last night so I connected it up but no joy and nothing on the KVM screen. I was told that a reboot may fix the problem so connected to the ALOM and rebooted. On the plus side, the KVM screen now works but I lost the ALOM connection. ... (0 Replies)
Discussion started by: jimmy54321
0 Replies

7. Solaris

Firmware password Solaris Sun Fire v440

Hi: I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Discussion started by: mguazzardo
1 Replies

8. Solaris

Sun Fire v440 Over heat Problem.

Dear Team, I need some expert advice to my problem. We have a Sun Fire v440 in our customer Place. Server is working fine and no hardware deviations are found except one problem that processors generating too much heat. I have verified and found that the room temperature was 26-27 degree.... (5 Replies)
Discussion started by: sudhansu
5 Replies

9. Solaris

Removing a disk from SUN Fire V440 running Solaris 8

Hi, I have a SUN Fire V440 server running Solaris 8. One of the 4 disks do not appear when issued the format command. The "ready to remove" LED is not on either. Metastat command warns that this disk "Needs maintenace". Can I just shutdown and power off the machine and then insert an... (5 Replies)
Discussion started by: Echo68
5 Replies

10. Solaris

Sun Fire v440 Hard disk or controller broken? WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1)

Hi, I have a Sun Fire V440 server that fails to boot up correctly. A lot of services are not started and the sytems acts really slow to commands. During boot I can see the following Error: WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1): SCSI transport failed: reason 'reset': retrying... (15 Replies)
Discussion started by: oliwei
15 Replies
vxpfto(1M)																vxpfto(1M)

NAME
vxpfto - set Powerfail Timeout (pfto) SYNOPSIS
vxpfto -g diskgroup -t timeout vxpfto [-g diskgroup] -t timeout volume_list vxpfto [-g diskgroup] -o pftostate={enabled|disabled} vxpfto [-g diskgroup] -o pftostate={enabled|disabled} volume_list DESCRIPTION
Powerfail Timeout is an attribute of a SCSI disk connected to an HP-UX host (see the pfto(7) man page). The vxpfto command sets the Power- fail Timeout interval on a set of Volume Manager disks, either all disks in a disk group, or all disks underlying the volumes listed. The first form of the command sets the same PFTO value for all the disks in the specified VxVM diskgroup. In the second form, all disks underlying the given list of volumes are selected, optionally restricted by the disk group specified with the -g option. If you specify a diskgroup, any volume in the list not belonging to the diskgroup is ignored. Use the -o pftostate option to disable or enable PFTO. By default, PFTO is enabled. You can enable PFTO either on all disks in a disk group, or on all disks underlying the volumes listed. If you invoke vxpfto without arguments, it displays a usage message. OPTIONS
-g diskgroup Specifies the disk group for the operation, either by disk group ID or by disk group name. -o pftostate={enabled|disabled} Enables or disables the use of PFTO for IO. -t timeout Specifies the PFTO value in seconds. The value must be zero or a positive integer. Zero represents the system default PFTO value. The default value depends on the disk driver controlling the disk device. volume_list A list of VxVM volume names. List items must be separated by white-space. EXIT CODES
vxpfto returns a zero if successful. If it encounters an error, vxpfto exits and displays a message on standard error. Defined exit codes are: 0 Success. 1 No PFTO value specified. 2 No diskgroup or volume list specified. 3 Illegal PFTO value specified. EXAMPLES
Set the PFTO value on all disks in disk group testdg to 100 seconds: vxpfto -t 100 -g testdg Set the PFTO value to 50 seconds on all disks underlying volume01 and volume02 in disk group testdg: vxpfto -t 50 -g testdg volume01 volume02 Set the PFTO value to 300 seconds on all disks underlying volume01 and volume02, even though they are not in the same disk group: vxpfto -t 300 volume01 volume02 Disable PFTO on all disks in disk group testdg: vxpfto -g testdg -o pftostate=disabled Enable PFTO on all disks underlying volume01 and volume02i in disk group testdg: vxpfto -g testdg -o pftostate=enabled volume01 volume02 SEE ALSO
vxdisk(1M), pfto(7) VxVM 5.0.31.1 24 Mar 2008 vxpfto(1M)
All times are GMT -4. The time now is 01:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy