Hello there, FreeNAS warriors!
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:
1) the internal SAS controller (Dell PERC H200), serving the four internal SAS HD
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.
Booting up with the first lane connected to the HBA, I find that in the FreeNAS I see 24 disks: da0 to da23.
It clearly has logged the 20 JBOD drives and the four internals all in one row. Ok...
I want to do the traditional "burn in" / s.m.a.r.t. logging / badblocks register on all of the 45 drives in the JBOD.
After a while, some of the drives seem to give me odd results (e.g. one of the drives is finishing the "smartctl -t long /dev/daX" in suspiciously short time, so I would like to identify it in the JBOD to pull it out.
sas2ircu should help with this, right?
Ok, I type in "sas2ircu list" and get the result
...so far so expected.
But when I try to find the serial number of the disk in question by typing "sas2ircu 0 display|grep WD-WCAVY096XXXX" I get no results.
Weird.
Ok, let's go the long way: "sas2ircu 0 display".
Here's the result. I am very, very confused:
Three Seagate and one Toshiba are my internal disks - they are connected to the Dell PERC H200 controller!
And the JBOD appears as "Enclosure 1, Slot 9" in the list?
I would be most grateful for any suggestion on how to proceed because this thing is confusing the heck out of me!
Many thanks!
Hanry
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:
1) the internal SAS controller (Dell PERC H200), serving the four internal SAS HD
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.
Booting up with the first lane connected to the HBA, I find that in the FreeNAS I see 24 disks: da0 to da23.
It clearly has logged the 20 JBOD drives and the four internals all in one row. Ok...
I want to do the traditional "burn in" / s.m.a.r.t. logging / badblocks register on all of the 45 drives in the JBOD.
After a while, some of the drives seem to give me odd results (e.g. one of the drives is finishing the "smartctl -t long /dev/daX" in suspiciously short time, so I would like to identify it in the JBOD to pull it out.
sas2ircu should help with this, right?
Ok, I type in "sas2ircu list" and get the result
Code:
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.
...so far so expected.
But when I try to find the serial number of the disk in question by typing "sas2ircu 0 display|grep WD-WCAVY096XXXX" I get no results.
Weird.
Ok, let's go the long way: "sas2ircu 0 display".
Here's the result. I am very, very confused:
Three Seagate and one Toshiba are my internal disks - they are connected to the Dell PERC H200 controller!
And the JBOD appears as "Enclosure 1, Slot 9" in the list?
I would be most grateful for any suggestion on how to proceed because this thing is confusing the heck out of me!
Many thanks!
Hanry
