itskamel

did you ever get this fixed? if so what was it?

how do you get it to show you the permissions? mine doesnt show folder permissions. do i have to enable it somewhere?

having the same issue, now i just have a error page on nextcloud.

Getting lots of parity errors. Attaching logs. Not sure where to start. tower-diagnostics-20220816-1731.zip

not sure what version i was on but i did a update and now nothing will upload over local network. if i try to open the web ui page i get "Internal Server Error". anyone else?

running on unraid 6.8.3 and vm backup 2021.3.11 set to run ever saturday night. looking through my files it looks like it hasnt actually done a backup since december of last year. if i go to the script and i select to run backup i get the notifiaction fairly quickly that it has finished but no new backup. attaching my log file. 2021-04-04 08:25:25 Start logging to log file. 2021-04-04 08:25:25 information: send_notifications is 1. notifications will be sent. 2021-04-04 08:25:25 information: only_send_error_notifications is 0. normal notifications will be sent if send_notifications is enabled. 2021-04-04 08:25:31 information: keep_log_file is 1. log files will be kept. 2021-04-04 08:25:31 information: number_of_log_files_to_keep is 1. this is probably a sufficient number of log files to keep. 2021-04-04 08:25:31 information: enable_vm_log_file is 0. vm specific logs will not be created. 2021-04-04 08:25:31 information: backup_all_vms is 1. vms_to_backup will be ignored. all vms will be backed up. 2021-04-04 08:25:31 information: use_snapshots is 0. vms will not be backed up using snapshots. 2021-04-04 08:25:31 information: kill_vm_if_cant_shutdown is 0. vms will not be forced to shutdown if a clean shutdown can not be detected. 2021-04-04 08:25:31 information: set_vm_to_original_state is 1. vms will be set to their original state after backup. 2021-04-04 08:25:31 information: number_of_days_to_keep_backups is 0. backups will be kept indefinitely. be sure to set number_of_backups_to_keep to keep backups storage usage down. 2021-04-04 08:25:31 information: number_of_backups_to_keep is 3. this is probably a sufficient number of backups to keep. 2021-04-04 08:25:31 information: inline_zstd_compress is 0. vdisk images will not be inline compressed. 2021-04-04 08:25:31 information: pigz_compress is 0. backups will not be post compressed. 2021-04-04 08:25:31 information: use_snapshots disabled, not adding snapshot_extension to vdisk_extensions_to_skip. 2021-04-04 08:25:31 information: snapshot_fallback is 0. snapshots will fallback to standard backups. 2021-04-04 08:25:31 information: pause_vms is 0. vms will be shutdown for standard backups. 2021-04-04 08:25:31 information: enable_reconstruct_write is 0. reconstruct write will not be enabled by this script. 2021-04-04 08:25:31 information: compare_files is 0. files will not be compared after backups. 2021-04-04 08:25:31 information: backup_xml is 1. vms will have their xml configurations backed up. 2021-04-04 08:25:31 information: backup_nvram is 1. vms will have their nvram backed up. 2021-04-04 08:25:31 information: backup_vdisks is 1. vms will have their vdisks backed up. 2021-04-04 08:25:31 information: start_vm_after_backup is 0. vms will not be started following successful backup. 2021-04-04 08:25:31 information: start_vm_after_failure is 0. vms will not be started following an unsuccessful backup. 2021-04-04 08:25:31 information: disable_delta_sync is 0. rsync will be used to perform delta sync backups. 2021-04-04 08:25:31 information: rsync_only is 0. cp will be used when applicable. 2021-04-04 08:25:31 information: actually_copy_files is 1. files will be copied. 2021-04-04 08:25:31 information: clean_shutdown_checks is 20. this is probably a sufficient number of shutdown checks. 2021-04-04 08:25:31 information: seconds_to_wait is 30. this is probably a sufficient number of seconds to wait between shutdown checks. 2021-04-04 08:25:31 information: keep_error_log_file is 1. error log files will be kept. 2021-04-04 08:25:31 information: number_of_error_log_files_to_keep is 10. this is probably a sufficient error number of log files to keep. 2021-04-04 08:25:31 information: started attempt to backup 001 Windows 10, 002 Windows 10, 003 Windows 10, Backup DNS, CentOS, Debian 002, Macinabox BigSur, Ubuntu to /mnt/user/Drive Backups/VM Backups/Automatic Backups 2021-04-04 08:25:31 information: 001 Windows 10 can be found on the system. attempting backup. 2021-04-04 08:25:31 information: removing old local 001 Windows 10.xml. 2021-04-04 08:25:31 information: creating local 001 Windows 10.xml to work with during backup. 2021-04-04 08:25:31 information: /mnt/user/Drive Backups/VM Backups/Automatic Backups/001 Windows 10 exists. continuing. 2021-04-04 08:25:31 information: finished attempt to backup 001 Windows 10, 002 Windows 10, 003 Windows 10, Backup DNS, CentOS, Debian 002, Macinabox BigSur, Ubuntu to /mnt/user/Drive Backups/VM Backups/Automatic Backups. 2021-04-04 08:25:31 information: cleaning out logs over 1. 2021-04-04 08:25:31 information: removed '/mnt/user/Drive Backups/VM Backups/Automatic Backups/logs/20210404_0812_unraid-vmbackup.log'. 2021-04-04 08:25:31 information: cleaning out error logs over 10. 2021-04-04 08:25:31 information: did not find any error log files to remove. 2021-04-04 08:25:31 Stop logging to log file.

