03:45:57 <lundman> not seeing disks on new hardware: pci15d9,1b4b
03:46:03 <lundman> any hope?
03:55:06 <kebe> lundman: pci15d9,1b4b is the motherboard one.
03:55:48 <kebe> try this:  `prtconf -d | grep 1000`  or `prtconf -vp | grep 1000`  I'm assuming you've an HBA of some sort on this supermicro (pci 15d9) machine?
03:56:25 * kebe is hoping 1000 matches because pci1000 is LSI-now-Broadcom.
03:57:42 <lundman> i took a guess, in data centre.. looking now
03:59:21 <lundman> grep for not attached might work too
04:01:03 <lundman> ok 15d9,1b99 
04:01:14 <lundman> pciex 1000,e6
04:01:20 <kebe_> Aha!
04:01:25 <kebe_> THAT is someting I can work with.
04:01:29 <lundman> you called it
04:01:37 <lundman> sas38xx
04:01:45 <kebe_> https://pci-ids.ucw.cz/read/PC/1000/00e6
04:01:55 <kebe_> Okay, first test...
04:02:08 <kebe_> `grep 1000,e9` /etc/driver_aliases
04:02:20 <kebe_> ooops e6 I meant
04:02:31 <kebe_> Likely no entry.
04:02:35 <lundman> none
04:02:52 <kebe_> This is OmniOS and you've a root pool that's NOT attached to the HBA, right?
04:02:57 <kebe_> Or is this the installer?
04:03:10 <lundman> installet 44
04:03:27 <kebe_> Hmmmm...
04:03:46 <lundman> highest 1000 is d2
04:03:56 <kebe_> can you *edit* and save-out /etc/driver_aliases?  (Is it like  ramdisk root?  Been a while since I've played with the OmniOS installer.)
04:04:20 <lundman> yes
04:04:48 <kebe> Okay, add a line like one of the other mpt_sas entries, but for 1000,e6.
04:04:56 <kebe> Make sure quotes are in the right places, etc.
04:05:40 <lundman> yep five
04:05:42 <lundman> err five
04:05:46 <lundman> done
04:05:50 <lundman> stood phone
04:06:05 <kebe> huh?  "stood phone"?
04:06:27 <lundman> sorry my phone auto corrected done to five
04:06:41 <lundman> running disks
04:06:46 <kebe> Okay.
04:06:47 <lundman> command
04:06:50 <kebe> No.
04:06:51 <kebe> not yet.
04:07:00 <lundman> ok
04:07:16 <kebe> First you utter "devfsadm" which will re-read the driver_aliases file.  THIS MIGHT NOT WORK.  THIS MIGHT EVEN PANIC YOUR KERNEL.
04:07:26 <kebe> You're the first person I know with a 38xx chipset to try this on.
04:07:32 <kebe> Good luck.
04:07:36 <lundman> ran
04:07:45 <kebe> Got your shell back?
04:07:49 <kebe> Any console noise even?
04:08:17 <lundman> yeah complaining about other things
04:08:26 <kebe> Hmmmm... like what?
04:08:32 <lundman> removing link. pcie0
04:08:41 <kebe> Huh...
04:08:47 <lundman> 347c invalid contents
04:08:50 <kebe> But you have your shell?
04:09:07 <kebe> Is that from mpt_sas or some other driver?
04:09:27 <lundman> shell ok
04:09:34 <lundman> i think unrelated
04:09:52 <kebe> Try diskinfo now?
04:10:09 <lundman> only usb
04:10:21 <kebe> Shit.  What does "modinfo | grep mpt_sas" have to say?
04:10:25 <lundman> wish i took bloody version
04:10:40 <kebe> Probably wouldn't have helped you.
04:10:57 <lundman> mptsas loaded 191 00.00.00.24
04:11:49 <kebe> SHould look more like:
04:11:50 <kebe> 249 fffffffff83d9000  37bd0 185   1  igb (Intel 1Gb Ethernet) 
04:11:59 <kebe> but "mpt_sas" and differenet values.
04:12:07 <lundman> yes it does
04:12:14 <kebe> Okay.  So the driver loaded...
04:12:17 <kebe> Wait.
04:12:19 <lundman> prtconf has it attached as well
04:12:24 <lundman> just no disks
04:12:48 <kebe> `cfgadm -l ` (might need to pipe it into a pager).
04:13:04 <kebe> Anything pop up there for scsi/SAS ?
04:13:11 <lundman> no cfgadm in installer
04:14:45 <kebe> Oh damn.
04:15:08 <kebe> Okay... if you can find someone to ROLL you an installer that has THAT line added in /etc/driver_aliases you can try again.
04:15:44 <kebe> I'd normally offer to roll a SmartOS USB or ISO but I've my own issues with getting a release out this week and helping RM with the IPD 38 YMM work.
04:16:27 <lundman> thanks. my time is up here, will ask them to send a card for us to play with
04:16:33 <lundman> thank you for your help
04:17:21 <kebe> You're not the only one asking about the 9500 with the 38xx chipset in it.  nomad has skin in that game too.
04:18:07 <kebe> Part of me thinks just adding the line to driver_aliases will be sufficient, from what I recall seeing in the freebsd equivalent of mpt_sas, but it's been long enough where I'm not 100% sure.
04:18:44 <lundman> yeah it certainly seemed happy to attach it
04:19:59 <kebe> My SAS-fu is weak.  We use NVME or SATA in-house at MNX, and I use SATA at home on both HDC (OmniOS) and Kebecloud (Triton/SmartOS).
04:21:45 <kebe> It's past midnight here, I'm off to bed.  (And tomorrow I have to run more tests on YMM before getting ready to cut this week's SmartOS.)
15:05:49 <nomad> kebe, we went ahead and ordered the new file server with both a 3008 and a 9500 card. Hopefully we'll be able to use the 9500 soonish.
15:07:03 <nomad> I'm going to try to find a way to get you access to a host with the 9500 (and the 3108 :) installed for when you (or someone else with devskill) has time to look at it.
18:42:55 <richlowe> when does bloody update its illumos?
18:44:41 <hadfl> usually on thursday
19:09:01 <pmooney> is there a plan to push updated versions of the onbld package with the gcc10-as-primary env files?
19:09:13 <pmooney> I saw that had been backported to the various branches
19:18:15 <hadfl> yes the packages should land after tomorrow's merge. let me know if you need them more urgently
19:19:08 <hadfl> that is for bloody. for the releases they'll be published with the next release which has no due date, yet
19:22:39 <pmooney> no urgency on bloody
19:23:37 <pmooney> considering gcc10 builds are expected for upstreaming now, does it make sense to get an updated package out for the releases?
19:25:51 <richlowe> I had no idea anyone at all used the onbld env files.
19:26:15 <richlowe> rather than the ones in usr/src/tools/env 
19:26:32 <richlowe> that's certainly good to know, because I need to sort out the onbld mess one day
19:42:39 <hadfl> we can certainly get a release out for just onbld for all releases rather than waiting for more things before cutting a new release
19:43:11 <hadfl> https://downloads.omnios.org/env/ << there are also up to date .env files to grab from here
22:55:26 <pmooney> richlowe: I use the omnios ones since they have the necessary local overrides
22:57:04 <pmooney> hadfl: I don't know what all is involved with cutting a release (more than pushing an updated package for developer/onbld), but considering that using those env files is the documented way for doing builds per the omnios site, it'd be nice for them to be in a configuration "acceptable" for the gate
22:57:39 <pmooney> I have no problem modifying my own local configs.  I'm just thinking about anyone else who walks up to the project