Beruflich Dokumente
Kultur Dokumente
Version: 2 Article Type: Break Fix Audience: Level 30 = Customers Last Published: Sat Feb 20 20:59:37 GMT 2016
Summary:
Version: 2 Article Type: Break Fix Audience: Level 30 = Customers Last Published: Sat Feb 20 20:59:37 GMT 2016
Summary:
Issue: Reseating the drive or inserting a different replacement drive does not resolve the issue.
After running the isi devices command, output similar to the following appears for the specific drive bay:
Bay 27 Lnum N/A [47;30m[EMPTY] [0m SN:N/A N/A
The /var/log/messages file on the affected node contains errors similar to the following:
2014-07-06T19:46:28-07:00 <0.7> example-17(id28) /boot/kernel.amd64/kernel:
(da17:mps0:0:36:0): lost device
After replacing a failed drive in an Isilon node, the drive cannot be added from the front panel or from the OneFS
command-line interface until the node is power cycled.
Cause:
When a drive was removed from a node, the physical port to which the drive was connected was not automatically reset.
As a result, before another drive could be connected to the port, the port had to be manually reset by turning the node off
and then on.
Resolution:
Permanent Fix:
1. Open an SSH connection to the node and log in using the "root" account.
2. Run the following command to shut down the node:
shutdown -p now
3. Allow the node a minute or two to spin down and reset, then power it back on.
4. When the node has finished booting, open an SSH connection to the node and log in using the "root" account.
5. Add the new drive to the node by running the following command, where <bay> is the bay number where the new drive
is located:
Product: Isilon, Isilon OneFS, Isilon OneFS 7.0, Isilon OneFS 7.1
Article Properties: Validation Status: Approved Original Create Date: Sat Feb 20 11:27:10 GMT 2016
Originally Created By: SFDC Admin Last Modified: Sat Feb 20 20:59:37 GMT 2016