01-11-2015
Your raidctl output at the end of your post says that, as you already know, you have two hardware raid1 mirrored drives. The disk/raid controller is presenting this pair of drives as one disk to the O/S. Control, writing and maintenance of this mirror lies solely with the hardware raid controller. The O/S thinks that it is talking to a single disk.
There is no issue if you carry out normal O/S patching on the system. Usual precautions with regards backup/recovery.
If you think this should be an abnormal process due to the presence of the hardware raid1 controller please describe why you think that.
---------- Post updated at 04:57 PM ---------- Previous update was at 04:48 PM ----------
I think that you might be being put off by the fact that the LSI hardware raid controller is integrated into the T5220.
If you had fitted an add-in raid controller card and through it's management console mirrored two disks and presented them to the host as one drive (so the host is unaware of the mirror), then the raid controller is just a SCSI controller as far as the host hardware is concerned.
What you have there is no different apart from the raid controller has been integrated by Sun (Oracle) into the hardware.
9 More Discussions You Might Find Interesting
1. Solaris
I don't understood why on SPARC-Platforms have not present RAID-Controller ? Sorry for my bad english, but it's crazy always setup software RAID !!! I whanna Hardware RAID and when i can find solution ? (7 Replies)
Discussion started by: jess_t03
7 Replies
2. Solaris
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)
Discussion started by: upengan78
6 Replies
3. Solaris
Hi,
I have a root with hardware RAID on c0t0d0 and c0t2d0. I would like to set the boot device sequence in OBP for both hdds.
I have checked in ls -l /dev/rdsk/ for the path of c0t2d0 but it does not exist. Can anyone shed some lights on this?
AVAILABLE DISK SELECTIONS:
0.... (12 Replies)
Discussion started by: honmin
12 Replies
4. UNIX for Dummies Questions & Answers
Hi
Can someone tell me what are the differences between software and hardware raid ?
thx for help. (2 Replies)
Discussion started by: presul
2 Replies
5. Solaris
Hi,
I have a question. Do LiveUpgrade supports hardware raid?
How to choose the configuration of the system disk for Solaris 10 SPARC?
1st Hardware RAID-1 and UFS
2nd Hardware RAID-1 and ZFS
3rd SVM - UFS and RAID1
4th Software RAID-1 and ZFS
I care about this in the future to take... (1 Reply)
Discussion started by: bieszczaders
1 Replies
6. Hardware
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)
Discussion started by: soliberus
6 Replies
7. Solaris
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)
Discussion started by: KhawHL
4 Replies
8. Solaris
Dear All ,
We need to do patching on one Solaris Server , where we have raid 0 configured.
What is the process to patch a Server if RAID 0 (Concat/Stripe) is there.
Below is the sample output.
# metadb
flags first blk block count
a m pc luo 16 ... (1 Reply)
Discussion started by: jegaraman
1 Replies
9. Solaris
Dear All ,
Pl find the below command ,
# raidctl -l
Controller: 1
Volume:c1t0d0
Disk: 0.0.0
Disk: 0.1.0
Disk: 0.3.0
#
raidctl -l c1t0d0
Volume Size Stripe Status Cache RAID
Sub Size ... (10 Replies)
Discussion started by: jegaraman
10 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