Driver issue - LSI 2308 - failed to add the device with handle xxxx to persistent table...

Status
Not open for further replies.

framewrangler

Dabbler
Joined
Nov 18, 2013
Messages
41
I’m having what I believe to be a driver issue with my FreeNAS build [FreeNAS-9.10.1-U4 (ec9a7d3)] and I’m hoping that someone out there can help point me in the right direction. The problem that I’m facing is that all new HDD installs to my server (disks 86-90) are failing to install or be recognized by FreeNAS, and seemingly the OS as well. All old or previously installed HDDs continue to function without issue. The problem persists after numerous reboots.

After installing a new SAS HDD the DMESG output will state the following:


Code:
mps1: _mapping_add_new_device: failed to add the device with handle 0x000e to persistent table because there is no free space available


The error message repeats for each new drive with the actual handle being unique to each drive. I will post pertanent DMESG and SAS2FLAH output below:


DMESG output relative to my Avago/LSI adapters

Code:
…
mps0: <Avago Technologies (LSI) SAS2308> port 0x6000-0x60ff mem 0xdf640000-0xdf64ffff,0xdf600000-0xdf63ffff irq 42 at device 0.0 on pci6
mps0: Firmware: 20.00.07.00, Driver: 21.00.00.00-fbsd
mps0: IOCCapabilities: 5285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>
mps1: <Avago Technologies (LSI) SAS2308> port 0xf000-0xf0ff mem 0xfbe40000-0xfbe4ffff,0xfbe00000-0xfbe3ffff irq 58 at device 0.0 on pci132
mps1: Firmware: 20.00.07.00, Driver: 21.00.00.00-fbsd
mps1: IOCCapabilities: 5285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>

mps1: _mapping_add_new_device: failed to add the device with handle 0x000e to persistent table because there is no free space available
mps1: _mapping_add_new_device: failed to add the device with handle 0x0017 to persistent table because there is no free space available
mps1: _mapping_add_new_device: failed to add the device with handle 0x001a to persistent table because there is no free space available
…



SAS2FLASH output

Code:
[root@storeserv01] ~# sas2flash -listall
LSI Corporation SAS2 Flash Utility
Version 16.00.00.00 (2013.03.01)
Copyright (c) 2008-2013 LSI Corporation. All rights reserved
Adapter Selected is a LSI SAS: SAS2308_2(D1)

Num  Ctlr  FW Ver  NVDATA  x86-BIOS  PCI Addr
----------------------------------------------------------------------------

0  SAS2308_2(D1)  20.00.07.00  14.01.00.06  07.39.02.00  00:06:00:00
1  SAS2308_2(D1)  20.00.07.00  14.01.00.06  07.39.02.00  00:84:00:00

Finished Processing Commands Successfully.
Exiting SAS2Flash.
[root@storeserv01] ~#




After opening a ticket with Broadcom I’ve been instructed to replace the currently installed Kernel driver with the manufacture variant which can be found on their site and is currently P20.00.00.00. I’m extremely apprehensive about this. Is this even a valid troubleshooting step with regard to a FreeNAS server? Is it critical to run the Kernel driver that is installed by default and otherwise unique to this build? I currently have the BIOS disabled within the LSI HBA configurations as well as a very low INIT13 number, possibly zero.

I appreciate any insight or experience you might be able to share on this matter.


Server specs

 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
You'll definitely want to file a bug report in the FreeNAS bug tracker. That's an odd one.

Once you do, add a link here, for future reference.
 

framewrangler

Dabbler
Joined
Nov 18, 2013
Messages
41
You'll definitely want to file a bug report in the FreeNAS bug tracker. That's an odd one.

Once you do, add a link here, for future reference.

I will do that now. Do you have any opinion or leads on the question of trying that manufacturer driver? I'm not certain if the kernel driver is mandatory when running FreeNAS or if 3rd party/manufacturer drivers are an option.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Do you have any opinion or leads on the question of trying that manufacturer driver? I'm not certain if the kernel driver is mandatory when running FreeNAS or if 3rd party/manufacturer drivers are an option.
The driver FreeNAS uses is straight from LSI. P21, currently. As for trying other drivers, that's far from trivial and involves recompiling FreeNAS from source with the "new" driver.
 

framewrangler

Dabbler
Joined
Nov 18, 2013
Messages
41
The driver FreeNAS uses is straight from LSI. P21, currently. As for trying other drivers, that's far from trivial and involves recompiling FreeNAS from source with the "new" driver.

Is there somewhere online where I can find and point to the P21 driver and show it to my Broadcom contact? It's becoming very clear that they haven't been really taking my questions and observations seriously. I thinking that the download page he sent me to is not exactly up to date.

https://www.broadcom.com/support/do...st+Bus+Adapter&po=&pa=&dk=#tab-current-Driver
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194

framewrangler

Dabbler
Joined
Nov 18, 2013
Messages
41
That's the page I linked to and it's nowhere to be found.

EDIT: I've reached back out to Broadcom in an attempt to get them to understand this driver status vs. what they are asking me to do.
 
Last edited:

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
That's the page I linked to and it's nowhere to be found.
I just checked and you seem to be right. All I can tell you is that P20 got an update that bumped the version to P21 a few months ago. It was committed by a Broadcom/Avago/LSI dev, so they should definitely be aware of it.
 

kyleg001

Cadet
Joined
May 2, 2017
Messages
1
I've added some new information to the freenas bug report https://bugs.freenas.org/issues/19880 it seems to be a limitation of the controller when using 'device persistence mapping', but I am unsure how to resolve the issue or switch the mapping method to 'enclosure slot mapping'.
 
Status
Not open for further replies.
Top