not seeing disks on new hardware: pci15d9,1b4b

any hope?

lundman: pci15d9,1b4b is the motherboard one.

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?

i took a guess, in data centre.. looking now

grep for not attached might work too

ok 15d9,1b99

pciex 1000,e6

Aha!

THAT is someting I can work with.

you called it

sas38xx

Okay, first test...

`grep 1000,e9` /etc/driver_aliases

ooops e6 I meant

Likely no entry.

none

This is OmniOS and you've a root pool that's NOT attached to the HBA, right?

Or is this the installer?

installet 44

Hmmmm...

highest 1000 is d2

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.)

yes

Okay, add a line like one of the other mpt_sas entries, but for 1000,e6.

Make sure quotes are in the right places, etc.

yep five

err five

done

stood phone

huh? "stood phone"?

sorry my phone auto corrected done to five

running disks

Okay.

command

No.

not yet.

ok

First you utter "devfsadm" which will re-read the driver_aliases file. THIS MIGHT NOT WORK. THIS MIGHT EVEN PANIC YOUR KERNEL.

You're the first person I know with a 38xx chipset to try this on.

Good luck.

ran

Got your shell back?

Any console noise even?

yeah complaining about other things

Hmmmm... like what?

removing link. pcie0

Huh...

347c invalid contents

But you have your shell?

Is that from mpt_sas or some other driver?

shell ok

i think unrelated

Try diskinfo now?

only usb

Shit. What does "modinfo | grep mpt_sas" have to say?

wish i took bloody version

Probably wouldn't have helped you.

mptsas loaded 191 00.00.00.24

SHould look more like:

249 fffffffff83d9000 37bd0 185 1 igb (Intel 1Gb Ethernet)

but "mpt_sas" and differenet values.

yes it does

Okay. So the driver loaded...

Wait.

prtconf has it attached as well

just no disks

`cfgadm -l ` (might need to pipe it into a pager).

Anything pop up there for scsi/SAS ?

no cfgadm in installer

Oh damn.

Okay... if you can find someone to ROLL you an installer that has THAT line added in /etc/driver_aliases you can try again.

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.

thanks. my time is up here, will ask them to send a card for us to play with

thank you for your help

You're not the only one asking about the 9500 with the 38xx chipset in it. nomad has skin in that game too.

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.

yeah it certainly seemed happy to attach it

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).

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.)

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.

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.

when does bloody update its illumos?

usually on thursday

is there a plan to push updated versions of the onbld package with the gcc10-as-primary env files?

I saw that had been backported to the various branches

yes the packages should land after tomorrow's merge. let me know if you need them more urgently

that is for bloody. for the releases they'll be published with the next release which has no due date, yet

no urgency on bloody

considering gcc10 builds are expected for upstreaming now, does it make sense to get an updated package out for the releases?

I had no idea anyone at all used the onbld env files.

rather than the ones in usr/src/tools/env

that's certainly good to know, because I need to sort out the onbld mess one day

we can certainly get a release out for just onbld for all releases rather than waiting for more things before cutting a new release

downloads.omnios.org/env << there are also up to date .env files to grab from here

richlowe: I use the omnios ones since they have the necessary local overrides

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

I have no problem modifying my own local configs. I'm just thinking about anyone else who walks up to the project