all of a sudden maybe after update i am unable to connect to sab. sonarr connects just fine. Test was aborted due to an error: Unable to connect to SABnzbd, HTTP request failed: [503:ServiceUnavailable] [GET] at [https://192.168.1.12:8080/api?mode=get_config&apikey=REMOVED&output=json] any help would be appreciated. i am not running deluge vpn

bump, anyone? i have been searching and searching but i do not see anyone else with this issue. I have been told it could possibly be a pic lanes issue but not sure how to confirm.

anyone? @limetech could this be a driver issue? Btw I might add, when I was using the onboard nic (1gb) the passthough of the gfx card worked fine. No network issues.

Unraid 6.8.3 Intel X540-T2 NIC AMD firepro W2100 Windows 10 VM on vlan if that matters When I boot Unriad without the gfx card passedthrough my dashboard shows my 10gbe link and everything is all good. As soon as I passthrough the gfx card and start the VM the link shows 1gb on the dashboard. I will attach my diag files incase anyone can help me out. I will also include a clip of the logs after the passthough is set and the VM is booting. Dec 7 22:46:21 Tower kernel: ixgbe 0000:81:00.0 eth0: NIC Link is Down Dec 7 22:46:21 Tower kernel: br0: port 1(eth0) entered disabled state Dec 7 22:46:21 Tower kernel: br0.100: port 1(eth0.100) entered disabled state Dec 7 22:46:24 Tower ntpd[3218]: Deleting interface #2 br0, 192.168.1.12#123, interface stats: received=1021, sent=1038, dropped=0, active_time=215923 secs Dec 7 22:46:24 Tower ntpd[3218]: 216.239.35.0 local addr 192.168.1.12 -> <null> Dec 7 22:46:24 Tower ntpd[3218]: 216.239.35.4 local addr 192.168.1.12 -> <null> Dec 7 22:46:24 Tower ntpd[3218]: 216.239.35.8 local addr 192.168.1.12 -> <null> Dec 7 22:46:24 Tower ntpd[3218]: 216.239.35.12 local addr 192.168.1.12 -> <null> Dec 7 22:46:40 Tower kernel: ixgbe 0000:81:00.0 eth0: NIC Link is Up 1 Gbps, Flow Control: None Dec 7 22:46:40 Tower kernel: br0: port 1(eth0) entered blocking state Dec 7 22:46:40 Tower kernel: br0: port 1(eth0) entered forwarding state Dec 7 22:46:40 Tower kernel: br0.100: port 1(eth0.100) entered blocking state Dec 7 22:46:40 Tower kernel: br0.100: port 1(eth0.100) entered forwarding state Dec 7 22:46:41 Tower kernel: ixgbe 0000:81:00.0 eth0: NIC Link is Down Dec 7 22:46:41 Tower kernel: br0: port 1(eth0) entered disabled state Dec 7 22:46:41 Tower kernel: br0.100: port 1(eth0.100) entered disabled state Dec 7 22:46:45 Tower kernel: ixgbe 0000:81:00.0 eth0: NIC Link is Up 10 Gbps, Flow Control: None Dec 7 22:46:45 Tower kernel: br0: port 1(eth0) entered blocking state Dec 7 22:46:45 Tower kernel: br0: port 1(eth0) entered forwarding state Dec 7 22:46:45 Tower kernel: br0.100: port 1(eth0.100) entered blocking state Dec 7 22:46:45 Tower kernel: br0.100: port 1(eth0.100) entered forwarding state Dec 7 22:46:47 Tower ntpd[3218]: Listen normally on 3 br0 192.168.1.12:123 Dec 7 22:46:47 Tower ntpd[3218]: new interface(s) found: waking up resolver Dec 7 22:46:58 Tower kernel: ixgbe 0000:81:00.0 eth0: NIC Link is Down Dec 7 22:46:58 Tower kernel: br0: port 1(eth0) entered disabled state Dec 7 22:46:58 Tower kernel: br0.100: port 1(eth0.100) entered disabled state Dec 7 22:47:01 Tower ntpd[3218]: Deleting interface #3 br0, 192.168.1.12#123, interface stats: received=3, sent=9, dropped=0, active_time=14 secs Dec 7 22:47:01 Tower ntpd[3218]: 216.239.35.0 local addr 192.168.1.12 -> <null> Dec 7 22:47:01 Tower ntpd[3218]: 216.239.35.4 local addr 192.168.1.12 -> <null> Dec 7 22:47:01 Tower ntpd[3218]: 216.239.35.8 local addr 192.168.1.12 -> <null> Dec 7 22:47:01 Tower ntpd[3218]: 216.239.35.12 local addr 192.168.1.12 -> <null> Dec 7 22:47:18 Tower kernel: ixgbe 0000:81:00.0 eth0: NIC Link is Up 1 Gbps, Flow Control: None Dec 7 22:47:18 Tower kernel: br0: port 1(eth0) entered blocking state Dec 7 22:47:18 Tower kernel: br0: port 1(eth0) entered forwarding state Dec 7 22:47:18 Tower kernel: br0.100: port 1(eth0.100) entered blocking state Dec 7 22:47:18 Tower kernel: br0.100: port 1(eth0.100) entered forwarding state Dec 7 22:47:20 Tower ntpd[3218]: Listen normally on 4 br0 192.168.1.12:123 Dec 7 22:47:20 Tower ntpd[3218]: new interface(s) found: waking up resolver tower-diagnostics-20201207-2324.zip

After more troubleshooting it has nothing to do with docker. It happens only when the gfx card is passedthrough the VM.

I have figured out that after a reboot it will show my connection as 10000, then iperf speeds test show good. So after i enable vm that has a vlan is when the connection goes to 1000! Posting my diagnostics with this thread. I have tested with another vm that is not on the vlan and speeds remain at 10000. anyone ever seen anything like this? both the unraid box and the windows pc have x540-t2 in them the switch is a unifi us-16-xg Connecting to host 192.168.1.12, port 5201 [ 4] local 192.168.1.13 port 49889 connected to 192.168.1.12 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 12.1 MBytes 101 Mbits/sec [ 4] 1.00-2.00 sec 16.5 MBytes 139 Mbits/sec [ 4] 2.00-3.01 sec 4.50 MBytes 37.3 Mbits/sec [ 4] 3.01-4.00 sec 5.75 MBytes 48.7 Mbits/sec [ 4] 4.00-5.00 sec 6.38 MBytes 53.7 Mbits/sec [ 4] 5.00-6.00 sec 3.12 MBytes 26.2 Mbits/sec [ 4] 6.00-7.01 sec 3.25 MBytes 26.9 Mbits/sec [ 4] 7.01-8.01 sec 4.50 MBytes 38.0 Mbits/sec [ 4] 8.01-9.01 sec 4.88 MBytes 40.6 Mbits/sec [ 4] 9.01-10.01 sec 5.75 MBytes 48.4 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 4] 0.00-10.01 sec 66.8 MBytes 55.9 Mbits/sec sender [ 4] 0.00-10.01 sec 66.5 MBytes 55.8 Mbits/sec receiver tower-diagnostics-20201204-2313.ziptower-diagnostics-20201204-2313.zip

