Jump to content

casperse

Members
  • Content Count

    414
  • Joined

  • Last visited

Everything posted by casperse

  1. I have created a new USB boot and replaced the config folder with the one I can access from the old drive? Would it be safe to try to boot from this USB? or is that a no go?
  2. Hi All HELP! I did a shutdown and a reboot with GUI and now I get this; I can connect using putty? and I did make some standard backup (Video guide) but I have no clue on how to get it restores without a UI? Best regards Casperse UPDATE I have also access to the flash drive through SAMBA (Other drives is not there because they need to be mounted through the UI (Encryption) So if I need access to the backup I need to start the array through the terminal and somehow type the password? SYSLOG Attached: syslog.txt LOG files from: cat /var/log/syslog PLEXZONE:~# -bash: Jun: command not found -bash: -bash:: command not found root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE kernel: md14: stopping root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE kernel: md13: stopping -bash: Jun: command not found root@PLEXZONE:~# root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE kernel: md13: stopping -bash: root@PLEXZONE:~#: command not found root@PLEXZONE:~# -bash: Jun: command not found Jun 10 18:18:54 PLEXZONE kernel: md15: stopping -bash: -bash:: command not found root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE kernel: md15: stopping -bash: Jun: command not found root@PLEXZONE:~# root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE kernel: md14: stopping -bash: Jun: command not found -bash: root@PLEXZONE:~#: command not found root@PLEXZONE:~# -bash: Jun: command not found -bash: -bash:: command not found root@PLEXZONE:~# root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE kernel: md15: stopping -bash: Jun: command not found -bash: root@PLEXZONE:~#: command not found root@PLEXZONE:~# -bash: Jun: command not found -bash: -bash:: command not found root@PLEXZONE:~# root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE kernel: md16: stopping -bash: Jun: command not found -bash: root@PLEXZONE:~#: command not found root@PLEXZONE:~# -bash: Jun: command not found -bash: -bash:: command not found root@PLEXZONE:~# root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE kernel: md17: stopping Jun 10 18:18:54 PLEXZONE kernel: md18: stopping -bash: root@PLEXZONE:~#: command not found root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE kernel: md18: stopping -bash: Jun: command not found root@PLEXZONE:~# -bash: Jun: command not found root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE kernel: md18: stopping -bash: -bash:: command not found root@PLEXZONE:~# root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE kernel: md18: stopping -bash: root@PLEXZONE:~#: command not found root@PLEXZONE:~# -bash: Jun: command not found root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE kernel: md19: stopping -bash: -bash:: command not found root@PLEXZONE:~# root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE kernel: md19: stopping -bash: root@PLEXZONE:~#: command not found root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE kernel: md20: stopping -bash: Jun: command not found root@PLEXZONE:~# -bash: Jun: command not found root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE kernel: md20: stopping -bash: -bash:: command not found root@PLEXZONE:~# root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE kernel: md20: stopping -bash: Jun: command not found -bash: root@PLEXZONE:~#: command not found root@PLEXZONE:~# -bash: Jun: command not found root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE kernel: md22: stopping -bash: -bash:: command not found root@PLEXZONE:~# root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE kernel: md22: stopping -bash: root@PLEXZONE:~#: command not found Jun 10 18:18:54 PLEXZONE avahi-daemon[7353]: Server startup complete. Host name is PLEXZONE.local. Local service cookie is 1712556334. root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE avahi-daemon[7353]: Server startup complete. Host name is PLEXZONE.local. Local service cookie is 1712556334. -bash: Jun: command not found root@PLEXZONE:~# -bash: Jun: command not found -bash: -bash:: command not found root@PLEXZONE:~# root@PLEXZONE:~# Jun 10 18:18:54 PLEXZONE avahi-daemon[7353]: Server startup complete. Host name is PLEXZONE.local. Local service cookie is 1712556334. -bash: root@PLEXZONE:~#: command not found root@PLEXZONE:~# Jun 10 18:18:55 PLEXZONE avahi-daemon[7353]: Service "PLEXZONE" (/services/ssh.s ervice) successfully established. -bash: syntax error near unexpected token `(' root@PLEXZONE:~# -bash: Jun: command not found root@PLEXZONE:~# Jun 10 18:18:55 PLEXZONE avahi-daemon[7353]: Service "PLEXZONE" (/services/ssh.s ervice) successfully established. -bash: -bash:: command not found -bash: syntax error near unexpected token `(' root@PLEXZONE:~# root@PLEXZONE:~# Jun 10 18:18:55 PLEXZONE avahi-daemon[7353]: Service "PLEXZONE" (/services/ssh.s ervice) successfully established. -bash: syntax error near unexpected token `(' root@PLEXZONE:~# -bash: syntax error near unexpected token `(' > root@PLEXZONE:~# Jun 10 18:18:55 PLEXZONE avahi-daemon[7353]: Service "PLEXZONE" (/services/smb.s ervice) successfully established. > -bash: syntax error near unexpected token `(' -bash: syntax error near unexpected token `(' root@PLEXZONE:~# root@PLEXZONE:~# Jun 10 18:18:55 PLEXZONE avahi-daemon[7353]: Service "PLEXZONE" (/services/sftp- ssh.service) successfully established. -bash: syntax error near unexpected token `(' root@PLEXZONE:~# -bash: syntax error near unexpected token `(' > root@PLEXZONE:~# Jun 10 18:19:17 PLEXZONE dbus-daemon[9951]: [session uid=0 pid=9948] Activating service name='org.a11y.Bus' requested by ':1.0' (uid=0 pid=9944 comm="firefox -- profile /usr/share/mozilla/firefox/9n35r") > -bash: syntax error near unexpected token `(' -bash: syntax error near unexpected token `(' root@PLEXZONE:~# root@PLEXZONE:~# Jun 10 18:19:17 PLEXZONE dbus-daemon[9951]: [session uid=0 pid=9948] Successfull y activated service 'org.a11y.Bus' -bash: root@PLEXZONE:~#: command not found root@PLEXZONE:~# Jun 10 18:23:00 PLEXZONE sshd[28663]: Accepted password for root from 192.168.0. 176 port 55467 ssh2 -bash: Jun: command not found -bash: Jun: command not found root@PLEXZONE:~# Jun 10 18:23:00 PLEXZONE sshd[28663]: Accepted password for root from 192.168.0. 176 port 55467 ssh2 root@PLEXZONE:~# -bash: Jun: command not found -bash: -bash:: command not found root@PLEXZONE:~# root@PLEXZONE:~# Jun 10 18:23:00 PLEXZONE sshd[28663]: Accepted password for root from 192.168.0. 176 port 55467 ssh2 -bash: root@PLEXZONE:~#: command not found root@PLEXZONE:~# Jun 10 18:23:57 PLEXZONE ntpd[2129]: kernel reports TIME_ERROR: 0x41: Clock Unsy nchronized root@PLEXZONE:~# -bash: Jun: command not found -bash: -bash:: command not found root@PLEXZONE:~# root@PLEXZONE:~# Jun 10 18:23:57 PLEXZONE ntpd[2129]: kernel reports TIME_ERROR: 0x41: Clock Unsy nchronized -bash: root@PLEXZONE:~#: command not found root@PLEXZONE:~# -bash: Jun: command not found -bash: -bash:: command not found root@PLEXZONE:~# root@PLEXZONE:~# root@PLEXZONE:~# root@PLEXZONE:~# root@PLEXZONE:~# -bash: root@PLEXZONE:~#: command not found root@PLEXZONE:~# -bash: root@PLEXZONE:~#: command not found root@PLEXZONE:~# -bash: -bash:: command not found root@PLEXZONE:~# root@PLEXZONE:~# The array is not set to autostart
  3. OK - Do anyone know if it's possible to do the SMB or NFS connect in the docker config using the Path option?
  4. This was this post: What did you mean "the plex application itself has the ability to access media over SMB, so there is no need to remote mount that media in Unraid" how?
  5. I have Plex docker running on Unraid and have one mounted folder on my Synology NAS through Unassigned Devices I don't think you can access SMB shares through the Plex UI using smb: But maybe directly using path in docker config settings for plex?
  6. Thanks for explaining this to me, your right I have to look at all the dockers! I am pretty sure that if I could create internal SMB mounts inside the docker application this would help on this issue when rebooting the server that is mounted by your excellent tool inside the Docker applications. Than main suspects would be: Plex Emby resilio sync @trurl You mention SMB mounts from plex, but using smb: does not seem to cut it? Yes ideally I would place everything on one server but I need two :-) and sharing is what a NAS should do best
  7. Thanks! - For some reason copying files from my Synology to a shared drive created ALL dirs as shares! And for some reason I couldnt delete the .files and therefore couldnt remove all the new created shares. So finding each share on each drive and deleting them with CM worked!
  8. I found a permission error in the log file from Radarr and removed change permission in my setup. But transfer is still really really slow, this is 561MB at 17:06 and the file was created 16:46 = 20 min! Are my mount point wrong? Update: now 3 hours later still executing the transfer Diagnostic files:diagnostics-20190501-1756.zip
  9. @wh0_cares I am in kind of the same situation, and I need some help increasing speed of copying (It takes hours, when Radarr copies after sort and renaming) My Movie folder is on a different system and mounted correctly (Ping enabled etc) My download folder is using the cash drive M2 and move is done nightly (So they should already be gone before move is initiated) Appdata is Cash only Download cash Yes Radarr mappings: It's not the network speed, copying from UNraid to the Mounted folder by PC or binhex-krusader works quick and without problems - Radarr just don't like mounted volumes? As always any input or things I can try is most welcome 🙂
  10. Hi All I have 3 mounts to my other server and I have some of the same problems it doesn't time out? Only way to get them working is stopping the array (Which could be because that stops all dockers?) Is there any way by console to stop UAD? and restart the service like stopping a single docker and not stopping the array? (Sorry if this has been asked before long thread) Best regards Casperse Please wait... collecting diagnostic information (this may take several minutes).......
  11. Thanks I will try this next time this happens. Do you think this could be Plex/docker causing this? I couldn't even stop the Plex docker before trying to stop the whole server
  12. Hi All I have been forced to cut the power 3 times since I started using Unraid instead of primary Synology server. I know this could be caused by me running the Version: 6.7.0-rc7 release And every time its been in relation to a docker application that wouldn't stop (Plex) or UAD not finding mounted drives I typically see a stopped on the UI like this: But the Array is still mounted, and it's just keeps stating: Logfiles: Can't get them when the server is in this "state" I do have console: root@TOWER:~# tail -f /var/log/syslog Apr 21 14:23:21 TOWER emhttpd: shcmd (4745): umount /etc/libvirt Apr 21 14:23:21 TOWER root: Stopping docker_load Apr 21 14:23:21 TOWER emhttpd: shcmd (4747): /etc/rc.d/rc.docker stop Apr 21 14:25:11 TOWER nginx: 2019/04/21 14:25:11 [error] 12777#12777: *1477951 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.0.176, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "e7591da5b3c213bd7e17dc48d29fc9dcd1283498.unraid.net", referrer: "https://e7591da5b3c213bd7e17dc48d29fc9dcd1283498.unraid.net/Main" Apr 21 14:26:12 TOWER nginx: 2019/04/21 14:26:12 [error] 12777#12777: *1477951 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.0.176, server: , request: "POST /update.htm HTTP/2.0", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "e7591da5b3c213bd7e17dc48d29fc9dcd1283498.unraid.net", referrer: "https://e7591da5b3c213bd7e17dc48d29fc9dcd1283498.unraid.net/Main" Apr 21 14:36:03 TOWER login[32238]: ROOT LOGIN on '/dev/pts/0' Apr 21 14:36:44 TOWER nginx: 2019/04/21 14:36:44 [error] 12777#12777: *1479468 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.176, server: , request: "POST /webGui/include/DashboardApps.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "e7591da5b3c213bd7e17dc48d29fc9dcd1283498.unraid.net", referrer: "https://e7591da5b3c213bd7e17dc48d29fc9dcd1283498.unraid.net/Dashboard" Apr 21 14:41:53 TOWER nginx: 2019/04/21 14:41:53 [error] 12777#12777: *1481156 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.176, server: , request: "POST /webGui/include/DashboardApps.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "e7591da5b3c213bd7e17dc48d29fc9dcd1283498.unraid.net", referrer: "https://e7591da5b3c213bd7e17dc48d29fc9dcd1283498.unraid.net/Dashboard" Apr 21 14:51:06 TOWER nginx: 2019/04/21 14:51:06 [error] 12777#12777: *1481156 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.176, server: , request: "POST /webGui/include/Download.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "e7591da5b3c213bd7e17dc48d29fc9dcd1283498.unraid.net", referrer: "https://e7591da5b3c213bd7e17dc48d29fc9dcd1283498.unraid.net/Tools/Diagnostics" Apr 21 14:54:15 TOWER login[8725]: ROOT LOGIN on '/dev/pts/0' Any input to what I could do when this happens next time? Br Casperse
  13. Update: Adding USB devices to the actual server made it work? (Don't seem to be able to delete these devices?)
  14. Hi @Jerky_san I just updated Unraid to Version: 6.7.0-rc7 and afterwards when I try to start this VM i get this error: internal error: unknown pci source type 'vendor' Anyone experienced the same? and maybee know of a quick solution? Thanks Logs: 2019-04-17 11:58:30.535+0000: 5584: info : libvirt version: 5.1.0 2019-04-17 11:58:30.535+0000: 5584: error : virUSBDeviceFindByVendor:218 : internal error: Did not find USB device 046d:c077 2019-04-17 11:58:30.781+0000: 5584: warning : virHostdevReAttachUSBDevices:1869 : Unable to find device 000.000 in list of active USB devices 2019-04-17 11:58:30.781+0000: 5584: warning : virHostdevReAttachUSBDevices:1869 : Unable to find device 000.000 in list of active USB devices 2019-04-17 11:59:28.634+0000: 5588: error : virUSBDeviceFindByVendor:218 : internal error: Did not find USB device 046d:c077 2019-04-17 11:59:28.877+0000: 5588: warning : virHostdevReAttachUSBDevices:1869 : Unable to find device 000.000 in list of active USB devices 2019-04-17 11:59:28.877+0000: 5588: warning : virHostdevReAttachUSBDevices:1869 : Unable to find device 000.000 in list of active USB devices 2019-04-17 11:59:54.230+0000: 5593: error : virDomainHostdevSubsysPCIDefParseXML:7471 : internal error: unknown pci source type 'vendor' 2019-04-17 12:00:02.880+0000: 5592: error : virDomainHostdevSubsysPCIDefParseXML:7471 : internal error: unknown pci source type 'vendor' 2019-04-17 12:00:08.092+0000: 5586: error : virDomainHostdevSubsysPCIDefParseXML:7471 : internal error: unknown pci source type 'vendor' 2019-04-17 12:01:53.411+0000: 5585: error : virUSBDeviceFindByVendor:218 : internal error: Did not find USB device 046d:c077 2019-04-17 12:01:53.655+0000: 5585: warning : virHostdevReAttachUSBDevices:1869 : Unable to find device 000.000 in list of active USB devices 2019-04-17 12:01:53.655+0000: 5585: warning : virHostdevReAttachUSBDevices:1869 : Unable to find device 000.000 in list of active USB devices 2019-04-17 12:07:38.847+0000: 5588: error : virUSBDeviceFindByVendor:218 : internal error: Did not find USB device 046d:c077 2019-04-17 12:07:39.101+0000: 5588: warning : virHostdevReAttachUSBDevices:1869 : Unable to find device 000.000 in list of active USB devices 2019-04-17 12:07:39.101+0000: 5588: warning : virHostdevReAttachUSBDevices:1869 : Unable to find device 000.000 in list of active USB devices 2019-04-17 12:08:29.534+0000: 5591: error : virDomainHostdevSubsysPCIDefParseXML:7471 : internal error: unknown pci source type 'vendor' 2019-04-17 12:09:44.069+0000: 5584: error : virDomainHostdevSubsysPCIDefParseXML:7471 : internal error: unknown pci source type 'vendor' 2019-04-17 12:10:04.432+0000: 5584: error : virDomainHostdevSubsysPCIDefParseXML:7471 : internal error: unknown pci source type 'vendor' 2019-04-17 12:11:18.173+0000: 5589: error : virDomainHostdevSubsysPCIDefParseXML:7471 : internal error: unknown pci source type 'vendor'
  15. @johnnie.black Thanks! copying all data away from the drive now!
  16. Sure thing diagnostics-20190411-0842.zip
  17. Hi All I am moving a lot of data on my Unraid server, and this morning I got this in the log file. (I have an array with 2 x Parity drives, was hoping these would correct errors) The disk have no errors in the SMART logs and the check is fine? Can I ignore this? no errors transferring data so would these be corrupt? Any recommendation to apps/tools for checksum or other solution to mitigate this when it happens? As always thanks for helping out spending your time answerings our many questions kernel: md: disk20 read error, sector=7015350792 kernel: md: disk20 read error, sector=7015350800 kernel: md: disk20 read error, sector=7015350808 kernel: md: disk20 read error, sector=7015350816 kernel: md: disk20 read error, sector=7015350824 kernel: md: disk20 read error, sector=7015350832 kernel: md: disk20 read error, sector=7015350840 kernel: md: disk20 read error, sector=7015350848 kernel: md: disk20 read error, sector=7015350856 kernel: md: disk20 read error, sector=7015350864 kernel: md: disk20 read error, sector=7015350872 kernel: md: disk20 read error, sector=7015350880 kernel: md: disk20 read error, sector=7015350888 kernel: md: disk20 read error, sector=7015350896 kernel: md: disk20 read error, sector=7015350904 kernel: md: disk20 read error, sector=7015350912 kernel: md: disk20 read error, sector=7015350920 kernel: md: disk20 read error, sector=7015350928 kernel: md: disk20 read error, sector=7015350936 kernel: md: disk20 read error, sector=7015350944 kernel: md: disk20 read error, sector=7015350952 kernel: traps: python[14567] general protection ip:1471431a2350 sp:14713ca30da0 error:0 in libpython2.7.so.1.0[147143113000+be000] root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token root: error: /webGui/include/Notify.php: wrong csrf_token root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token root: error: /webGui/include/DeviceList.php: wrong csrf_token root: error: /webGui/include/DeviceList.php: wrong csrf_token root: error: /webGui/include/DeviceList.php: wrong csrf_token root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token root: error: /plugins/dynamix.system.temp/include/SystemTemp.php: wrong csrf_token root: error: /webGui/include/DeviceList.php: wrong csrf_token root: error: /webGui/include/Notify.php: wrong csrf_token BTW I also have this error but all mounted drives is working okay? root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
  18. Just updated and then the UAD icon was "looking" for my mount points the last 15 min and then went unresponsive? I then went to the console and found this - sorry camera phone (Locked I could not write anything) I then tried Putty, and got ind and tried to do a "powerdown" hoping it will close down nicely.... UPDATE: I can see that the 192.168.0.10 cant connect thats the mount to my other server...but that shouldnt lock it down right? Okay, ended up cutting the power, and bootet with GUI, stopped all auto mounts and then started the array I then manually mounted each drive and its up and running again (Havent rebooted the server in a very long time so maybee it juste needed to be flipped
  19. @Squid I am writing in this thread because its the same issue, with the exception that I havent edited anything, standard docker install and backup setup following video I now get the following errors by email: /bin/sh: line 1: 31625 Killed /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Output says: # Generated docker monitoring schedule: 10 0 1 * * /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php check &> /dev/null # Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated mover schedule: 40 3 * * * /usr/local/sbin/mover &> /dev/null # Generated parity check schedule: 0 5 * * 0 /usr/local/sbin/mdcmd check &> /dev/null || : # Generated plugins version check schedule: 10 0 1 * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null # Generated array status check schedule: 20 0 * * * /usr/local/emhttp/plugins/dynamix/scripts/statuscheck &> /dev/null # Generated Unraid OS update check schedule: 11 0 1 * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null # Generated cron settings for docker autoupdates 0 4 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateDocker.php >/dev/null 2>&1 # Generated cron settings for plugin autoupdates 0 4 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 # Generated ssd trim schedule: 0 20 * * * /sbin/fstrim -a -v | logger &> /dev/null # Generated system data collection schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null # Refresh Recycle Bin trash sizes every minute: * * * * * /usr/local/emhttp/plugins/recycle.bin/scripts/get_trashsizes &> /dev/null And: # If you don't want the output of a cron job mailed to you, you have to direct # any output to /dev/null. We'll do this here since these jobs should run # properly on a newly installed system. If a script fails, run-parts will # mail a notice to root. # # Run the hourly, daily, weekly, and monthly cron jobs. # Jobs that need different timing may be entered into the crontab as before, # but most really don't need greater granularity than this. If the exact # times of the hourly, daily, weekly, and monthly cron jobs do not suit your # needs, feel free to adjust them. # # Run hourly cron jobs at 47 minutes after the hour: 47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null # # Run daily cron jobs at 4:40 every day: 40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null # # Run weekly cron jobs at 4:30 on the first day of the week: 30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null # # Run monthly cron jobs at 4:20 on the first day of the month: 20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null 0 4 2 * * /usr/local/emhttp/plugins/ca.backup2/scripts/backup.php &>/dev/null 2>&1 Any insight to this would be greatly appreciated
  20. Hi All Lidarr is running fine for me except for one thing! Folder access rights? when Lidarr creates folders for music I cant write to them before after having run the Unraid "New Permissions" for my music shared folder? I can't find any setting to set user and chmod in the UI, so my Q is can I set some special parameter string for Lidarr in the docker configuration? As always your feedback is much appriciated
  21. SOLUTION: On a older version of UAD 4-6 weeks ago I had to mount all my drives using the IP address (Same user and access rights) The new updated one I don't have to write any IP it finds the Host-name and then everything works! (Old Bug?)
  22. Do I need to create a Nobody user account? (The mounted drives using UAD is done with a user that have write access!)
  23. I checked the settings and they are set to 100? (MB?) Thanks for the link so this would still be correct solution for this problem: And YES! I am back to normal - THANKS @Squid !!!! Docker image disk utilization: 18-03-2019 17:42 Notice [TOWER] - Docker image disk utilization returned to normal level Docker utilization of image file /mnt/user/system/docker/docker.img So adding this line to all Docker images as a standard would be a good thing to do?, since I cannot enable the docker log rotation without reinstalling all my dockers? I am running 6.7.0-rc5 UPDATE: Got execution error on the sync docker so I had to remove the Extra parameters, trying the second time and it is still running
  24. Hi All & @Squid I have not been running Unraid that long and I seem to be having the same issue, getting these warnings: I then go to the Docker page and check size and get: This doesn't look to bad? I already extended the docker image to : 40G But doing the command: root@TOWER:~# du -h -d 1 /var/lib/docker/ 524K /var/lib/docker/containerd 23G /var/lib/docker/containers 0 /var/lib/docker/plugins 39G /var/lib/docker/btrfs 17M /var/lib/docker/image 52K /var/lib/docker/volumes 0 /var/lib/docker/trust 104K /var/lib/docker/network 0 /var/lib/docker/swarm 16K /var/lib/docker/builder 56K /var/lib/docker/buildkit 0 /var/lib/docker/unraid 0 /var/lib/docker/tmp 0 /var/lib/docker/runtimes 61G /var/lib/docker/ What to do next? UPDATE: just went to 78% I can see that Plex is busy generating video and Thumb preview? 548K /var/lib/docker/containerd 24G /var/lib/docker/containers 0 /var/lib/docker/plugins 39G /var/lib/docker/btrfs 17M /var/lib/docker/image 52K /var/lib/docker/volumes 0 /var/lib/docker/trust 104K /var/lib/docker/network 0 /var/lib/docker/swarm 16K /var/lib/docker/builder 56K /var/lib/docker/buildkit 0 /var/lib/docker/unraid 0 /var/lib/docker/tmp 0 /var/lib/docker/runtimes 62G /var/lib/docker/
  25. @Squid Any insight in what I could try? The volume is mounted and working, somehow Radarr just doesn't want to write in the Synology folder