Sponsored Content
Operating Systems Solaris Sun Fire v440 Hard disk or controller broken? WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1) Post 303044057 by oliwei on Thursday 13th of February 2020 05:25:14 AM
Old 02-13-2020
Hi,


the status is shown as optimal. I would guess that if a disk is failed or failing raidctl would show that? How can I identify which of the two disks are bad if raidctl claims everything is ok. I have powered down the server many times. I have not replugged all the cables yet. I will give it a try.

Last edited by hicksd8; 02-13-2020 at 06:32 AM..
 

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

USB Hard Disk Drive Supported by Sun Fire V890

Hi, Can anyone suggest me any USB Hard Disk Drive which I can connect to Sun Fire V890 and take backup at a quick speed. A test with SolidState USB Hard Drive for backup work was taking writing at 2GB per hour for a 75GB backup. Regards, Tushar Kathe (1 Reply)
Discussion started by: tushar_kathe
1 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. AIX

SCSI PCI - X RAID Controller card RAID 5 AIX Disks disappeared

Hello, I have a scsi pci x raid controller card on which I had created a disk array of 3 disks when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk ) suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Discussion started by: filosophizer
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

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 Insufficient metadevice database replicas located. Use Metadb to delete databases which are broken. Boot disks are mirrored and other disks are ZFS configuration. Please... (2 Replies)
Discussion started by: samnyc
2 Replies

10. 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
vxreattach(1M)															    vxreattach(1M)

NAME
vxreattach - reattach disk drives that have once again become accessible SYNOPSIS
/etc/vx/bin/vxreattach [-br ] [accessname...] /etc/vx/bin/vxreattach -c accessname DESCRIPTION
The vxreattach utility reattaches disks to the disk group they were in and retains the same media name. This operation may be necessary if a disk has a transient failure, or if Veritas Volume Manager (VxVM) starts with some disk drivers unloaded and unloadable. Disks then enter the failed state. If the problem is fixed, vxreattach may be able to reattach the disks without plexes being flagged as stale, as long as the reattach happens before any volumes on the disk are started. vxreattach tries to find a disk in the same disk group with the same disk ID for the disk(s) to be reattached. The reattach operation may fail even after finding the disk with the matching disk ID if the original cause (or some other cause) for the disk failure still exists. vxreattach is usually invoked by vxdiskadm when performing disk recovery. It is not intended to be run directly by an administrator. OPTIONS
-b Performs the reattach operation in the background. -c Checks if a reattach is possible. No operation is performed, but the name of the disk group and disk media name at which the disk can be reattached is displayed. -r Tries to recover stale plexes of any volumes on the failed disk. It does this by calling vxrecover. EXIT CODES
A zero exit status is returned if the reattach is performed; non-zero is returned otherwise. See vxintro(1M) for a list of standard exit codes. EXAMPLES
Check if reattachment of disk c1t2d0 is possible: /etc/vx/bin/vxreattach -c c1t2d0 If reattachment is possible, vxreattach returns with an exit status of 0 and displays the disk group name and disk media name. If reat- tachment is not possible, vxreattach returns an exit status of 2 and displays an error. Attempt to reattach the disk in the foreground and try to recover stale plexes of any volumes on the disk: /etc/vx/bin/vxreattach -r c1t2d0 If the reattachment is successful, vxreattach returns an exit status of 0. Otherwise, if an error occurs, vxreattach returns a non-zero exit code as defined on vxintro(1M). FILES
/etc/default/vxplex Standard defaults file that can be used to determine whether FastResync is used when attaching plexes. See vxplex(1M) for details. SEE ALSO
vxdiskadm(1M), vxintro(1M), vxplex(1M), vxrecover(1M) VxVM 5.0.31.1 24 Mar 2008 vxreattach(1M)
All times are GMT -4. The time now is 11:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy