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
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
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
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
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
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
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
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
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
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
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
BIO(4) BSD Kernel Interfaces Manual BIO(4)
NAME
bio -- Block IO ioctl tunnel pseudo-device
SYNOPSIS
pseudo-device bio
DESCRIPTION
The bio driver provides userland applications ioctl(2) access to devices otherwise not found as /dev nodes. The /dev/bio device node oper-
ates by delegating ioctl calls to a requested device driver. Only drivers which have registered with the bio device can be accessed via this
interface.
The following device drivers register with bio for volume management:
arcmsr(4) Areca Technology Corporation SATA RAID controller
cac(4) Compaq RAID array controller
ciss(4) Compaq Smart ARRAY 5/6 SAS/SATA/SCSI RAID controller
mfi(4) LSI Logic & Dell MegaRAID SAS RAID controller
The following ioctl calls apply to the bio device:
BIOCLOCATE Locate a named device and give back a cookie to the application for subsequent ioctl calls. The cookie is used to tunnel
further ioctls to the right device.
BIOCINQ Retrieve number of volumes and physical disks for a specific device.
BIOCDISK Retrieve detailed information for the specified physical disk. Information returned can include status, size, channel,
target, lun, vendor name, serial number, and processor device (ses).
BIOCDISK_NOVOL Is just the same as BIOCDISK but doesn't require the disks to be in volume sets, so this applies to any physical disk con-
nected to the controller.
Note: this ioctl might not be supported on all hardware.
BIOCVOL Retrieve detailed information for the specified volume. Information returned can include status, size, RAID level, number
of disks, device name association (sd?) and vendor name.
BIOCALARM Control the alarm beeper on the device. Supported states are: disable alarm, enable alarm, silence alarm, status and test
alarm.
Note: These options might not be supported on all hardware.
BIOCBLINK Blink an LED of the specified physical disk. Supported blink states are: blink LED, unblink LED and blink alarm LED.
Note: This option is only supported if the disk is governed by ses(4) and the hardware supports hardware blinking.
BIOCSETSTATE Alter the state of specified physical disk. Supported states are: create/remove hot-spare, create/remove pass through
disk, start/stop consistency check in a volume, online disk and offline disk.
Note: These options might not be supported on all hardware.
BIOCVOLOPS For operations in volume sets. It's able to create and remove a volume set in a supported RAID controller.
Note: this ioctl might not be supported on all hardware.
FILES
/dev/bio ioctl tunnel device
SEE ALSO
ioctl(2), bioctl(8)
HISTORY
The bio driver first appeared in OpenBSD 3.2 and NetBSD 4.0.
AUTHORS
The bio driver was written by Niklas Hallqvist <niklas@openbsd.org>. The API was written by Marco Peereboom <marco@openbsd.org> and was
extended even more for NetBSD by Juan Romero Pardines <xtraeme@netbsd.org>.
BSD
May 25, 2008 BSD