Multipaths to an HP D2700

bignick8t3

Cadet
Joined
Jun 12, 2017
Messages
5
Evening All,

Been running FreeNAS for a few years now and have been able to find all my answers until now...

I've recently connected the D2700 to my system and its loaded with 20x HGST 600GB SAS drives.
After connecting the SAS cables and firing up I saw the button appear for "Multipaths" and this has thrown me completely.

I understand the concept but not how the 20x disks from the D2700 are presented within FreeNAS.

If I look under "View Disks" I see the 20x disks as I would expect.
If I look under "View Multipaths" I have a total of 17 disks.

Lastly if I then open the "Volume Manager" I see all 17 multipath disks along with 6x of the disks using their own ID's (da63, da62 etc)

I believe the HBA is running p19 based on the following:
mps0: Firmware: 19.00.00.00, Driver: 21.02.00.00-fbsd

If I need to provide further information that I haven't already please do let me know, if anyone can enlighten me on this I'd be most grateful.

Nick
 

bignick8t3

Cadet
Joined
Jun 12, 2017
Messages
5
What a plum I forgot quite an important part!

Running 11.2U6
 
Joined
Dec 29, 2014
Messages
1,135
Connecting both of the SAS cables to the D2700 will give you a multipath if the drive is a dual port one. I suspect that means 3 of your disks in that D2700 are single port drives.
 

bignick8t3

Cadet
Joined
Jun 12, 2017
Messages
5
Ah okay that does make sense.

Anyway of checking this, with FreeNAS or by any other means?

I only ask as I did look over all 20 drives when I received them and from memory they were all the same.

Thanks,

Nick
 
Joined
Dec 29, 2014
Messages
1,135
I would use camcontrol devlist. On my system, the output looks like this.
Code:
root@freenas2:/nonexistent # camcontrol devlist
<ATA ST91000640NS CC03>            at scbus1 target 8 lun 0 (pass0,da0)
<ATA ST91000640NS CC03>            at scbus1 target 9 lun 0 (pass1,da1)
<ATA ST91000640NS CC03>            at scbus1 target 10 lun 0 (pass2,da2)
<ATA ST91000640NS CC03>            at scbus1 target 11 lun 0 (pass3,da3)
<ATA ST91000640NS CC03>            at scbus1 target 12 lun 0 (pass4,da4)
<ATA ST91000640NS CC03>            at scbus1 target 13 lun 0 (pass5,da5)
<ATA ST91000640NS CC03>            at scbus1 target 14 lun 0 (pass6,da6)
<ATA ST91000640NS CC03>            at scbus1 target 15 lun 0 (pass7,da7)
<ATA ST91000640NS CC02>            at scbus1 target 16 lun 0 (pass8,da8)
<ATA ST91000640NS CC02>            at scbus1 target 17 lun 0 (pass9,da9)
<ATA ST91000640NS CC03>            at scbus1 target 18 lun 0 (pass10,da10)
<ATA ST91000640NS BK03>            at scbus1 target 19 lun 0 (pass11,da11)
<ATA ST91000640NS BK03>            at scbus1 target 20 lun 0 (pass12,da12)
<ATA ST91000640NS BK03>            at scbus1 target 21 lun 0 (pass13,da13)
<ATA ST91000640NS BK03>            at scbus1 target 22 lun 0 (pass14,da14)
<ATA ST91000640NS BK03>            at scbus1 target 23 lun 0 (pass15,da15)
<ATA ST91000640NS BK03>            at scbus1 target 24 lun 0 (pass16,da16)
<TOSHIBA AL13SEB300 5706>          at scbus1 target 25 lun 0 (pass17,da17)
<TOSHIBA MBF2300RC 5704>           at scbus1 target 26 lun 0 (pass18,da18)
<CISCO UCS 240 0809>               at scbus1 target 27 lun 0 (ses0,pass19)
<HV Hypervisor_0 1.01>             at scbus3 target 0 lun 0 (pass20,da19)


Then you could use diskinfo -v /dev/da0 to show more details about the disk (model number in particular). Obviously the daX part would be different. Here is what that look like on my system.
Code:
root@freenas2:/nonexistent # diskinfo -v /dev/da0
/dev/da0
        512             # sectorsize
        1000204886016   # mediasize in bytes (932G)
        1953525168      # mediasize in sectors
        0               # stripesize
        0               # stripeoffset
        121601          # Cylinders according to firmware.
        255             # Heads according to firmware.
        63              # Sectors according to firmware.
        ATA ST91000640NS        # Disk descr.
        9XG7N91W        # Disk ident.
        Not_Zoned       # Zone Mode
 

bignick8t3

Cadet
Joined
Jun 12, 2017
Messages
5
Many thanks for this.

The NetApp X422 drives are all okay but I have some J600SS drives.

The J600SS GCGC seem to work okay but the J600SS BEBE are the problem drives.

Thanks again for your assistance, now I know where to look.
 
Joined
Jul 3, 2015
Messages
926
Sounds like you might have a mix of SAS and SATA drives as only SAS can be multipathed.
 

bignick8t3

Cadet
Joined
Jun 12, 2017
Messages
5
Afternoon,

Don't think they were SATA drives but although they share the same model number they've different part numbers.

Needless to say I was able to get hold of some more drives with the same model and part code and they work as expected.

Many thanks for the assistance.
 
Top