01-28-2015
Did you try entering "boot" and hitting "enter"?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
This last monday the inittab file became corrupted and the server refused to start... A set of boot / root disks made from another SCO server saved the day.. Anyway, I would like to make a set from the production server just so I have a set created from that machine. The command I would be using is... (1 Reply)
Discussion started by: LowOrderBit
1 Replies
2. UNIX for Dummies Questions & Answers
hello guys.
I just installed SCO 5.0.6 OpenServer it went all the way to the end of the installation and the first boot try it gave me this message.
not a directory
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot (2 Replies)
Discussion started by: josramon
2 Replies
3. UNIX for Advanced & Expert Users
Hi friends,
i am getting the following error while booting my system which has SCo UNIX .
=========================
H iinit
PANIC: srmountfun-Error 22
mounting of rootdev hd(1/42)
cannot dump 40863 pages to dempdev hd(1/41) : Space for only 0 pages.
Dump not completed.
safe to power off... (3 Replies)
Discussion started by: sveera
3 Replies
4. SCO
hi, i m a newbie and installed sco unix on my machine. Also i installed win-xp. i tried to modify the boot.ini file but it does not give me a choice in the begining.
please guide me on this. do we get a boot loader for unix like LILO or GRUB?
:confused: (3 Replies)
Discussion started by: 187final
3 Replies
5. UNIX for Dummies Questions & Answers
I have been passed a SCO OS5 server that will not boot up, Im a UNIX starter to say the least, So I was wondering if Im dealing with something simple and I dont know it!
The server starts up to the Boot prompt and in either multiple or single mode it will stop during the boot process and wait. ... (0 Replies)
Discussion started by: cscmsupport
0 Replies
6. UNIX for Dummies Questions & Answers
Just installing 5.0.5 on a DELL OPTIFLEX GX520. Using a 40GB IDE Drive.
Installation appeared to work but on rebooting it hangs at the "LOADING KERNEL hd(40)unix.bss
Any ideas please (1 Reply)
Discussion started by: farmacy
1 Replies
7. SCO
Hello those more knowledgeable than I:
I have been trying to get xp and SCO to coexist on the same system. I have tried several different ways to make both work, here's the list:
-install xp, image it, move the partition to the end of drive, verify it boots, image again,
-boot off of SCO... (6 Replies)
Discussion started by: stay0ut
6 Replies
8. SCO
Our system is not booting up properly. It keeps going to this screen:
Enter Run Level (0-6, s or S):
I tried to hit all nos# 0-6 is just goes to hung state.
Tried s or S & it brings me to single user mode. I've checked the file systems & found out that all three had 98%. I tried to... (86 Replies)
Discussion started by: jedimaster
86 Replies
9. SCO
hi
i have image SCo Unix 5.0.6 and I want transfer on my HP ML350 G5
after Transfer show this message :
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot
this hp server used smart array E200i and P400 and sco not recognized HDD
tanks (7 Replies)
Discussion started by: moein.mojtaba
7 Replies
10. UNIX for Beginners Questions & Answers
We have a legacy system that runs on SCO OpenServer 5.0.6, and I've rebuilt the server a couple of times so we can have access to old historical data. That system suddenly went offline for no known reason, and I know that the configuration has not been altered, there is nobody with access to the... (63 Replies)
Discussion started by: spock9458
63 Replies
consvar(8) System Manager's Manual consvar(8)
NAME
consvar - Manipulate system firmware console environment variables
SYNOPSIS
/sbin/consvar [-v] [-nc] -g -s -l -a -d [variable] [value]
OPTIONS
Verbose mode. Prints out the system IDs used by firmware, the current firmware revision, and information about the process. Get the value
of the specified console environment variable. Set the value of the specified console environment variable. List the values of all vari-
ables supported by this platform that are not disabled. This is similar to the show SRM console command. Save the values of all environ-
ment variables to non-volatile storage. Setting a variable with the -s option only updates the in-memory copy of console environment vari-
ables. The save process could take a long time on some platforms, so it is recommended that the variables are saved after all set opera-
tions have been performed. List the system and exception database information. Do not perform value conversion. Variables that contain
device information have an underlying console bootstring format. If this option is used, consvar does not convert between the Tru64 UNIX
names for these devices, but accepts and displays the raw values. The same goes for integer values which are converted between strings and
hexadecimal values.
DESCRIPTION
Use the consvar command to get, set, list, and save console environment variables available on SRM system firmware. Some firmware versions
on some platforms do not comply with the Alpha SRM when dealing with certain variables, or operations. To ensure UNIX functionality with
such firmware, an exception database is consulted and these operations are disabled. By default, consvar accepts and displays device values
with Tru64 UNIX device names, or their device special file names. The raw console bootstrings can be used by providing the -nc option. For
information regarding the console environment variables, please refer to the Alpha System Reference Manual.
RETURN VALUES
Success. Failure.
EXAMPLES
To show the values of all available console variables, enter: % consvar -l To get the value of the booted_dev variable, enter: % consvar -g
booted_dev
A message similar to the following will be displayed: booted_dev = disk0 To set the value of boot_dev, enter the device name of the
required boot device: % consvar -s boot_dev disk0
To save the values of the variables across system resets, enter: % consvar -a If an operation fails, you can find out if it is dis-
abled by using the -v option. For example, to see if the bootdef_dev variable is disabled, enter: % consvar -v -g bootdef_dev The
exception database can be printed out along with the status of the current platform's console variable support by entering: %
consvar -v -d
FILES
Specifies the command path. Exception database.
SEE ALSO
Functions: getsysinfo(2), setsysinfo(2)
consvar(8)