Jump to content

drdebian

Members
  • Content Count

    36
  • Joined

  • Last visited

Community Reputation

5 Neutral

About drdebian

  • Rank
    Advanced Member
  • Birthday August 31

Converted

  • Gender
    Male
  • ICQ
    6478117

Recent Profile Visitors

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

  1. Can't wait... In the meantine, Jottacloud's support sent me this: I tried it and it actually works, which is good enough until the updated plugin arrives...
  2. hi there... are there any known issues with the jottacloud remote? I can't seem to authenticate agains the jottacloud servers anymore with rclone... rclone v1.48.0 - os/arch: linux/amd64 - go version: go1.12.6 2019/08/14 06:24:10 Failed to create file system for "ula-jottacloud:": couldn't get account info: failed to get endpoint url: error 401: org.springframework.security.authentication.AuthenticationCredentialsNotFoundException: Token mismatch! (Unauthorized) I tried everything, including removing the remote from the config and recreating it... to no avail... any help welcome!
  3. Yes, exactly. Hardware-accelerated video transcoding goes a long way in making older CPUs a viable option.
  4. I think you should be good to go if you enable the i915 QSV driver for hardware transcoding and stick to h.264.
  5. Yes, works perfectly in Handbrake and Plex. Just added the command to load the right kernel module in the go script and that was it.
  6. According to https://wiki.debianforum.de/Benchmark_für_Festplattenverschlüsselung you should be able to get 80+ MB/s with LUKS encryption even on an old CPU like that. It certainly won't leave room for other CPU-intensive tasks, but for file storage you should be fine.
  7. Whatever the board is doing, a single x4 lane should easily be able to handle your 2 SSDs at maximum speed.
  8. Have you looked at Syncthing yet? I use it exactly for this purpose and it works like a charm.
  9. I think your USB stick should work just fine. If it doesn't, just add a USB expansion card.
  10. yes, I think it should.
  11. I'm not sure, but I think there still are some driver issues with the 9th gen processors... which is why I went with an i7-8700, just to be on the safe side.
  12. May 31 15:26:01 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token I've been getting this strange message since I added a bunch of new disk to the array... Any ideas? Running the latest 6.7.0 release with the latest version of the plugin...
  13. Some time since I updated to the latest version, my binhex-plexpass won't start anymore. Looking at the logs I find this: https://hub.docker.com/u/binhex/ 2019-05-24 18:38:45.014222 [info] System information Linux tower 4.19.41-Unraid #1 SMP Sat May 11 18:09:00 BST 2019 x86_64 GNU/Linux 2019-05-24 18:38:46.621172 [info] PUID defined as '99' 2019-05-24 18:38:47.209716 [info] PGID defined as '100' 2019-05-24 18:38:51.399034 [info] UMASK defined as '000' 2019-05-24 18:38:51.754883 [info] Permissions already set for volume mappings 2019-05-24 18:38:51.777302 [info] TRANS_DIR defined as '/config/transcode' 2019-05-24 18:38:51.991930 [info] Starting Supervisor... 2019-05-24 18:39:27,039 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2019-05-24 18:39:27,039 INFO Set uid to user 0 succeeded 2019-05-24 18:39:27,489 INFO supervisord started with pid 6 2019-05-24 18:39:28,491 INFO spawned: 'plexmediaserver' with pid 47 2019-05-24 18:39:28,491 INFO reaped unknown pid 7 2019-05-24 18:39:29,493 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2019-05-24 18:39:53,679 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23113827220008 for <Subprocess at 23113827664168 with name plexmediaserver in state RUNNING> (stdout)> 2019-05-24 18:39:53,679 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23113827218208 for <Subprocess at 23113827664168 with name plexmediaserver in state RUNNING> (stderr)> 2019-05-24 18:39:53,679 INFO exited: plexmediaserver (exit status 255; not expected) 2019-05-24 18:39:53,679 DEBG received SIGCLD indicating a child quit 2019-05-24 18:39:54,680 INFO spawned: 'plexmediaserver' with pid 52 2019-05-24 18:39:54,738 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23113826857544 for <Subprocess at 23113827664168 with name plexmediaserver in state STARTING> (stdout)> 2019-05-24 18:39:54,738 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23113826906624 for <Subprocess at 23113827664168 with name plexmediaserver in state STARTING> (stderr)> 2019-05-24 18:39:54,738 INFO exited: plexmediaserver (exit status 255; not expected) 2019-05-24 18:39:54,738 DEBG received SIGCLD indicating a child quit 2019-05-24 18:39:55,739 INFO spawned: 'plexmediaserver' with pid 57 2019-05-24 18:39:55,827 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23113826857544 for <Subprocess at 23113827664168 with name plexmediaserver in state STARTING> (stdout)> 2019-05-24 18:39:55,827 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23113827218352 for <Subprocess at 23113827664168 with name plexmediaserver in state STARTING> (stderr)> 2019-05-24 18:39:55,827 INFO exited: plexmediaserver (exit status 255; not expected) 2019-05-24 18:39:55,827 DEBG received SIGCLD indicating a child quit 2019-05-24 18:39:57,829 INFO spawned: 'plexmediaserver' with pid 62 2019-05-24 18:39:57,854 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23113826857544 for <Subprocess at 23113827664168 with name plexmediaserver in state STARTING> (stdout)> 2019-05-24 18:39:57,854 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23113826906624 for <Subprocess at 23113827664168 with name plexmediaserver in state STARTING> (stderr)> 2019-05-24 18:39:57,854 INFO exited: plexmediaserver (exit status 255; not expected) 2019-05-24 18:39:57,854 DEBG received SIGCLD indicating a child quit 2019-05-24 18:40:00,857 INFO spawned: 'plexmediaserver' with pid 67 2019-05-24 18:40:00,881 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23113826857544 for <Subprocess at 23113827664168 with name plexmediaserver in state STARTING> (stdout)> 2019-05-24 18:40:00,881 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23113826906984 for <Subprocess at 23113827664168 with name plexmediaserver in state STARTING> (stderr)> 2019-05-24 18:40:00,882 INFO exited: plexmediaserver (exit status 255; not expected) 2019-05-24 18:40:00,882 DEBG received SIGCLD indicating a child quit 2019-05-24 18:40:01,883 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly Any ideas?