Disk/SVM related issues are not out of the question but I think you're probably seeing
http://bugs.opensolaris.org/view_bug.do?bug_id=6454468 and its friend http://bugs.opensolaris.org/view_bug.do?bug_id=6595328 To confirm, boot from Solaris CD and check the date. -tony > 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) > -------------------
