Hi,
I have t5120 sparc and I have 2 146 G drives in the system. I will be installing solaris 10 and also want the system mirrored using Hardware RAID "1"
The System did come preinstalled as it comes from sun. I did not do much on it.
I booted system using boot cdrom -s
gave format... (6 Replies)
Hi,
I have problem creating hardware raid on T5120 with 4 disks. After the hardware raid 1 created, then I used the raidctl -l c1t0d0 and raidctl -l c1t2d0
the output of volume c1t0d0 contain disk 0.0.0 0.1.0, also the volume c1t2d0 contain disk 0.0.0 0.1.0 and should be 0.2.0 0.3.0
so I... (15 Replies)
Good Day,
We have bought Sun Sparc Enterprise T5120 with pre-installed Solaris 10 Sparc
But i need on this server Solaris 9. I have inserted in to DVD-rom (USB DVD-rom) with Solaris 9 for Sparc.
Then log into shell and type: reboot -- cdrom.
System rebooted and i have this message:
... (3 Replies)
Hi All
I have a Sun T2000 server. Couple of years ago I had configured and mirrored the boot drive with an other drive using hardware RAID 1 using raidctl command.
Following is the hardware RAID output.
root@oracledatabaseserver / $ raidctl
RAID Volume RAID RAID Disk... (0 Replies)
Hi all
I've just received my T3-1. It has 8 disks and I would like to configure RAID1 on the disks. The Sun documentation states that you can either use the OpenBoot PROMP utility called Fcode or you can use software via the Solaris OS.
The documentation doesn't make it clear if:
1. The... (6 Replies)
Server Model: T5120 with 146G x4 disks.
OS: Solaris 10 - installed on c1t0d0.
Plan to use software raid (veritas volume mgr) on c1t2d0 disk.
After format and label the disk, still not able to detect using vxdiskadm.
Question:
Should I remove the hardware raid on c1t2d0 first?
My... (4 Replies)
Hi All, I'm new to this site. I have a few question since I'm in the process how to to repair my raid on Sun V240 Server.
1. How can we create RAID in Sun Sparc v240?
2. What utility can help people create RAID in Sun Sparc v240?
3. Do we need any special software to create the... (12 Replies)
We have hardware RAID configured on Sun-Blade-T6320 and one of the disk got failed. Hence we replaced the failed disk. But the hot swapped disk not recognized by RAID. Kindly help on fixing this issue.
We have 2 LDOM configured on this server and this server running on single disk.
#... (8 Replies)
Discussion started by: rock123
8 Replies
LEARN ABOUT NETBSD
bio
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