Get rid of FW Upload tce invalid! messages

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

RonanR

Member
Jul 27, 2018
47
2
8
Hi,
I'm currently using Napp-it on Omnios151038. When I use sas3ircu so I can get the correct slot info, I got the log file flooded by "FW Upload tce invalid!" warning messages.
I know these message aren't critical, but as it flood the messages log, it makes huge log files and its quite difficult to read afterward.
Is there a way to avoid this?
Many thanks in advance
Ronan
 

gea

Well-Known Member
Dec 31, 2010
3,156
1,195
113
DE
sas3ircu is a very valuable tool. Sadly Broadcom does not support any longer. There are only quite old versions available and the newer ones of them are for Oracle Solaris only. There is a patch to make them work under OmniOS but all versions have the annoying console messages that cannot be avoided even with a 2> /dev/null.

Only solution is to disable use of sas3ircu in menu Disks > Disk Detection > select sas3iru (set to none). Napp-it itself does not need sas3ircu for disk detection or disk maps. Only downside is that you can no longer detect disks via red alert led (you can use the dd detection method). If you have created a map via sas3ircu you must re-create as the otherwise used driver based slot detection gives different slot numbers,

disk map ex
 

Attachments

Last edited:

RonanR

Member
Jul 27, 2018
47
2
8
Hi Gea,
I've got a server with two SAS backplane which both are recognized as e0 m0 without sas3ircu, so I can map only half of the drives because the slot numbers are duplicated.
With sas3ircu, I properly got e0 m0 and e0 m1 (or is it e1 m0? I can't remember and I don't have access to the server right now), so all drives are available for mapping.
That's why I was searching for a solution.
Ronan
 

gea

Well-Known Member
Dec 31, 2010
3,156
1,195
113
DE
which napp-it release?
direct connect or expander?
expander daisy chain cabling or each backplane to a different HBA port?
 

RonanR

Member
Jul 27, 2018
47
2
8
Hi Gea,
I've made tests on a second server, using 3 bakcplanes of 15 disks each, each backplane connected to a different SAS port on a Supermicro AOC S3216 HBA card. Napp-It version is 21.06.
When I issue the command echo "::mptsas -t" | sudo mdb -k to get disk info without sasircu, I got:
Code:
        mptsas_t inst ncmds suspend  power
