09-24-2009
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 commands
boot: defbootstr link=mdac
boot: ahslink
boot: defbootstr ahslink=mdac Sdsk=mdac(0,0,0,1)
boot: defbootstr ahslink=mdac Sdsk=mdac(0,0,1)
but these command are not working.....
plz help me.. i want to solve the problem with in 2days..
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
CS(1) The Canonical Csound Reference CS(1)
NAME
cs - Starts Csound with a set of options that can be controlled by environment variables, and input and output files determined by the
specified filename stem. .
DESCRIPTION
Starts Csound with a set of options that can be controlled by environment variables, and input and output files determined by the specified
filename stem.
SYNTAX
cs [-OPTIONS] <name> [CSOUND OPTIONS ... ]
INITIALIZATION
Flags:
o - OPTIONS = OPTIONS is a sequence of alphabetic characters that can be used for selecting the Csound executable to be run, as well as
the command line flags (see below). There is a default for the option 'r' (selects real-time output), but it can be overridden.
o <name> = this is the filename stem for selecting input files; it may contain a path. Files that have .csd, .orc, or .sco extension are
searched, and either a CSD or an orc/sco pair that matches <name> the best are selected. MIDI files with a .mid extension are also
searched, and if one that matches <name> at least as close as the CSD or orc/sco pair, it is used with the -F flag.
NOTE
The MIDI file is not used if any -M or -F flag is specified by the user - new in version 4.24.0) Unless there is any option (-n or
-o) related to audio output, an output file name with the appropriate extension is automatically generated (based on the name of
selected input files and format options). The output file is always written to the current directory.
NOTE
file name extensions are not case sensitive.
o [CSOUND OPTIONS ... ] = any number of additional options for Csound that are simply copied to the final command line to be executed.
The command line that is executed is generated from four parts:
1. Csound executable (possibly with options). This is exactly one of the following (the last one has the highest precedence):
o a built-in default
o the value of the CSOUND environment variable
o environment variables with a name in the format of CSOUND_x where x is an uppercase letter selected by characters of the -OPTIONS
string. Thus, if the -dcba option is used, and the environment variables CSOUND_B and CSOUND_C are defined, the value of CSOUND_B
will take effect.
2. Any number of option lists, added in the following order:
o either some built-in defaults, or the value of the CSFLAGS environment variable if it is defined.
o environment variables with a name in the format of CSFLAGS_x where x is an uppercase letter selected by characters of the -OPTIONS
string. Thus, if the -dcba option is used, and the environment variables CSFLAGS_A and CSFLAGS_C are defined as '-M 1 -o dac' and
'-m231 -H0', respectively, the string '-m231 -H0 -M 1 -o dac' will be added.
3. The explicit options of [CSOUND OPTIONS ... ].
4. Any options and file names generated from <name>.
NOTE
Quoted options that contain spaces are allowed.
EXAMPLES
Assuming the following environment variables:
CSOUND = csoundfltk.exe -W
CSOUND_D = csound64.exe -J
CSOUND_R = csoundfltk.exe -h
CSFLAGS = -d -m135 -H1 -s
CSFLAGS_D = -f
CSFLAGS_R = -m0 -H0 -o dac1 -M "MIDI Yoke NT: 1" -b 200 -B 6000
And a directory that contains:
foo.orc piano.csd
foo.sco piano.mid
im.csd piano2.mid
ImproSculpt2_share.csd foobar.csd
The following commands will execute as shown:
cs foo => csoundfltk.exe -W -d -m135 -H1 -s -o foo.wav
foo.orc foo.sco
cs foob => csoundfltk.exe -W -d -m135 -H1 -s
-o foobar.wav foobar.csd
cs -r imp -i adc => csoundfltk.exe -h -d -m135 -H1 -s -m0 -H0
-o dac1 -M "MIDI Yoke NT: 1"
-b 200 -B 6000 -i adc
ImproSculpt2_share.csd
cs -d im => csound64.exe -J -d -m135 -H1 -s -f -o im.sf
im.csd
cs piano => csoundfltk.exe -W -d -m135 -H1 -s
-F piano.mid -o piano.wav
piano.csd
cs piano2 => csoundfltk.exe -W -d -m135 -H1 -s
-F piano2.mid -o piano2.wav
piano.csd
CREDITS
Author: Istvan Varga
Jan 2003
AUTHORS
Barry Vercoe
MIT Media Lab
Author.
Dan Ellis
MIT Media Lab,
Cambridge
Massachussetts
Author.
COPYRIGHT
5.10 08/01/2011 CS(1)