Replace Server CRUs

WARNING: Whenever you need to lift the system, get others to assist you. To avoid injury, do not attempt to lift the system by yourself.

WARNING: Opening or removing the system cover while the system is powered on may expose you to a risk of electric shock.

Caution: Do not operate the system without the cover for a duration exceeding five minutes. Operating the system without the system cover can result in component damage.

Caution: Many repairs may only be done by a certified service technician. You should only perform troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or telephone service and support team. Damage due to servicing that is not authorized by Quantum is not covered by your warranty. Read and follow the safety instructions that are shipped with your product.

Note: It is recommended that you always use an antistatic mat and antistatic strap while working on components inside the system.

Caution: To ensure proper operation and cooling, all bays in the system and system fans must be always populated with a component or a blank.

  • Key to the bezel lock.

    Note: Only required when you have a locking bezel.

  • #2 Phillips screwdriver
  • #1 Phillips screwdriver
  • T6, T8, T10, and T15 Torx screwdrivers
  1. Push the bezel latch in from the left, and pull the left end of the bezel outward, away from the server node.
  2. Detach the right end of the bezel, and remove.

  1. Attach the right end of the bezel onto the server node.
  2. Attach the left side of the bezel onto the server. You should hear an audible "click" when it is installed correctly.

To maintain proper server cooling, make sure that all empty drive slots have drive blanks installed. Use the following tasks to remove and install your server's 2.5 inch drive blanks.

Review the following prerequisites before removing or installing drive blanks.

  1. Press the release button.
  2. Slide the drive blank out of the drive slot.

  1. Insert the drive blank into the drive slot.
  2. Make sure the release button clicks into place.
  3. Install the front bezel, as applicable.

Review the following prerequisites before working with drive carriers.

  1. Remove the screws from the slide rails on the drive carrier.
  2. Lift the drive out of the drive carrier.

  1. With the connector end of the drive toward the back, insert the drive into the drive carrier.

  2. Align the screw holes on the drive with the set of screw holes on the drive carrier.

    When aligned correctly, the back of the drive is flush with the back of the drive carrier.

  3. Attach the screws to secure the drive to the carrier.

Boot drive locations

The two left-most boot SSD drives shown below in blue for a server node with a hardware RAID (PERC RAID controller card) are configured as a RAID pair:

Safety instructions

Read the Safety Instructions. See Safety Information.

Bezel

If installed, remove the bezel. See Remove and Install the Server Bezel.

Proper server cooling

To maintain proper server cooling, make sure that all empty drive slots have drive blanks installed if the drive will be removed for longer than 5 minutes. See Remove and Install Drive Blanks.

Adjacent drives

When installing a drive, ensure that the adjacent drive or drive blank is fully installed.

If you insert a drive carrier and attempt to lock its handle next to a partially installed carrier, the partially installed carrier's shield spring can be damaged and rendered unusable.

Replacement drive

If you install a replacement hot-swap boot drive when the server is powered on, the drive automatically begins to rebuild.

Use the blank replacement CRU drive supplied by Quantum, which will be the exact type and capacity as the drive it is replacing. Otherwise, make sure that the drive is the exact type and capacity as the drive it is replacing, and is blank or contains data that you do not need. Any data on the replacement drive is lost during drive configuration.

For these StorNext releases, before replacing the boot drive, in order to delay an issue and further delay the replacement later on in the configuration, Quantum recommends you reboot the system first, in order to unmount the file system on the boot drive.

For StorNext 7.1 and later

If a boot drive fails, order a replacement drive. The drive will automatically rebuilds. Follow ALL steps below to rebuild the drive.This applies to all systems running StorNext 7.1 and later, and servers with a PERC RAID card installed (hardware RAID).

For StorNext 6.2 through 7.0.3:

If the boot drive fails, order a replacement drive. When you replace the failed drive with a new one, the drive will automatically rebuild.

Complete Step 1 and Step 2 below to replace the drive.

