Description
Customer unable to bring up RE successfully and noticed RE stuck in boot loop.
Symptoms
RE stuck in boot loop after code upgrade with below logs being printed on the console .
error: no suitable video mode found.
Booting in blind mode
setpci: Unable to parse filter -s Invalid function number.
Try `setpci --help' for more information.
Cannot get kernel page_offset_base symbol address
Cannot get kernel _stext symbol address
VMHost crash kernel loaded at reserved memory
Current Boot: Boot0005* EFI Hard Drive (SFSA050GV3AA2TO-I-LB-22A-JUN)
detected current boot medium.. ssd
Starting file system check on rootfs
fsck from util-linux 2.28.1
e2fsck 1.43 (17-May-2016)
jrootb_P: recovering journal
Setting free inodes count to 103313 (was 103317)
Setting free blocks count to 153712 (was 155841)
jrootb_P: clean, 27759/131072 files, 370576/524288 blocks
fsck from usystemd[1]: [/etc/systemd/system/reboot.target.d/override.conf:2] Failed to parse JobTimeoutSec= parameter, ignoring:
Cannot get driver information: No such device
sh[2227]: PF driver reset failed, trying to reinitialize
[FAILED] Failed to start vehostd service.
See 'systemctl status vehostd.service' for details.
[ OK ] Created slice system-failure_handler.slice.
[ OK ] Started Failure Handler Service.
Starting vsmartd service...
[FAILED] Failed to start vsmartd service.
See 'systemctl status vsmartd.service' for details.
[ OK ] Started Failure Handler Service.
Starting rasdaemon service...
[FAILED] Failed to start rasdaemon service.
See 'systemctl status rasdaemon.service' for details.
[ OK ] Started Failure Handler Service.
Starting resild service...
[FAILED] Failed to start resild service.
See 'systemctl status resild.service' for details.
[ OK ] Started Failure Handler Service.
Starting jsntp service...
[FAILED] Failed to start jsntp service.
See 'systemctl status jsntp.service' for details.
[ OK ] Started Failure Handler Service.
[ OK ] Started /etc/rc.local Compatibility.
[ OK ] Stopped jsntp service.
Starting jsntp service...
[ OK ] Stopped vsmartd service.
Starting vsmartd service...
[ OK ] Stopped rasdaemon service.
Starting rasdaemon service...
[ OK ] Stopped resild service.
Starting resild service...
[ OK ] Stopped vehostd service.
Starting vehostd service...
[ OK ] Started Getty on tty1.
[ OK ] Started Serial Getty on ttyS0.
[ OK ] Reached target Login Prompts.
[FAILED] Failed to start jsntp service.
See 'systemctl status jsntp.service' for details.
[FAILED] Failed to start rasdaemon service.
See 'systemctl status rasdaemon.service' for details.
[FAILED] Failed to start vehostd service.
See 'systemctl status vehostd.service' for details.
[FAILED] Failed to start resild service
.
See 'systemctl status resild.service' for details.
[ OK ] Started Failure Handler Service.
[ OK ] Started Failure Handler Service.
[ OK ] Started Failure Handler Service.
[ OK ] Started Failure Handler Service.
[
FAILED] Failed to start vsmartd service.
See 'systemctl status vsmartd.service' for details.
[ OK ] Started Failure Handler Service.
[ OK ] Stopped rasdaemon service.
Starting rasdaemon service...
[ OK ] Stopped vehostd service.
Starting vehostd service...
[ OK ] Stopped resild service.
Starting resild service...
[ OK ] Stopped vsmartd service.
Starting vsmartd service...
[ OK ] Stopped jsntp service.
Starting jsntp service...
[FAILED] Failed to start rasdaemon service.
See 'systemctl status rasdaemon.service' for details.
[FAILED] Failed to start vsmartd service.
See 'systemctl status vsmartd.service' for details.
[FAILED] Failed to start jsntp service.
See 'systemctl status jsntp.service' for details.
[ OK ] Started Failure Handler Service.
[ OK ] Started Failure Handler Service.
[ OK ] Started Failure Handler Service.
[FAILED] Failed to start resild service.
See 'systemctl status resild.service' for details.
[ OK ] Started Failure Handler Service.
[FAILED] Failed to start vehostd service.
See 'systemctl status vehostd.service' for details.
[ OK ] Started Failure Handler Service.
[ OK ] Stopped vsmartd service.
Starting vsmartd service...
[ OK ] Stopped jsntp service.
Starting jsntp service...
[ OK ] Stopped resild service.
Starting resild service...
[ OK ] Stopped vehostd service.
Starting vehostd service...
[ OK ] Stopped rasdaemon service.
Starting rasdaemon service...
[FAILED] Failed to start vsmartd service.
See 'systemctl status vsmartd.service' for details.
[FAILED] Failed to start jsntp service.
See 'systemctl status jsntp.service' for details.
[FAILED] Failed to start resild service.
See 'systemctl status resild.service' for details.
[FAILED] Failed to start vehostd service.
See 'systemctl status vehostd.service' for details.
[FAILED] Failed to start rasdaemon service.
See 'systemctl status rasdaemon.service' for details.
[ OK ] Started Failure Handler Service.
[ OK ] Started Failure Handler Service.
[ OK ] Started Failure Handler Service.
[ OK ] Started Failure Handler Service.
[ OK ] Started Failure Handler Service.
[ OK ] Stopped jsntp service.
Starting jsntp service...
[ OK ] Stopped resild service.
Starting resild ssh[3389]: 4 logical volume(s) in volume group "jvg_P" now active
sh[3389]: 4 logical volume(s) in volume group "jvg_S" now active
sh[3389]: Reading volume groups from cache.
sh[3389]: Found volume group "jvg_P" using metadata type lvm2
sh[3389]: Found volume group "jvg_S" using metadata type lvm2
sh[3389]: Cleaned RW Root, proceeding...
Solution
From the console logs we can see that vehostd daemon is failing to start. The daemon is responsible for the host junos OS . If it is failing to start junos RE wont come up.
We can try to reseat the RE by sending a tech on site and also try to perform a USB installation .
https://www.juniper.net/documentation/us/en/software/junos/junos-install-upgrade/topics/topic-map/install-software-on-mx.html
If both of the above steps doesn't work then proceed for RMA .
Modification History
2024-08-29 : Article Created
[MX/PTX]RE stuck in boot loop during upgrade.