09-24-2009
there are three disk they are
" Segate cheetah Model no: ST318406LC ultra3 SCSI 10k 18GB "
three disk are same disk
10 More Discussions You Might Find Interesting
1. 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
2. SCO
hi all
i use sco open server reliseas 5 on my system i get an image from system hard disk to another hard disk with acronis software and start system with new(backup)hard disk, but during the boot process some errors generate as follow
warning:hd:noroot disk controler was found
hd:a boot-time... (2 Replies)
Discussion started by: mehran_malek
2 Replies
3. 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
4. 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
5. 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
6. 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
7. 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
8. Solaris
Hi All
Hope it's okay to post on this sub-forum, couldn't find a better place
I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies
9. Solaris
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
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
vximportdg
vximportdg(1M) vximportdg(1M)
NAME
vximportdg - import a disk group into the Veritas Volume Manager configuration
SYNOPSIS
vximportdg daname new_dgname
DESCRIPTION
The vximportdg utility performs a temporary import of the disk group contained on the disk device specified by daname to the disk group
specified by new_dgname. As the persistent disk group information is not changed within the private partition of the affected disk, the
import is only valid for the duration of the bootload or until a vxdg deport is performed.
ARGUMENTS
daname Specifies the device name (disk access name) of one of the member disks of the disk group to be imported. The other members are
imported automatically.
new_dgname
Specifies the disk group to be imported.
USAGE
One reason to use the vximportdg utility is to import a second generation of the rootdg disk group so that its objects are available for
use while a system is running on a different rootdg. To prevent volumes on the second generation rootdg from having the same device minor
numbers as volumes (such as rootvol) on the active rootdg, the importation assigns temporary non-conflicting device minor numbers. If this
occurs, vximportdg outputs warning messages detailing the mapping of the minor numbers.
SEE ALSO
vxdg(1M)
VxVM 5.0.31.1 24 Mar 2008 vximportdg(1M)