Weird security output- Want help understanding what it is

[Ceetan]

I recently got this out put from my FreeNAS box

Code:

Darwin.local kernel log messages:
> ugen0.3: <vendor 0x0557> at usbus0 (disconnected)
> ipmi0: uhub1: KCS: Reply address mismatch
> at uhub0, port 12, addr 2 (disconnected)
> ugen0.4: <vendor 0x0557> at usbus0 (disconnected)
> ukbd0: at uhub1, port 1, addr 3 (disconnected)
> ums0: at uhub1, port 1, addr 3 (disconnected)
> ipmi0: KCS Error Data ff
> ipmi0: KCS Error Data ff
> usbd_setup_device_desc: getting device descriptor at addr 4 failed, USB_ERR_SHORT_XFER
> ugen0.3: <vendor 0x0557> at usbus0
> uhub1: <vendor 0x0557 product 0x7000, class 9/0, rev 2.00/0.00, addr 4> on usbus0
> uhub1: 4 ports with 3 removable, self powered
> ugen0.4: <vendor 0x0557> at usbus0
> ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 5> on usbus0
> kbd0 at ukbd0
> ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 5> on usbus0
> ums0: 3 buttons and [XYZ] coordinates ID=0
> ipmi0: KCS: Error retry exhausted
> ugen0.4: <vendor 0x0557> at usbus0 (disconnected)
> ukbd0: at uhub1, port 1, addr 5 (disconnected)
> ums0: at uhub1, port 1, addr 5 (disconnected)
> ugen0.4: <vendor 0x0557> at usbus0
> ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 6> on usbus0
> kbd0 at ukbd0
> ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 6> on usbus0
> ums0: 3 buttons and [Z] coordinates ID=0
> ipmi0: KCS: Failed to start write
> ipmi0: KCS error: ff
> ugen0.3: <vendor 0x0557> at usbus0 (disconnected)
> ipmi0: uhub1: KCS: Reply address mismatch
> at uhub0, port 12, addr 4 (disconnected)
> ugen0.4: <vendor 0x0557> at usbus0 (disconnected)
> ukbd0: at uhub1, port 1, addr 6 (disconnected)
> ums0: at uhub1, port 1, addr 6 (disconnected)
> ipmi0: KCS Error Data ff
> ipmi0: KCS Error Data ff
> usbd_setup_device_desc: getting device descriptor at addr 7 failed, USB_ERR_SHORT_XFER
> ugen0.3: <vendor 0x0557> at usbus0
> uhub1: <vendor 0x0557 product 0x7000, class 9/0, rev 2.00/0.00, addr 7> on usbus0
> uhub1: 4 ports with 3 removable, self powered
> ugen0.4: <vendor 0x0557> at usbus0
> ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 8> on usbus0
> kbd0 at ukbd0
> ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 8> on usbus0
> ums0: 3 buttons and [XYZ] coordinates ID=0
> ipmi0: KCS: Error retry exhausted
> ugen0.4: <vendor 0x0557> at usbus0 (disconnected)
> ukbd0: at uhub1, port 1, addr 8 (disconnected)
> ums0: at uhub1, port 1, addr 8 (disconnected)
> ugen0.4: <vendor 0x0557> at usbus0
> ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 9> on usbus0
> kbd0 at ukbd0
> ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 9> on usbus0
> ums0: 3 buttons and [Z] coordinates ID=0
> ipmi0: KCS: Failed to start write
> ipmi0: KCS error: ff
> ugen0.3: <vendor 0x0557> at usbus0 (disconnected)
> uhub1: at uhub0, port 12, addr 7 (disconnected)
> ipmi0: KCS: Reply address mismatch
> ugen0.4: <vendor 0x0557> at usbus0 (disconnected)
> ukbd0: at uhub1, port 1, addr 9 (disconnected)
> ums0: at uhub1, port 1, addr 9 (disconnected)
> ipmi0: KCS Error Data ff
> ipmi0: KCS Error Data ff
> usbd_setup_device_desc: getting device descriptor at addr 10 failed, USB_ERR_SHORT_XFER
> ugen0.3: <vendor 0x0557> at usbus0
> uhub1: <vendor 0x0557 product 0x7000, class 9/0, rev 2.00/0.00, addr 10> on usbus0
> uhub1: 4 ports with 3 removable, self powered
> ugen0.4: <vendor 0x0557> at usbus0
> ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 11> on usbus0
> kbd0 at ukbd0
> ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 11> on usbus0
> ums0: 3 buttons and [XYZ] coordinates ID=0
> ipmi0: KCS: Error retry exhausted
> ugen0.4: <vendor 0x0557> at usbus0 (disconnected)
> ukbd0: at uhub1, port 1, addr 11 (disconnected)
> ums0: at uhub1, port 1, addr 11 (disconnected)
> ugen0.4: <vendor 0x0557> at usbus0
> ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 12> on usbus0
> kbd0 at ukbd0
> ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 12> on usbus0
> ums0: 3 buttons and [Z] coordinates ID=0
> ipmi0: KCS: Failed to start write
> ipmi0: KCS error: ff
> ugen0.3: <vendor 0x0557> at usbus0 (disconnected)
> ipmi0: uhub1: KCS: Reply address mismatch
> at uhub0, port 12, addr 10 (disconnected)
> ugen0.4: <vendor 0x0557> at usbus0 (disconnected)
> ukbd0: at uhub1, port 1, addr 12 (disconnected)
> ums0: at uhub1, port 1, addr 12 (disconnected)
> ipmi0: KCS Error Data ff
> ipmi0: KCS Error Data ff
> usbd_setup_device_desc: getting device descriptor at addr 13 failed, USB_ERR_SHORT_XFER
> ugen0.3: <vendor 0x0557> at usbus0
> uhub1: <vendor 0x0557 product 0x7000, class 9/0, rev 2.00/0.00, addr 13> on usbus0
> uhub1: 4 ports with 3 removable, self powered
> ugen0.4: <vendor 0x0557> at usbus0
> ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 14> on usbus0
> kbd0 at ukbd0
> ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 14> on usbus0
> ums0: 3 buttons and [XYZ] coordinates ID=0
> ipmi0: KCS: Error retry exhausted
> ugen0.4: <vendor 0x0557> at usbus0 (disconnected)
> ukbd0: at uhub1, port 1, addr 14 (disconnected)
> ums0: at uhub1, port 1, addr 14 (disconnected)
> ugen0.4: <vendor 0x0557> at usbus0
> ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 15> on usbus0
> kbd0 at ukbd0
> ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 15> on usbus0
> ums0: 3 buttons and [Z] coordinates ID=0
> ipmi0: KCS: Failed to start write
> ipmi0: KCS error: ff
> ugen0.3: <vendor 0x0557> at usbus0 (disconnected)
> ipmi0: uhub1: KCS: Reply address mismatch
> at uhub0, port 12, addr 13 (disconnected)
> ugen0.4: <vendor 0x0557> at usbus0 (disconnected)
> ukbd0: at uhub1, port 1, addr 15 (disconnected)
> ums0: at uhub1, port 1, addr 15 (disconnected)
> ipmi0: KCS Error Data ff
> ipmi0: KCS Error Data ff
> usbd_setup_device_desc: getting device descriptor at addr 16 failed, USB_ERR_SHORT_XFER
> ugen0.3: <vendor 0x0557> at usbus0
> uhub1: <vendor 0x0557 product 0x7000, class 9/0, rev 2.00/0.00, addr 16> on usbus0
> uhub1: 4 ports with 3 removable, self powered
> ugen0.4: <vendor 0x0557> at usbus0
> ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 17> on usbus0
> kbd0 at ukbd0
> ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 17> on usbus0
> ums0: 3 buttons and [XYZ] coordinates ID=0
> ipmi0: KCS: Error retry exhausted
> ugen0.4: <vendor 0x0557> at usbus0 (disconnected)
> ukbd0: at uhub1, port 1, addr 17 (disconnected)
> ums0: at uhub1, port 1, addr 17 (disconnected)
> ugen0.4: <vendor 0x0557> at usbus0
> ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 18> on usbus0
> kbd0 at ukbd0
> ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 18> on usbus0
> ums0: 3 buttons and [Z] coordinates ID=0
> ipmi0: KCS: Failed to start write
> ipmi0: KCS error: ff

-- End of security output --

From what I could gather, this seems to actually be to issues, both of which are, to some degree, known. One seems to be related to usb, one the IPMI. I gathered it was a good idea to powercycle everythig, and I have yet to see it repeat itself. Howevere, I want to incrase FreeNAS literacy, so i would like to understans more about it.

So Question 1:
What/Why is the IPMI bit?

Question 2:
The USB-thing, is that because I have conected the UPS to an usb3-port, when ideal, it should be 2.

Question 3: Should i take some addidtional precautionary measures.

Bonas Question: How can I check if I have the lates BIOS and IPMI- frimware? The Supermicro site is hare to navigate.

 

[Ericloewe]

Is this on your X11SSL-CF? For future reference, please explicitly include the hardware you're using to make things clearer and to help people on mobile, since sigs don't show up there.

Bonas Question: How can I check if I have the lates BIOS and IPMI- frimware? The Supermicro site is hare to navigate.

Google "X11SSL-CF". Open the supermicro product page twice. In one tab, click on BIOS updates, in the other BMC/IPMI firmware.

The USB-thing, is that because I have conected the UPS to an usb3-port, when ideal, it should be 2.

No. It could be a misbehaving USB device, but it's hard to say for sure. Possibly a dodgy USB hub?

What/Why is the IPMI bit?

They could have a common root cause, since the BMC also interacts via USB.

It's a bit of a weird series of errors. Might have been a fluke, so just keep an eye on things and if the problem returns we'll figure out what to do.

 

[Ceetan]

Ak...I always forget that sigs don't show on mobile .
This is the hardware
FreeNAS 9.10-u2 Stable
MOBO: Supermicro X11SSL-CF with
CPU: Intel Core i3-6100
RAM 2*16GB Crucial DDR4 ECC 2133MHz (CT2K16G4WFD8213)
8* WD Red WD40EFRX 64MB 4TB in RAIDZ2
BOOT: 90GB Corsair SSD
CASE: Fractal design node 804
PSU:EVGA SuperNOVA 650 G2
UPS: APC BE700G-GR
Fan Control: Hybrid CPU & HD Fan Zone Controller Script

 

[Ceetan]

Got some more output, of a diffrent nature this time. Figured it didn't merit a new thread. What is it trying to tell me about da2?
Should I be worried about the warnings?
Some googling lead me to believe they were pretty minor but I would still like to understand them.

Code:

Darwin.local changes in mounted filesystems:
3c3
< freenas-boot/ROOT/9.10.2 /					zfs	 rw,noatime,nfsv4acls	0 0
---
> freenas-boot/ROOT/9.10.2-U1 /				 zfs	 rw,noatime,nfsv4acls	0 0

Darwin.local kernel log messages:
> FreeBSD 10.3-STABLE #0 r295946+1805185(9.10.2-STABLE): Wed Jan 11 17:12:42 UTC 2017
> avail memory = 33078190080 (31545 MB)
> mpr0: Firmware: 12.00.02.00, Driver: 13.01.00.00-fbsd
> mpr0: SAS Address for SATA device = 49665d6fedb1cb89
> mpr0: SAS Address from SAS device page0 = 4433221100000000
> ada0 at ahcich1 bus 0 scbus2 target 0 lun 0
> ada0: <Corsair CSSD-F90GB2 2.0> ATA8-ACS SATA 2.x device
> ada0: Serial Number 11026523330003350029
> ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
> ada0: Command Queueing enabled
> ada0: 85857MB (175836528 512 byte sectors)
> ada0: quirks=0x1<4K>
> ada0: Previously was known as ad6
> da2 at mpr0 bus 0 scbus0 target 2 lun 0
> da2: <ATA WDC WD40EFRX-68W 0A82> Fixed Direct Access SPC-4 SCSI device
> da2: Serial Number	  WD-WCC4E7ZT7A7J
> da2: 600.000MB/s transfers
> da2: Command Queueing enabled
> da2: 3815447MB (7814037168 512 byte sectors)
> da2: quirks=0x8<4K>
> Timecounter "TSC-low" frequency 1848091476 Hz quality 1000
> Trying to mount root from zfs:freenas-boot/ROOT/9.10.2-U1 []...
> warning: KLD '/boot/kernel/dtraceall.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/dtrace.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/dtmalloc.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/dtnfscl.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/fbt.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/fasttrap.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/lockstat.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/sdt.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/systrace.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/systrace_freebsd32.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/profile.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/smbus.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/t3_tom.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/toecore.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/t4_tom.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/uhid.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/ums.ko' is newer than the linker.hints file
> warning: KLD '/boot/kernel/ng_ether.ko' is newer than the linker.hints file
> Syncing disks, vnodes remaining...0 0 0 0 done
> Uptime: 1m14s
> FreeBSD 10.3-STABLE #0 r295946+1805185(9.10.2-STABLE): Wed Jan 11 17:12:42 UTC 2017
> CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (3696.16-MHz K8-class CPU)
> mpr0: Found device <881<SataDev,Direct>,End Device> <6.0Gbps> handle<0x000f> enclosureHandle<0x0001> slot 6
> mpr0: Found device <881<SataDev,Direct>,End Device> <6.0Gbps> handle<0x0010> enclosureHandle<0x0001> slot 7
> SMP: AP CPU #2 Launched!
> Timecounter "TSC-low" frequency 1848080670 Hz quality 1000
> Trying to mount root from zfs:freenas-boot/ROOT/9.10.2-U1 []...

-- End of security output --

 

[joeschmuck]

I recieved a simliar output when I upgraded to 9.10.2-U1. This is a normal "Security" output, you can ignore this, you should not see this again until you upgrade again.

Your referencing the FreeNAS version is incorrect. I could assume that you are either using 9.10.1-U2 or 9.10.2-U2. Don't forget to use the entire version number. I will assume you mean 9.10.1-U2 since 9.10.2-U2 doesn't exist.

 

[Jailer]

Just got a similar error in my console and IPMI is not accessible. I have no USB devices attached to my system. I suspect since it was after 3AM I'll get the security run output email tomorrow.

System specs:
FreeNAS-9.10.2-U1 (86c7ef5)
Supermicro X10SL7-F
Xeon E-3 1240V3
32GB 2x Crucial ECC DDR3 1600 CT2KIT102472BD160B
6x3TB WD Greens RAIDZ2
Supermicro 16GB SATA DOM
Seasonic SS-660XP2

Code:

Jan 18 04:01:12 freenas ugen0.2: <vendor 0x0000> at usbus0 (disconnected)
Jan 18 04:01:12 freenas uhub3: at uhub1, port 7, addr 1 (disconnected)
Jan 18 04:01:12 freenas ipmi0: KCS: Reply address mismatch
Jan 18 04:01:12 freenas ugen0.3: <vendor 0x0557> at usbus0 (disconnected)
Jan 18 04:01:12 freenas ukbd0: at uhub3, port 1, addr 2 (disconnected)
Jan 18 04:01:12 freenas ums0: at uhub3, port 1, addr 2 (disconnected)
Jan 18 04:01:24 freenas ipmi0: KCS Error Data ff
Jan 18 04:01:31 freenas usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_SHORT_XFER
Jan 18 04:01:32 freenas ugen0.2: <vendor 0x0000> at usbus0
Jan 18 04:01:32 freenas uhub3: <vendor 0x0000 product 0x0001, class 9/0, rev 2.00/0.00, addr 3> on usbus0
Jan 18 04:01:32 freenas uhub3: 4 ports with 3 removable, self powered
Jan 18 04:01:33 freenas ugen0.3: <vendor 0x0557> at usbus0
Jan 18 04:01:33 freenas ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 4> on usbus0
Jan 18 04:01:33 freenas kbd0 at ukbd0
Jan 18 04:01:33 freenas ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 4> on usbus0
Jan 18 04:01:33 freenas ums0: 3 buttons and [XYZ] coordinates ID=0
Jan 18 04:01:42 freenas ipmi0: KCS Error Data ff
Jan 18 04:01:45 freenas ugen0.3: <vendor 0x0557> at usbus0 (disconnected)
Jan 18 04:01:45 freenas ukbd0: at uhub3, port 1, addr 4 (disconnected)
Jan 18 04:01:45 freenas ums0: at uhub3, port 1, addr 4 (disconnected)
Jan 18 04:01:48 freenas ugen0.3: <vendor 0x0557> at usbus0
Jan 18 04:01:48 freenas ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 5> on usbus0
Jan 18 04:01:48 freenas kbd0 at ukbd0
Jan 18 04:01:48 freenas ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 5> on usbus0
Jan 18 04:01:48 freenas ums0: 3 buttons and [Z] coordinates ID=0
Jan 18 04:01:48 freenas ipmi0: KCS: Error retry exhausted

 

[Jailer]

I did a reset on the BMC to factory defaults and it seems to be working again now.
ipmitool raw 0x3c 0x40

 

[Ceetan]

Got some more

Code:

