Sco Unix HFS file system error


 
Thread Tools Search this Thread
Operating Systems SCO Sco Unix HFS file system error
# 1  
Old 03-19-2012
Network Sco Unix HFS file system error

HI,

I have sco unix server currently i am trying to boot its not booting and giving error as HTFS error message contains -
Code:
Warning : can not identify block 496 for i number 438 on HTFS dev hd (1/42).
Warning : exit - /etc/init (PID 1) died, status 0x0000008B

server is not getting boot sicen three months please help me to get rid of this issue.

Last edited by vbe; 03-20-2012 at 10:19 AM..
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

UNIX SCO release 5.05 system does not boot

UNIX sco release 5.05 system does not boot: cannot open device hd(40)/boot stage 1 boot failure: error loading hd(40)/boot what to do? (5 Replies)
Discussion started by: Joaoalpande
5 Replies

2. SCO

UNIX SCO release 5.05 system does not boot

UNIX sco release 5.05 system does not boot: cannot open device hd(40)/boot stage 1 boot failure: error loading hd(40)/boot what to do? (1 Reply)
Discussion started by: Joaoalpande
1 Replies

3. UNIX for Dummies Questions & Answers

Error UNIX: UNIX SCO release 5.05 system does not boot

UNIX sco release 5.05 system does not boot:cannot open device hd(40)/boot stage 1 boot failure: error loading hd(40)/bootWhat to do? (2 Replies)
Discussion started by: Joaoalpande
2 Replies

4. SCO

Read and write into file system from SCO

hi Knows someone what kind of file system uses SCO Unix 5.0.6? Which linux or unix LIVE CD can read and write into file system from SCO Unix? I've tried to boot SCO using Knoppix 6.2.1 LIVE CD, but cannot mount. # mount -t sysv /dev/sda1 /mnt mount: wrong fs type, bad option, bad superblock... (2 Replies)
Discussion started by: ccc
2 Replies

5. SCO

SCO Server: /u file system missing

Hello All, I have a SCO Unix server and when I do the command "df -kP" I get the following: Filesystem 1024-blocks Used Available Capacity Mounted on /dev/root 2048000 934936 1113064 46% / /dev/boot 15360 6419 8941 42% /stand It should say Filesystem 1024-blocks Used Available... (4 Replies)
Discussion started by: mikep9
4 Replies

6. UNIX for Dummies Questions & Answers

unix system v release 3.2 (sco-unix?)

another unix printing issue. our client based pc's used to print some form's to our hp printer. as of the moment they can not print. i have checked & did the ff: #lpstat -r (scheduler is running) i dunno if i need to restart the whole unix box via shutdown or just checking at... (15 Replies)
Discussion started by: jedimaster
15 Replies

7. UNIX for Dummies Questions & Answers

Limit number of user accessing to SCO UNIX System

Hi, In my company, we are using SCO UNIX system and Informix database. Recently, there have been a lot of users accessing to server and sometimes it has made server run very slow. So, I intend to limit number of users of 30 only. Although I have tried to search on the Internet for several days,... (1 Reply)
Discussion started by: trinhnguyen
1 Replies

8. SCO

UNIX SCO based Healthcare system

Hi Guys I have got a problem and I would really be grateful if some1 could sort out the problem. I have got a healthcare system named MEDISCAN, its SCO Unix based system, I need to convert the data files into ORACLE data. The problem is that I have been unable to open the files, whatever... (1 Reply)
Discussion started by: Faysal_Mazhar
1 Replies

9. Filesystems, Disks and Memory

SCO TCP/IP runtime System for SCO Unix

Hi everyone i have a question for all of you. It may be basic or it may be a good one. I recently aquired a copy of "SCO TCP/IP runtime System for SCO Unix" (thats what the disks say) and for the life of me i can not get it to load. i have tried opening the disk in linux and it can not determine... (0 Replies)
Discussion started by: Cerberus
0 Replies

10. UNIX for Dummies Questions & Answers

SCO UNIX System V/386, Release 3.2

I was just wondering if there is a way to recursive grep for something in this version of UNIX... so that I don't have to do it a directory at a time? (1 Reply)
Discussion started by: PBNOSGT
1 Replies
Login or Register to Ask a Question
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.07 06/23/2009 CS(1)