Some customers have experienced issues with the 2.0 restore script after receiving a newly RMA-ed appliance that may result with the device failing to boot, leaving the system in single-user/maintenance mode.
The issue occurs because the following files are restored when they should actually be ignored by the restore script:
When you are restoring an appliance that was recently RMA-ed using the restore script, you will find that this may cause your system not to boot as the boot mount has a different UUID.
Before running the restore script, take a copy of these 4 files that exist on your newly RMA-ed box and store them somewhere you can easily access after a reboot.
CAUTION: You may have to restore attributes of these four files manually while in maintenance mode if the appliance fails to boot.
A backup can be done to the /root directory, as an example, like the following:
Take a copy of your current /etc/fstab for reference. You will need to take the entries referencing any external mount points (such as a DAC) and copy those into your new fstab (/root/fstab-backup).
Once you add those entries, you can copy the new fstab over the /etc/fstab.
[root@ldec1 ~]# cp /root/fstab-backup /etc/fstab
Once you feel confident with your reapplication of these files and you are sure that you have either direct access to the appliance or by use of an iDRAC, you can reboot the box to ensure that it will boot properly.
NOTE: If you find yourself booting into maintenance mode despite these changes, run the following command after logging in as root to allow you to edit files in the /etc directory:
mount -o remount,rw /
If you are unsure of any of the steps above or experience any issues, contact RSA Customer Support and quote this article number for further assistance.