Jump to content

Xaero

Members
  • Content Count

    237
  • Joined

  • Last visited

  • Days Won

    2

Xaero last won the day on July 19

Xaero had the most liked content!

Community Reputation

67 Good

About Xaero

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. Xaero

    10gbit speeds?

    The M.2 cache drive should be capable of delivering higher speeds than that. Use something more low level than Samba for testing first. https://datapacket.com/blog/10gbps-network-bandwidth-test-iperf-tutorial/ Use iperf to test that the link is actually capable of full 10gbit speed. If not, eliminating the switch is fairly easy (use a crossover cable, and set a static IP on the PC in the same subnet) Rerun the iperf test. If the speed is recitfied without the switch in place - several things can come up; I've heard that these Mikrotrik devices have a "dual OS" and that sometimes the RouterOS works faster than the SwitchOS; and vice-versa, depending on the internal hardware of the device itself. If it is, then you are looking into Samba performance tuning and ensuring both clients are using SMB3 and not SMB2.
  2. I'd wait for a response from Norco. I don't recall which backplane version I have - but mine is fully populated with 24 8tb drives and I have been able to hot swap without any damage to any drives or the backplanes. Mine use a single 4 pin molex power cable each. I know there were variants with SATA, and dual 4 pin molex prior to mine. I bought the case ~4 years ago now.
  3. +1 I have learned my lesson from this.
  4. Ah, I misunderstood the initial request. Yes, that makes sense and is approachable from a software engineering perspective. Start at the source tree level 0. If tree level 0 and all subdirectories fits, just merge with the existing tree. If tree level 0 doesn't fit, jump to tree level 1 and iterate over subdirectories in level 1 until something doesn't fit. Once it doesn't fit make a new tree on another drive. Simple enough. I was thinking this request was for some arbitrary content type. If it's just based on folders its not that hard.
  5. What criteria would this be based on? There has to be the possibility for simple If This Then That logic to decide when/where to split the data. This is a drawback to the merged filesystem approach to bulk data storage that Unraid takes. If the file is larger than a single volume - it can't go on the array at all. Similarly, if a directory or set of directories is larger than a single volume, it must be split across multiple volumes. I can't think of a way any software engineer could approach this in a logical, and universal fashion. Sure, we could write an implementation for one specific use case - but that's about the limit. The only thing I can think of would be to use a "keep together" list and allow selecting specific folders to try to force onto a singular volume. If those directories ever didn't fit the free space of a disk, it would have to store data on another disk. It's just not feasible imho.
  6. Mounted to the back of the motherboard? Excellent. Use some thick thermal pads so that the pad makes contact with the motherboard tray. Problem solved. The motherboard tray is now a giant passive heatsink for your NVME disk.
  7. So I had everything working. Updated only the plugin and now only my first peer can ever get a handshake. And even though I get a handshake - the WebUI, no LAN or server hosted content is accessible, and neither is the internet. I just want a relatively easy to use VPN for myself and the people I have accessing it and I cannot figure out what I'm doing wrong now. I didn't touch any configuration other than updating wireguard from the original release to the one from November. Not sure what all should be posted so here's the censored wireguard config(s) for the half-working peer: /etc/wireguard/wg0.conf: [Interface] #include=/webGui/include/update.wireguard.php #file=/etc/wireguard/wg0.conf #cfg=/etc/wireguard/wg0.cfg #cmd=update #name=Blackhole #vtun=wg0 #wg=active #subnets1=192.168.1.74, 10.253.0.1 #subnets2=192.168.1.0/24, 10.253.0.1 #shared1=192.168.1.74, 10.253.0.0/24 #shared2=192.168.1.0/24, 10.253.0.0/24 #internet=192.168.1.74:51820 #Home PrivateKey= Address=10.253.0.1 ListenPort=51820 PostUp=iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE PostUp=logger -t wireguard 'Tunnel WireGuard-wg0 started' PostDown=iptables -t nat -D POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE PostDown=logger -t wireguard 'Tunnel WireGuard-wg0 stopped' [Peer] # PublicKey= PresharedKey= AllowedIPs=10.253.0.0/24, 192.168.1.74, 192.168.1.254 /etc/wireguard/peers/etc/wireguard/peers/peer-Blackhole-wg0-1.conf: [Interface] # PrivateKey= Address=10.253.0.2/32 DNS=192.168.1.254 [Peer] #Home PresharedKey= PublicKey= Endpoint=dyndns:51820 AllowedIPs=192.168.1.0/24, 10.253.0.0/24 I feel like an IPTables rule is missing, but I don't know enough to figure out what it is. My reasoning is that the result of attempting to ping the DNS server (192.168.1.254) results in a Destination Host Unreachable from 10.253.0.1 (the unraid server) The handshake completes so I know the peer keys and endpoints are right, something on the routing side is wrong.
  8. Oh man. I thought something seemed off just hadn't looked into it yet as I noticed a bunch of new content didn't seem to be working properly with tvdb. Phew.
  9. On the contrary I moved to this from Transdroid. Transdroid doesn't let you specify a download location, and is missing other features for rtorrent clients. A shame, really as when I used it with deluge it was fine. Deluge wasn't able to handle some of my larger downloads so I migrated away from it.
  10. This is something quick and dirty I did to enable the use of the Mobile UI plugin for ruTorrent with the Linuxserver.io docker: First: Download and extract the mobile ui plugin from: https://github.com/xombiemp/rutorrentMobile Once downloaded, Extract the plugin into the appdata config folder for rutorrent, naming it "mobile" The contents of that folder should look like this: Once complete, edit your rutorrent docker and add the following path: Afterwards, when a mobile device connects to the rutorrent WebUI it will be presented with a slick mobile interface that looks like this (image stolen from Google):
  11. That also didn't exist until well after this thread was made.
  12. I've been meaning to dig a bit deeper as this solution seems "kludgy" overall (no offense - its a great solution) I think the intended method would be to use a containerized router solution that doesn't update often, if at all. The client containers would connect using that as their network, and then the endpoint connector ("WAN" in a router sense) would have a static IP. All routing would go through that "WAN" container, and if it rebooted/updated it would be a momentary network interruption, rather than having to rebuild all of the containers. I'll update here if I ever get around to doing such a setup.
  13. This disk should be bootable presuming the bios/UEFI settings are correct and that EFI System partition is readable by the UEFI used. That is going to vary heavily from vendor to vendor.
  14. What does fdisk -l /dev/disk/by-id/ata-KINGSTON.... look like? If I'm not mistaken, you'd need to be booting UEFI only or have the UEFI boot order entry for the disk in question before the legacy options for all devices. My experience with UEFI booting is fairly limited. I do see you are using the raw disk (or at least, think you are, the node is cut off) It's possible to treat the first partition of a disk as the disk with VirtIO and then you end up with a disk image stored as a partition.
  15. Need additional information. When using VirtIO did you use the RawDISK or did you create a disk image on a partition on that disk? Is the target machine using BIOS or EFI? What's the VM configuration look like? In theory, with a RawDISK you should be able to yank it from the VM environment and transplant it into a physical machine with no headaches. In fact I use VMs for testing disks that I image rather than a physical box as it simplifies my workflow. Most likely you are trying to boot a UEFI disk with a legacy BIOS or a legacy BIOS compatible disk with UEFI only.