Sponsored Content
Operating Systems SCO Warning HD: no root disk controller was found Post 302356183 by mselvaprakash on Thursday 24th of September 2009 09:43:46 PM
Old 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

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

warning:hd:no root disk controler was found

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

[Joy Share] - Replace an unknown status controller on HP FC60 disk array

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

SCO 5.0.7 no root disk controller found error during install

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

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 # vxdisk list DEVICE TYPE DISK GROUP STATUS c0t0d0s2 auto:none - - online... (2 Replies)
Discussion started by: kingston
2 Replies

6. 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

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

Lost Root Password on VXVM Encapsulated Root Disk

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

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

10. Solaris

Sun Fire v440 Hard disk or controller broken? WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1)

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
vxreattach(1M)															    vxreattach(1M)

NAME
vxreattach - reattach disk drives that have once again become accessible SYNOPSIS
/etc/vx/bin/vxreattach [-br ] [accessname...] /etc/vx/bin/vxreattach -c accessname DESCRIPTION
The vxreattach utility reattaches disks to the disk group they were in and retains the same media name. This operation may be necessary if a disk has a transient failure, or if Veritas Volume Manager (VxVM) starts with some disk drivers unloaded and unloadable. Disks then enter the failed state. If the problem is fixed, vxreattach may be able to reattach the disks without plexes being flagged as stale, as long as the reattach happens before any volumes on the disk are started. vxreattach tries to find a disk in the same disk group with the same disk ID for the disk(s) to be reattached. The reattach operation may fail even after finding the disk with the matching disk ID if the original cause (or some other cause) for the disk failure still exists. vxreattach is usually invoked by vxdiskadm when performing disk recovery. It is not intended to be run directly by an administrator. OPTIONS
-b Performs the reattach operation in the background. -c Checks if a reattach is possible. No operation is performed, but the name of the disk group and disk media name at which the disk can be reattached is displayed. -r Tries to recover stale plexes of any volumes on the failed disk. It does this by calling vxrecover. EXIT CODES
A zero exit status is returned if the reattach is performed; non-zero is returned otherwise. See vxintro(1M) for a list of standard exit codes. EXAMPLES
Check if reattachment of disk c1t2d0 is possible: /etc/vx/bin/vxreattach -c c1t2d0 If reattachment is possible, vxreattach returns with an exit status of 0 and displays the disk group name and disk media name. If reat- tachment is not possible, vxreattach returns an exit status of 2 and displays an error. Attempt to reattach the disk in the foreground and try to recover stale plexes of any volumes on the disk: /etc/vx/bin/vxreattach -r c1t2d0 If the reattachment is successful, vxreattach returns an exit status of 0. Otherwise, if an error occurs, vxreattach returns a non-zero exit code as defined on vxintro(1M). FILES
/etc/default/vxplex Standard defaults file that can be used to determine whether FastResync is used when attaching plexes. See vxplex(1M) for details. SEE ALSO
vxdiskadm(1M), vxintro(1M), vxplex(1M), vxrecover(1M) VxVM 5.0.31.1 24 Mar 2008 vxreattach(1M)
All times are GMT -4. The time now is 09:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy