I new to the forums....and I'm new to Solaris and Linux...I just got Solaris 9 and I finally managed to install it; I bought a brand new hard drive.

Everything was working yesterday, I accessed files, looked up help files, and all....but I could not find a "Shut Off" option....I had to log out and mannualy "turn off" my computer by pressing the off switch.

I went to turn it on today, it boots up, kinda....it stops on this white screen right before the log-on screen and asks me for some kind of level to use 0-6, s or S, but I dont kno what to do....can anyone help me?!

Thanks in Advance, Thorrn4!

Enter 3. It boots up the machine in multi-user mode and makes all resources available over the network. Read the man page of "init" as soon as you login; it helps you understand the run levels 0 to 6 and s/S

The command to shut the machine down is: "shutdown" Or "init 5". So, more man pages to read

In case if you are not aware of Solaris 10, please have a look at http://www.sun.com/software/solaris/ web page. Solaris 10 is the new (free) OS with lots of good features, compared to many of the contemporary operating systems

EnjOy!

I tried it...still won't boot...I wrote down some information on the page, maybe it can be clearer:

Warning - unable to repair the /filesystem. Run fsck mannually (fsck -F utf /dev/rdsk/c1d0s0).........

Enter Run level (0-6, s or S) [3]: 3 **I typed in the last "3"**

INIT cannot create /var/adm/utmpx
INIT SINGLE USER MODE




Also...what is "man pages" and where do I type "shutdown"? (I've never used UNIX before)

Thank you!!

Huh! looks like your file system was screwed due to the abrupt (windows style ) shutdown ie., hitting the power off button without using graceful shutdown command

So, try to repair the file system with the following sequence of steps (in case if you haven't observed it carefully, Solaris OS being helpful with the error message and showed some commands to run inorder to fix the problem):

1) Enter single user mode. To get there, power up the machine and type "s" Or "S" at "Enter Run level (0-6, s or S) [3]: " prompt
2) Once you are there, type "fsck -F utf /dev/rdsk/c1d0s0" to check and repair the file system
3) If step(2) succeeds, type "init 3" to enter multi-user mode and to get the graphical login screen

>>> Also...what is "man pages" ...
man pages show information pertaining to a command of interest (kinda online help page). For example, if you want to know how to use "ls" command or the available options for "ls", simply type "man ls" in a terminal window. It displays information something like:

% man ls
User Commands ls(1)

NAME
ls - list contents of directory

SYNOPSIS
/usr/bin/ls [-aAbcCdeEfFghHilLmnopqrRstux1@] [file...]

/usr/xpg4/bin/ls [-aAbcCdeEfFghHilLmnopqrRstux1@] [file...]

/usr/xpg6/bin/ls [-aAbcCdeEfFghHilLmnopqrRstux1@] [file...]

DESCRIPTION
For each file that is a directory, ls lists the contents of
the directory. For each file that is an ordinary file, ls
repeats its name and any other information requested. The
output is sorted alphabetically by default. When no argument
is given, the current directory is listed. When several
arguments are given, the arguments are first sorted
appropriately, but file arguments appear before directories
and their contents.
....
....

If you want to read the man pages with a browser, please visit: http://docs.sun.com/app/docs/coll/40.16

>>> and where do I type "shutdown"?
You have to type it on a terminal console with "root" privileges to shut the machine down.

Moral of the story:
Do not use your strength to shutdown a UNIX box, but use the commands provided for such a task

THANK YOU!!! I'll try it out as soon as I know where the terminal console is located....can anyone help me with that?
(I kno that should kno what and where it is...but I guess that it doesnt take much to install Unix )

after I type ''fsck.....'' i got an error [b]fsck: opperaton not applicable to FSType utf

WHAT NOW?!

Oh!! I must have copy/pasted the fsck command from the error message you posted earlier; my mistake

It must be "fsck -F ufs /dev/rdsk/c1d0s0", where UFS is the default file system on Solaris

>>> ... as soon as I know where the terminal console is located
terminal console, terminal window, console window, terminal, console, command line window etc., are pretty much used interchangeably to refer to a command based window where you can type commands. To open it up: right click on the desktop and select Hosts -> Terminal Console Or This Host under workspace popup menu

And when you are typing fsck .. etc., commands during bootup, you are doing it on a console window

it still does not work....here is what I do/get:

I typed in fsck -F ufs /dev/rdsk/c1d0s0
it goes through Phase 1-4
...ADJUST? init 3 (I put in init 3)
**Phase 5 - ...........
FILE SYSTEM STATE IN SUPERBLOCK IS WRONG; FIX? WHAT DO I PLACE HERE?!?! (I placed yes and then enter) and it brought be to the:
#
I placed exit and then CTRL+D to the prompt:
ENTER RUN LEVEL: 3
INIT cannot create /var/adm/utpx
INIT single user mode

Next step is to try "fsck -y". With -y option, fsck assumes a "Yes" response to all the questions it is going to ask

Then run "mountall" command to mount all file systems and proceed to "init 3"

If none of these works, run "fsck -y" , followed by "reboot"

try man fsck,

You will need th -y option, you may need to use another superblock. The man pages tell you how to do this cause I cant remember right now.

It will not hurt to use another superblock. The super block is important as it stores important information about the structure of your disk. If it is corrupted you would not be able to recover. However Solaris have thought of this and as it is so important they copy it all over the disk. Found by running newfs with -Nv options. look at the -o options in the man pages.

Also you should boot into single user first. Boot off the cdrom.

Hope that helps,
neil.

thanx for all your help guys...I reinstalled Solaris; the problem was fixed, I did a fresh install; thanx for the support though!

I have another problem...but for another topic, thank you once again

Wow,

You will need to do a fsck again in the future at some point. Next time you may not be able to just re-install the system.

Still glad you got it working.

neil.