IT44590: VSNAP HANGS DURING BOOT IF DISK USED BY CLOUD CACHE AREA IS DISCONNECTED

APAR status

• Closed as program error.

Error description

• On a vSnap server that was originally deployed using version
  10.1.11, if a disk used by the cloud cache area
  (i.e./opt/vsnap-data mountpoint) is disconnected without
  modifying the boot entry in /etc/fstab, then the vSnap may boot
  into emergency mode during the next reboot.
  
  Following screen will be seen on the console when booting:
  Welcome to emergency mode! After logging in, type "journalctl
  -xb" to view system logs, "systemctl reboot" to reboot,
  "systemctl default" or ^D to try again to boot into default
  mode.
  Give root password for maintenance
  (or type Control-D to continue):
  
  The issue is caused by the missing 'nofail' option in /etc/fstab
  for the /opt/vsnap-data filesystem.
  
  | MDVREGR - 10.1.10 |
  
  IBM Spectrum Protect Plus Versions Affected:
  IBM Spectrum Protect Plus 10.1.11.x
  

Local fix

• To reset the root password, follow steps 1 to 14 of this
  procedure:
  Resetting the serveradmin password, see
  https://www.ibm.com/docs/en/spp/10.1.15?topic=installations-rese
  tting-serveradmin-password.
  
  After resetting the root password, update /etc/fstab and add
  'nofail' mount option for the /opt/vsnap-data filesystem:
  
  /dev/mapper/vsnapdata-vsnapdatalv  /opt/vsnap-data xfs  nofail 0
  0
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus level 10.1.11 till 10.1.15.        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply the fixing level when available. For fresh             *
  * installations, this problem is fixed in IBM Spectrum Protect *
  * Plus level 10.1.16. Note that this is subject to change at   *
  * the discretion of IBM.                                       *
  *                                                              *
  * For upgrade, this is a permanent restriction.                *
  ****************************************************************
  

Problem conclusion

• For fresh/new installations: IBM Spectrum Protect Plus
  previously configured the vSnap to fail to boot if the
  /opt/vsnap-data disk was missing at startup. In IBM Spectrum
  Protect Plus 10.1.16 and later, this configuration has been
  changed to allow a vSnap to start, even when the /opt/vsnap-data
  cannot be found on startup. This allows a vSnap to continue
  booting if there is an issue with the /opt/vsnap-data disk and
  allows a user to troubleshoot the missing /opt/vsnap-data disk
  after boot.
  
  For upgrades: This is a permanent restriction and the local fix
  must be applied manually. If the upgraded vSnap is virtual,
  apply the local fix (do not apply the local fix when upgrading a
  physical vSnap).
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• vSnap
  

Fix information

• Fixed component name

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels