Frutool::assert::serialize_conf: <ft_conf.c:544> '0'

System Administration
1

Hi
I use a SUN SPARC 5120 with Solaris 10. The server hangs in the startup. In the end of the startup it says : frutool::assert::serialize_conf: <ft_conf.c:544> '0'. When I use the service port and type : show /SP/faultmgmt/0 it says "No such target". Does anyone know what is checked at line 544 in file ft_conf.c and what I need to do, to get my server to start again. Appreciate all help that I can get. /Johan

2

Welcome!

does the Solaris kernel load and display itself?
Are there some other messages?
Is it really hung? Hit Enter, give it a Ctrl-C.

3

Hi

I have only used the serial service port on the backside of the server. The yellow service LED is OFF. Ethernet is not enabled, so it seems to be hanging after failing with some test. I will try to connect a terminal and reboot the system, and then try Your suggestion. /Johan

4

What do the show /SYS and show /SYSTEM (two different sets of output) commands show on the ILOM?

Is the main CPU powered on? Or is just the ILOM running?

If the main CPU isn't powered on, what happens when you running the following commands (answering yes when asked)?

start /SYS
start /HOST/console

5

Hi

Thanks for helping me.

The power is on and I am using the ILOM.
I have used the command that You suggest, but in the end of the startup the prompt hangs in the console window, and I can not reach the server or the files.
According to what I can see the system says that all hardwares are OK.
The problem is that the network LEDs are turned on, on the IP port, but it is not possible to ping the server, only the service port which is on a separate card with a separate IP address answers. The IP addresses are on the same subnet so if one answers the other one should also answer on ping.
I still believe that the assert messages has something to do with the hanging of the console window.

regards
Johan

6

What is the last thing that you see after running start /HOST/console?

There are a lot of things that could go wrong between the start /SYS command and Solaris responding to pings. Anything between configuration and hardware problems.

7

Hi
I have discovered that the problem is that the root disk is broken.
Thanks for all answers.
/Johan