JunOS:密码恢复失败

网络工程 瞻博网络
2021-07-23 16:43:13

我正在尝试在 MX80 上恢复 root 密码,但我收到了一些错误并且不知道它们的意思(它不是实时的,所以暗示性的“破坏性”步骤是可以接受的);

我采取的步骤如下;

  • 在提示下重新启动路由器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 后,我进入配置模式,然后尝试重置 root 密码并提交配置;

这是我遇到的错误;它们是什么意思,我该如何纠正?它甚至需要更正吗(我认为是这样!):

[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>

我将重新安装,看看会发生什么。

1个回答

它可能是一个损坏的文件系统 - 路由器是否在没有正确关闭的情况下重新启动?如果是这种情况,请尝试从 U 盘启动并重新安装(重新分区)CF 卡:

请求系统快照分区媒体压缩闪存(或类似的,检查手册以获取确切的设备名称)