FreeNas and Adaptec 51645

[justusiv]

I have been looking around and not coming up with anything.
I have my FreeNas up and running however i am using an Adaptec 51645 and the drives are not showing up. So i assume the drivers aren't loaded for the card. I am looking for some guidance on this issue.
Thank you.

 

[dlavigne]

It's showing as supported: https://www.freebsd.org/releases/9.1R/hardware.html#DISK.

Post the output of camcontrol devlist

 

[justusiv]

i ran that and it does see the drives

< ST32000644NS SN11> at scbus8 target 0 lun 0 (pass0)
< ST32000644NS SN11> at scbus8 target 1 lun 0 (pass1)
< ST32000644NS SN11> at scbus8 target 2 lun 0 (pass2)
< ST32000644NS SN11> at scbus8 target 3 lun 0 (pass3)
<Kingston DataTraveler 3.0 PMAP> at scbus16 target 0 lun 0 (pass4,da0)

I must be doing something silly.
When i click view disks its empty.

 

[dlavigne]

Have you made a volume yet?

 

[justusiv]

I don't know what i am doing wrong, but the drives are not showing up as "Available disks".
I hooked up a drive directly to the MOBO and it shows up just fine.

*EDIT*
Ok i am at a loss here.
Windows does see them just fine. They are setup as JBOD in the controller.
When in FreeNas the command we ran earlier sees them but the GUI doesn't list them at all.
Ideas?

 

[justusiv]

Ugh this might be my issue. i just installed server 2012 and i dont see the disks either must be a build problem at this point.
I will keep you posted.
Thanks for your time.

 

[cyberjock]

You may need to be in JBOD mode or create a RAID with the disks to make them accessible. Keep in mind that RAIDing disks is not recommended for ZFS. ;)

 

[justusiv]

You may need to be in JBOD mode or create a RAID with the disks to make them accessible. Keep in mind that RAIDing disks is not recommended for ZFS. ;)

All the drives are in JBOD mode. according to the controller.
I will peak around inside the controller more to see if anything jumps out.
Windows sees them just fine as JBOD in this setup.

 

[cyberjock]

Sounds like a bug or something. You should have the device names after the "pass" in your camcontrol devlist output.

Here's mine for example...

Code:

<ATA WDC WD20EARS-00S 0A80>        at scbus3 target 0 lun 0 (pass1,da1)
<ATA WDC WD20EARS-00S 0A80>        at scbus3 target 1 lun 0 (pass2,da2)
<ATA WDC WD20EARS-00S 0A80>        at scbus3 target 2 lun 0 (pass3,da3)
<ATA WDC WD20EARS-00S 0A80>        at scbus3 target 3 lun 0 (pass4,da4)
<ATA WDC WD20EARS-00S 0A80>        at scbus3 target 8 lun 0 (pass5,da5)
<ATA WDC WD20EARS-00S 0A80>        at scbus3 target 9 lun 0 (pass6,da6)

 

[justusiv]

:( Where do i go from here? Any time the drive goes through the 51645 is doesn't get that device name.
*EDIT*
Plugged the drive directly into the mobo and it gets a name.

<ST32000644NS SN11> at scbus12 target 1 lun 0 (ada0,pass1)

 

[justusiv]

Just a status update.
I know its not recommended but i setup a bunch of simple volumes(single drive raids) and now it sees it the drives as opposed to running them as JBOD it didn't see them. Running the camcontrol devlist i still don't see device names but i see them in the GUI.
Thoughts on why the JBOD setup isnt working?

 

[enyboricua]

I am having the same exact problem. FreeNAS does not assign a device name even though it can see the drives with this card in JBOD mode.

Sounds like a bug or something. You should have the device names after the "pass" in your camcontrol devlist output./QUOTE]

If it is a bug should we submit a bug report?


Here is my output:

<WDC WD40EFRX-68W 80.0> at scbus0 target 0 lun 0 (pass0)
<WDC WD40EFRX-68W 80.0> at scbus0 target 1 lun 0 (pass1)
<WDC WD40EFRX-68W 80.0> at scbus0 target 2 lun 0 (pass2)
<WDC WD40EFRX-68W 80.0> at scbus0 target 3 lun 0 (pass3)
<WDC WD40EFRX-68W 80.0> at scbus0 target 4 lun 0 (pass4)
<WDC WD40EFRX-68W 80.0> at scbus0 target 5 lun 0 (pass5)
<INTEL SSDSA2CT040G3 4PC10302> at scbus7 target 0 lun 0 (ada0,pass6)
<CENTON DS Pro 8.07> at scbus14 target 0 lun 0 (pass7,da0)

 

[saridnour]

Been looking online and can't find an answer and this thread was as close if not the same issue. I hope someone here can help.

My supported adaptec 5805z is setup with a Raid-0 as a test. The OS can see & load the card but is not assigning a name to the logical or physical disks.

<NECVMWar VMware IDE CDR10 1.00> at scbus1 target 0 lun 0 (pass0,cd0)
<VMware Virtual disk 1.0> at scbus2 target 0 lun 0 (pass1,da0)
<WDC WD2000JD-00H 08.0> at scbus3 target 4 lun 0 (pass2) <--- ?
< ST3160023AS 3.43> at scbus3 target 5 lun 0 (pass3) <--- ?
< OCZ-AGILITY3 2.50> at scbus3 target 7 lun 0 (pass4) <--- ?

My end goal is to set this drive up as a raid6 and use iscsi to share out the resource and possibly have a backup drive to mirror it too.
If someone has a better solution please feel free to share.

I am running FreeNas and have tried versions 8 (last rel ver), 9.1, current release and daily alpha with Same result.
I am running in ESXI latest using my adaptec 5805z raid card in pass through mode.
I am building my VMDK's from setup using the iso's from freenas.
The same passthrough and raid combo works fine in a win 7 vm.

I know windows and am learning Linux so bare with me a bit but am pretty resourceful & with enough detail or pointers can work through most things. Google is my friend.. :)


Why do I not get an daX name for these drives?
Why do I not see a listing for the built up logical raid-0 drive?
Why is freenas not seeing anything (assumed its do to no name being issued)?
Can I force a name assignment?
Anything else I need do for FreeNas to see the drive(s)?
Anyone recommend using another distro to do iscsi easily from a hardware raid in the event this does not work (or I'm going about this wrong)?

Thanks in advance for any and all info. I can do all this in windows just want to make it work in Linux :)
-saridnour
Seattle

 

[saridnour]

Bump.. sure hope someone has some info here... My SAN is sitting unused as can't leverage it the way I need to..

 

[cyberjock]

The solution is to not use that card. Adaptec cards are the bane of existence for FreeNAS. Hardware RAID + ZFS = fail.

Go with one of the recommended models in one of our many stickies/guides around the forum and you'll see this problem go away.

 

[saridnour]

Thanks CyberJock, well already bought the card so I'm a bit committed to it at this point.. Just wanted to run iscsi SAN but guess will stick to windows solutions for now.
Was already concerned with running under esxi and why wanted a hardware solution.. had thought that one was supported. oh well...
Maybe I will build out with my LSI in esxi and go software in Freenas as a redundant to "play" with it.

-saridnour