Troubleshooting Other Issues

The serial number for StorNext Storage Manager is physically located on the front side of the media kit box. In addition, the administrator initially responsible for the software may have received the serial number through email when either he or she requested license information.

Both StorNext Storage Manager and StorNext File System have serial numbers in the format S/N SN000123 (for example, SN02728).

Note: The serial number is not available through the StorNext application.

Quantum testing has determined that there is an extremely small chance of the metadata controller causing a system failure if metadata or journal activity is interrupted by the loss of connectivity to the metadata LUN (one occurrence during a week of testing by unplugging disk devices from the metadata controller every five minutes).

If a metadata write exceeds the space allocated (due to loss of disk), StorNext may stop all kernel activity on the metadata controller to avoid potential data corruption. This is a timing issue when metadata I/O activity is attempted during a tear-down of internal data structures as a result of losing disk space.

You can avoid downtime from this system failure by configuring a redundant metadata controller with the High Availability (HA) feature.

You should recover from this particular failure by bringing the metadata controller back online and running the cvfsck command to repair the metadata before allowing clients to remount the file system.

After a crash and restart, the next time Storage Manager initiates, the MySQL database will check internal logs to determine whether there were any unfinished transactions, and normally will automatically make corrections. If it cannot make necessary corrections, MySQL will not complete startup. In this case contact Quantum Technical Support.

Firefox: Unable to connect. Firefox can't establish a connection to the server

Internet Explorer: Internet Explorer cannot display the webpage

If you encounter this condition, restart the StorNext GUI on the MDC server by doing the following:

1. Open a root UNIX shell window on the MDC.
2. Run the command service stornext_web restart

The "service" command will return before the service is ready to be accessed by a browser. Wait a few moments before trying to connect, and then retry if that fails.

Importing media can fail with the message "No new media found." This occurs after selecting Storage Destinations > Library > Add Media Mailbox from StorNext’s Setup menu. To fix this problem, try putting the media in one of the other mailboxes and then re-run the import. If the operation still fails, you can run the import manually by performing these steps:

1. Open up a UNIX root shell on the MDC server.
2. Source the profile by running
   ./usr/adic/.profile
3. Obtain a list of available mailboxes for an archive by running /usr/adic/MSM/bin/mmportinfo <archivename>
4. Import media into an archive from a specific mailbox by running /usr/adic/gui/scripts/library.pl add_media --archive=<archivename>

--importmethod=mailbox --mailbox=<mailbox>

Example:

/usr/adic/gui/scripts/library.pl add_media --archive=archive01

--importmethod=mailbox --mailbox=16:LTO:0,0,15,16