TheWombat Posted January 30, 2020 Share Posted January 30, 2020 I have a Synology diskstation which uses rsync to backup to my UnRaid server. It was working fine on 6.7.x but having upgraded UnRaid to 6.8.2 my Synology can no longer connect. Any suggestions on what to look for to figure out what has caused the issue? I have a separate user called "backup" on UnRaid that has read-write access to the private backup share. I've included the rsyncd.conf file, however the backup doesn't even get to the point of starting. Other than the upgrade from 6.7.x to 6.8.2 nothing else was changed on either UnRaid or Synology. rsyncd.conf Quote Link to comment
drdebian Posted January 31, 2020 Share Posted January 31, 2020 I can gladly report that in my experience, v6.8.2 has greatly improved my SMB speeds. Upgrading two servers also went smoothly, so this version is a win! Quote Link to comment
bonienl Posted January 31, 2020 Share Posted January 31, 2020 13 hours ago, TheWombat said: I have a Synology diskstation which uses rsync to backup to my UnRaid server. It was working fine on 6.7.x but having upgraded UnRaid to 6.8.2 my Synology can no longer connect. Any suggestions on what to look for to figure out what has caused the issue? I have a separate user called "backup" on UnRaid that has read-write access to the private backup share. I've included the rsyncd.conf file, however the backup doesn't even get to the point of starting. Other than the upgrade from 6.7.x to 6.8.2 nothing else was changed on either UnRaid or Synology. rsyncd.conf 830 B · 4 downloads Unraid 6.8 does no longer allow scripts to run directly from the USB device. There are two possible solutions: Start the script using bash. E.g. bash <script-name> Copy the script to /tmp, chmod +x <script-name> and execute /tmp/<script-name> Quote Link to comment
TheWombat Posted January 31, 2020 Share Posted January 31, 2020 1 hour ago, bonienl said: Unraid 6.8 does no longer allow scripts to run directly from the USB device. There are two possible solutions: Start the script using bash. E.g. bash <script-name> Copy the script to /tmp, chmod +x <script-name> and execute /tmp/<script-name> Thank you, that worked Quote Link to comment
tjb_altf4 Posted February 1, 2020 Share Posted February 1, 2020 After dealing the igb driver drama with 6.8.1, happy to report so far so good under 6.8.2 I'm glad we have an engaged community and responsive dev team to get on top issues like these quickly 1 Quote Link to comment
squirrellydw Posted February 1, 2020 Share Posted February 1, 2020 upgraded from 6.8.1. to 6.8.2 a few days ago and no issues. You guys rock! 1 Quote Link to comment
bitcore Posted February 1, 2020 Share Posted February 1, 2020 (edited) Since 6.8.1, the linux kernel included supposedly included the fix for threadripper 3 where the MCE=off boot option was no longer required. Can anyone confirm that this is indeed the case? Also, are you able to actually read the ECC log if you have ECC memory? https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4-4.19-4.14-MCE-Fix-TR Thanks! Edited February 1, 2020 by bitcore Quote Link to comment
Stef-dk Posted February 2, 2020 Share Posted February 2, 2020 (edited) I have a TP-Link TG-3468 networks card. after updating it dont work. when rolling back to 6.8.1 it is back. any idea how to get it working with 6.8.2 Edited February 2, 2020 by Stef-dk Quote Link to comment
JorgeB Posted February 2, 2020 Share Posted February 2, 2020 57 minutes ago, Stef-dk said: I have a TP-Link TG-3468 That uses a very common Realtek chipset and it's working with v6.8.2, I have one on my test server, please start a thread on the general support forum and don't forget to add the diagnostics. Quote Link to comment
Joey Macaraeg Posted February 2, 2020 Share Posted February 2, 2020 Upgraded from 6.8.1 to 6.8.2. No noticeable issues. 1 Quote Link to comment
rollieindc Posted February 2, 2020 Share Posted February 2, 2020 (edited) Updated from 6.8.0 to 6.8.2 - Spun down all the VMs and Dockers first. Went well. No issues with Plex docker (upgraded it too!) Had one issue with the Windows 10VM, but after resetting the GPU and Chrome remote desktop interface, it worked fine again. Thanks! Edited February 2, 2020 by rollieindc 1 Quote Link to comment
Kaldek Posted February 3, 2020 Share Posted February 3, 2020 Upgraded successfully from 6.8.1 to 6.8.2. I waited for the unraid Nvidia build for 6.8.2 to be released. Everything working fine. 1 Quote Link to comment
bitcore Posted February 3, 2020 Share Posted February 3, 2020 Upgraded from 6.6.6. It took me a while to want to move away from the number of the beast.... Alas, security et. al. Seems to be OK. VM boots fine. webgui feels faster/snappier. Running on very old hardware (circa 2008): Gigabyte EP45-UD3P, core 2 quad Q9550, 8GB, Arecca ARC-1880IX-12 1 Quote Link to comment
jpowell8672 Posted February 3, 2020 Share Posted February 3, 2020 (edited) Upgraded successfully from 6.8.1 to 6.8.2. I waited for the Unraid Nvidia build 6.8.2 to be released. Everything working fine except for error: failed to connect to the hypervisor same as 6.8.1. Edited February 3, 2020 by jpowell8672 Quote Link to comment
ramblinreck47 Posted February 4, 2020 Share Posted February 4, 2020 On 1/29/2020 at 2:08 PM, scubieman said: Does this support 9th gen igpu? 9700k ? It appears this uses 4.19.98 and i need 4.20. This correct? I’ve seen people say that the 9th Gen iGPU has actually been working since they upgraded to 6.8.0, which seems weird since it’s still not 4.20. Have you tried it out on any stable release since 6.8.0? Quote Link to comment
Ntouchable Posted February 4, 2020 Share Posted February 4, 2020 Upgraded from 6.7.2 to 6.8.2. All seems good. Quote Link to comment
mifronte Posted February 5, 2020 Share Posted February 5, 2020 I had problem booting after upgrading to 6.8.1 where the server came up with a random IP address and was unresponsive by both the console and GUI. It took a cold boot where I had to manually completely power down the server. It gave me a scare. So I would like to be prepared before I upgrade to 6.8.2. What should I be backing up on the flash just in case I have to redo the flash? Quote Link to comment
JorgeB Posted February 5, 2020 Share Posted February 5, 2020 Just now, mifronte said: What should I be backing up on the flash just in case I have to redo the flash? Config folder. Quote Link to comment
limetech Posted February 5, 2020 Author Share Posted February 5, 2020 3 hours ago, mifronte said: What should I be backing up on the flash just in case I have to redo the flash? Main/Flash click Flash Backup. 1 Quote Link to comment
chris_netsmart Posted February 5, 2020 Share Posted February 5, 2020 Just update. Amd all ok. Thanks unraid. 1 Quote Link to comment
mifronte Posted February 5, 2020 Share Posted February 5, 2020 (edited) Ok, just updated and the server rebooted with some random IP address of 169.264.246.72 so this means I can't access the GUI. My network is 10.168.x.x so I don't know where it is getting its IP address. I am going to create a support thread. Edited February 5, 2020 by mifronte Quote Link to comment
Frank1940 Posted February 5, 2020 Share Posted February 5, 2020 8 minutes ago, mifronte said: How do I safely power down via the console? type poweroff Quote Link to comment
mifronte Posted February 5, 2020 Share Posted February 5, 2020 After update, my server is using an unknown IP address of 169.264.246.72. So this makes my server unaccessible except via IPMI console. Quote Link to comment
mifronte Posted February 5, 2020 Share Posted February 5, 2020 I made a back up of my flash drive using the unRAID flash backup prior to updating to 6.8.2. How do I revert back to it? I need my server up and running. Quote Link to comment
limetech Posted February 5, 2020 Author Share Posted February 5, 2020 21 minutes ago, mifronte said: After update, my server is using an unknown IP address of 169.264.246.72. So this makes my server unaccessible except via IPMI console. That means it can't get an IP address from your dhcp server. What release did you upgrade from? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.