Solaris 10 Instal Error on V480: svc.configd malformed integer

[rhcole]

I am having problems installing Solaris 10 on a SunFire V480.
When booting, a relatively new Sol 10 DVD image, a 3/05 DVD, or a NET boot image,
the messages are slightly different, however, the problem is the same.
I saw that someone in this news group solved this by installing Solaris 9....
But that is not what i wanted!

I have patched the firmware to version 4.22.34,
but that did not change anything.

Any suggestions?
Regards,
Richard

Output from console:

SunOS Release 5.10 Version Generic_120011-14 64-bit
Copyright 1983-2007 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Configuring devices.
Using RPC Bootparams for network configuration information.
Attempting to configure interface ge0...
svc.configd: Fatal error: malformed integer "               35.75"
Dec 11 07:34:52 svc.startd[7]: Failed to add svc:/system/install-setup:default (Software caused connection abort).
svc.startd: Unable to bind a new repository handle: repository server unavailable
svc.configd: Fatal error: /etc/svc/volatile/svc_nonpersist.db: integrity check failed. Details in /etc/svc/volatile/db_errors
Dec 11 07:34:52 svc.startd[44]: restarting after interruption
svc.configd: Fatal error: /etc/svc/volatile/svc_nonpersist.db: integrity check failed. Details in /etc/svc/volatile/db_errors
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
svc.configd exited with status 102 (database initialization failure)
#

[DukeNuke2]

try a newer solaris 10 version (latest is 10 8/07!) and separte ALL network cable from your machine. boot from dvd and try again...

[rhcole]

So, Disconnecting the network cables....
and trying my "newer" (i think 8/07, will check this evening) Image in the DVD
gives the following result.

On the side: Solaris 9 works fine. I was able to set up the T300 raid using Sol 9.
Regards,
Richard

                                                                     
Rebooting with command: boot cdrom
Boot device: /pci@8,700000/ide@6/cdrom@0,0:f  File and args:
SunOS Release 5.10 Version Generic_120011-14 64-bit
Copyright 1983-2007 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Configuring devices.
Using RPC Bootparams for network configuration information.
Attempting to configure interface ce1...
Skipped interface ce1
Attempting to configure interface ce0...
SUNW,pci-gem0: Could not Establish Link -- Check if the cable is plugged in.
Skipped interface ce0
Attempting to configure interface ge0...
SUNW,pci-gem0: Could not Establish Link -- Check if the cable is plugged in.
Skipped interface ge0
svc.configd: Fatal error: malformed integer "               97.75"
Dec 11 09:18:36 svc.startd[7]: svc:/system/device/local:default: couldn't note log location: Software caused connection abort
Dec 11 09:18:36 svc.startd[7]: svc:/system/device/local:default: get_method decode instance FMRI failed: connection to repository broken
Dec 11 09:18:36 svc.startd[7]: svc:/system/device/local:default: instance libscf_get_method failed
Dec 11 09:18:36 svc.startd[7]: system/device/local:default failed: transitioned to maintenance (see 'svcs -xv' for details)
svc.configd: Fatal error: /etc/svc/volatile/svc_nonpersist.db: integrity check failed. Details in /etc/svc/volatile/db_errors
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
svc.configd exited with status 102 (database initialization failure)
#

[DukeNuke2]

looks like an defect solaris 10 medium... but i'm not sure!

[rhcole]

I thought so as well, however,
the Sol 10 3/05 comes with just about the same error....

I initially thought it was the drive, however, Sol 9 can be installed via the drive with no problems at all...

Regards,
Richard

[maal]

Hello Richard,

capture the current OBP settings for future reference (printenv, a few systems have hidden settings, that are only displayed with printenv -a) and issue set-defaults.

Sometimes this can resolve weird problems during boot-up. Maybe it doesn't solve your issue, but it's definetely worth a try.

Michael

[rhcole]

           
So I checked and my image is Sol 10 8/07.

And tried your suggestion "set-defaults".
The Network cables are disconnected,
the T300 is disconnected.
The result is not the same, but not much different.... ;-)
The last 4 lines repeat INDEFINITELY....

Any other suggestions?
Advice, where I might also ask?
Regards,
Richard

                                                           
Rebooting with command: boot cdrom
Boot device: /pci@8,700000/ide@6/cdrom@0,0:f  File and args:
SunOS Release 5.10 Version Generic_120011-14 64-bit
Copyright 1983-2007 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
svc.configd: Fatal error: unexpected database change
graph.c:2789: set_dependencies() failed with unexpected error 131.  Aborting.
svc.configd: Fatal error: malformed integer "               25.75"

svc.configd: smf(5) database integrity check of:

    /etc/svc/repository.db

  failed. The database might be damaged or a media error might have
  prevented it from being verified.  Additional information useful to
  your service provider is in:

    /etc/svc/volatile/db_errors

  The system will not be able to boot until you have restored a working
  database.  svc.startd(1M) will provide a sulogin(1M) prompt for recovery
  purposes.  The command:

    /lib/svc/bin/restore_repository

  can be run to restore a backup version of your repository.  See
  http://sun.com/msg/SMF-8000-MY for more information.

Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
svc.configd exited with status 102 (database initialization failure)
svc.startd: Could not exec() sulogin: No such file or directory
Requesting System Maintenance Mode

[maal]

Hello Richard,

Any other suggestions?
Advice, where I might also ask?

Run full diagnostics (setenv diag-switch? true  setenv diag-level max).

Try to boot with the verbose option (boot cdrom -v), maybe the DVD media is bad (use another copy).

If the system is under service contract coverage, open a service case. It's impossible to diagnose this type of problems on a user-to-user forum, the system requires close inspection.

Michael

[Hexxer]

Im not realy sure....but this could be a DVD-rom Hardwareproblem? If the image and the dvd ist ok?
if I remember correctly there are a patch for some dvd roms (firmware) but i dont no for which hardware.

Hxx

[maal]

This does not apply to the ATAPI/IDE Interface Slimline 1/2" Height DVD drive used in the V480.

Some of the early Sun SCSI DVD-ROM (Toshiba SD-M1401) have been delivered with "special" firmware for downward compatibility with Solaris 2.5.1. The blocksize was pre-set to 512 byte, booting from DVD requires a blocksize of 2048 byte (you can read from DVD with 512 byte blocksize, but not boot!). Patch 111649-02 contains a firmware update for these drives.
I learned this the hard way, a second-hand Pioneer drive was jumpered to 512 byte blocksize, booting from Solaris DVD failed, but the DVD was perfectly mountable.

Michael

[Hexxer]

right, Toshiba thats what i mean.

Are these images burned by yourself? How do you check the burned dvd? You can download it again and burn it to an dvd-rw...or burn it slower as the dvd mean.

Hxx