Project

General

Profile

Bug #18136

Default installation does not configure correct drivers for Dell PERC H730 controller.

Added by Paul Chown almost 4 years ago. Updated over 3 years ago.

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

Dell R730xd fitted with a PERC H730 Mini controller set to HBA mode.

ChangeLog Required:
No

Description

I’m a newbie with FreeNAS/FreeBSD so could accept that the following might not be a bug but is instead configuration information about which an installer should be made aware. It has been my experience that the default installation does not correctly configure the drivers for Dell PERC H730 controllers.

Before raising this bug I filed an enquiry on the FreeNAS forums, if you want the full details it’s here: [[https://forums.freenas.org/index.php?threads/smartd-failing-to-start-freenas-9-10-1-running-on-dell-r730xd.46594/]]

Configuration

Dell R730xd server with a PERC H730 mini controller set to HBA mode.
FreeNAS FreeNAS-9.10.1 (d989edd)

Before purchasing this server I checked the FreeBSD HCL as recommended by the FreeNAS hardware requirements page http://www.freenas.org/hardware-requirements.

Mindful of the need to not use hardware RAID, before installing FreeNAS I configured the PERC H730 controller to HBA mode.

Symptoms

The installation appears to complete without issue.

However, the UI cannot be used to start SMART.

The smartd.conf file had been populated with entries like this:

@cat /usr/local/etc/smartd.conf ################################################
  1. smartd.conf generated by /etc/ix.rc.d/ix-smartd ################################################
    /dev/mfisyspd0 -a -n never -W 0,0,0 -m root -M exec /usr/local/www/freenasUI/tools/smart_alert.py
    /dev/mfisyspd1 -a -n never -W 0,0,0 -m root -M exec /usr/local/www/freenasUI/tools/smart_alert.py
    /dev/mfisyspd2 -a -n never -W 0,0,0 -m root -M exec /usr/local/www/freenasUI/tools/smart_alert.py -s S/(01|02|03|04|05|06|07|08|09|10|11|12)/../(1|2|3|4|5|6|7)/(19)
    /dev/mfisyspd3 -a -n never -W 0,0,0 -m root -M exec /usr/local/www/freenasUI/tools/smart_alert.py -s S/(01|02|03|04|05|06|07|08|09|10|11|12)/../(1|2|3|4|5|6|7)/(19)
    @

Folk on the FreeNAS community site informed me that device names beginning with “mfi” indicated hardware RAID in use despite my having set the controller to HBA mode.

The device list looked like this:

# camcontrol devlist
<HGST HUS726060AL5214 KK06> at scbus0 target 0 lun 0 (pass0)
<HGST HUS726060AL5214 KK06> at scbus0 target 1 lun 0 (pass1)
<HGST HUS726060AL5214 KK06> at scbus0 target 2 lun 0 (pass2)
<HGST HUS726060AL5214 KK06> at scbus0 target 3 lun 0 (pass3)

Resolution

According to the FreeBSD HCL the PERC H730 is supported by the mrsas(4) driver (the H730 is constructed with a LSI SAS 3108 controller).

Reading the mrsas(4) man page I discovered that:
“Older MegaRAID controllers are supported by mfi(4) and will not work with mrsas, but both the mfi(4) and mrsas drivers can detect and manage the LSI MegaRAID SAS 2208/2308/3008/3108 series of controllers.

The device.hints(5) option is provided to tune the mrsas driver's behavior for LSI MegaRAID SAS 2208/2308/3008/3108 controllers. By default, the mfi(4) driver will detect these controllers.”

By editing /boot/device.hints adding the line

{{{
hw.mfi.mrsas_enable="1"
}}}

and re-booting I was able to enable SMART and the device list had da<n> devices listed

# camcontrol devlist -v
scbus0 on mrsas0 bus 0:
<> at scbus0 target -1 lun ffffffff ()
scbus1 on mrsas0 bus 1:
<HGST HUS726060AL5214 KK06> at scbus1 target 0 lun 0 (pass0,da0)
<HGST HUS726060AL5214 KK06> at scbus1 target 1 lun 0 (pass1,da1)
<HGST HUS726060AL5214 KK06> at scbus1 target 2 lun 0 (pass2,da2)
<HGST HUS726060AL5214 KK06> at scbus1 target 3 lun 0 (pass3,da3)

Issue

If FreeNAS should automatically install correctly on hardware in the HCL then I think this is a bug in the installer, i.e. the installer should identify the controller in use and set the required hint. Otherwise it’s a note which needs to be filed to assist future system builders (which I have already done at forums.freenas.org)

Associated revisions

Revision 70668840 (diff)
Added by Warren Block over 3 years ago

Add a note about setting up the Dell PERC H730. Ticket: #18136

History

#1 Updated by Heather Ownby almost 4 years ago

  • Assignee set to Sean Fagan

#2 Updated by Sean Fagan almost 4 years ago

  • Assignee changed from Sean Fagan to Josh Paetzel

Actually, Josh? Thoughts or comments on this?

#3 Updated by Paul Chown almost 4 years ago

  • Seen in changed from 9.10.1 to 9.10.1-U2

Just noticed latest version is 9.10.1-U2 (I was using a 9.10.1 which I downloaded at the end of August).

Have just made a fresh install of 9.10.1-U2 and encountered the same behaviour.

#4 Updated by Josh Paetzel almost 4 years ago

  • Status changed from Unscreened to Screened
  • Priority changed from No priority to Nice to have

So one thing we could do, is on install if a MegaRAID is detected give the user a choice between the mfi driver and the mrsas driver.

Let me think about that for a bit.

If you create a tunable of type loader in the GUI instead of a device.hints entry that change will persist across upgrades and so forth.

#5 Avatar?id=14398&size=24x24 Updated by Kris Moore almost 4 years ago

  • Target version set to 49

Still something you want to consider a knob for? If so, lets throw it into 9.10.3 milestone.

#6 Updated by Bonnie Follweiler almost 4 years ago

  • Target version changed from 49 to 9.10.3

#7 Updated by Josh Paetzel over 3 years ago

  • Status changed from Screened to Unscreened
  • Assignee changed from Josh Paetzel to Kris Moore

#8 Avatar?id=14398&size=24x24 Updated by Kris Moore over 3 years ago

  • Category changed from 1 to 201
  • Assignee changed from Kris Moore to William Grzybowski

#9 Updated by William Grzybowski over 3 years ago

  • Status changed from Unscreened to Screened

These controllers are tricky, I am not sure how I feel about making a decision for the user.

#10 Avatar?id=14398&size=24x24 Updated by Kris Moore over 3 years ago

  • Assignee changed from William Grzybowski to Dru Lavigne

Yea, I'm a bit leery on changing any behavior here. Dru, do we have an Errata section we can just throw this "hint" into for future reference?

#11 Updated by Dru Lavigne over 3 years ago

  • Category changed from 201 to Documentation
  • Assignee changed from Dru Lavigne to Warren Block
  • Target version changed from 9.10.3 to 9.10.2-U2

Yup, easy enough to add a note to the docs.

#12 Avatar?id=14398&size=24x24 Updated by Kris Moore over 3 years ago

  • Target version changed from 9.10.2-U2 to 9.10.3

#13 Updated by Warren Block over 3 years ago

  • Status changed from Screened to Resolved

#14 Updated by Dru Lavigne over 3 years ago

  • Target version changed from 9.10.3 to N/A

Also available in: Atom PDF