Date: Thu, 19 Nov 2015 16:20:57 -0700 From: Scott Long <scott4long@yahoo.com> To: Jonathon Reinhart <jonathon.reinhart@gmail.com> Cc: Sean Bruno <sbruno@freebsd.org>, freebsd-scsi@freebsd.org Subject: Re: ciss(4) HP Smart Array P840 Message-ID: <78A8F47E-211F-4DE1-8B39-8978A5D9B7F5@yahoo.com> In-Reply-To: <CAPFHKzeetkCrvA1PwqoGYKUALEAAWpS9=%2Bm8MRF7wnW_Wf%2BwXA@mail.gmail.com> References: <CAPFHKzf65eSsg0aNe5wjS1jUVeh7gd9xgvAvMVuc6Shunsc9GA@mail.gmail.com> <564E05E7.8020307@freebsd.org> <CAPFHKzeetkCrvA1PwqoGYKUALEAAWpS9=%2Bm8MRF7wnW_Wf%2BwXA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Nov 19, 2015, at 12:44 PM, Jonathon Reinhart = <jonathon.reinhart@gmail.com> wrote: >=20 > On Thu, Nov 19, 2015 at 12:24 PM, Sean Bruno <sbruno@freebsd.org> = wrote: >> On 11/19/15 09:03, Jonathon Reinhart wrote: >>> Hello all, >>>=20 >>> TL;DR: Why isn't the P840 supported by ciss(4)? >>>=20 >> I think I was the last person actively maintaining this driver for an >> employer. HP doesn't have staff to do this support any longer and I >> no longer work/have this hardware. >>=20 >> That's pretty much it as far as I can tell with this product line. >> Someone has to put in the effort to get farther along with the = hardware. >>=20 >>>=20 >>> I tried to setup FreeNAS 9.3 (running 9.3-RELEASE-p25) on an HP >>> DL380 Gen9, with the P840 RAID controller. I didn't realize that >>> the P840 is not officially supported by the ciss(4) driver. In my >>> troubleshooting, I ended up in the same place as documented on this >>> forums.freenas.org post >>> = <https://forums.freenas.org/index.php?threads/hp-gen9-server-w-p840-hba-mo= de-no-drives-visible.28620/>: >>>=20 >>>=20 >>>> It's interesting that camcontrol devlist shows the drives, but >>>> there are no da* or ada* designations for them. I don't know what >>>> that means, but I'd speculate it's something driver-related. >>>=20 >>> Indeed: >>>=20 >>> # camcontrol devlist -v scbus0 on ciss0 bus 0: scbus1 on ciss0 bus >>> 32: <ATA ST1000DM003-1ER1 CC46> at scbus1 target 4 lun 0 >>> (pass0) <ATA ST1000DM003-1ER1 CC46> at scbus1 target 5 lun 0 >>> (pass1) scbus2 on ciss0 bus 33: ... >>>=20 >>> But there are no device names listed there, after passX, or in >>> /dev. >>>=20 >>=20 >> ciss(4) has "scsi-like" features which mean that behavior like this = is >> kind of expected. >>=20 >>> I see in the ciss source >>> = (https://github.com/freebsd/freebsd/blame/master/sys/dev/ciss/ciss.c#L320)= >>>=20 >>>=20 >> that the VID/DID for this card (0x103C, 0x3239) is listed. >>>=20 >>=20 >> Yup. I was asked to add that almost 3 years ago by HP before their >> team and my employment ended. >>=20 >>> I'm new to FreeBSD, but I'm confused as to how the driver supports >>> this card enough to read the drive model numbers, but not enough >>> to actually use the drives. Is there something I'm missing, or is >>> there some other technical reason this controller can't be used? >>>=20 >>> Thank you for your time, >>>=20 >>> Jonathon Reinhart >>=20 >>=20 >> I'm more than willing to help out here, you might want to push on HP >> if possible to get someone to reach out to me with details on what >> needs to be modified to support this controller. I no longer have >> valid contacts to get this information. :-( >>=20 >> sean >>=20 >> bcc jonathon >=20 > Thanks for the quick reply, Sean. >=20 > I took a quick look at the Linux hpsa driver (which obsoletes cciss) > to see if they treat these new cards any differently, and they don't > appear to do so, at all. AFAICT every supported board uses the same > "SA5_access" method. Which makes me again wonder why, given the > FreeBSD driver has the right VID/DID, it doesn't *just work*. I'd > probably have to turn on CISS debugging to see if there's any useful > info. Since you can see the volumes in camcontrol, the low-level driver and = communications protocol is working. What=E2=80=99s odd at the moment is = that the volumes are returning an inquiry response that CAM doesn=E2=80=99= t fully understand; that=E2=80=99s why you get the pass devices but no = da devices. Can you use camcontrol to do an inquiry request and send me = the results? Something like the following: sudo camcontrol cmd -n pass -u 0 -v -c "12 00 00 00 ff 00" -i 255 - | hd Thanks, Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?78A8F47E-211F-4DE1-8B39-8978A5D9B7F5>