10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
getStatusi86()
{
#storing logical volume name
volumelist=`cfgadm -val | grep "Logical Volume" | awk '{print substr($1,9,14)}'`
controller=`echo $volumelist | awk '{print substr($1,2,1)}'`
#errordisk=""
volume1=`echo $volumelist | awk '{print $1}'`
for volume in $volumelist
do... (1 Reply)
Discussion started by: frintocf
1 Replies
2. Solaris
I tried using raidctl earlier today to use my 2 disks in a RAID1 setup and I totally destroyed my OS install. I'm sure I did something funky and it freaked out. No big deal...right?
This is what I was seeing after a reboot.
I decided to just reinstall the OS. It let me go through all of... (3 Replies)
Discussion started by: kingdbag
3 Replies
3. Solaris
I have boot disk mirrored using hardware raid i.e raidctl command.
If I want to place an order for a spare drive and keep it at our location for spare, how do I find the disk specification since #format does not reveal this.
The server is T2000 running Solaris 10.
Any help please. (5 Replies)
Discussion started by: Tirmazi
5 Replies
4. Solaris
using the internal 2 drives mirror was created using raidctl on 100's of our servers . sometime when one drive fails we dont face any issue & we replace the drive with out any problem . but sometimes when one drive fails , system becomes unresponsive and doesnot allow us to login , the only way to... (1 Reply)
Discussion started by: skamal4u
1 Replies
5. UNIX for Dummies Questions & Answers
Hello people i have a question, when i put raidctl -l on sun fire show this
Volume Size Stripe Status Cache RAID
Sub Size Level
Disk ... (0 Replies)
Discussion started by: enkei17
0 Replies
6. UNIX for Advanced & Expert Users
Hello World:
Recently I ran into an issue where a collegue had installed a Sun T5140 with twin 136GB disks in them. However, he forgot to execute the raidctl command first to mirror c1t0d0 to c1t1d0 boo hoo:) So along I come and try to mirror the disks by booting to sigle user... (1 Reply)
Discussion started by: rambo15
1 Replies
7. Solaris
Setting up a T5240 with two disks c1t0d0 and c1t1d0.
I am trying to use raidctl but when I issue.
raidctl -l
I get
Controller 1
Disk: 0.0.0
Disk: 0.1.0
So I try
raidctl -c '0.0.0 0.1.0' -r 1 1
and I get "Array in use."
I try (4 Replies)
Discussion started by: photon
4 Replies
8. Solaris
At my own eys I can see 4 disks inside of server. Previous admin told me that hardware mirror is done.
What I see with "format" is 2 disks - I suspect that these are 2 MIRRORS.
I just cant be sure because raidctl show this:
# raidctl -l c0t0d0
Volume Size Stripe ... (0 Replies)
Discussion started by: czezz
0 Replies
9. UNIX for Dummies Questions & Answers
I am mirroring a single partition drive with raidctl. The source partition was mounted when I created the mirror with raidctl -c c1t1d0 c1t3d0. The source disk was defined with s2 and s6 only.
I didn't think to umount it first.
Is there a problem with that? (2 Replies)
Discussion started by: csgonan
2 Replies
10. UNIX for Dummies Questions & Answers
I am using raidctl on a v440 disk and noticed it resyncs after every boot, which takes about 30 minutes because of the size of the partition. I am concerned with what happens during the resync if "writes" happen to the disk before it is complete?
Any info would be helpful.
Thanks (0 Replies)
Discussion started by: csgonan
0 Replies
tms(4) Kernel Interfaces Manual tms(4)
Name
tms - TMSCP magnetic tape interface
Syntax
For UNIBUS, Q-bus:
controller klesiu0 at uba0
controller uq0 at klesiu0 csr 0174500 vector uqintr
tape tms0 at uq0 drive 0
For MSI Bus:
adapter msi0 at nexus?
controller dssc0 at msi0 msinode 0
tape tms0 at dssc0 drive 3
For VAXBI:
controller klesib0 at vaxbi0 node 0
controller uq0 at klesib0 vector uqintr
tape tms0 at uq0 drive 0
controller aie0 at vaxbi? node?
controller bvpssp0 at aie0 vector bvpsspintr
tape tms0 at bvpssp0 drive 0
For MSI Bus:
adapter msi0 at nexus?
controller dssc0 at msi0 msinode 0
tape tms0 at dssc0 drive 0
For VAX CI/HSC:
adapter ci0 at nexus?
adapter ci0 at vaxbi? node?
controller hsc0 at ci0 cinode 6
tape tms0 at hsc0 drive 3
Description
Prior to Version 2.0, this device was referenced by tmscp(4).
The TMSCP driver provides a standard tape drive interface, as described in This is a driver for any controller that adheres to the Tape
Mass Storage Control Protocol (TMSCP). The TMSCP controllers communicate with the host through a packet-oriented protocol termed the Tape
Mass Storage Control Protocol. This driver also supports n-buffered reads and writes to the raw tape interface (used with streaming tape
drives). See for further details.
Tape Support
TK50, TK70, TF70, TU81, TU81e, TA78, TA79, TA81, RV20, TA90, TA90E, TA91
Diagnostics
All diagnostic messages are sent to the error logger subsystem.
Files
See Also
mtio(4), nbuf(4), MAKEDEV(8), uerf(8), tapex(8)
Guide to the Error Logger
tms(4)