General Feature Card Maintenance and Troubleshooting Tasks

Performing a Soft Boot of the Feature Card

In certain situations, you may be required to perform a soft reboot of the feature card. If possible, shut down the applications running on the card before performing a soft boot.

To perform the soft boot, log in as user root and issue the following command:

reboot -f

Monitoring the Feature Card

To monitor your feature card hardware performance, follow the directions outlined for viewing the SL4000 GUI Hardware tab. Refer to the SL40000 Library Guide for more information.

Updating Your IP Address, Host Name, or Other Network Related Items

If you need to change your IP address, host name, or other network-related information for the feature card, complete the following steps described in Configuring the Feature Card and Preparing for ACSLS Installation.

See:

Not Enough Disk Space in the root Partition on the Feature Card

Depending on where you store your ACSLS diagnostic bundles, you may run out of disk space in the root partition on the feature card. You may need to manage this space to maintain a reasonable size or create a soft link to point to the logs elsewhere. The following is an example of the commands you may perform as user root to enable more space, if required:

mkdir /u01/tmp
ln -s /u01/tmp/diags /tmp/diags
chmod 777 /u01/tmp /tmp/diags /u01/tmp/diags

Establishing Mount Points after Removing and Re-inserting a Feature Storage Card

When you remove and re-insert a feature storage card in the SL4000 library, a new mount point is created and the previous mount point may be retained. To eliminate confusion, use one of the following methods to remove the previous mount point if it is also displayed:

Automatic unmount (preferred)

Reboot the impacted feature card following the procedure described in "Performing a Soft Boot of the Feature Card".
Manual unmount
1. Manually unmount the devices associated with '/bkupa' and '/bkupb' using the following operating system command:
```
umount <filesystemName>
```
  where <filesystemName> is the /bkupa or /bkupb name.
2. Run the following script:
```
/usr/local/bin/featureCard_acslsStorageManager.sh
```

Troubleshooting and Recovering from Unexpected ACSLS Storage Problems

If you encounter issues where disk layout or mount points have been lost, you may need to repair the file system and storage setup for ACSLS. Depending on the issue, you may need to complete the following steps one or more times to return the system to a normal state:

Before running any of the commands detailed in the following steps, log in as user acsss and enter the following command to shut down the ACSLS application:
```
acsss shutdown
```
You may be required to rerun featureCard_acslsStorageManager.sh as user root. This command assumes that you have shut down the ACSLS application. To repair ACSLS storage-related issues, issue the following command:
```
cd /usr/local/bin./featureCard_acslsStorageManager.sh
```
A soft reboot may be required as part of the command sequence above, to ensure that all settings have been updated correctly. To do this, log in as user root and issue the following command:
```
reboot
```
An issue may require you to mirror RAID storage. Monitor the mirroring process and ensure that it has been completed before continuing to enable ACSLS. As user root, you can use the following command to monitor the rebuilding of the mirror.
Open a separate terminal window and enter:
```
watch cat /proc/mdstat
```
Monitor the mdstat display to determine when rebuilding of the mirrored drive is complete. Within minutes, [UU] is displayed, indicating that the rebuilding operation has completed.After [UU] is displayed, you can proceed with enabling ACSLS.