JunOS : 비밀번호 복구 실패

MX80에서 루트 암호를 복구하려고하는데 몇 가지 오류가 발생하며 그 의미가 무엇인지 모릅니다.

내가 취한 단계는 다음과 같습니다.

• 프롬프트에서 라우터를 재부팅하십시오 Hit [Enter] to boot immediately, or space bar for command prompt-공간을 확보했습니다

• boot -s단일 사용자 모드로 부팅하기 위해 들어 갑니다

• 프롬프트에서 Enter full pathname of shell or 'recovery' for root password recovery or RETURN for /bin/sh:내가 입력recovery

• CLI에 들어가면 구성 모드로 들어간 다음 루트 암호를 재설정하고 구성을 커밋합니다.

이것은 내가 오류를 경험했다; 그들은 무엇을 의미하며 어떻게 해결할 수 있습니까? 심지어 수정해야합니까 (그렇다고 가정합니다!) :

[edit]
root# set system root-authentication plain-text-password 
New password:
Retype new password:

[edit]
root# commit    
error: could not open database: /var/run/db/juniper.data: No such file or directory
error: Database open failed for file '/var/run/db/juniper.data': No such file or directory
error: commit failed: daemon file propagation failed

[edit]
root# WATCHDOG_TIMER : Loss of soft watchdog
panic: Loss of soft watchdog
Entering boot mastership relinquish phase
KDB: enter: panic
[thread pid 11 tid 100005 ]
Stopped at      kdb_enter+0x1a4:        addis   r3, r0, -0x5f7a
db>

MX80은 JunOS 11.4R1.14를 실행 중입니다. 재부팅했는데 비밀번호가 재설정되지 않았습니다. 다시 시도해야합니까, 아니면 먼저이 라우터에 문제가 있습니까? 나는 아무것도 손상하고 싶지 않습니다.

최신 정보

이것에 대한 업데이트로서; 오늘은 복구 모드로 다시 부팅했지만 아무 것도하지 않았습니다. 라우터가 "root>"에 앉아 전화를하고있었습니다. 몇 분 동안 전화를하는 동안 라우터는 갑자기 공황 상태에 빠졌습니다.

Enter full pathname of shell or 'recovery' for root password recovery or RETURN for /bin/sh: recovery

Performing filesystem consistency checks ...
/dev/da0s1a: 1466 files, 91908 used, 361032 free (56 frags, 45122 blocks, 0.0% fragmentation)
/dev/da0s1e: 9 files, 8 used, 50273 free (17 frags, 6282 blocks, 0.0% fragmentation)

Performing mount of main filesystems ...

Performing filesystem consistency of secondary filesystems ...
/dev/da1s1f: 232 files, 362550 used, 1105677 free (125 frags, 138194 blocks, 0.0% fragmentation)

Performing mount of secondary filesystems ...
Verified manifest signed by PackageProduction_11_4_0
Verified jboot signed by PackageProduction_11_4_0
Verified jbase-ppc-11.4R1.14 signed by PackageProduction_11_4_0
Mounted jkernel package on /dev/md1...
Verified manifest signed by PackageProduction_11_4_0
veriexec: fingerprint for dev 73, file 49356 f743694d46ccdfd6bc72f0793c1cc0e8e5bdf80e != b3dfc26ab4c595f569e86791aa3dcfa4a277892c
Verified jkernel-ppc-11.4R1.14 signed by PackageProduction_11_4_0
Mounted jpfe package on /dev/md2...
Mounted jdocs package on /dev/md3...
Verified manifest signed by PackageProduction_11_4_0
Verified jdocs-11.4R1.14 signed by PackageProduction_11_4_0
Mounted jroute package on /dev/md4...
Verified manifest signed by PackageProduction_11_4_0
Verified jroute-ppc-11.4R1.14 signed by PackageProduction_11_4_0
Mounted jcrypto package on /dev/md5...
Verified manifest signed by PackageProduction_11_4_0
Verified jcrypto-ppc-11.4R1.14 signed by PackageProduction_11_4_0
machdep.bootsuccess: 1 -> 1

Performing initialization of management services ...
mgd: error: could not open database: /var/run/db/schema.db: No such file or directory
mgd: error: Database open failed for file '/var/run/db/schema.db': No such file or directory
mgd: error: could not open database schema: /var/run/db/schema.db
mgd: error: could not open database schema
mgd: error: database schema is out of date, rebuilding it
mgd: error: could not open database: /var/run/db/juniper.data: No such file or directory
mgd: error: Database open failed for file '/var/run/db/juniper.data': No such file or directory
mgd: error: Cannot read configuration: Could not open configuration database

Performing checkout of management services ...

NOTE: Once in the CLI, you will need to enter configuration mode using
NOTE: the 'configure' command to make any required changes. For example,
NOTE: to reset the root password, type:
NOTE:    configure
NOTE:    set system root-authentication plain-text-password
NOTE:    (enter the new password when asked)
NOTE:    commit
NOTE:    exit
NOTE:    exit
NOTE: When you exit the CLI, you will be asked if you want to reboot
NOTE: the system

Starting CLI ... 
root> WATCHDOG_TIMER : Loss of soft watchdog
panic: Loss of soft watchdog
###Entering boot mastership relinquish phase
KDB: enter: panic
[thread pid 11 tid 100005 ]
Stopped at      kdb_enter+0x1a4:        addis   r3, r0, -0x5f7a
db>

다시 설치하고 어떻게되는지 보겠습니다.

파일 시스템이 손상되었을 수 있습니다. 라우터가 제대로 종료되지 않고 재부팅 되었습니까? 이 경우 USB 스틱에서 부팅하고 CF 카드를 다시 설치 (재 파티션 사용)하십시오.

시스템 스냅 샷 파티션 미디어 컴팩트 플래시 요청 (또는 유사한 장치 이름은 설명서를 확인하십시오)