Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

6 Neutral

About ideaman924

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

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

  1. Yes, I'm still using it on my server and it works perfectly :) Maybe the drives do not support write caching under Linux? Wild guess
  2. Hello, I got this warning from Fix Common Problems, on my UnRAID server: My server has an ASRock A55M-VS motherboard with an AMD A4-3400 APU chip. Is there a way to install a CPU Scaling Driver? Thanks in advance! Forgot to mention - server is running UnRAID 6.8.2. BIOS is up to date (last release was like 2 or 3 years ago)
  3. Hello all. I have a small UnRAID server running a couple of Docker containers, no VMs. It chugs along and handles local streaming (Plex) reasonably well. The problem is remote streaming - my server will just completely lock up and require a forceful reboot with the power button. I've theorized it's either the system overheating, or an OOM issue. To rule out overheating, I cleaned out the server chassis about 2 months ago. I also repasted the CPU thermal compound. I ran a stress test utility to make sure that it won't freeze while running CPU intensive tasks. (My server does not have a GPU.) Since it's still freezing, I think it's the server running out of memory. My server has 8 GB of RAM, which is not much but shouldn't freeze for a simple 1080p transcode through Plex. I'm guessing it's something in the Plex Docker that's using too much RAM and causing UnRAID to kill off essential services such as the nginx process or the shfs process. To complicate matters I'm currently away from my server so I can only fix things remotely (WebUI is accessible over VPN). A family member can reboot the server but that's all they can do, no upgrading the RAM or anything like that. Anybody know how to get UnRAID to restrict the amount of RAM available to the Plex Docker, or make it use less RAM while transcoding in real time?
  4. As a workaround I guess I could change the command in the go file to copy instead of symlink, and then set the executable flag in /usr/local/bin. That's one option.
  5. Hi, I tried that but it says: root@server:/mnt/user# bash duplicacy list /usr/local/bin/duplicacy: /usr/local/bin/duplicacy: cannot execute binary file Any alternatives?
  6. Hello! I have a duplicacy executable in /boot/config/plugins that takes care of backing up my server. After the update to 6.8.0, I can no longer run the executable, as the command returns "permission denied" from bash. I looked at the permissions and it seems like I cannot set the executable flag even if I'm root. Is this something that changed with UnRAID 6.8.0? Where should I store my executable? Thanks!
  7. Hi all! I'm trying to set up Duplicati on UnRAID. Can anybody verify these mappings? (Container) ----> (Host) /tmp ----> /tmp/duplicati (RW/Slave) /backups ----> /mnt/user/backup-duplicati/ (RW/Slave) /source ----> /mnt/user (RO/Slave) I'm thinking about deleting the /backups mapping since this server will not receive any backups. Is that OK? Also, is RW/Slave RO/Slave really necessary? I saw in the SpaceInvadersOne video that this supposedly helps improve performance for Docker containers. Is that true or should I set it back to RW/RO?
  8. Yup, it's there. I switched back to Firefox anyway so it's a non-issue, though. Firefox gives a warning but it lets me continue at least by adding an exception.
  9. Hi @dlandon, There's a problem with the generated certificate - Chrome does not allow access to Zoneminder at all. I'm guessing it's because of this? https://stackoverflow.com/questions/43665243/invalid-self-signed-ssl-cert-subject-alternative-name-missing/56530824#56530824 Any chance the generation could be fixed so that it includes that parameter?
  10. For anyone who needs the script here it is: #!/bin/bash # Drives declare -a StringArray=("ata-WDC_WD2003FYYS-70W080_WJUN0123456" "DRIVE2" "DRIVE3" "DRIVE4") # Show status echo "Current drive status: " for drive in ${StringArray[@]}; do hdparm -W /dev/disk/by-id/$drive done # Enable write caching for drive in ${StringArray[@]}; do hdparm -W 1 /dev/disk/by-id/$drive done # Show status again echo "Finished running, check if the write cache was enabled!" for drive in ${StringArray[@]}; do hdparm -W /dev/disk/by-id/$drive done Replace the serial codes in the StringArray and you should be good to go! Pop it in User Scripts.
  11. Thank you for the tip! Script works like a charm.
  12. What about the changing values for /dev/sda, /dev/sdb...?
  13. Hi all. When I reboot my server all four of my drives come up with disabled write cache. They're the WD RE 2TB ones. Running hdparm -W 1 /dev/sd<value> fixes the problem but only until the next reboot. Do I just set those lines in the go file? Won't the values change across reboots? How do I get them to enable every time I start up the server? Thanks. derrickserver-diagnostics-20190521-1151.zip
  14. Quick question - I'm not sure if this has been answered before. Google search doesn't show anything. I tried accessing my Plex server today but it was unresponsive (WebUI wouldn't load, iOS app reported "Unexpected Response" under the server name, and then stopped showing the server entirely). This is what I got when I opened up the Docker logs: ... Starting Plex Media Server. Starting Plex Media Server. ... After restarting the Docker: [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... usermod: no changes ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 50-gid-video: executing... [cont-init.d] 50-gid-video: exited 0. [cont-init.d] 60-plex-update: executing... No update required [cont-init.d] 60-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting Plex Media Server. [services.d] done. Starting Plex Media Server. Starting Plex Media Server. ... Anybody know what the hell is going on? I think I applied some updates a couple weeks ago but didn't check after the update to see if it broke anything. Obviously that's now coming to bite me in the ass... EDIT: I spoke too soon. Checked in the appdata folder and it seems like my database is corrupt. Here are the logs if anybody is interested: Apr 30, 2019 22:51:10.896 [0x14eddb07a700] INFO - Plex Media Server v1.15.5.994-4610c6e8d - Docker Docker Container (LinuxServer.io) x86_64 - build: linux-x86_64 debian - GMT 08:00 Apr 30, 2019 22:51:10.896 [0x14eddb07a700] INFO - Linux version: 4.19.33-Unraid, language: en-US Apr 30, 2019 22:51:10.896 [0x14eddb07a700] INFO - Processor AMD A8-3870 APU with Radeon(tm) HD Graphics Apr 30, 2019 22:51:10.896 [0x14eddb07a700] INFO - /usr/lib/plexmediaserver/Plex Media Server Apr 30, 2019 22:51:10.895 [0x14ede77c5f00] DEBUG - BPQ: [Idle] -> [Starting] Apr 30, 2019 22:51:10.896 [0x14ede77c5f00] DEBUG - FeatureManager: Using cached data for features list Apr 30, 2019 22:51:10.896 [0x14ede77c5f00] DEBUG - Opening 20 database sessions to library (com.plexapp.plugins.library), SQLite 3.26.0, threadsafe=1 Apr 30, 2019 22:51:10.960 [0x14ede77c5f00] DEBUG - Running migrations. (EPG 0) Apr 30, 2019 22:51:10.963 [0x14ede77c5f00] ERROR - SQLITE3:(nil), 11, database corruption at line 65066 of [bf8c1b2b7a] Apr 30, 2019 22:51:10.963 [0x14ede77c5f00] ERROR - SQLITE3:(nil), 11, statement aborts at 10: [select max(max(metadata_items.changed_at),max(metadata_items.resources_changed_at)) from metadata_items] database disk image is malformed Apr 30, 2019 22:51:10.963 [0x14ede77c5f00] ERROR - Database corruption: sqlite3_statement_backend::loadOne: database disk image is malformed So if you have similar problems check Library/Application Support/Plex Media Server/Logs. Now I need to figure out how to fix this stupid database corruption... EDIT2: Fixed it. If you can't waste time with database recovery just nuke this file: /Plug-in Support/Databases/com.plexapp.plugins.library.db and launch the Docker image again. Otherwise follow this article: https://support.plex.tv/articles/201100678-repair-a-corrupt-database/ . Hope this helps someone.
  15. I ended up just re-configuring the default gateway, re-registering and then started up the array as normal. Thanks anyway @remotevisitor!