Project

General

Profile

Bug #25704

Add hot spare description to Guide

Added by Brandt Winchell over 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
No priority
Assignee:
Warren Block
Category:
Documentation
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

Version:FreeNAS-9.10.2-U6 (561f0d7a1)
Setup (general): 10 x 3TB drives in 5 x mirrored vdevs (production), 2 x 1TB SSD in 1 x mirrored vdev (production), 5 x 3TB in 1 x raidz vdev (backups), 1 x 3TB spare, 1 x 400GB PCI (slog), 1 x 240GB L2
Motherboard: Tyan S7012
CPU: 2 x E5620
Mem: 144GB
Controller: 3 x IBM M1015 (16 x SATA III & 3 SSD)
Case: Norco RPC-2212
Drives: 16 x 7.2K SATA III (3TB)
1 x SSD (240GB L2ARC)
1 x Intel SSD 750 (400GB SLOG)

ChangeLog Required:
No

Description

After a failed drive and successful resilver, the failed/unavailable drive is still attached to the volume and volume status is degraded. The system alert notification is not showing any failed drives. Spare drive is still attached to vdev.

Related FreeNas forumns: https://forums.freenas.org/index.php?threads/not-sure-what-hard-drive-has-failed.57133/

History

#1 Updated by Brandt Winchell over 1 year ago

  • File debug-cdanas002-20170827205141.txz added

#2 Updated by Brandt Winchell over 1 year ago

  • Description updated (diff)
  • Seen in changed from Unspecified to 9.10.2-U6
  • Hardware Configuration updated (diff)

#3 Updated by Brandt Winchell over 1 year ago

  • Hardware Configuration updated (diff)

#4 Updated by Dru Lavigne over 1 year ago

  • Assignee changed from Release Council to William Grzybowski

William: please pass to Sasha if this is not a middleware issue.

#5 Updated by William Grzybowski over 1 year ago

  • Assignee changed from William Grzybowski to Alexander Motin

Alexander Motin, I am not sure the expected behavior when a spare is IN USE. Can you clarify, please?

#6 Updated by Alexander Motin over 1 year ago

I haven't used spare drives for some time, but if my memory serve me well, that may be a correct operation. Spare drive may be just borrowed by the pool until user makes final decision. You can detach lost drive and then spare will become permanent part of the pool, or you can replace failed drive with another, and then after another rebuild spare drive will become spare again. Though somebody could check that.

#7 Updated by Alexander Motin over 1 year ago

I think my memory was right. Here is a guide how it works on Solaris (should be all the same aside of device naming): http://docs.oracle.com/cd/E19253-01/819-5461/6n7ht6qvt/index.html

#8 Updated by Alexander Motin over 1 year ago

  • Assignee changed from Alexander Motin to William Grzybowski

It look correct from the OS side. William is going to check presence of respective buttons in UI.

#9 Updated by William Grzybowski over 1 year ago

  • Status changed from Unscreened to Closed: Behaves correctly

UI present Replace and Detach buttons so this is behaving correctly as far as we can see.

#10 Updated by Dru Lavigne over 1 year ago

  • Category changed from 129 to Documentation
  • Status changed from Closed: Behaves correctly to Unscreened
  • Assignee changed from William Grzybowski to Warren Block
  • Target version set to 11.1
  • Private changed from Yes to No

Reopening as this could be clearer in the documentation.

#11 Updated by Dru Lavigne over 1 year ago

  • File deleted (debug-cdanas002-20170827205141.txz)

#12 Updated by Dru Lavigne about 1 year ago

  • Status changed from Unscreened to Resolved
  • Target version changed from 11.1 to 11.1-BETA1

#13 Updated by Dru Lavigne about 1 year ago

  • Subject changed from Drive still connected after resilver to Add hot spare description to Guide

#14 Updated by Bonnie Follweiler about 1 year ago

  • Needs QA changed from Yes to No
  • QA Status Test Passes FreeNAS added
  • QA Status deleted (Not Tested)

Also available in: Atom PDF