Jump to content

lordbob75

Members
  • Content Count

    127
  • Joined

  • Last visited

Community Reputation

4 Neutral

About lordbob75

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. Ok, that's good to know. I thought mine needed balancing but maybe not now that I look again. Well for now I won't turn on the balance script and I'll keep a closer eye on it to see if it ever needs it. Hopefully not, in which case I'll just keep the scrub one.
  2. @CarpNCod thank you so much for posting that. I can't believe it was just before I started looking for this, and I only just found out you need to regularly balance the btrfs pool... Thanks to @Helmonder for the original as well. I've taken that and used it to schedule a weekly scrub as well as a monthly balance (same script but running a balance). I do have a question about the log file though, where do you find that? I haven't run it yet, but wanted to do a test run and then check out the log file to make sure it works. I'm also curious since you aren't correcting errors, if it does need to be corrected will it throw and error and alert you in the notification? I'm not sure if that's the point of the error handling or if it's just if the script/command fails. Edit: Oh and now that I know how to create a notification like that, I'm totally going to go back over my scripts and add more! Edit2: oh I really don't have any scripts that need notifications, oh well.
  3. Yes you have to delete it. I tried force update first but it doesn't do anything.
  4. Since the GitHub post didn't specify anything for UnRAID specifically, I'll post it here to confirm it for anyone who's unsure. Simply delete your current container (and image). Reinstall the container, and choose the Default (or Latest). I just did this in less than 15 minutes and it was extremely painless and saved all my settings. You can search for the container easily enough but if you're unsure which one you had installed you can always check Previous Apps in the left menu.
  5. Oh I'm sure it's my fault somehow, I just dunno how. Screenshot of settings: @ich777 Alrighty I think I have it figured out. I believe the server was continually rebooting itself (taking about a minute to do so) and throwing an error when it tried to start, causing the reboot. Error seems to have been caused by an out-dated map-settings file, which has now been corrected. Server is stable, and the log is no longer being spammed. Problem solved! Confirmed I can connect to it as well. Not sure what exactly happened with the map file, but I'm sure it was because of updates.
  6. Turns out the Factorio container is causing this. Will post on their thread for assistance.
  7. @ich777 I'm using your Factorio container (thanks for setting that up by the way) It works fine, except that it's spamming my server log with network device renaming: Dec 26 22:40:41 SkyNet kernel: eth0: renamed from veth8b51caa Dec 26 22:40:44 SkyNet kernel: veth8b51caa: renamed from eth0 Dec 26 22:41:45 SkyNet kernel: eth0: renamed from veth21fc8e6 Dec 26 22:41:48 SkyNet kernel: veth21fc8e6: renamed from eth0 Dec 26 22:42:52 SkyNet kernel: veth3e0c201: renamed from eth0 Dec 26 22:44:57 SkyNet kernel: eth0: renamed from veth1eb2f47 Dec 26 22:44:59 SkyNet kernel: veth1eb2f47: renamed from eth0 Dec 26 22:46:00 SkyNet kernel: eth0: renamed from veth9ec956c Dec 26 22:46:03 SkyNet kernel: veth9ec956c: renamed from eth0 Dec 26 22:47:04 SkyNet kernel: eth0: renamed from veth7c9b7a0 Dec 26 22:47:07 SkyNet kernel: veth7c9b7a0: renamed from eth0 Dec 26 22:48:10 SkyNet kernel: veth55156c5: renamed from eth0 Dec 26 22:49:11 SkyNet kernel: eth0: renamed from vethea63aa1 Dec 26 22:49:14 SkyNet kernel: vethea63aa1: renamed from eth0 Dec 26 22:51:20 SkyNet kernel: veth495550d: renamed from eth0 Dec 26 22:53:41 SkyNet kernel: eth0: renamed from vethf9f63eb Dec 26 22:53:44 SkyNet kernel: vethf9f63eb: renamed from eth0 Dec 26 22:53:46 SkyNet kernel: eth0: renamed from vethfc8a62b Dec 26 22:53:49 SkyNet kernel: vethfc8a62b: renamed from eth0 Dec 26 22:53:51 SkyNet kernel: eth0: renamed from veth75ee072 Dec 26 22:53:53 SkyNet kernel: veth75ee072: renamed from eth0 Dec 26 22:53:55 SkyNet kernel: eth0: renamed from veth87a2bb1 Dec 26 22:54:00 SkyNet kernel: eth0: renamed from veth1f27aac Do you have any idea why it's doing that? I'm assuming I set something up wrong, but have no clue as to what.
  8. My log (var/log) is filling up in just a few days. Every minute or so, I see something like this: Dec 22 09:37:10 SkyNet kernel: eth0: renamed from veth6080b4e Dec 22 09:37:13 SkyNet kernel: veth6080b4e: renamed from eth0 Dec 22 09:38:14 SkyNet kernel: eth0: renamed from vethc5927d2 Dec 22 09:40:22 SkyNet kernel: veth8a37082: renamed from eth0 Dec 22 09:41:23 SkyNet kernel: eth0: renamed from vethd0831d7 Dec 22 09:41:26 SkyNet kernel: vethd0831d7: renamed from eth0 Dec 22 09:42:27 SkyNet kernel: eth0: renamed from veth6b0d449 I found one other thread with the same issue, but that was caused by PiHole which I'm not running. I can't figure out how to determine which container is causing the issue either. Any ideas on a fix?
  9. Are there any recent guides to setup a network boot server on UnRAID? It would be pretty useful to set it up so I could boot any PC on my network with a recovery tool or install a different OS without needing to make a new USB drive. I found some guides or threads that looked good, but they are very out of date:
  10. I did find the solution to this actually. Posting it here for anyone else that needs it: https://forums.plex.tv/t/error-transcoder-ac3_eae-0x2fd4f40-eae-timeout-eae-not-running-or-wrong-folder/189917/33 Basically one of the Codec folders (/mnt/user/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Codecs/EasyAudioEncoder-141-linux-ubuntu-x86_64/EasyAudioEncoder) doesn't have executable permissions. Running 'chmod 777 EasyAudioEncoder' gives it executable permissions and lets the file play.
  11. I added that to my last post in the edits. It is set to /transcode and it works fine for every other file except whatever this type is. I posted the permissions in the last post as well.
  12. It's my RAM (64GB), space isn't an issue there. root@SkyNet:/# ls -la /tmp total 16 drwxrwxrwt 16 nobody users 420 Oct 2 23:20 ./ drwxr-xr-x 18 root root 400 Sep 28 18:15 ../ drwxrwxrwt 2 nobody users 40 Sep 20 22:55 .ICE-unix/ -r--r--r-- 1 nobody users 11 Sep 20 22:55 .X0-lock drwxrwxrwt 2 nobody users 60 Sep 20 22:55 .X11-unix/ drwxrwxrwx 2 nobody users 40 Sep 20 22:55 .preclear/ drwxr-xr-x 3 nobody users 60 Sep 20 23:46 Transcode/ -rw-rw-rw- 1 nobody users 21 Oct 2 23:20 blah drwxrwxrwx 3 nobody users 60 Sep 20 22:55 ca.backup2/ drwxrwxrwx 3 nobody users 100 Sep 20 23:27 ca.turbo/ drwxrwxrwx 3 nobody users 60 Oct 2 01:00 community.applications/ drwxrwxrwx 2 nobody users 60 Sep 20 22:55 emhttp/ -rw-rw-rw- 1 nobody users 0 Sep 20 23:27 error-output.txt drwxrwxrwx 2 nobody users 120 Oct 2 04:40 fix.common.problems/ drwxr-xr-x 4 nobody users 80 Sep 20 22:55 notifications/ -rwxrwxrwx 1 nobody users 40 Sep 20 23:27 php.reload* drwxr-xr-x 2 nobody users 760 Sep 24 17:34 plugins/ -rw-rw-rw- 1 nobody users 7 Sep 20 23:28 test drwx------ 2 nobody users 40 Sep 20 22:56 tmux-0/ drwxrwxrwx 2 nobody users 40 Sep 20 22:55 unassigned.devices/ drwxrwxrwx 5 nobody users 140 Sep 20 23:27 user.scripts/ edit: I should add this I think: transcode folder in plex is set to /transcode Edit2: Plex was playing something that works while I grabbed that permissions. No PMS folder there.
  13. I do not appear to be able to play certain files in Plex. I believe it's to do with this error message: ERROR - [Transcoder] [truehd_eae @ 0x1541440] EAE timeout! EAE not running, or wrong folder? Could not read '/tmp/pms... However, there does not appear to be any sort of fix for this. Could anyone assist in figuring it out? I did try deleting my codecs folder, which made no difference. I have also optimized the database, cleaned bundles and trash. From what I could tell, it's like a year old bug with Plex? Almost forgot, attached logs. Plex Media Server Logs_2018-10-02_17-42-54.zip