Sponsored Content
Operating Systems SCO Warning HD: no root disk controller was found Post 302356061 by mselvaprakash on Thursday 24th of September 2009 11:54:00 AM
Old 09-24-2009
i hav used tis command also but it's still not working dude........
 

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
tis(3)							     Library Functions Manual							    tis(3)

NAME
tis, tis_intro - Introduction to Thread-Independent Services (tis) DESCRIPTION
Thread-independent services (tis) routines compose a Compaq-proprietary interface to the DECthreads multitasking library. The tis inter- face provides services that assist with the development of thread-safe libraries. Thread synchronization can involve significant run-time cost, which is undesirable in a nonthreaded environment. In the nonthreaded envi- ronment, the tis interface enables you to build thread-safe libraries that are efficient, yet provide the necessary synchronization when called from a threaded environment. When threads are not active within the process, tis routines execute only the minimum steps necessary: code running in a nonthreaded envi- ronment is not burdened by the run-time synchronization that is necessary when the same code is run in a threaded environment. When threads are active, tis routines provide the necessary thread-safe synchronization. The tis objects created using this interface are fully interchangeable with DECthreads Pthreads (POSIX 1003.1c) objects. So, a mutex can be created by using static initialization (or using tis_mutex_init(3)) and can be locked, the DECthreads core library (libpthread.so) sub- sequently activated, and the mutex unlocked. Keys created by tis_key_create(3) are valid when a threaded run-time environment is loaded. Note that errno is NOT used by the tis routines. To indicate errors, the tis routines return integer values indicating the type of error. In a nonthreaded environment, condition variables should not be used to guard operations (for example, with tis_cond_wait(3)). In a threaded environment, the guidelines for using the DECthreads Pthread routines also pertain to the use of the corresponding tis routine. The tis routines can be classified into the following associated groups: General routines Thread cancellation routines Thread-specific data key routines Mutex routines Condition variable routines Read-write lock routines General Routines Obtains a value representing a desired expiration time. Calls a one-time initialization routine that can be executed. Obtains the identi- fier of the calling thread. Thread Cancellation Routines Changes the calling thread's cancelability state. Creates a cancellation point in the calling thread. Thread-Specific Data Key Routines Obtains the data associated with the specified thread-specific data key. Generates a unique thread-specific data key. Deletes a thread- specific data key. Sets the value associated with the specified thread-specific key. Mutex Routines Locks the DECthreads global mutex. Destroys the specified tis mutex object. Initializes a tis mutex object. Locks the specified tis mutex if not already locked. Tries to lock the specified tis mutex. Unlocks the specified tis mutex. Unlocks the DECthreads global mutex. Condition Variable Routines Wakes all threads waiting on the specified condition variable. Destroys the specified condition variable object. Initializes a condition variable object. Wakes at least one thread that is waiting on the specified condition variable. Causes the calling thread to wait for the specified condition variable to be signaled or broadcast, such that it will awake after a specified period of time. Causes the calling thread to wait for the specified condition variable to be signaled or broadcast. Read-Write Lock Routines Acquires the specified read-write lock for read access. Attempts to acquire the specified read-write lock for read access; returns immedi- ately if already locked. Unlocks the specified read-write lock already acquired for read access. Destroys the specified read-write lock object. Initializes a read-write lock object. Acquires the specified read-write lock for write access. Attempts to acquire the specified read-write lock for write access; returns immediately if already locked. Unlocks the specified read-write lock already acquired for write access. delim off delim off tis(3)
All times are GMT -4. The time now is 02:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy