06-07-2013
Hi hicksd8,
Thanks for the reply.
Its a zfs server and the factory install was done using an incorrect disk configuration (two 600gb disks and two 300gb disks). By the time the server got to me, I needed to reinstall solaris with the correct number of disks, so i added three 300gbSSD disks (for a sybase db) and another 600gb disk for the hotspare pool.
However the solaris install puts the root disk on disk0 (300gb) but at the end of the solaris sys-unconfig, the svm defines disk1 (600gb) as the root mirror.
Ideally, i need my 300gb root disk mirrored to another 300gb disk.
I've moved around the disks physically and tried cfgadm, but no luck.
Do you have any ideas?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello all,
How does the Solaris identifies the controller subscript ? ( like c0txdxs0 or c1txdxsx ?? )
I have a unix box ( Ultra 30) running with 2.5.1.
When I connected an external hard disk to the on-board scsi port, it got identified as c0t1dxsx...
(... (1 Reply)
Discussion started by: shibz
1 Replies
2. Solaris
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
3. Solaris
Dear Solarizer,
If i have a disk let say like this c1t0d0s0
How to change the controller to be come example : c3t0d0s0
Thanxs For your replay
Regads,
tpx (3 Replies)
Discussion started by: tpx99
3 Replies
4. SCO
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. HP-UX
Replace an unknown status controller on HP FC60 disk array
Author:JoyOnline JoyChangLu@gmail.com
Trouble description:
The users detected that the status of controller at A is unknown.
Analysis and diagnostic:
Physical observed all leds on enclosure of disk array is normal.
The... (4 Replies)
Discussion started by: JoyOnLine
4 Replies
6. SCO
I'm "attempting" to install SCO 5.0.7 on an HP ML370 G4 server and am ready to bash the keyboard with head now. I keep getting the error message "WARNING hd: no root disk controller found" when running the bootable install cd.
I have a raid 5 array with an online spare created using 4 36.3 GB... (2 Replies)
Discussion started by: FrictionBurn
2 Replies
7. Solaris
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
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none - - online... (2 Replies)
Discussion started by: kingston
2 Replies
8. SCO
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
9. Solaris
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
10. Solaris
Hi,
I have a Sun Fire V440 server that fails to boot up correctly. A lot of services are not started and the sytems acts really slow to commands. During boot I can see the following Error:
WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1):
SCSI transport failed: reason 'reset': retrying... (15 Replies)
Discussion started by: oliwei
15 Replies
LEARN ABOUT HPUX
vxbootsetup
vxbootsetup(1M) vxbootsetup(1M)
NAME
vxbootsetup - set up system boot information on a Veritas Volume Manager disk
SYNOPSIS
/etc/vx/bin/vxbootsetup [-g diskgroup] [medianame ... ]
DESCRIPTION
The vxbootsetup utility configures physical disks so that they can be used to boot the system. Before vxbootsetup is called to configure a
disk, the required volumes, standvol, rootvol and swapvol (and optionally, dumpvol) must be created on the disk. All of these volumes must
be contiguous with only one subdisk.
The -g option may be used to specify the boot disk group.
If no medianame arguments are specified, all disks that contain usable mirrors of the root, swap, /usr and /var volumes are configured to
be bootable.
If medianame arguments are given, only the disks that are associated with the specified disk names are configured to be bootable.
vxbootsetup requires that:
o The root volume must be named rootvol and must have a usage type of root.
o The swap volume must be named swapvol and must have a usage type of swap.
o The volumes containing /usr and /var (if any) must be named usr and var, respectively.
See the chapter "Recovery from Boot Disk Failure" in the Veritas Volume Manager Troubleshooting Guide for detailed information on how the
system boots and how VxVM impacts the system boot process. The vxmirror, vxrootmir, and vxresize utilities call vxbootsetup automatically.
If you use vxassist, or vxmake and vxplex to create mirrors of the root volume on a disk, you must run vxbootsetup explicitly to make the
disk bootable.
ARGUMENTS
medianame
Specifies the disk name (disk media name) of a VM disk that is to be configured as bootable.
SEE ALSO
disksetup(1M), edvtoc(1M), vxassist(1M), vxevac(1M), vxinstall(1M), vxintro(1M), vxmake(1M), vxmirror(1M), vxplex(1M), vxresize(1M),
vxrootmir(1M)
Veritas Volume Manager Troubleshooting Guide
VxVM 5.0.31.1 24 Mar 2008 vxbootsetup(1M)