Note: This DOES NOT apply to systems upgraded to StorNext 7.1 and later, on systems that come with StorNext 7.1 or later) pre-installed, or servers shipped with a software RAID (no PERC card installed).

For StorNext 6.1.1 and earlier:

If the boot drive fails, order a replacement drive. If this drive fails and you are running StorNext 6.1.1 or earlier, and you are able within your environment, upgrade to StorNext 6.2 or later, and complete Step 1 and Step 2 below to replace the drive. If your system needs to remain at StorNext 6.1.1 or earlier, contact Quantum Support for assistance with the replacement.

  1. Press the release button to open the drive handle.
  2. Slide the drive carrier out of the drive slot.

    Note: If you are not immediately replacing the drive, insert a drive blank in the empty drive slot.

  3. Remove the drive from the drive carrier:
    1. Remove the screws from the slide rails on the drive carrier.
    2. Lift the drive out of the drive carrier.

     

  1. Install the drive into its carrier:

    1. With the connector end of the drive toward the back, insert the drive into the drive carrier.

    2. Align the screw holes on the drive with the set of screw holes on the drive carrier.

      When aligned correctly, the back of the drive is flush with the back of the drive carrier.

    3. Attach the screws to secure the drive to the carrier.

  2. Press the release button on the front of the drive carrier and open the drive handle.
  3. Insert the drive carrier into the drive slot until the carrier seats fully into the server (engages the backplane).
  4. Close the drive handle to lock the drive in place.

  5. Install the front bezel, as applicable.

Boot drive locations

The two boot SSD drives shown in blue and located below the DVD drive for a server node WITH a software RAID (no PERC RAID controller card) are configured as a virtual RAID pair:

Safety instructions

Read the Safety Instructions. See Safety Information.

Bezel

If installed, remove the bezel. See Remove and Install the Server Bezel.

Proper server cooling

To maintain proper server cooling, make sure that all empty drive slots have drive blanks installed if the drive will be removed for longer than 5 minutes. See Remove and Install Drive Blanks.

Adjacent drives

When installing a drive, ensure that the adjacent drive or drive blank is fully installed.

If you insert a drive carrier and attempt to lock its handle next to a partially installed carrier, the partially installed carrier's shield spring can be damaged and rendered unusable.

Replacement drive

If you install a replacement hot-swap boot drive when the server is powered on, the drive automatically begins to rebuild.

Use the blank replacement CRU drive supplied by Quantum, which will be the exact type and capacity as the drive it is replacing. Otherwise, make sure that the drive is the exact type and capacity as the drive it is replacing, and is blank or contains data that you do not need. Any data on the replacement drive is lost during drive configuration.

For these StorNext releases, before replacing the boot drive, in order to delay an issue and further delay the replacement later on in the configuration, Quantum recommends you reboot the system first, in order to unmount the file system on the boot drive.

For StorNext 7.1 and later

If a boot drive fails, order a replacement drive. The drive will no longer automatically rebuilds. Follow ALL steps below to rebuild the drive.This applies to all systems running StorNext 7.1 and later, and servers with a software RAID (no PERC card).

For StorNext 6.2 through 7.0.3:

If the boot drive fails, order a replacement drive. When you replace the failed drive with a new one, the drive will automatically rebuild.

Complete Step 1 and Step 2 below to replace the drive.

Note: This DOES NOT apply to systems upgraded to StorNext 7.1 and later, on systems that come with StorNext 7.1 or later) pre-installed, or servers shipped with a software RAID (no PERC card installed).

For StorNext 6.1.1 and earlier:

