[What x570 motherboard for virtualization with a 3900x?]

On 12/3/2019 at 3:20 PM, mbezzo said:

So, turns out that 3950 is damn near impossible to acquire, so I’ve “settled” on a 3900x which should arrive today. I’ll see if I can get the IOMMU groups here soon!

Hey, I am looking to buy the same board...wondering if you could share the IOMMU groups. Thanks!

[SMB bind network interface]

I tried and couldn’t get it work. SMB for whatever reason was always bound to the main Interface and I couldn’t get it to use the LAGG interface.

[SMB bind network interface]

16 hours ago, gagefox said:

did you ever figure this out? Im having the same problem

No. Apparently you can’t change from the default interface. 

[Samsung SSD HBA TRIM]

Confirmed! Downgraded my LSI-9207-8e from P20_IT to P16_IT and fstrim worked great. I am running 4x860 EVOs in a BTRFS array as my cache pool.

 

Thanks to whoever that found the solution

[Docker getting stuck]

Hi all, I am having quite a few issues with my instance of Unraid. I tried going the diagnostics dump but I dont think I am savvy enough to find the issue. I have attached diag report, I would appreciate if someone could help me through troubleshooting.

 

Thanks

rangoonnas-diagnostics-20190205-1008.zip

[SMB bind network interface]

Hello all,

 

I have 4 network interfaces out of which 1 interface is in Management VLAN and the other three are bonded via LACP. I would like to bind the samba service to the bonded interface. I added the following to the SMB extra conf page but doesn't seem to be working.

 

bind interfaces only = yes
interfaces = lo br1

Tried bond1 and br1, both did not work. Any advice?

 

Thanks

[Hardware issues]

15 minutes ago, Frank1940 said:

In both SA120 racks or just one?  Over what period of time did these errors to occur?   Remember a CRC is not a hard failure.  It simply says that the data that came out of the end of that cable was not what was sent.  When that occurs, the data will simply be resent which if the errors are widely spaced out is virtually unnoticeable.  Plus, the error count is from the day when you first put power to them.  'Fixing' the cause will not change the count back to zero, it simply would not increase beyond the current count. 

 

I find it a bit difficult to believe that both cables are bad.  Be sure that you can't isolate the problem a bit more.  Also consider that the cables could have electrical noise coupled into them since they are not inside of a metal case which would help to shield them.  

 

So I looked the CRC error count and it looks like the counter is going up for drives in one of the SA120s. I will replace that cable and report back. 

 

Btw, is there anyway to clear these counts?

 

[Hardware issues]

13 hours ago, Frank1940 said:

Suggestion.  Why don't you go through all of the SMART reports in your diagnostics file and make a list of the disks that the disks have the CRC errors. Then using that list determine exactly what hardware is involved with those disks. 

 

I suspect that you will find that there will be some piece(s) of  hardware that is/are common to all of the disks with CRC errors.    

 

Looks like the devices are all in SA120s...I guess I buy the SF-8088 cables now?

[Hardware issues]

Hello all,

 

I am running quite a few disks in an R710 hooked up to two SA120s(daisy chained using SF-8088 cables). I am getting quite a few CRC errors...after reading through the forum, it looks like a data cable issue(?). Now these cables cost $25 each so before I drop $50 trying to debug, is there anything else I can do to narrow down the issue?

 

Any help is appreciated.

 

Thanks

rangoonmediasrv-diagnostics-20180715-2100.zip