d2dyno

Members
 View Profile  See their activity

  • Posts

    95

  • Joined

  • Last visited

 Content Type 

Everything posted by d2dyno

  1. d2dyno
    Looking for `iotop`, `lftp`, `libmediainfo`/`mediainfo` and `vnstat` to be added.
  2. d2dyno
    I see the same issue on multiple devices and different browsers
  3. d2dyno
    I'm getting the same error over and over on the new debian apt mirror docker: ---Something went horribly wrong, can't find the mirror directory!--- Even though from within the container, I can see/ls the directory: /debian-mirror/data/mirror
  4. d2dyno
    I used the User Scripts plugin to run this script on first start of array : #!/bin/bash # umask setup umask 077 # Variable Setup CONFIG=/boot/config/ssh HOME_SSH=/root/.ssh ZSH="/root/.oh-my-zsh" mkdir -p $HOME_SSH cp $CONFIG/pre-set/* $HOME_SSH chmod 700 $HOME_SSH chmod 644 $HOME_SSH/id_rsa.pub chmod 600 $HOME_SSH/id_rsa chmod 600 $HOME_SSH/authorized_keys ### Install zsh shits HOME="/root" sh -c "$(wget https://raw.githubusercontent.com/robbyrussell/oh-my-zsh/master/tools/install.sh -O -)" umask g-w,o-w chsh -s $(which zsh) env zsh -l newplugins="git tmux zsh-autosuggestions" sed -i "s/(git)/($newplugins)/" /root/.zshrc sed -i "s#\(ZSH_THEME *= *\).*#\1agnoster#" /root/.zshrc echo "cd /mnt/user/" >> /root/.zshrc git clone https://github.com/zsh-users/zsh-autosuggestions $ZSH/custom/plugins/zsh-autosuggestions chmod 700 /root/.oh-my-zsh/custom/plugins/zsh-autosuggestions ### # Copy terminal (zsh) history cp /boot/config/.zsh_history /root Combined with this array stop script to copy ZSH history and SSH keys: #!/bin/bash # Copy terminal (zsh) history touch /boot/config/.zsh_history echo "$(cat /root/.zsh_history)" >> /boot/config/.zsh_history # Variable Setup CONFIG=/boot/config/ssh HOME_SSH=/root/.ssh # Copy any new keys on exit rsync -avhW $HOME_SSH/ $CONFIG/pre-set As for .zshrc (or aliases), I use /boot/config/go to write to /etc/profile on startup (how I was taught here to do it): # Re-make aliases on boot echo " #### Aliases copied from /boot/config/go #### alias size='du -c -h -d 1 | sort -h' export TERM=xterm-color #### End Aliases ####">>/etc/profile These are just example aliases and settings, use your own (though I do love that size alias)
  5. d2dyno
    Initially had 0 problems with this plugin and Plex, but now the containers are super touchy, sometimes working with --runtime=nvidia and sometimes not. The error I often get is: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex2' --net='bridge' --cpuset-cpus='25,26,27,28,29,30,31,57,58,59,60,61,62,63' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'VERSION'='latest' -e 'PUID'='99' -e 'PGID'='100' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-1e9824c9-cf6f-9a6d-9b75-dccaa79ba9a1' -p '1901:1900/tcp' -p '32401:32400/tcp' -p '33400:33400/tcp' -v '/mnt/disks/union-thd-plex2/misc/':'/misc':'rw,slave' -v '/mnt/disks/union-thd-plex2/misc2/':'/misc2':'rw,slave' -v '/mnt/disks/union-thd-plex2/misc3/':'/misc3':'rw,slave' -v '/mnt/user/Photos/server2/':'/photos':'rw' -v '/mnt/cache/Transcode/plex2':'/transcode':'rw' -v '/mnt/disks/nvmepool/appdata/plex2':'/config':'rw,slave' --runtime=nvidia 'linuxserver/plex' 598820f4e09e0ac0f5bdb8234210fecdc67487b3d3a3392e094b2683cccd2bdc /usr/bin/docker: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused "process_linux.go:432: running prestart hook 1 caused \"error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization error: cuda error: initialization error\\n\""": unknown. The command failed. EDIT: so when I run 'watch nvidia-smi' it comes up with my gpu, then later says no devices found.
  6. d2dyno
    Same. This should be on the front page / on the github
  7. d2dyno
    Yes I did. Using bridge as always, tried adding NET_ADMIN via extra arguments, did not change any behaviour. /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='openvpn-as' --net='bridge' --cpuset-cpus='5,6,37,38' --privileged=true -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'INTERFACE'='eth0' -e 'PGID'='100' -e 'PUID'='99' -p '943:943/tcp' -p '11194:11194/udp' -v '/mnt/disks/nvmepool/appdata/openvpn-as':'/config':'rw,slave' --cap-add=NET_ADMIN --label="traefik.protocol=https" --label="traefik.enable=true" --label="traefik.port=943" --label="traefik.frontend.rule=Host:ovpn.example.nl" --restart unless-stopped 'linuxserver/openvpn-as:latest' log-docker.txt openvpn.log
  8. d2dyno
    I'm getting this on a fresh install. Fresh because the update wiped out my config folder: https://github.com/linuxserver/docker-openvpn-as/issues/108 Getting this in container log Unpacking openvpn-as (2.8.3-f28d2eae-Ubuntu18) ... Setting up openvpn-as-bundled-clients (7) ... Setting up openvpn-as (2.8.3-f28d2eae-Ubuntu18) ... Automatic configuration failed, see /usr/local/openvpn_as/init.log You can configure manually using the /usr/local/openvpn_as/bin/ovpn-init tool. /var/lib/dpkg/info/openvpn-as.postinst: line 68: systemctl: command not found Stopping openvpn-as now; will start again later after configuring cat: /var/run/openvpnas.pid: No such file or directory kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
  9. d2dyno
    Not using jumbo frames is a workaround, not a fix. I use that MTU on purpose, and never had issues except with this plugin.
  10. d2dyno
    Same exact issue with SFP+ aggregated (802.3ad) NiC, MTU 9000. Also using Unifi gear.
  11. d2dyno
    Updated my BIOS (On PRIME X399-A went from 0808 -> 1203) and the Quadro now displays. It's very possible the update simply reset settings that needed to be changed too. I kept the 'fake' DP connected just in case. Thanks for all the help!
  12. d2dyno
    Are you speaking of this? If so, the output is: nvidia-smi --query-gpu=gpu_name,gpu_bus_id,gpu_uuid --format=csv,noheader | sed -e s/00000000://g | sed 's/\,\ /\n/g' No devices were found I bought these to see if that will resolve it: https://www.amazon.com/gp/product/B075873RJR
  13. d2dyno
    Here you are EDIT: better quality
  14. d2dyno
    The nvidia-smi one? That says no devices found, same message as web GUI. Yes, installed following instructions in the OP (install plugin, use plugin to install Nvidia unraid OS). Sent from my HD1905 using Tapatalk
  15. d2dyno
    Just installed this 6.8.2 version, to complement my new P2000. However after installing this modded unraid version, powering off my system, installing the P2000, and powering the server back on, the Nvidia plugin shows "No devices were found". Checking lspci/System Devices, it shows the card is indeed installed: IOMMU group 18:[10de:1c30] 0a:00.0 VGA compatible controller: NVIDIA Corporation GP106GL [Quadro P2000] (rev a1) [10de:10f1] 0a:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1) I read somewhere I need to connect something to the DisplayPort for the GPU to be recognized, but the server is just in a rack with no monitor so that's not ideal (except maybe a fake DisplayPort device). Anyone know the best course of action?
  16. d2dyno
    I had a similar issue, but with non hard-linked files. I think it had more to do with rsync itself. I ended up using rclone move to finish the task of removing orphaned/ already copied files from my cache drive (which was a remarkable 2TB).
  17. d2dyno
    I opted to remove the whole file, because just removing notifyCalc still left me with an error about 2019/05/20 16:38:26 Unable to start the app: configuration variable provided but not defined: notifyMove. After removing the conf file, unbalance now starts.
  18. d2dyno
    killall unbalance unbalance: no process found ✘ ⚡ root@TheiaHD  /mnt/user  /usr/local/emhttp/plugins/unbalance/unbalance -port 6237 configuration variable provided but not defined: notifyCalc Usage of /usr/local/emhttp/plugins/unbalance/unbalance: -apiFolders="/var/local/emhttp": folders to look for api endpoints -checkForUpdate=1: checkForUpdate: 0 - dont' check; 1 (default) - check -config="/boot/config/plugins/unbalance/unbalance.conf": config location -dryRun=true: perform a dry-run rather than actual work -folders="": deprecated - do not use -logdir="/boot/logs": pathname where log file will be written to -notifyPlan=0: notify via email after plan operation has completed (unraid notifications must be set up first): 0 - No notifications; 1 - Simple notifications; 2 - Detailed notifications -notifyTransfer=0: notify via email after transfer operation has completed (unraid notifications must be set up first): 0 - No notifications; 1 - Simple notifications; 2 - Detailed notifications -port="6237": port to run the server -refreshRate=250: how often to refresh the ui while running a command (in milliseconds) -reservedAmount=512: Minimun Amount of space to reserve -reservedUnit="Mb": Reserved Amount unit: Mb, Gb or % -rsyncArgs="-X": custom rsync arguments -verbosity=0: include rsync output in log files: 0 (default) - include; 1 - do not include 2019/05/20 15:11:39 Unable to start the app: configuration variable provided but not defined: notifyCalc
  19. d2dyno
    Same issue here on 6.7.0
  20. d2dyno
    I cannot add my server via the app for some reason. Tried http, https, and the port the controller plugin shows, with true same reason - app brings me back to an empty page. Also the blue button seems to be missing text. Video: https://streamable.com/af0s2
  21. d2dyno
    I saw this issue earlier yesterday when mover was running for the first time since I've been on RC5. Thinking maybe a kernel update would fix it, I updated to RC6. same error shortly after starting mover. Caused a drive to either fail or erroneously be marked as failed. Either way, I had to drop it from array and am now clearing it (also couldn't preclear without immediate pre-read error on RC). Trying to rule out software errors, I downgraded back to unraid stable (6.6.7), ran mover AND preclear simultaneously, and not a peep in the syslog. Will continue to monitor it, but I do believe this is an issue with the RC.
  22. d2dyno
    Today while running a large mover transfer, my system logs are being spammed with: Mar 31 20:04:48 TheiaHD kernel: mpt3sas_cm0: fault_state(0x5862)! Mar 31 20:04:48 TheiaHD kernel: mpt3sas_cm0: sending diag reset !! Mar 31 20:04:49 TheiaHD kernel: mpt3sas_cm0: diag reset: SUCCESS Mar 31 20:04:50 TheiaHD kernel: mpt3sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k Mar 31 20:04:50 TheiaHD kernel: mpt3sas_cm0: _base_display_fwpkg_version: complete Mar 31 20:04:50 TheiaHD kernel: mpt3sas_cm0: LSISAS3224: FWVersion(16.00.01.00), ChipRevision(0x01), BiosVersion(00.00.00.00) Mar 31 20:04:50 TheiaHD kernel: mpt3sas_cm0: Protocol=( Mar 31 20:04:50 TheiaHD kernel: Initiator Mar 31 20:04:50 TheiaHD kernel: ,Target Mar 31 20:04:50 TheiaHD kernel: ), Mar 31 20:04:50 TheiaHD kernel: Capabilities=( Mar 31 20:04:50 TheiaHD kernel: TLR Mar 31 20:04:50 TheiaHD kernel: ,EEDP Mar 31 20:04:50 TheiaHD kernel: ,Snapshot Buffer Mar 31 20:04:50 TheiaHD kernel: ,Diag Trace Buffer Mar 31 20:04:50 TheiaHD kernel: ,Task Set Full Mar 31 20:04:50 TheiaHD kernel: ,NCQ Mar 31 20:04:50 TheiaHD kernel: ) Mar 31 20:04:50 TheiaHD kernel: mpt3sas_cm0: sending port enable !! Mar 31 20:04:53 TheiaHD kernel: igb 0000:05:00.0 eth1: Reset adapter Mar 31 20:04:53 TheiaHD dhcpcd[3665]: eth1: carrier lost Mar 31 20:04:57 TheiaHD kernel: igb 0000:05:00.0 eth1: igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Mar 31 20:04:57 TheiaHD dhcpcd[3665]: eth1: carrier acquired Mar 31 20:04:58 TheiaHD dhcpcd[3665]: eth1: soliciting a DHCP lease Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: port enable: SUCCESS Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: search for end-devices: start Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:0: handle(0x0019), sas_addr(0x3000000080000000) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:0: enclosure logical id(0x5000000080000000), slot(3) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:1: handle(0x001a), sas_addr(0x3000000080000001) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:1: enclosure logical id(0x5000000080000000), slot(2) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:2: handle(0x001b), sas_addr(0x3000000080000002) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:2: enclosure logical id(0x5000000080000000), slot(0) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:3: handle(0x001c), sas_addr(0x3000000080000003) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:3: enclosure logical id(0x5000000080000000), slot(1) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:4: handle(0x001d), sas_addr(0x3000000080000004) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:4: enclosure logical id(0x5000000080000000), slot(7) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:5: handle(0x001e), sas_addr(0x3000000080000005) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:5: enclosure logical id(0x5000000080000000), slot(6) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:6: handle(0x001f), sas_addr(0x3000000080000006) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:6: enclosure logical id(0x5000000080000000), slot(4) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:8: handle(0x0020), sas_addr(0x3000000080000008) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:8: enclosure logical id(0x5000000080000000), slot(19) Mar 31 20:04:59 TheiaHD kernel: handle changed from(0x0021)!!! Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:7: handle(0x0021), sas_addr(0x3000000080000007) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:7: enclosure logical id(0x5000000080000000), slot(5) Mar 31 20:04:59 TheiaHD kernel: handle changed from(0x0020)!!! Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:9: handle(0x0022), sas_addr(0x300000008000000a) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:9: enclosure logical id(0x5000000080000000), slot(16) Mar 31 20:04:59 TheiaHD kernel: handle changed from(0x0023)!!! Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:10: handle(0x0023), sas_addr(0x3000000080000009) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:10: enclosure logical id(0x5000000080000000), slot(18) Mar 31 20:04:59 TheiaHD kernel: handle changed from(0x0022)!!! Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:11: handle(0x0024), sas_addr(0x300000008000000b) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:11: enclosure logical id(0x5000000080000000), slot(17) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:12: handle(0x0025), sas_addr(0x300000008000000c) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:12: enclosure logical id(0x5000000080000000), slot(23) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:13: handle(0x0026), sas_addr(0x300000008000000d) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:13: enclosure logical id(0x5000000080000000), slot(22) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:14: handle(0x0027), sas_addr(0x300000008000000e) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:14: enclosure logical id(0x5000000080000000), slot(20) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:15: handle(0x0028), sas_addr(0x300000008000000f) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:15: enclosure logical id(0x5000000080000000), slot(21) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:16: handle(0x0029), sas_addr(0x3000000080000010) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:16: enclosure logical id(0x5000000080000000), slot(11) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:17: handle(0x002a), sas_addr(0x3000000080000011) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:17: enclosure logical id(0x5000000080000000), slot(10) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:18: handle(0x002b), sas_addr(0x3000000080000012) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:18: enclosure logical id(0x5000000080000000), slot(8) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:19: handle(0x002c), sas_addr(0x3000000080000013) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:19: enclosure logical id(0x5000000080000000), slot(9) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:25: handle(0x002d), sas_addr(0x3000000080000014) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:25: enclosure logical id(0x5000000080000000), slot(15) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:21: handle(0x002e), sas_addr(0x3000000080000015) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:21: enclosure logical id(0x5000000080000000), slot(14) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:20: handle(0x002f), sas_addr(0x3000000080000016) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:20: enclosure logical id(0x5000000080000000), slot(12) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:22: handle(0x0030), sas_addr(0x3000000080000017) Mar 31 20:04:59 TheiaHD kernel: scsi target12:0:22: enclosure logical id(0x5000000080000000), slot(13) Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: search for end-devices: complete Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: search for end-devices: start Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: search for PCIe end-devices: complete Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: search for expanders: start Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: search for expanders: complete Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: _base_fault_reset_work: hard reset: success Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: removing unresponding devices: start Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: removing unresponding devices: end-devices Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: Removing unresponding devices: pcie end-devices Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: removing unresponding devices: expanders Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: removing unresponding devices: complete Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: scan devices: start Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: scan devices: expanders start Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: break from expander scan: ioc_status(0x0022), loginfo(0x310f0400) Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: scan devices: expanders complete Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: scan devices: end devices start Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: break from end device scan: ioc_status(0x0022), loginfo(0x310f0400) Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: scan devices: end devices complete Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: scan devices: pcie end devices start Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: log_info(0x3003011d): originator(IOP), code(0x03), sub_code(0x011d) Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: log_info(0x3003011d): originator(IOP), code(0x03), sub_code(0x011d) Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: break from pcie end device scan: ioc_status(0x0021), loginfo(0x3003011d) Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: pcie devices: pcie end devices complete Mar 31 20:04:59 TheiaHD kernel: mpt3sas_cm0: scan devices: complete Mar 31 20:04:59 TheiaHD kernel: sd 12:0:7:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:0:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:14:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:4:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:5:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:3:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:9:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:16:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:11:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:13:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:22:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:10:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:15:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:18:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:1:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:8:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:12:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:2:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:19:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:21:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:17:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:20:0: Power-on or device reset occurred Mar 31 20:04:59 TheiaHD kernel: sd 12:0:6:0: Power-on or device reset occurred Mar 31 20:05:02 TheiaHD kernel: igb 0000:05:00.0 eth1: Reset adapter theiahd-diagnostics-20190401-0114.zip
  23. d2dyno
    I recently went from 6.6.6 to RC5, and everything has been running stable for the past 3 days.
  24. d2dyno
    I'll try and compile it when I get time. Have you been able to compile this?
  25. d2dyno
    BBR is primarily meant to improve OUTGOING speeds, as it was designed initially for YouTube to cut down on bandwidth waste. My use case for BBR is a 40+ MB/s speed improvement in seeding on torrent clients from a gigabit connection. Multiple high bandwidth Plex streams and downloading from your server outside of your network would likely see a performance increase as well.