Jump to content

Taramu

Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Taramu

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. EDIT: Had a network wide issue because of DHCP snooping. My switches blocked the requests, whitelisting the switchports fixed it. Does Pihole work as DHCP server work for someone? I can't get it to work since hours, tried everything. No other DHCP server in my network. I tried setting the container to following network interfaces: - host with Unraid Server IP: DHCP Request of client won't get answered, client disconnects. I can see the client IP / MAC in Pihole. Client chooses APIPA address (169.x.x.x) - br0 with custom IP in client subnet: Same as with host, can see the client IP / MAC but client gets disconnected. Client chooses APIPA (169.x.x.x). Everything besides DHCP works. I don't know why it doesn't work. Same issue with Adguard Home.
  2. SwOS doesn't display any values for TX / RX optical power on my switch. I changed the cabling and replaced the SFP+ passive cable from FS with an active cable from Netgear, which I use to connect my Switch Uplinks. Same issue with the speed, I'm starting to think the network is not the problem. Does someone have a suggestion what to check next? I'll probably try every PCIe slot of both PCs, even if the Mellanox cards are connected to 16x Gen3 PCIe slots right now.
  3. I guess I can't lookup the optical power at my Mikrotik, because I'm using SwOS. What I'm seeing are the RX / TX rates and the error count. There are no errors and data gets transfered. I don't have another SFP+ cable to check if this one is the culprit. I'm using following cable: https://www.fs.com/de/products/30760.html Is it possible to get diagnostic values for the PCIe slots via Unraid?
  4. I stopped troubleshooting at the Windows side and set both systems to Unraid. Same problem sadly, even with a direct connection between both systems.
  5. I booted the second system also with Unraid and connected both Mellanox ConnectX-3 cards via SFP+ together. Set static IPs for both systems in the same subnet and installed iPerf 3 on both systems. The result is even worse. The transfer rate is below 3.0 Gbit/s now. Is there anything I can do directly at the Unraid systems? I guess something seems wrong here, the results should be much better. I tried the latest stable 6.8.3 and the latest 6.9-beta1.
  6. Thanks, this topic was an interesting read. Sadly I'm not using an Antivirus which could limit the transfer speed. I'm testing with a clean Windows 10 installation on which Windows Defender was disabled completely. The switch between both systems is a Mikrotik CRS305-1G-4S+IN running SwOS with the latest software. Both systems are connected via SFP+ and shown with 10Gbps link speed. Since there is no routing between and both systems are in a plain Layer 2 network, the bottleneck should not come from the network. I hope.
  7. Hello together, I finally built my Unraid rig, which is based on a Dell T20 with following hardware: - CPU: Xeon E3-1225 v3 @3.20 GHz - 16 GB DDR ECC RAM @1600 MHz - 10Gbps NIC Mellanox ConnectX-3 - Cache Drive: Samsung MZFLV256 NVMe PCIe M.2 256GB (Should reach 10Gbps easily, at least for read-only) - HDD: WD Red 6TB Sadly, I'm not even close to transfer files at 10 Gbps, I'm reaching around 300 - 400 Mbyte/s when transfering files via SMB to the cache drive, from a local SSD of my system (Crucial MX 500). The transfer was tested between two systems, both using a Mellanox ConnectX-3 Card and both connected via SFP+ to the same switch in the same VLAN. Running iPerf (which should measure the raw network transfer rate, excluding a potential bottleneck of a SSD) gives me following result shown in the screenshot. Could someone help me to find the bottleneck of my system? Thanks a lot and stay healthy!
  8. Hello, after installing Seafile successfully with the docker template of cmer, I'm facing some issues with the web interface. I'm running the pro version. At first I installed the community edition, stopped my docker container and switched to the pro edition. Now I can't open the preinstalled .doc file inside my browser (Tried with Firefox and Chrome) and get following error when clicking on it: "Document convertion failed." I looked up the Seafile wiki to solve this issue They recommend to kill the service soffice with following command: pkill -f soffice.bin Sadly this didn't work for me. Does someone have a solution? Edit: Solved the problem with following guide: https://manual.seafile.com/deploy_pro/office_documents_preview.html LibreOffice needs to be installed with following command, directly on the container: docker exec -it <Seafile Container-Name> bash apt-get install libreoffice libreoffice-script-provider-python