I'm getting bunches and bunches of these in dmesg:

Dec 19 11:07:00 hvfs1 ahci: [ID 296163 kern.warning] WARNING: ahci0: ahci port 5 has task file error

Dec 19 11:07:00 hvfs1 ahci: [ID 687168 kern.warning] WARNING: ahci0: ahci port 5 is trying to do error recovery

Dec 19 11:07:00 hvfs1 ahci: [ID 693748 kern.warning] WARNING: ahci0: ahci port 5 task_file_status = 0x451

Dec 19 11:07:00 hvfs1 ahci: [ID 332577 kern.warning] WARNING: ahci0: the below command (s) on port 5 are aborted

Dec 19 11:07:00 hvfs1 ahci: [ID 117845 kern.warning] WARNING: satapkt 0xfffffe844ff199e8: cmd_reg = 0xb0 features_reg = 0x0 sec_count_msb = 0x0 lba_low_msb = 0x4f lba_mid_msb = 0x4f lba_high_msb = 0x0 sec_count_lsb = 0x0 lba_low_lsb = 0x0 lba_mid_lsb = 0x4f lba_high_lsb = 0xc2 device_reg = 0x0 addr_type = 0x4 cmd_flags = 0x12

Dec 19 11:07:00 hvfs1 ahci: [ID 657156 kern.warning] WARNING: ahci0: error recovery for port 5 succeed

also saw for port 4, suspect lower numbers as well but it's scrolling off the top of the log.

an, nope, just 4 & 5

also, should 'smbd[554]: [ID 801721 daemon.error] SMF initialization problem: %s#012: handle not bound' be reported in the OmniOS or Illumos bug tracker?

illumos, but that looks unfortunate.

that's on x86 right?

I have a bug open for the %s thing at least, and I even wrote a patch but I need to rework it

Ok, that's a thing that sometimes happens?

last time I saw that was on another platform, and it was Bad.

The fact the handle is not bound might be, but the wonky error message is illumos 15132 (fenix)

BUG 15132: libsmb SMF initialization problem messages incorrect (In Progress)

↳ illumos.org/issues/15132 | code.illumos.org/c/illumos-gate/+/2484

I just need to find 30 minutes to finish that off

whew

richlowe, yes, x86.

should I not bother filing the report about the 'handle not bound' thing then?

any hints on what I should be doing about the ahci problem?

I'm assuming those are real disks on ports 4 and 5?

Are you running smartctl or smartmon? I've noticed when I run smartctl I see the cmd_reg... line, folowed by the recovery line.

I'm running smartd.

hmm. I'm starting to think there's a real hardware problem here :(

I'm migrating a bunch of VMDKs back to this host (just patched & rebooted) and it's going very slowly.

Dec 19 11:34:35 hvfs1 mr_sas: [ID 992625 kern.notice] mr_sas0: cmd retry count = 1

Dec 19 11:34:35 hvfs1 mr_sas: [ID 992625 kern.notice] mr_sas0: cmd retry count = 1

Dec 19 11:34:35 hvfs1 mr_sas: [ID 692495 kern.notice] NOTICE: mr_sas0: TBOLT adapter reset successfully

Dec 19 11:34:00 hvfs1 mr_sas: [ID 270009 kern.warning] WARNING: mr_sas0: io_timeout_checker: FW Fault, calling reset adapter

Dec 19 11:34:00 hvfs1 mr_sas: [ID 643100 kern.notice] mr_sas0: io_timeout_checker: fw_outstanding 0x2A max_fw_cmds 0x39F

Dec 19 11:34:14 hvfs1 mr_sas: [ID 229198 kern.notice] NOTICE: Device scan in progress ...#012

Dec 19 11:34:35 hvfs1 mr_sas: [ID 564675 kern.notice] NOTICE: mr_sas0: mrsas_print_pending_cmds(): Called

oh yeah, not looking happy :(

ZFS isn't complaining at all.

ugh. Looks like 15 DEC saw a burst of these errors. Yeah, it's not unique to today.

Is there a way to map "NOTICE: Device scan in progress ...#012" (logged by mr_sas to /var/adm/messages) to an actual device?

all of the hits I'm seeing in splunk mention #012 so I'm hoping that's just a failing SSD I can kick out of the pool.

I don't know it, but there likely is. (Unless it's dynamic every boot?)

I'm seeing it across multiple boots with the same number so I presume it's static.

I told the vendor we bought this box from we didn't need hardware RAID but they seem to have ignored that specification and given me an HBA that really wants to 'help'.

megaraid is megaannoying.

I have a feeling I'm going to be kicking this over to them to resolve.