================================================================================
fffffe23741f8000    0     0       0 ON=D0
                
                  mptsas_target_t slot devhdl      wwn     ncmds throttle   dr_flag dups
                 ----------------------------------------------------------------------
                 fffffe2375e95000    0   18 5000cca0bfc5633d   0     MAX   INACTIVE 0
                 fffffe23771d9080    1   19 5000cca0bfc526d0   0     MAX   INACTIVE 0
                 fffffe23771d9600    2   20 5000cca0bfc547cc   0     MAX   INACTIVE 0
                 fffffe237aa02500    3   21 5000cca0bfc559ec   0     MAX   INACTIVE 0
                 fffffe23781e2100    4   22 5000cca0bef01f98   0     MAX   INACTIVE 0
                 fffffe23779ae080    5   23 5000cca0c2d06df7   0     MAX   INACTIVE 0
                 fffffe237aa02f00    6   24 5000cca0c2d04d72   0     MAX   INACTIVE 0
                 fffffe23779ae500    7   25 5000cca0c2d04d73   0     MAX   INACTIVE 0
                 fffffe237aa02280    8   26 5000cca0c2d04314   0     MAX   INACTIVE 0
                 fffffe23781e2f00    9   27 5000cca0c2d034ed   0     MAX   INACTIVE 0
                 fffffe237aa02180   10   28 5000cca0c2cfe01b   0     MAX   INACTIVE 0
                 fffffe23779ae700   11   29 5000cca0c2d06acc   0     MAX   INACTIVE 0
                 fffffe237aa02c00   12   30 5000cca0c2d02ccc   0     MAX   INACTIVE 0
                 fffffe23781e2b80   13   31 5000cca0c2cafb38   0     MAX   INACTIVE 0
                 fffffe237aa02680   14   32 5000cca0c2d046bd   0     MAX   INACTIVE 0
                 fffffe23771d9680   20   33 50015b21408a477d   0     MAX   INACTIVE 0
                 fffffe237aa02200    0   36 5000cca0c2d04590   0     MAX   INACTIVE 0
                 fffffe2376e65700    1   37 5000cca0c2d046a5   0     MAX   INACTIVE 0
                 fffffe237aa02e80    2   38 5000cca0c2d03413   0     MAX   INACTIVE 0
                 fffffe237aa02800    3   39 5000cca0c2d01b3c   0     MAX   INACTIVE 0
                 fffffe23779aea80    4   40 5000cca0c2d04e33   0     MAX   INACTIVE 0
                 fffffe23781e2a00    5   41 5000cca0c2d06e0f   0     MAX   INACTIVE 0
                 fffffe23bebeab00    6   42 5000cca0c2d04de9   0     MAX   INACTIVE 0
                 fffffe23bebeaa80    7   43 5000cca0c2d04de2   0     MAX   INACTIVE 0
                 fffffe23bebeaa00    0   44 5000cca0c2d03553   0     MAX   INACTIVE 0
                 fffffe23bebea980    1   45 5000cca0c2d04e6b   0     MAX   INACTIVE 0
                 fffffe23bebea900    2   46 5000cca0c2d0386d   0     MAX   INACTIVE 0
                 fffffe23bebea880    3   47 5000cca0c2d03316   0     MAX   INACTIVE 0
                 fffffe23bebea800    4   48 5000cca0c2d041e9   0     MAX   INACTIVE 0
                 fffffe23bebea780    5   49 5000cca0c2cfdd43   0     MAX   INACTIVE 0
                 fffffe23bebea700    6   50 5000cca0c2d03477   0     MAX   INACTIVE 0
                 fffffe23bebea680    7   51 5000cca0c2d0394f   0     MAX   INACTIVE 0
                 fffffe23bebea600    8   52 5000cca0c2cfee01   0     MAX   INACTIVE 0
                 fffffe23bebea580    9   53 5000cca0c2d04261   0     MAX   INACTIVE 0
                 fffffe23bebea500   10   54 5000cca0c2d049f7   0     MAX   INACTIVE 0
                 fffffe23bebea480   11   55 5000cca0c2d046cb   0     MAX   INACTIVE 0
                 fffffe23bebea400   12   56 5000cca0c2ced51e   0     MAX   INACTIVE 0
                 fffffe23bebea380   13   57 5000cca0c2d036a2   0     MAX   INACTIVE 0
                 fffffe23bebea300   14   58 5000cca0c2d067b5   0     MAX   INACTIVE 0
                 fffffe23bebea280    8   59 5000cca0c2d076a6   0     MAX   INACTIVE 0
                 fffffe23bebea200    9   60 5000cca0c2d01a56   0     MAX   INACTIVE 0
                 fffffe23781d2e00   10   61 5000cca0c2d02742   0     MAX   INACTIVE 0
                 fffffe23bebea180   11   62 5000cca0c2d06e1b   0     MAX   INACTIVE 0
                 fffffe23bebea100   12   63 5000cca0c2d07456   0     MAX   INACTIVE 0
                 fffffe23bebea080   13   64 5000cca0c2d0713a   0     MAX   INACTIVE 0
                 fffffe23bebea000   14   65 5000cca0c2d06a85   0     MAX   INACTIVE 0
                 fffffe23bf08df00   20   66 50015b21408a4a7d   0     MAX   INACTIVE 0
                 fffffe23bf08de80   20   67 50015b21408b3c7d   0     MAX   INACTIVE 0
                
                     mptsas_smp_t devhdl      wwn          phymask
                 ---------------------------------------------------------
                 fffffe238ae375a0     17  50015b21408a477f    000f
                 fffffe238acfeba8     34  50015b21408a4a7f    00f0
                 fffffe23779021f0     35  50015b21408b3c7f    0f00
 

gea

Well-Known Member
Dec 31, 2010
3,156
1,195
113
DE
Can you compare a daisy chain cabling HBA -> jbod1 -> jbod2 -> jbod3 ?
Otherwise unique slot numbers would require a HBA per backplane.

Maybe a switch from slot id detection to devhdl may help to give a unique result but this would require some tests with different HBAs