Sponsored Content
Operating Systems Solaris Sun Fire v440 Hard disk or controller broken? WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1) Post 303044055 by hicksd8 on Thursday 13th of February 2020 05:15:54 AM
Old 02-13-2020
The Raid controller is not showing no problems, as you put it.

RESYNCING means that the controller is remirroring the Raid1 disks because of a problem. Depending on the capacity of the Raid1 disks (they will typically be exactly the same size) this resyncing shouldn't take very long, however, whilst this is in progress, system response time will be impacted. Once complete, the status should become OPTIMAL.

If the resyncing is falling over for some reason then the process might be restarting over and over and OPTIMAL is never achieved. What for that. If that is the case I would be inclined to first if possible take the system down and re-seat all SCSI/SATA cables both ends (disk and mobo) and all disk power supply plugs. Reboot and see if the problem persists. If it does, then most likely one of the disks is faulty. It's possible but unlikely that the raid controller is faulty. All the moving parts are the disks.

You could remove the faulty raid1 drive (the one continuously resyncing) and put it on another machine running diagnostics. Perhaps completely reformat and try again. Otherwise, it's a new disk required.
 

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
sautil(1M)																sautil(1M)

NAME
sautil - support utility for the HP SmartArray RAID controller family SYNOPSIS
device_file [-N] device_file [-s] device_file fw_image device_file fw_image physical_drive_id device_file fw_image encl_physical_drive_id device_file device_file device_file device_file logical_drive_number device_file rate device_file device_file device_file device_file [-raw] device_file device_file physical_drive_id [-raw] device_file device_file device_file DESCRIPTION
The command is a support tool for the HP SmartArray RAID Controller Family. This command allows the system administrator to perform tasks such as: 1) Retrieving RAID configuration and status information for the controller, logical drive, physical disk, cache, etc.; 2) Retrieving RAID driver information (driver state, trace log, statistics, etc.); 3) Downloading new revisions of controller or disk firmware; 4) Sending instructions to the firmware (reset controller, scan SCSI bus, etc.); and 5) Recreating the controller device file(s). Prerequisites Some of the options are intended for use by HP support personnel and require detailed knowledge of the RAID SA driver or firmware to inter- pret the output. Security Restrictions requires either the superuser privilege or and privileges. See privileges(5) for more information about privileged access on systems that support fine-grained privileges. Options recognizes the following options and parameters as indicated in the section above. Keyword options are order-dependent, but are not case- sensitive. device_file Most options require a device file parameter, e.g., The device file for a specific RAID SA controller can be determined from the output. When the device file parameter is specified without any options, will display information such as the RAID SA driver state, controller hardware path, firmware revision, capacity expansion and rebuild priority settings, cache status and settings, logical drive configuration and physical drive properties. When the optional argument is specified, persistent device files (see intro(7)) are displayed for logical drives. When the optional argument is specified, a subset of the information is displayed. This option downloads the specified firmware image file (fw_image) to the controller. The image file name is case-sensitive. The firmware download process usually completes within one minute, but could theoretically take up to eight minutes. All I/O to the controller are temporarily halted dur- ing this time. This option downloads the specified firmware image file (fw_image) to physical disk specified by the (physical_drive_id). The image file name is case-sensitive. physical_drive_id To specify the SCSI physical disk. It can be represented as such as: 4:12. Valid channel numbers are between 1 and 4. Valid target numbers are between 0 and 15. To specify the SAS/SATA physical disk. It can be represented as either such as: 2I:1:10 or (wwid), such as: 0x500000e010f16432. This option downloads the specified firmware image file (fw_image) to the storage enclosure processor. This option is supported on SAS Smart Array HBAs only. The image file name is case-sensitive. The firmware download process takes ten to fifteen minutes. All I/O to the controller are temporarily halted during this time. encl_physical_drive_id To specify the storage enclosure processor. It can be represented as either such as: 1E:1:0 or (wwid), such as: 0x500000e010f16432. This option resets the controller. Some situations that may require a controller reset are: 1) OLR was performed and the logical drives on the replacement controller are not detected; 2) a disk enclosure with an existing RAID configuration was hot-added and the logical drives on that enclosure are not detected. This option tells the controller to rescan all SCSI buses. A situation that may require a scan is when a physical disk is hot-inserted into the system's internal drive bay. This option tells the controller to start rebuilding any logical drives that are in state. All logical drives in this state will eventually transition to Heavy I/O to the controller may delay this transition. There is no adverse impact if this option is invoked when no logical drives are in state. This option grants permission to the controller to set the state of the specified failed logical drive (logical_drive_number) to "OK" and to set the states of all failed physical disks that have been replaced via hot-plug exchanges to "OK". WARNING: While this option preserves the RAID configuration (logical drive configurations, controller settings, etc.), data on the failed logical drive may have already been compromised. If more disks have failed than the RAID level can accommo- date, you will need to restore your data from backup media. This option tells the controller to set the SCSI transfer rate to a lower speed than it would normally allow. Valid arguments for the rate field are (and ultra-160 for controllers that support Ultra-320). This option displays statistics counters maintained by the RAID SA "ciss" driver. This option clears the statistics counters maintained by the RAID SA "ciss" driver. This option displays the trace buffer of the RAID SA "ciss" driver. This option displays the firmware error log of the RAID SA controller. When the optional argument is specified, the raw data (in bytes) are displayed. This option clears the firmware error log of the RAID160 SA controller. It is not available for SmartArray 640x controllers. This option displays the error log for the physical disk specified by the (physical_drive_id). When the optional argument is specified, the raw data (in bytes) are displayed. This option displays the RAID SA controller's PCI configuration header. This option allows interactive reading of the RAID SA controller's registers. WARNING: Reading an invalid register may cause a system crash. This option is only available for SAS/SATA. Vital Product Data contains Product Description, Part Number, Engineering Date Code, Serial Number, Miscellaneous Informa- tion, Manufacturing Date Code, EFI Version, Asset Tag, HBA Firmware Version, and WWN. This option runs the RAID SA startup script to recreate the device files (/dev/cissX). Logical Drive State Definitions All physical disks in the logical drive are operational. Some possible causes: 1) Multiple physical disks in a fault-tolerant (RAID 1, 1+0, 5, ADG) logical drive have failed. 2) One or more disks in a RAID 0 logical drive have failed. 3) Cache data loss has occurred. 4) Array expansion was aborted. 5) The logical drive is temporarily disabled because another logical drive on the controller had a missing disk at power-up. Also known as "degraded" state. A physical disk in a fault tolerant logical drive has failed. For RAID 1, 1+0 or 5, data loss may result if a second disk should fail. For RAID ADG, data loss may result if two additional disks should fail. A replacement disk is present, but rebuild hasn't started yet (another logical drive may be currently rebuilding). The logical drive will also return to this state if the rebuild had been aborted due to unrecoverable read errors from another disk. One or more physical disks in this logical drive are being rebuilt. While the logical drive was in a degraded state, the system was powered off and a disk other than the failed disk was replaced. Shut off the system and replace the correct (failed) disk. While the system was off, one or more disks were removed. Note: the other logical drives are held in a temporary "failed" state when this occurs. The data in the logical drive is being reorganized because: 1) Physical disks have been added to the array (capacity expansion). 2) The stripe size is being changed (stripe-size migration). 3) The RAID level is being changed (RAID-level migration). A capacity expansion operation is in progress (or is queued up) that will make room on the disks for this new logical drive. Until room has been made on the physical disks, this newly configured logical drive cannot be read or written. The logical drive is waiting to undergo data reorganization (see above). Possible causes for the delay are a rebuild or expansion operation may already be in progress. Physical Disk State Definitions The physical disk is configured in one or more logical drives and is operational. The physical disk is configured as a spare disk. The physical disk has not been configured in any logical drives. The configured physical disk has failed. RETURN VALUE
returns the following values: Successful completion. Command line syntax error. Incompatible CISS driver API. Failure opening a file. Other error. EXAMPLES
Display RAID subsystem information for the controller Update the firmware on the controller using the firmware image file Update the firmware on the physical disk (SCSI ID "13") connected to channel "2" of controller using the firmware image file located in the current directory: Recreate the device files for all RAID SA controllers in the system: AUTHOR
was developed by HP. FILES
Executable file. Device files. SEE ALSO
saconfig(1M), privileges(5), intro(7). sautil(1M)
All times are GMT -4. The time now is 05:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy