Hardware > Sun SPARC

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

<< < (2/3) > >>

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

Navigation

[0] Themen-Index

[#] Nächste Seite

[*] Vorherige Sete