A file system error during the boot sequence prevents the SDI VM from completing the startup process. Workaround is available to correct the underlying file system error so the VM can boot normally.

• The VM stalls during the boot process.

• File system validation encounters issues (such as bad sectors).

• The system hangs at the file-system check with no visible progress.

• The console displays a blank or frozen screen.

To run fsck on SDI below steps needs to be followed.

Step 1: Powercycle the SDI vm

  Press Arrow keys during boot-up. The GNU GRUB menu appears.

Step 2: Select Ubuntu. Then, press e to edit

Step 3: Replace keywords: in line starting -  linux

FROM:
ro quiet splash $vt_handoff  OR  remove everythig including ro xxxxx  xxxx

TO:
rw init=/bin/bash/

Once you have made the change press F10 or CTRL + x to perform boot into a single mode

Step 4: From single user mode:

# df -kh
Confirm that your system partition is mounted as read/write (rw):
# mount | grep -w /

Step 5: (Skip this if you only want to run fsck)
To reset root password, from here type  

#passwd root

Note: you might need root user to edit file which are not permitted by cysupport user)

Step 6: unmount, run fsck, remount, reboot.

# umount /dev/sda2
# cat /etc/fstab
# fsck -y /dev/disk/by-uuid/1516e5fc-ab7a-45cc-9dd0-833792332f42
# mount /dev/sda2
# reboot -f

Please note : It might happen that multiple partitions have bad sectors so check all partitions if any errors show during boot.

Note : If you face any issues, please contact JUNIPER JTAC Support for assistance.