Bootup Errors Post Chassis Change

Status
Not open for further replies.

eroji

Contributor
Joined
Feb 2, 2015
Messages
140
I recently swapped my chassis from a Chenbro RM23612 to a Supermicro SC846E for more room and better thermal. However, it seems like that the backplane in the Chenbro was direct attach and Supermicro is expander type. Both ran on 3 Mini-SAS cables to my 2 M1015 in IT mode. I expected the switch to cause some problems, but after I had everything installed and plugged it, it booted up and loaded FreeNAS to my surprise. Although, I am now seeing these errors in the bootup process that I am wondering I need to be concerned and if I can do anything to get rid of them.

_mapping_get_dev_info: failed to compute the hashed SAS Address for SATA device with handle 0x000a
_mapping_get_dev_info: failed to compute the hashed SAS Address for SATA device with handle 0x000b
_mapping_get_dev_info: failed to compute the hashed SAS Address for SATA device with handle 0x000c

_mapping_get_dev_info: failed to compute the hashed SAS Address for SATA device with handle 0x0012
_mapping_get_dev_info: failed to compute the hashed SAS Address for SATA device with handle 0x0013
_mapping_get_dev_info: failed to compute the hashed SAS Address for SATA device with handle 0x0014
_mapping_get_dev_info: failed to compute the hashed SAS Address for SATA device with handle 0x0015

(probe1:mps1:0:19:5): CAM status: CCB request completed with an error
(probe1:mps1:0:19:5): Retrying command
(probe0:mps1:0:18:5): INQUIRY. CDB: 12 a0 00 00 24 00
(probe0:mps1:0:18:5): CAM status: CCB request completed with an error
(probe0:mps1:0:18:5): Retrying command
(probe2:mps1:0:20:5): INQUIRY. CDB: 12 a0 00 00 24 00
(probe2:mps1:0:20:5): CAM status: CCB request completed with an error
(probe2:mps1:0:20:5): Retrying command
(probe3:mps1:0:21:5): INQUIRY. CDB: 12 a0 00 00 24 00
(probe3:mps1:0:21:5): CAM status: CCB request completed with an error
(probe3:mps1:0:21:5): Retrying command
(probe1:mps1:0:19:5): INQUIRY. CDB: 12 a0 00 00 24 00
(probe1:mps1:0:19:5): CAM status: CCB request completed with an error
(probe1:mps1:0:19:5): Retrying command
(probe0:mps1:0:18:5): INQUIRY. CDB: 12 a0 00 00 24 00
(probe0:mps1:0:18:5): CAM status: CCB request completed with an error
(probe0:mps1:0:18:5): Retrying command
(probe2:mps1:0:20:5): INQUIRY. CDB: 12 a0 00 00 24 00
(probe2:mps1:0:20:5): CAM status: CCB request completed with an error
(probe2:mps1:0:20:5): Retrying command
(probe3:mps1:0:21:5): INQUIRY. CDB: 12 a0 00 00 24 00
(probe3:mps1:0:21:5): CAM status: CCB request completed with an error
(probe3:mps1:0:21:5): Retrying command
(probe1:mps1:0:19:5): INQUIRY. CDB: 12 a0 00 00 24 00
(probe1:mps1:0:19:5): CAM status: CCB request completed with an error
(probe1:mps1:0:19:5): Retrying command
(probe0:mps1:0:18:5): INQUIRY. CDB: 12 a0 00 00 24 00
(probe0:mps1:0:18:5): CAM status: CCB request completed with an error
(probe0:mps1:0:18:5): Retrying command
(probe2:mps1:0:20:5): INQUIRY. CDB: 12 a0 00 00 24 00
(probe2:mps1:0:20:5): CAM status: CCB request completed with an error
 
Joined
Oct 2, 2014
Messages
925
What version of the expander is in the supermicro? Full hardware specs would be nice, mobo,cpu,ram,etc. I can tell you with my backplane i have 2 SAS cables connected to a single M1015, i would try unplugging one of the SAS lanes and see what happens, and while youre in there get the make/model of the backplane please :P
 

eroji

Contributor
Joined
Feb 2, 2015
Messages
140
Certainly. My apologies.

So, here they are:

System Spec:
2x Intel E5 2660 CPU
128GB Samsung ECC RDIMM
SupermicroX9DRI-F Motherboard
Intel X520-DA 10GbE Fibre card
Intel 750 400GB PCIe SSD
2x IBM M1015 (Flashed to 9211-i8 IT mode, with 3 SAS lanes connected to backplane)
4x HGST 4TB 7200RPM, 2x WD Red 4TB, 6x Toshiba 5TB 7200RPM (All in mirrors in pairs and stripe for the zpool)

Old Chassis:
Chenbro RM23612 with 80H10323602A1 12 Port Backplane
http://www.chenbro.com/en-global/DownloadFile/download/764

New Chassis:
SupermicroSC846E16 with BPN-SAS2-846EL1 24 Port Backplane
 
Joined
Oct 2, 2014
Messages
925
I would try removing the third SAS cable, and remove one of the M1015's. Also nice spec's :P
 

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,553
I'm far from a hardware guru, but I don't think you should have multiple HBAs connected to a sas expander backplane populated with SATA drives.
 
Joined
Oct 2, 2014
Messages
925
I'm far from a hardware guru, but I don't think you should have multiple HBAs connected to a sas expander backplane populated with SATA drives.
I wouldnt do it because it does sound like a recipe for disaster , i would only do it if i had a SAS card with SAS ports; allowing it to all be on one card still.
 

eroji

Contributor
Joined
Feb 2, 2015
Messages
140
Well, you guys are awesome lol. Taking the second card out did the trick. No error at all now. I had no idea having separate HBAs on same backplane was the root of the errors. Well, the more you know...
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
If you have sas drives you can use that type of configuration to do multipath and have redundancy in your controller.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
If you have sas drives you can use that type of configuration to do multipath and have redundancy in your controller.
If the backplane supports it. With only three exposed SFF-8087 connectors, it sounds like it's a single-expander backplane - which means it doesn't.
 
Joined
Oct 2, 2014
Messages
925
If the backplane supports it. With only three exposed SFF-8087 connectors, it sounds like it's a single-expander backplane - which means it doesn't.
I think the backplane version with 6 SFF-8087's would do dual controllers for fail over/redundancy
 
Status
Not open for further replies.
Top