分类:
2009-02-25 13:07:23
设备掉电后无法启动,启动报错信息如下
Root password for system maintenance (control-d to bypass):
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
for more information.
TRIT0850053
The svc.startd daemon then exits and starts sulogin to enable you to perform maintenance.
# /lib/svc/bin/restore_repository
|
Repository Restore utility See for more information on the use of this script to restore backup copies of the smf(5) repository.
If there are any problems which need human intervention, this script will give instructions and then exit back to your shell.
Note that upon full completion of this script, the system will be rebooted using reboot(1M), which will interrupt any active services. |
The following backups of /etc/svc/repository.db exists, from oldest to newest:
... list of backups ... |
Typically, the most recent backup option is selected.
Please enter one of:
1) boot, for the most recent post-boot backup
2) manifest_import, for the most recent manifest_import backup.
3) a specific backup repository from the above list
4) -seed-, the initial starting repository. (All customizations
will be lost.)
5) -quit-, to cancel.
Enter response [boot]:
If you press Enter without specifying a backup to restore, the default response, enclosed in [] is selected. Selecting -quit- exits the restore_repository script, returning you to your shell prompt.
Note -
Selecting -seed- restores the seed repository. This repository is designed for use during initial installation and upgrades. Using the seed repository for recovery purposes should be a last resort.
After the backup to restore has been selected, it is validated and its integrity is checked. If there are any problems, the restore_repository command prints error messages and prompts you for another selection. Once a valid backup is selected, the following information is printed, and you are prompted for final confirmation.
After confirmation, the following steps will be taken:
svc.startd(1M) and svc.configd(1M) will be quiesced, if running.
/etc/svc/repository.db
-- renamed --> /etc/svc/repository.db_old_YYYYMMDD_HHMMSS
/etc/svc/volatile/db_errors
-- copied --> /etc/svc/repository.db_old_YYYYMMDD_HHMMSS_errors
repository_to_restore
-- copied --> /etc/svc/repository.db
and the system will be rebooted with reboot(1M).
Proceed [yes/no]?
The system reboots after the restore_repository command executes all of the listed actions.