Trying to route sonarr and radarr through the proxy. I keep getting proxy failed. I know it works because I can use the same settings in firefox and see the ip change, aswell if I set it in windows. Am I missing something simple? ip=192.168.1.12 -this is the server that privoxy is running on. port=8118 **edit, I was able to get them working by running it in bridge mode. However it does not seem to like that I specify a LOCAL IP that is using dnscrypt.

last night I noticed some problems with sab. I restarted the docker and now I can not access the UI unless I set the docker to VPN=OFF. here is a log. https://pastebin.com/iV6hfwY9 I think i figured it out. seems PIA changed from us-texas.privateinternetaccess.com to us-dal.privateinternetaccess.com. Seems there were a few other changes if anyone else is having this issue.

glad i found this thread. seems this is happening to me. i will try the -i br0 option and see how that goes.

Thank you. Is there any fix for this yet?

ok makes sense now. so should i make a script where it will mount the drive, rsync, then unmount the drive and see how that goes? btw thanks for the reply.

ok that makes sense, so i only have it set to rsync once daily when that machine is on. i wonder why it is trying at 9am? should be doing it at 6am only. also that is from a workstation PC to the array. should have nothing to do with "unassigned drives".

here they are. tower-diagnostics-20200620-1150.zip

I noticed that every once in a while I get a error in my log. Anyone know what this means? And or should I be concerned? I do have my dockers and VM's running on the NVME samsung drive.

Getting a error and I have searched but I am not sure what is going on.

6.8.3

Ok, I will backup indeed. I am on the latest version if that matters.

I have dual cache drives. Raid 1 from what I have read. (I have not changed any settings). Can i pull drive 2 and just replace it with a new one? Or do I still need to move everything off the drives?

Trying to connect to my controller. I do see this error in my logs. can anyone guide me? 2020-05-22 11:02:12,467 localhost-startStop-1 ERROR Recovering from StringBuilderEncoder.encode('[2020-05-22T06:02:12,451] <localhost-startStop-1> INFO system - Current System IP: 192.168.1.11 ') error: org.apache.logging.log4j.core.appender.AppenderLoggingException: Error writing to stream logs/server.log org.apache.logging.log4j.core.appender.AppenderLoggingException: Error writing to stream logs/server.log I have deleted the image and reinstalled from the CA. still same result.