Description

After upgrading to 23.4R2 user may not be able to create a Snapshot on Backup-RE.

There might be no active alarms on the device

Symptoms

It seems to be an Mounting-Problem on both Disks, primary and secondary.

In /var/log/messages we can see entrys like wrong fs type, bad superblock and so on.


Feb 18 08:41:14.119 2025 lab-router-re0 : %USER-3: re1 Feb 18 08:41:14.118 2025 lab-router-re1 other-RE: vhclient.50780.daemon[51119]: mount: /tmp/vers-oZt/rootp: wrong fs type, bad option, bad superblock on /dev/sdb3, missing codepage or helper program, or other error. mount: /tmp/vers-oZt/rootb: wrong fs type, bad option, bad superblock on /dev/sdb4, missing codepage or helper program, or other error. mount: /tmp/vers-oZt/junos: wrong fs type, bad option, bad superblock on /dev/mapper/jvg_S-jlvmjunos, missing codepage or helper program, or other error. mount: /tmp/vers-oZt/vm: wrong fs type, bad option, bad superblock on /dev/mapper/jvg_S-jlvmvm, missing codepage or helper program, or other error. :error[141]


Feb 18 09:19:50.901 2025 lab-router-re0 : %USER-3: re1 Feb 18 09:19:50.899 2025 lab-router-re1 other-RE: vhclient.54765.daemon[54792]: mount: /tmp/vers-MsR/rootp: wrong fs type, bad option, bad superblock on /dev/sdb3, missing codepage or helper program, or other error. mount: /tmp/vers-MsR/rootb: wrong fs type, bad option, bad superblock on /dev/sdb4, missing codepage or helper program, or other error. mount: /tmp/vers-MsR/junos: wrong fs type, bad option, bad superblock on /dev/mapper/jvg_S-jlvmjunos, missing codepage or helper program, or other error. mount: /tmp/vers-MsR/vm: wrong fs type, bad option, bad superblock on /dev/mapper/jvg_S-jlvmvm, missing codepage or helper program, or other error. umount: /tmp/vers-MsR/rootp: not mounted. umount: /tmp/vers-MsR/rootb: not mounted. umount: /tmp/vers-MsR/junos: not mounted. umount: /tmp/vers-MsR/vm: not mounted. :error[0]

 

Solution

This usually points to a HW issue with the RE. Try the below steps as workaround:


  1. Rebooting RE via CLI
  2. Reseat RE
  3. USB Recovery can be tried as the last option.

If none of the above steps resolve the issue, the RE may need to be replaced.

Modification History

2025-03-01 : Article Created