If the boot drive fails, order a replacement drive. If this drive fails and you are running StorNext 6.1.1 or earlier, and you are able within your environment, upgrade to StorNext 6.2 or later, and complete Step 1 and Step 2 below to replace the drive. If your system needs to remain at StorNext 6.1.1 or earlier, contact Quantum Support for assistance with the replacement.

  1. Press the release button to open the drive handle.
  2. Slide the drive carrier out of the drive slot.

    Note: If you are not immediately replacing the drive, insert a drive blank in the empty drive slot.

  3. Remove the drive from the drive carrier:
    1. Remove the screws from the slide rails on the drive carrier.
    2. Lift the drive out of the drive carrier.

     

  1. Install the drive into its carrier:

    1. With the connector end of the drive toward the back, insert the drive into the drive carrier.

    2. Align the screw holes on the drive with the set of screw holes on the drive carrier.

      When aligned correctly, the back of the drive is flush with the back of the drive carrier.

    3. Attach the screws to secure the drive to the carrier.

  2. Press the release button on the front of the drive carrier and open the drive handle.
  3. Insert the drive carrier into the drive slot until the carrier seats fully into the server (engages the backplane).
  4. Close the drive handle to lock the drive in place.

  5. Install the front bezel, as applicable.
  1. Log in to the CLI of the server node with the replaced boot drive:
    1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network.
    2. Initiate an ssh session to the system using Terminal or PuTTY:
      1. Log in to the command line using the following credentials:
        • User name: stornext
        • Password: <stornext user account password>

          Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

      2. Enter sudo rootsh to gain root user access.
      3. Enter the password for the stornext user account again.
  2. Open the Service Menu as -admin:

    To launch the Service Menu, enter:

    sh /opt/DXi/scripts/service.sh -admin

    The Service Menu displays.

  3. Select More Tools > SW RAID Tools > SW RAID Repair.

  4. The failed disk is reported and a prompt appears requesting if you want to proceed with the software RAID disk repair.

  5. Press y to begin the software RAID disk repair process.

  6. The required replacement drive information is displayed and a prompt appears requesting that you confirm the replacement drive is already inserted. If you have the replacement drive ready or already inserted, press y to continue.

  7. The failed partitions from the failed drive are removed from the RAID mirror and a prompt appears requesting that you confirm the new drive is installed and locked in its slot. Insert the new drive, if the new drive is not already inserted, and press y.

  8. The RAID partitions are created on the new drive and the SW RAID disks are repaired to include the new partitions on the new drive. The RAID re-synchronization process is initiated and the Service Menu displays the progress of the re-synchronization process.

    Note: Quantum recommends you wait until this process is completed, before you perform other activities on your system.

  9. Open an additional SSH session and enter the following to monitor the progress of the rebuild activity:

    cat /proc/mdstat

    A recovery percentage complete displays for each partition that is being rebuilt.

  10. When the re-synchronization process is complete, the output displays a healthy status for the RAID disks.

StorNext requirement

The procedure below, which leverages the appliance Service Menu included in StorNext 7.1, and requires StorNext 7.1 or later is installed on the system.

Safety instructions

Read the Safety Instructions. See Safety Information.

Bezel

If installed, remove the bezel. See Remove and Install the Server Bezel.

Proper server cooling

To maintain proper server cooling, make sure that all empty drive slots have drive blanks installed if the drive will be removed for longer than 5 minutes. See Remove and Install Drive Blanks.

Adjacent drives

When installing a drive, ensure that the adjacent drive or drive blank is fully installed.

If you insert a drive carrier and attempt to lock its handle next to a partially installed carrier, the partially installed carrier's shield spring can be damaged and rendered unusable.

Replacement drive

Use the blank replacement CRU drive supplied by Quantum, which will be the exact type and capacity as the drive it is replacing. Otherwise, make sure that the drive is the exact type and capacity as the drive it is replacing, and is blank or contains data that you do not need. Any data on the replacement drive is lost during drive configuration.

The single 1 TB scratch drive (shown below in green), can be replaced, but how it can be replaced depends on the release of StorNext installed on the system.

Scratch drive on a system with a hardware RAID (PERC RAID controller card):

Scratch drive on a system with a software RAID (no PERC RAID controller card):

For these StorNext releases, before replacing the scratch drive, in order to delay an issue and further delay the replacement later on in the configuration, Quantum recommends you reboot the system first, in order to unmount the file system on the scratch drive.

