On 7/31/06, Ganesh Hiregoudar <Ganesh.Hiregoudar at sun.com> wrote:
>
> gavin wrote:
> > Machine: SunBlade 1500
> > OS: Solaris10 Sparc
> >
> > 1. reboot my machine
> >
> > 2. output messages as below repeatdly, and user can not enter into
> Maintaince mode:
> > 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
> >
> > 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.
> > 3. According to "http://sun.com/msg/SMF-8000-MY";, sulogin will be
> lauched, so user can enter into Maintaince mode to execute recoverery. But
> sulogin is not launched, so user can to enter into Maintaince mode.
> >
> > 4. Insert Solaris DVD into cdrom, then "boot cdrom", also get the same
> result as step 2
> >
> > 5. "Boot net" via JumpStart, also get the same result as step 2
> >
> >
> Did you try with "boot milestone=none" at OK prompt.
> This will give you more debug messages and start recover the corrupted
> db by running the following
>
> /lib/svc/bin/restore_repository
>
>
> Regards
> Ganesh.
>
Hi,
I am facing the similar issue right now, and I tried so many things like
booting into single root shell via net jumpstart, booting into single user
mode, but then the looped messages would not stop even when I give the
correct root password... it just does not let me IN to the maintenance
shell. Ugly and Pathetic.
Could there any problem that could be with my 2 disks that are under svm?
and more importantly that I notice the fsck messages. Any ideas what should
I be doing with them? Please suggest.
---------
NOTICE: /: unexpected free inode 2147, run fsck(1M)
NOTICE: /: unexpected free inode 2147, run fsck(1M)
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)
Root password for system maintenance (control-d to bypass):
single-user privilege assigned to /dev/console.
Entering System Maintenance Mode
Aug 21 02:29:46 su: 'su root' succeeded for root on /dev/console
NOTICE: /: unexpected free inode 2147, run fsck(1M)
NOTICE: /: unexpected free inode 2147, run fsck(1M)
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)
Root password for system maintenance (control-d to bypass):
NOTICE: /: unexpected free inode 2147, run fsck(1M)
NOTICE: /: unexpected free inode 2147, run fsck(1M)
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)
-------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/smf-discuss/attachments/20070821/4adf68af/attachment.html>
