Help... SAS HBA are driving me mad...

Hanry

Cadet
Joined
Dec 29, 2017
Messages
3
<div class="bbWrapper">Hello there, FreeNAS warriors!<br /> <br /> I inherited a SuperMicro 45-disk JBOD this week and would like to FreeNAS it. As a host I have a Dell R515, perfectly suited to the task - installed a fresh FreeNAS on it. The Dell has two SAS controllers:<br /> 1) the internal SAS controller (Dell PERC H200), serving the four internal SAS HD<br /> 2) LSI SAS controller I pulled from an IBM server. It is flashed as HBA, with LSI 2008 (B2) firmware, and has worked fine in the past in this server. The JBOD is currently configured with 20 disks on one lane and 25 disks on the other lane.<br /> <br /> Booting up with the first lane connected to the HBA, I find that in the FreeNAS I see 24 disks: da0 to da23. <br /> It clearly has logged the 20 JBOD drives and the four internals all in one row. Ok...<br /> <br /> I want to do the traditional &quot;burn in&quot; / s.m.a.r.t. logging / badblocks register on all of the 45 drives in the JBOD.<br /> After a while, some of the drives seem to give me odd results (e.g. one of the drives is finishing the &quot;smartctl -t long /dev/daX&quot; in suspiciously short time, so I would like to identify it in the JBOD to pull it out.<br /> sas2ircu should help with this, right?<br /> Ok, I type in &quot;sas2ircu list&quot; and get the result<br /> <div class="bbCodeBlock bbCodeCode"><div class="type">Code:</div><pre> Adapter Vendor Device SubSys SubSys Index Type ID ID Pci Address Ven ID Dev ID ----- ------------ ------ ------ ----------------- ------ ------ 0 SAS2008 1000h 72h 00h:02h:00h:00h 1028h 1f1eh SAS2IRCU: Utility Completed Successfully. </pre></div><br /> ...so far so expected.<br /> But when I try to find the serial number of the disk in question by typing &quot;sas2ircu 0 display|grep WD-WCAVY096XXXX&quot; I get no results.<br /> Weird.<br /> Ok, let's go the long way: &quot;sas2ircu 0 display&quot;.<br /> Here's the result. I am very, very confused:<br /> <blockquote data-attributes="" data-quote="" data-source="" class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch"> <div class="bbCodeBlock-content"> <div class="bbCodeBlock-expandContent js-expandContent "> LSI Corporation SAS2 IR Configuration Utility.<br /> Version 20.00.00.00 (2014.09.18) <br /> Copyright (c) 2008-2014 LSI Corporation. All rights reserved. <br /> <br /> Read configuration has been initiated for controller 0<br /> ------------------------------------------------------------------------<br /> Controller information<br /> ------------------------------------------------------------------------<br /> Controller type : SAS2008<br /> BIOS version : 7.11.10.00<br /> Firmware version : 7.15.08.00<br /> Channel description : 1 Serial Attached SCSI<br /> Initiator ID : 0<br /> Maximum physical devices : 39<br /> Concurrent commands supported : 2607<br /> Slot : 0<br /> Segment : 0<br /> Bus : 2<br /> Device : 0<br /> Function : 0<br /> RAID Support : Yes<br /> ------------------------------------------------------------------------<br /> IR Volume information<br /> ------------------------------------------------------------------------<br /> ------------------------------------------------------------------------<br /> Physical device information<br /> ------------------------------------------------------------------------<br /> Initiator at ID #0<br /> <br /> Device is a Hard disk<br /> Enclosure # : 1<br /> Slot # : 0<br /> SAS Address : 5000c50-0-57b6-4759<br /> State : Ready (RDY)<br /> Size (in MB)/(in sectors) : 1907729/3907029167<br /> Manufacturer : SEAGATE <br /> Model Number : ST2000NM0023 <br /> Firmware Revision : GS0D<br /> Serial No : Z1X1XXXX<br /> GUID : N/A<br /> Protocol : SAS<br /> Drive Type : SAS_HDD<br /> <br /> Device is a Hard disk<br /> Enclosure # : 1<br /> Slot # : 1<br /> SAS Address : 5000c50-0-57b6-3ced<br /> State : Ready (RDY)<br /> Size (in MB)/(in sectors) : 1907729/3907029167<br /> Manufacturer : SEAGATE <br /> Model Number : ST2000NM0023 <br /> Firmware Revision : GS0D<br /> Serial No : Z1X1XXXX<br /> GUID : N/A<br /> Protocol : SAS<br /> Drive Type : SAS_HDD<br /> <br /> Device is a Hard disk<br /> Enclosure # : 1<br /> Slot # : 2<br /> SAS Address : 5000c50-0-57b9-d4dd<br /> State : Ready (RDY)<br /> Size (in MB)/(in sectors) : 1907729/3907029167<br /> Manufacturer : SEAGATE <br /> Model Number : ST2000NM0023 <br /> Firmware Revision : GS0D<br /> Serial No : Z1X1XXXX<br /> GUID : N/A<br /> Protocol : SAS<br /> Drive Type : SAS_HDD<br /> <br /> Device is a Hard disk<br /> Enclosure # : 1<br /> Slot # : 3<br /> Device is a Hard disk<br /> Enclosure # : 1<br /> Slot # : 2<br /> SAS Address : 5000c50-0-57b9-d4dd<br /> State : Ready (RDY)<br /> Size (in MB)/(in sectors) : 1907729/3907029167<br /> Manufacturer : SEAGATE<br /> Model Number : ST2000NM0023<br /> Firmware Revision : GS0D<br /> Serial No : Z1X1XXXX<br /> GUID : N/A<br /> Protocol : SAS<br /> Drive Type : SAS_HDD<br /> <br /> Device is a Hard disk<br /> Enclosure # : 1<br /> Slot # : 3<br /> Device is a Hard disk<br /> Enclosure # : 1<br /> Slot # : 2<br /> SAS Address : 5000c50-0-57b9-d4dd<br /> State : Ready (RDY)<br /> State : Ready (RDY)<br /> Size (in MB)/(in sectors) : 1907729/3907029167<br /> Manufacturer : SEAGATE<br /> Model Number : ST2000NM0023<br /> Firmware Revision : GS0D<br /> Serial No : Z1X1XXXX<br /> GUID : N/A<br /> Protocol : SAS<br /> Drive Type : SAS_HDD<br /> <br /> Device is a Hard disk<br /> Enclosure # : 1<br /> Slot # : 3<br /> SAS Address : 5000039-6-d812-73d6<br /> State : Ready (RDY)<br /> Size (in MB)/(in sectors) : 1907729/3907029167<br /> Manufacturer : TOSHIBA<br /> Model Number : MG04SCA20EN<br /> Firmware Revision : DS04<br /> Serial No : 2690A11UXXXX<br /> GUID : N/A<br /> Protocol : SAS<br /> Drive Type : SAS_HDD<br /> <br /> Device is a Enclosure services device<br /> Enclosure # : 1<br /> Slot # : 9<br /> SAS Address : 5d81f06-0-dd41-6000<br /> State : Standby (SBY)<br /> Manufacturer : DP<br /> Model Number : BACKPLANE<br /> Firmware Revision : 1.10<br /> Serial No : 3AID2YR<br /> GUID : N/A<br /> Protocol : SAS<br /> Device Type : Enclosure services device<br /> ------------------------------------------------------------------------<br /> Enclosure information<br /> ------------------------------------------------------------------------<br /> Enclosure# : 1<br /> Logical ID : 5c81f660:dd416000<br /> Numslots : 9<br /> StartSlot : 0<br /> Primary Boot Slot : 0<br /> ------------------------------------------------------------------------<br /> SAS2IRCU: Command DISPLAY Completed Successfully.<br /> SAS2IRCU: Utility Completed Successfully. </div> <div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div> </div> </blockquote><br /> Three Seagate and one Toshiba are my internal disks - they are connected to the Dell PERC H200 controller!<br /> And the JBOD appears as &quot;Enclosure 1, Slot 9&quot; in the list?<br /> <br /> I would be most grateful for any suggestion on how to proceed because this thing is confusing the heck out of me!<br /> Many thanks!<br /> Hanry</div>
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,079
<div class="bbWrapper">Someone recently created a resource about this very thing:<br /> <br /> <a href="https://forums.freenas.org/resources/find-a-drive-on-a-sas-backplane.104/" target="_blank" class="link link--external" rel="nofollow ugc noopener">https://forums.freenas.org/resources/find-a-drive-on-a-sas-backplane.104/</a><br /> <br /> You should be able to give the command: <code class="bbCodeInline">sesutil locate da12 on</code>, to turn on the locate light for the drive and all you need to know is the da#</div>
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,079
<div class="bbWrapper"><blockquote data-attributes="member: 81549" data-quote="Hanry" data-source="post: 514797" class="bbCodeBlock bbCodeBlock--expandable bbCodeBlock--quote js-expandWatch"> <div class="bbCodeBlock-title"> <a href="/community/goto/post?id=514797" class="bbCodeBlock-sourceJump" rel="nofollow" data-xf-click="attribution" data-content-selector="#post-514797">Hanry said:</a> </div> <div class="bbCodeBlock-content"> <div class="bbCodeBlock-expandContent js-expandContent "> Weird.<br /> Ok, let's go the long way: &quot;sas2ircu 0 display&quot;. </div> <div class="bbCodeBlock-expandLink js-expandLink"><a role="button" tabindex="0">Click to expand...</a></div> </div> </blockquote>You probably need to be looking at adapter 1 instead of adapter 0.</div>
 

Hanry

Cadet
Joined
Dec 29, 2017
Messages
3
<div class="bbWrapper">Thank you Chris - I did read quite a few similar posts from over the years but had not come across that most recent one - I shall certainly try the 'camcontrol devlist' tomorrow morning!<br /> <br /> As for the adapter - there is no 'adapter 1' - that is what is driving me crazy. 'sas2ircu list' shows exactly one adapter (item 0), and that one adapter appears to be accessing disks which are physically connected to two different HBAs - madness!</div>
 
Top