> (da2:mpr0:0:2:0): WRITE(10). CDB: 2a 00 04 40 c5 50 00 00 08 00
> (da2:mpr0:0:2:0): CAM status: SCSI Status Error
> (da2:mpr0:0:2:0): SCSI status: Check Condition
> (da2:mpr0:0:2:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
> (da2:mpr0:0:2:0): Retrying command (per sense data)
> (da6:mpr0:0:6:0): WRITE(10). CDB: 2a 00 06 62 69 88 00 00 08 00
> (da6:mpr0:0:6:0): CAM status: SCSI Status Error
> (da6:mpr0:0:6:0): SCSI status: Check Condition
> (da6:mpr0:0:6:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
> (da6:mpr0:0:6:0): Retrying command (per sense data)

What do you think? marginal connection errors? My cables are edging in length.

 

[tvsjr]

Those particular errors could indicate any number of issues, from a failing drive to a failing HBA, cable, etc. Are the errors only on da2 and da6? I'd probably run a long SMART test on both drives to see what shows up.

 

[Ceetan]

It seems to have occurred again :/

Code:

Darwin.local kernel log messages:
> (da2:mpr0:0:2:0): WRITE(10). CDB: 2a 00 09 f9 72 60 00 00 08 00
> (da2:mpr0:0:2:0): CAM status: SCSI Status Error
> (da2:mpr0:0:2:0): SCSI status: Check Condition
> (da2:mpr0:0:2:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
> (da2:mpr0:0:2:0): Retrying command (per sense data)
> (da2:mpr0:0:2:0): WRITE(10). CDB: 2a 00 0a 6d 87 30 00 00 08 00
> (da2:mpr0:0:2:0): CAM status: SCSI Status Error
> (da2:mpr0:0:2:0): SCSI status: Check Condition
> (da2:mpr0:0:2:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
> (da2:mpr0:0:2:0): Retrying command (per sense data)
> (da1:mpr0:0:1:0): WRITE(10). CDB: 2a 00 58 75 fd 08 00 00 08 00
> (da1:mpr0:0:1:0): CAM status: SCSI Status Error
> (da1:mpr0:0:1:0): SCSI status: Check Condition
> (da1:mpr0:0:1:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
> (da1:mpr0:0:1:0): Retrying command (per sense data)

Smart results look okay as far as I can see,
http://pastebin.com/S2dUTBQf

I don't like where this is heading:
Failing hba most likely, or? As it is integrated into the mobo, It seems I may have to replace the entire thing :(

 

[Jailer]

Start with the cables, it's the easiest and cheapest thing to check first so rule that out before you go any further.

 

[Ceetan]

Can anyone recomend a cable brand?

 

[Ericloewe]

Anything that's not Super Happy Sun China Gold Quality Extra Awesome brand or equivalent.

 

[Ceetan]

OK. So I got some new output that I wanted some advice on.

first this bit

Code:

> (da2:mpr0:0:2:0): WRITE(10). CDB: 2a 00 0a 4d ed 70 00 00 08 00
> (da2:mpr0:0:2:0): CAM status: SCSI Status Error
> (da2:mpr0:0:2:0): SCSI status: Check Condition
> (da2:mpr0:0:2:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
> (da2:mpr0:0:2:0): Retrying command (per sense data)
> (da6:mpr0:0:6:0): WRITE(10). CDB: 2a 00 58 92 2c b8 00 00 08 00
> (da6:mpr0:0:6:0): CAM status: SCSI Status Error
> (da6:mpr0:0:6:0): SCSI status: Check Condition
> (da6:mpr0:0:6:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset, or bus device reset occurred)
> (da6:mpr0:0:6:0): Retrying command (per sense data)

It should be note that i (after i got the above) recently exported and imported the pool, as I changed to shorter breakout cables, and I got the impression that it was maybe a good thing to do.
folowing that, I got this

Code:

> CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (3696.18-MHz K8-class CPU)
> mpr0: SAS Address for SATA device = 49696b69de9fbe87
> mpr0: SAS Address from SATA device = 49696b69de9fbe87
> mpr0: SAS Address for SATA device = 49665d6fedb1cb89
> mpr0: SAS Address from SATA device = 49665d6fedb1cb89
> mpr0: SAS Address for SATA device = 4967566ddda3cc87
> mpr0: SAS Address from SATA device = 4967566ddda3cc87
> mpr0: Found device <881<SataDev,Direct>,End Device> <6.0Gbps> handle<0x000c> enclosureHandle<0x0001> slot 2
> mpr0: Found device <881<SataDev,Direct>,End Device> <6.0Gbps> handle<0x000b> enclosureHandle<0x0001> slot 3
> da0: Serial Number      WD-WCC4E7ZT7A7J
> da1: Serial Number      WD-WCC4E4LZFSDL
> da2: Serial Number      WD-WCC4E5EX6EEJ
> da3 at mpr0 bus 0 scbus0 target 3 lun 0
> da3: <ATA WDC WD40EFRX-68W 0A82> Fixed Direct Access SPC-4 SCSI device
> da3: Serial Number      WD-WCC4E3KNSVUV
> da3: 600.000MB/s transfers
> da3: Command Queueing enabled
> da3: 3815447MB (7814037168 512 byte sectors)
> da3: quirks=0x8<4K>
> Timecounter "TSC-low" frequency 1848091650 Hz quality 1000
> GEOM_ELI: Device da0p1.eli created.
> GEOM_ELI: Encryption: AES-XTS 128
> GEOM_ELI:     Crypto: hardware

It seems mostly to be the type of out pot that describes "current status" of sorts, but the GELI bits have me a little worried.

I also got this little bit,

Code:

> sonewconn: pcb 0xfffff800375b6930: Listen queue overflow: 2 already in queue awaiting acceptance

Any thing i should pay special attention to?