For StorNext 7.1 and later

If the scratch drive fails, order a replacement drive, then follow the procedure below. If the drive fails in server node 2, the StorNext Unified UI becomes unusable when the scratch disk fails. Because volumes are gone and no users are defined, you will have to go through some additional configuration steps after the scratch drive is replaced for server node 2. This applies to all systems running StorNext 7.1 and later, and servers with a PERC RAID card installed (hardware RAID) and those with a software RAID (no PERC card).

For StorNext 6.2 through 7.0.3:

Note: This DOES NOT apply to systems upgraded to StorNext 7.1 and later, on systems that come with StorNext 7.1 or later) pre-installed, or servers shipped with a software RAID (no PERC card installed).

If the scratch drive fails, order a replacement drive. When you replace the failed drive with a new one, the drive will automatically rebuild.

Complete Step 1 and Step 2 below to replace the drive.

For StorNext 6.1.1 and earlier:

If the scratch drive fails and needs to be replaced, it cannot be replaced without help from Quantum. If this drive fails and you are running StorNext 6.1.1 or earlier, upgrade to StorNext 6.2 or later and complete Step 1 and Step 2 below to replace the drive. If your system needs to remain at StorNext 6.1.1 or earlier, contact Quantum Support for assistance with the replacement.

  1. Press the release button to open the drive handle.
  2. Slide the drive carrier out of the drive slot.

    Note: If you are not immediately replacing the drive, insert a drive blank in the empty drive slot.

  3. Remove the drive from the drive carrier:
    1. Remove the screws from the slide rails on the drive carrier.
    2. Lift the drive out of the drive carrier.

     

  1. Install the drive into its carrier:

    1. With the connector end of the drive toward the back, insert the drive into the drive carrier.

    2. Align the screw holes on the drive with the set of screw holes on the drive carrier.

      When aligned correctly, the back of the drive is flush with the back of the drive carrier.

    3. Attach the screws to secure the drive to the carrier.

  2. Press the release button on the front of the drive carrier and open the drive handle.
  3. Insert the drive carrier into the drive slot until the carrier seats fully into the server (engages the backplane).
  4. Close the drive handle to lock the drive in place.

  5. Install the front bezel, as applicable.
  6. Reboot the Xcellis server node with the replaced scratch drive:
    1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network.
    2. Initiate an ssh session to the system using Terminal or PuTTY:
      1. Log in to the command line using the following credentials:
        • User name: stornext
        • Password: <stornext user account password>

          Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

      2. Enter sudo rootsh to gain root user access.
      3. Enter the password for the stornext user account again.
  7. Enter:
    8. reboot
  8. Wait for the system to reboot.
  1. Open an ssh session to the CLI and log in to the server node with the new scratch drive:
    1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network.
    2. Initiate an ssh session to the system using Terminal or PuTTY:
      1. Log in to the command line using the following credentials:
        • User name: stornext
        • Password: <stornext user account password>

          Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

      2. Enter sudo rootsh to gain root user access.
      3. Enter the password for the stornext user account again.
  2. Open the Service Menu as -admin:

    To launch the Service Menu, enter:

    sh /opt/DXi/scripts/service.sh -admin

    The Service Menu displays.

  3. Select More Tools > Engineering Tools > Scratch Disk Menu.

  4. From the Scratch Disk Management menu, select Check health of /scratch disk.

    5. If the scratch disk is ready to be configured, you should see output like the following:

    *** Scratch Filesystem Disk Configuration Status ***

    The disk installed in slot 2 is ready to be configured for /scratch filesystem

    Note: If you see the following error message, contact Quantum support and have them help you add the correct entry into the file:

    ERROR: /scratch entry missing or commented out in /etc/fstab

    Note: If you see the following error message, make sure the drive has been loaded and correctly seated in drive slot 2. Remove and reseat the drive and try this menu option again:

    No disk was found in disk slot 2 for /scratch filesystem.
    Please install the disk for /scratch filesystem in slot 2 to continue.

  5. From the Scratch Disk Management menu, select Configure new /scratch disk.

    6. Note: If you see the following error message, contact Quantum support and have them help you add the correct entry into the file:

    ERROR: /scratch entry missing or commented out in /etc/fstab

    Note: If you see the following error message, make sure the drive has been loaded and correctly seated in drive slot 2. Remove and reseat the drive and try this menu option again:

    No disk was found in disk slot 2 for /scratch filesystem.
    Please install the disk for /scratch filesystem in slot 2 to continue.

    Next, you will see one of the following diagrams showing where slot 2 is located, depending on your server type:

    +=============+=============+=============+=============+=============+
    | slot 0      | slot 2      | empty       | empty       | empty       |
    +=============+=============+=============+=============+=============+
    | slot 1      | empty       | empty       | empty       | empty       |
    +=============+=============+=============+=============+=============+
    +=============+=============+=============+=============+=============+
    | XXXXXXXXXXXXXXXXXXXXXXXXX | slot 2      | empty       | empty       |
    +=============+=============+=============+=============+=============+
    | slot 0      | slot 1      | empty       | empty       | empty       |
    +=============+=============+=============+=============+=============+

  6. Enter "y" to confirm that the drive has been installed in slot 2:

    7. Can you confirm that a disk is installed in slot 2 of the server as shown above (y/n)? y

    You will see the following message if the drive is present in slot 2:

    The disk installed in slot 2 is ready to be configured for /scratch filesystem.

  7. Enter "y" to confirm that the drive has been installed in slot 2:

    8. Are you sure you want to continue and configure this disk for /scratch filesystem (y/n)? y

    ("..." indicates additional output displayed; green text indicates differences for PERC card systems; orange indicates difference shown on node 2 server nodes containing the docker)

    ...
    Recreating RAID0 LUN on [32:2]
    Slot 2 disk preparation by PERC completed successfully
    diskreplace.sh: New disk of size (10000204886016) detected in slot 2, and will be
    configured for /scratch file system.
    INFO: SCRATCH_DISK_PATH: 1rwxrwxrwx 1 root root 9 Dec 12 16:13 pci-0000:00:11.5-ata-5.0 -> ../../sdc
    INFO: SCRATCH_DISK_NAME: sdc
    Shutting down services dependent on /scratch during /scratch disk configuration
    Stopping active docker service
    Stopping systemd mount process for scratch
    Checking status of systemd mount process for scratch
    Configuring scratch disk sdc...
    ...

    ("..." indicates additional output displayed; orange indicates difference shown on node 2 server nodes containing the StorNext Unified UI docker)

    ...
    diskreplace.sh: New disk of size (10000204886016) detected in slot 2, and will be
    configured for /scratch file system.
    INFO: SCRATCH_DISK_PATH: 1rwxrwxrwx 1 root root 9 Dec 12 16:13 pci-0000:00:11.5-ata-5.0 -> ../../sdc
    INFO: SCRATCH_DISK_NAME: sdc
    Shutting down services dependent on /scratch during /scratch disk configuration
    Stopping active docker service
    Stopping systemd mount process for scratch
    Checking status of systemd mount process for scratch
    Configuring scratch disk sdc...
    ...

    Be patient for the configuration to complete, as it will take a long time.

    The new UUID for /scratch is added to the /etc/fstab file during these steps, as well as configuring the directories and permissions, changing drive partitions, and mounting the file system (or the virtual disk partition for PERC card [hardware RAID] server nodes).

    Additional time for this step is required for the following scenarios:

    • For node 2 servers additional software configuration of the StorNext Unified UI docker and API gateway in /scratch/docker and starting those services.

    • For configuration of systems with PERC cards, it will take additional time for the disk for striping the disk as RAID0 for use as a virtual disk.

    (server node 1)

    Here's confirmation on server node 1 that the configuration was successful. ("..." indicates additional output exists output displayed; green text indicates success)

    ...
    sdc disk partitions prior to new partitioning:
    Wiping disk clean:
    Creating a single msdos partition on /dev/sdc
    Setting scratch disk /dev/sdc partion to a primary partition
    Making an ext3 filesystem on /dev/sdc1 partition, this may take some time...
    New disk sdc configured with single partition as: /dev/sdc1
    Updating UUID of /scratch entry in the /etc/fstab file
    ...
    /scratch disk configuration completed successfully.

    For node 2 systems, you will see output which displays the uninstallation and reinstallation of the StorNext Unified UI (UUI) and API gateway, and the docker service being made active again. Any error messages seen on the output during this portion of the configuration are benign and can be ignored. After these node 2 specific tasks are complete, you will see a confirmation that the configuration was successful (green text indicates success).

    ...
    Restarting active docker service to recreate dirs in /scratch/docker
    UUI autostart disabled
    Uninstalling APIGW packages from previous to /scratch disk failure
    Removing possible api gateway networks from previous to /scratch disk failure
    Uninstalling SN USBE from previous to /scratch disk failure
    Running /opt/quantum/log_service/uninstall.sh
    Running /opt/quantum/usbe/uninstall.sh
    /opt/quantum/usbe/uninstall.sh Failed
    Removing quantum-uui-usbe-containers
    Removing quantum-uui-log-service-containers
    Uninstalling SN USUI from previous to /scratch disk failure
    Running /opt/quantum/usui/uninstall.sh
    /opt/quantum/usui/uninstall.sh Failed
    Removing quantum-usui-docker
    Uninstalling UUI packages from previous to /scratch disk failure
    Uninstalling quantum-uui-graphite
    Uninstalling quantum-uui-graphite-container
    Uninstalling quantum-update-service-docker
    UUI autostart enabled
    Reinstalling API Gateway
    quantum-api-gateway: Running API Gateway post-install steps, this may take 5-10 minutes, please wait ...done
    quantum-api-gateway: Set up docker containers ...............................done
    quantum-api-gateway: Running API Gateway post-install steps, this may take 5-10 minutes, please wait ...done
    quantum-api-gateway: Set up docker containers ...............................done
    quantum-api-gateway: Checking kong database for required bootstrap/migrations ..........done
    quantum-api-gateway: Bootstrapping endpoint database ........done
    quantum-api-gateway: Start API Gateway .......................done
    quantum-api-gateway: Initialize keycloak ........done
    quantum-api-gateway: Initialize kong routes .....done
    quantum-api-gateway: Update SSL certificate ...done
    quantum-api-gateway: Set volume tags ...done
    quantum-api-gateway: Complete post-install ...Post installation now complete
    Reinstalling SN USBE ...
    Reinstalling SN USUI ...
    /scratch disk configuration completed successfully.
  8. Verify the health of the drive to determine if configuration of the scratch drive is complete . From the *** Scratch Disk Management *** menu, select Check health of /scratch disk.

    9. Output should look like (green text indicates success):

    /scratch disk has not changed and is in good state.

    For server node 1 scratch drives, if the configuration of the scratch disk completes successfully, the replacement procedure is complete. Close your SSH terminal or PuTTY sessions.

    If the configuration of the scratch disk does not complete successfully, you will see an error message. This typically happens if the server node was not rebooted after replacing the scratch drive, and indicates that the system did not unmount the file system on the scratch drive ("..." indicates additional output exists before the failure output; scratch failures indicated in green text):

    ...
    Stopping systemd mount process for scratch
    Failed to stop scratch.mount
    Checking status of systemd mount process for scratch
    /scratch disk configuration failed.
    Please check /var/log/DXi/hdd_replace.log file for further information
    about the failure.
    If the problem is failure to stop scratch.mount service, this may be
    due to stale software state of /scratch disk before its failure.
    In that case, you will need to reboot the system first to clear the failed
    scratch disk software stale state before using this procedure to configure
    replacement disk for /scratch after the reboot.
  9. If the configuration of the scratch disk did not complete successfully, reboot the server node to unmount and remount the file system:

    10. If you see this error, you need to reboot the server to unmount it. Here's what to do:

    1. Reboot the server node with the replaced scratch drive at this time:
    2. Log in to the CLI.
      1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network.
      2. Initiate an ssh session to the system using Terminal or PuTTY:
        1. Log in to the command line using the following credentials:
          • User name: stornext
          • Password: <stornext user account password>

            Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

        2. Enter sudo rootsh to gain root user access.
        3. Enter the password for the stornext user account again.
    3. Enter:
      4. reboot
    4. Wait for the system to reboot.
    5. Log in to the CLI of the server node with the replaced scratch drive:
      1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network.
      2. Initiate an ssh session to the system using Terminal or PuTTY:
        1. Log in to the command line using the following credentials:
          • User name: stornext
          • Password: <stornext user account password>

            Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

        2. Enter sudo rootsh to gain root user access.
        3. Enter the password for the stornext user account again.
    6. Open the Service Menu as -admin:

      To launch the Service Menu, enter:

      sh /opt/DXi/scripts/service.sh -admin

      The Service Menu displays.

    7. Select More Tools > Engineering Tools > Scratch Disk Menu.

  10. Verify the health of the drive to determine if configuration of the scratch drive is complete . From the *** Scratch Disk Management *** menu, select Check health of /scratch disk.

    11. Output should look like (green text indicates success):

    /scratch disk has not changed and is in good state.

    For server node 1 scratch drives, if the scratch drive status is correct, the replacement procedure is complete. Close your SSH terminal or PuTTY sessions.

    For server node 2, there are still a few steps to do before the scratch drive replacement is complete:

  1. Verify that the docker is running:
    1. Log into the CLI of the server node, if not already logged in.
      1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network.
      2. Initiate an ssh session to the system using Terminal or PuTTY:
        1. Log in to the command line using the following credentials:
          • User name: stornext
          • Password: <stornext user account password>

            Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

        2. Enter sudo rootsh to gain root user access.
        3. Enter the password for the stornext user account again.
    2. View the status of the docker service. Enter:
      3. systemctl status docker -l

      How can I tell if the docker service is running correctly or not?

      You should see the following output if docker service is running ("..." indicates additional content shown; green text indicates the docker service is operating properly):

      ● docker.service - Docker Application Container Engine
      Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
      Drop-In: /etc/systemd/system/docker.service.d
               └─apigr.conf, docker-http-proxy.conf, log-service.conf, update-service.conf, usbe.conf, usui.conf
      Active: active (running) since Wed 2023-02-15 12:15:38 CST; 28min ago
      ...

      If you don't see the above output, you will likely see output similar to the following ("..." indicates additional content shown; red text indicates docker is currently inactive):

      ● docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)                                                      t: disabled)
  Drop-In: /etc/systemd/system/docker.service.d
           └─connect.conf
   Active: inactive (dead) since Fri 2023-02-17 13:11:18 PST; 16s ago
     Docs: https://docs.docker.com
  Process: 27129 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/container
d/containerd.sock (code=exited, status=0/SUCCESS)
 Main PID: 27129 (code=exited, status=0/SUCCESS)
      ...

      At this time, if the docker service did not start, you will be unable to log in to the Unified UI directly. Because the scratch drive stores Unified UI log in credentials, you must complete the Unified UI Registration Wizard. However, since the docker is not running you will instead see the following error message:

      In all these cases, you will need to restart the docker service to get the system functioning again.

  2. If the docker is running, continue to the next step. If the docker service IS NOT running, restart the docker service:

    1. Log into the CLI of the server node, if not already logged in.
      1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network.
      2. Initiate an ssh session to the system using Terminal or PuTTY:
        1. Log in to the command line using the following credentials:
          • User name: stornext
          • Password: <stornext user account password>

            Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

        2. Enter sudo rootsh to gain root user access.
        3. Enter the password for the stornext user account again.
    2. Enter the docker restart command:
      3. systemctl restart docker

  3. Verify that the unified connector is running on server node 2:

    1. Log into the CLI of the server node, if not already logged in.
      1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network.
      2. Initiate an ssh session to the system using Terminal or PuTTY:
        1. Log in to the command line using the following credentials:
          • User name: stornext
          • Password: <stornext user account password>

            Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

        2. Enter sudo rootsh to gain root user access.
        3. Enter the password for the stornext user account again.
    2. View the status of the unified connector. Enter:
      3. systemctl status unified-connector -l

      How can I tell if the unified connector is running correctly or not?

      You should see the following output if the unified connector is running ("..." indicates additional content shown; text in green indicates the unified connector is operating properly):

      unified-connector.service - Quantum Unified Connector
      Loaded: loaded (/usr/lib/systemd/system/unified-connector.service; enabled; vendor preset: disabled)
      Active: active (running) since Tue 2023-02-14 14:15:44 CST; 22h ago
      ...

      If you don't see the above output, you will need to restart the unified connector.

      You will also be unable to complete the Unified UI Registration Wizard if the unified connector is not running. On step 4 of the Registration Wizard, to "Login to Quantum Unified UI", you will see the following error message:

  4. If the unified connector service is running on server node 2, continue to the next step. If the unified connector service IS NOT running, restart the unified connector:

    1. Log into the CLI of server node 2, if not already logged in.
      1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network.
      2. Initiate an ssh session to the system using Terminal or PuTTY:
        1. Log in to the command line using the following credentials:
          • User name: stornext
          • Password: <stornext user account password>

            Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

        2. Enter sudo rootsh to gain root user access.
        3. Enter the password for the stornext user account again.
    2. Restart the unified connector. Enter:
      3. systemctl restart unified-connector

  5. For server node 2 scratch drive replacements, once the unified connector is running, recreate the StorNext Unified UI user account, or link to your existing myStorNext account, using the StorNext Unified UI registration wizard to user account.

    6. See the Registration Wizard of the "Overview of MyStorNext" page in the StorNext Documentation Center.

    Note: On the Create User Account page, click the "LINK EXISTING MYSTORNEXT PORTAL ACCOUNT" option if you already had a user account on myStorNext prior to replacing the scratch drive.

  6. Log in to the StorNext Unified UI to verify the unified connector is operating on both the host Xcellis server node 2 and all client systems.

    7. Note: If you are still unable to log into the StorNext Unified UI, restart docker again using the instructions in Step 12.

    Once you successfully log in to the Unified UI, you will see issues on the clients page if the unified connector is not running. Any systems without a running unified connector will show "Health" status in gray (healthy status would be green) and the "UC Version" (unified connector version) status of "None", as shown here (StorNext client system):

    Note: (IMPORTANT!) For all client systems, including the Xcellis server node, that indicates a "UC Version" of "None", log in to the affected system and restart the unified connector, as described in the section below:

    1. Log into the CLI of the client system.
    2. Restart the unified connector. Enter (Linux client example):
      3. systemctl restart unified-connector
    1. Log into the CLI of server node 2, if not already logged in.
      1. Open an SSH connection to the appropriate server and use the IP address assigned to the node on the Management or LAN Client network.
      2. Initiate an ssh session to the system using Terminal or PuTTY:
        1. Log in to the command line using the following credentials:
          • User name: stornext
          • Password: <stornext user account password>

            Note: "password" is the default password for the stornext user account. If the password has been changed, use the current password. Beginning with StorNext 7.0.2, you must change the default password for the stornext user account. As of StorNext 7.0.2, the first time you log in, you will be prompted to change the password to a different one.

        2. Enter sudo rootsh to gain root user access.
        3. Enter the password for the stornext user account again.
    2. Restart the unified connector. Enter:
      3. systemctl restart unified-connector

    For server node 2 scratch drives, the replacement procedure is complete. Close your SSH terminal or PuTTY sessions.