UNIX for Beginners Questions & Answers

I saw your new thread. You cannot fsck the filesystem you are booted from. If you need to fsck your root filesystem you should take your system down, boot it from your distribution media (DVD):

Code:

ok> Boot cdrom -s

and when in single user, issue the fsck command on your hard disk root filesystem.

I'll follow this with another post pertaining to this original thread.

My response to your thread "No login from SP" is this.

Before you create a thread like this you should fully understand the hardware platform you are dealing with by reading the supplied documentation. Posting here when you don't have knowledge of the platform is not a lot of good.

Now having been very critical, which doesn't help you much, I'm now going to give you some generic starting notes with regards to Sun kit. What I'm about to write is generic for Sun SPARC kit and may not directly apply to your platform; however, most of it will.

1. What you have there is a main SPARC system (Let's call it the System) and an underlying (Linux/Unix) system called the Service Processor SC (let's call it the Appliance) which can run diagnostics on and control the System.

2. The Appliance boots as soon as power volts is supplied. It doesn't have an on/off switch. So anything you see on a screen connected to SER-MGT port when you apply volts to the chassis is from the Appliance (up to a point).

3. When the Appliance has booted you will get an OK> prompt. Here you can login (if you know the password which is different from the Solaris root password). You can type 'help' to get a list of commands. One such command is "poweron" or "power on" which will turn power on to the System. Once that is done you can give the command 'boot'.

4. Now when you are on the console connected to the SER-MGT port you can talk to either the Appliance or the System. If you are talking to the Appliance giving the command:

Code:

ok> console

will switch you to the System (Solaris OS if it's running), and if you are talking to Solaris typing:

Code:

 
 #.  <no return needed>

will drop you back to the Appliance (Service Processor ok> prompt).
When everything is running properly you can switch between the two at will.

5. So it's not difficult to see that if you are connected to the System and you have not issued any command to the Appliance to power the system up, then you are talking to fresh air and will get no response whatsoever.

I suggest that you read the documentation about Sun Service Processors, etc to understand that you have two separate systems there; the Appliance and the System. The first controls the second.

However, don't let that put you off posting further questions here. You will soon get it.

Hope that helps.