Sponsored Content
Operating Systems Solaris Help needed to find out the disk controller for veritas disks Post 302437708 by kingston on Friday 16th of July 2010 02:21:39 AM
Old 07-16-2010
Help needed to find out the disk controller for veritas disks

hi all
i am using vxvm 5.1 on my sun blade 150 which is running with solaris 5.10. When i give the command "vxdisk list" it gives the following output
Code:
# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c0t0d0s2     auto:none       -            -            online invalid
disk_0       auto:cdsdisk    disk_0       rootdg       online
disk_1       auto:cdsdisk    disk_1       kingston     online
disk_2       auto:cdsdisk    -            -            online
disk_3       auto:cdsdisk    kingston01   kingston     online
disk_4       auto:cdsdisk    -            -            online
disk_5       auto:cdsdisk    -            -            online

My question is, i have ultrascsi storage box which is having 6 sun 36 GB hard disks. here for the root disk, it is straightaway giving the c#t#d#s# number. i am not getting for other disks. There is one command, i hope it is "vxddlam" with some option can give the exact controller and its respect disk names. Can someone tell me that command?

thanks in advance ...Kingston S
 

10 More Discussions You Might Find Interesting

1. Solaris

Controller target disk?

Hi, I am a newbie to Solaris. I want to know how to find out the controller target and disk number on a SunFire V890 box that has 6X72GB disks. The probe-scsi output is as shown below: /pci@8,600000/SUNW,qlc@2 LiD HA LUN --- Port WWN --- ----- Disk description ----- 0 0 0 ... (1 Reply)
Discussion started by: sudhir_shet
1 Replies

2. SCO

driver needed for hp smartarry p200i sas raid controller

recently we have purchased hp proliant ml350 g5 server and configured raid 5 with hp smartarray p200i sas controller.but i could not found any sas raid controller hp smartarry p200i driver for sco unix 5.0.7 :(.i searched on hp support site,but no use.any one can help. (3 Replies)
Discussion started by: prakrithi
3 Replies

3. Solaris

RAID controller needed for SVM?

hi this may be a very stupid question, but im quite new to Solaris (gonna buid my first system, Solaris 10 on x86 system, connected to other windows systems in a home network) i wanna put a RAID 5 system in there to back up my other systems at home; iv read that its really so easy with SVM to... (4 Replies)
Discussion started by: Landser
4 Replies

4. SCO

Warning HD: no root disk controller was found

hi... i hav a problem to install sco unix while installing sco unix 5.0.5 in acer altos with hardware raid am getting error "Warning HD: no root disk controller was found system error 5: while getting fs type flushing controller: DAC960PRL cache done." i hav use the following... (18 Replies)
Discussion started by: mselvaprakash
18 Replies

5. SCO

Change Disk controller in SCO 6.0.0

So today I tried to upgrade a customer from a Proliant with an HPSAS controller to an Intel server with a MEGASAS controller. First, I downloaded the megasas driver from SCO and installed it on the old system. Then I created a new Microlite Edge emergency boot cd with the new driver on it. I... (2 Replies)
Discussion started by: jgt
2 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

Changed disk controller -> drops into GRUB?!

I changed disk controller. Unplugged every disk, inserted another controller card, an IBM M1015. The disks are recognized in BIOS, and the controller card's BIOS shows up. But after that, I drop into GRUB and a prompt. That is all. How shall I solve this problem? I am thinking of booting from... (2 Replies)
Discussion started by: kebabbert
2 Replies

8. Solaris

Disk controller reassignment

Hi The scenario in the oracle t4-1 hardware with solaris 10 is as follows: 1. The initial install on the server was performed with an incorrect disk layout. 2. New disks were ordered and slot into the server. 3. The disks are allocated a controller and a disk number based on the disk or... (13 Replies)
Discussion started by: kerrygold
13 Replies

9. UNIX for Beginners Questions & Answers

How to extend a disk in veritas volume manager in veritas cluster?

Hi Experts, I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system. #hastatus -sum -- System State Frozen A node1 running 0 A node2 running 0 -- Group State -- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies

10. Solaris

Disks are not visible in Veritas Volume manager

Hi I have created a new setup for VCS for doing some testing on virtual box. After creating 3 Solaris 10 machine (147148-26) with VCS. Here I have used one machine as ISCSI Storage. VCS Version is bash-3.2# /opt/VRTS/bin/haclus -value EngineVersion 6.0.10.0 bash-3.2# bash-3.2# pkginfo... (4 Replies)
Discussion started by: hb00
4 Replies
SYSTEMD-NETWORKD-WAIT-ONLINE.SERVICE(8) 		     systemd-networkd.service			   SYSTEMD-NETWORKD-WAIT-ONLINE.SERVICE(8)

NAME
systemd-networkd-wait-online.service, systemd-networkd-wait-online - Wait for network to come online SYNOPSIS
systemd-networkd-wait-online.service /lib/systemd/systemd-networkd-wait-online DESCRIPTION
systemd-networkd-wait-online is a one-shot system service that waits for the network to be configured. By default, it will wait for all links it is aware of and which are managed by systemd-networkd.service(8) to be fully configured or failed, and for at least one link to gain a carrier. OPTIONS
The following options are understood: -i, --interface= Network interface to wait for before deciding if the system is online. This is useful when a system has several interfaces which will be configured, but a particular one is necessary to access some network resources. This option may be used more than once to wait for multiple network interfaces. When used, all other interfaces are ignored. --ignore= Network interfaces to be ignored when deciding if the system is online. By default, only the loopback interface is ignored. This option may be used more than once to ignore multiple network interfaces. --timeout= Fail the service if the network is not online by the time the timeout elapses. A timeout of 0 disables the timeout. Defaults to 120 seconds. SEE ALSO
systemd(1), systemd-networkd.service(8) systemd 237 SYSTEMD-NETWORKD-WAIT-ONLINE.SERVICE(8)
All times are GMT -4. The time now is 02:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy