Ver7o

Thankfully the files moved OK. Upon reboot, the shares were visible again. There were also the mentioned duplicates, but only of top level folder (the files inside those moved fine). Had to move those again and now everything is as it should be. Thanks for helping guys, appreciate it.

Ah, only just realized how badly I worded the question. I meant if files will end up being affected because something crashed while Unbalance was still running.

This won't affect any files or Unbalance which is running? Thanks!

Hello, Today I decided to move specific shares to specific disks so the data is not scattered across multiple disks causing unneccessary disk spinups. Before moving the data Unbalance plugin kept telling me I should run "docker safe new permssions" as there were issues. I did run that and the plugin stopped reporting issues upon which I ran the mover. It is still running atm. Here is where the heart attack comes in. I tried to access a share from my windows box just not and it wouldn't connect. So I checked Unraid shares tab and its saying "There are no exportable user shares". A few google searches reveal a reboot can help, but I just want to have more info what to do right not before I risk rebooting and not being able to get diagnostics anymore. syslog is spitting out something like this: May 3 15:29:09 Tower smbd[27783]: [2021/05/03 15:29:09.281737, 0] ../../source3/smbd/service.c:841(make_connection_snum) May 3 15:29:09 Tower smbd[27783]: make_connection_snum: '/mnt/user/Backup' does not exist or permission denied when connecting to [Backup] Error was Transport endpoint is not connected May 3 15:29:09 Tower smbd[27783]: [2021/05/03 15:29:09.285374, 0] ../../source3/smbd/service.c:841(make_connection_snum) May 3 15:29:09 Tower smbd[27783]: make_connection_snum: '/mnt/user/Backup' does not exist or permission denied when connecting to [Backup] Error was Transport endpoint is not connected May 3 15:29:09 Tower smbd[27783]: [2021/05/03 15:29:09.288965, 0] ../../source3/smbd/service.c:841(make_connection_snum) May 3 15:29:09 Tower smbd[27783]: make_connection_snum: '/mnt/user/Backup' does not exist or permission denied when connecting to [Backup] Error was Transport endpoint is not connected May 3 15:41:10 Tower smbd[27783]: [2021/05/03 15:41:10.670767, 0] ../../source3/smbd/service.c:168(chdir_current_service) May 3 15:41:10 Tower smbd[27783]: chdir_current_service: vfs_ChDir(/mnt/user/Downloads) failed: Transport endpoint is not connected. Current token: uid=1000, gid=100, 4 groups: 100 3003 3004 3005 May 3 15:41:10 Tower smbd[27783]: [2021/05/03 15:41:10.670896, 0] ../../source3/smbd/service.c:180(chdir_current_service) May 3 15:41:10 Tower smbd[27783]: chdir_current_service: vfs_ChDir(/mnt/user/Downloads) failed: Transport endpoint is not connected. Current token: uid=1000, gid=100, 4 groups: 100 3003 3004 3005 May 3 15:41:10 Tower smbd[27783]: [2021/05/03 15:41:10.673892, 0] ../../source3/smbd/service.c:168(chdir_current_service) tower-diagnostics-20210503-1333.zip

Hey, thanks for that. I set this up and it seemed to work until today. Today inform IP got overwritten with dockers internal IP again, so this doesn't help.

Jesus christ, I'm regretting going the ubiquiti route. Half page adverts, high power consumption of the switch, electronics in my AP whining when there is traffic on a device connected to wifi... Anyway, has anyone found the cause of devices forgetting the correct inform IP (which causes then to be reported as disconnected or in endless adoption loop)? For me, it happens every few days for no apparent reason. Nothing on the network or docker changes, but somehow inform IP gets overwritten with the dockers internal IP every few days. Having to SSH or switching host/bridge gets annoying over time.

Hey guys, I'm getting this error in my syslog daily. I have an external HDD mounted as unassigned device for some backups. fstrim: /mnt/disks/My_Passport: FITRIM ioctl failed: Device or resource busy as far as I understand this, its trying to trim it, but since its a HDD it can't? How do I tell it to stop?

Droppin in to say I had spindown issues in RC2 and removing dynamix autofan plugin didn't fix it. Upon upgrading to 6.9.0 the issue persisted, but this time removing dynamix autofan looks to have solved it.

Yes, it it shows up with "mount" as an option.

Just to add to the disks not spinning down issue. I had an unassigned thumb drive hooked to my server and the syslog was throwing "emhttpd: spinning down /dev/sde" notices every 15min. I unmounted the drive yesterday, however, to my surprise, syslog is still filing with "emhttpd: spinning down /dev/sde" every 15min. Anyone experiencing the same?

I started off with the same. Read events would spin the disks and after 15min, they would spin down. After the troubleshooting shit I did, mentioned above in topic... even the 15min spindown no longer works. I decided to just give it up and wait for a version bump and hopefully a fix.

I use Mullvad. Haven't had a single problem yet. As far as I can tell, then support port forwarding on all of their servers.

Just throwing this out there is maybe there is someones else experiencing similar issues. I use Bromite on mobile, and everytime I visit unraid forums, the browser hangs and ask to force close. Sometimes it loads the forum homepage, and hangs in the next selected section or sometimes it hangs outright. And it only happens on this page (unraid webgui is fine). Haven't otherwise experienced a browser crash on mobile.

I'm gonna ask my question here as it's somewhat related to this topic. I had 2 events with the thumb drive running unraid so far. Both times I copied the config folder over to the new thumb drive, and both times I was greeted by a rather old config (6 months ish), as the dockers listed were long gone and not installed anymore. The reason this baffles me is that both times I copied the config folder from a less then a week old thumb drive backup (I have weekly backups of my thumb drive using the excellent CA plugin). I was able to one click reinstall everything using the "past apps" tab in CA, but still... What is happening here and how to fix it?

Do you see the docker you used if you go under "past apps" (or something like that - going off memory) in the community apps tab? The good thing about that awesome feature is that not only has your apps/docker install history, it also remembers the config you used with it. That basically means reinstalling everything is a one click affair.

TurboWrite doesn't seem to be the reason for this. Spin ups still happen without it. Jan 25 20:53:42 Tower emhttpd: spinning down /dev/sdb Jan 25 20:53:42 Tower emhttpd: spinning down /dev/sdc Jan 25 20:53:42 Tower emhttpd: spinning down /dev/sdd Jan 25 21:24:30 Tower emhttpd: read SMART /dev/sdc Jan 25 21:39:32 Tower emhttpd: spinning down /dev/sdc Jan 25 21:51:53 Tower emhttpd: read SMART /dev/sdd Jan 25 22:06:55 Tower emhttpd: spinning down /dev/sdd Jan 25 22:53:12 Tower emhttpd: read SMART /dev/sdc Jan 25 23:05:09 Tower emhttpd: read SMART /dev/sdd Jan 25 23:05:19 Tower emhttpd: read SMART /dev/sdb Jan 25 23:20:11 Tower emhttpd: spinning down /dev/sdd Jan 25 23:22:21 Tower emhttpd: spinning down /dev/sdb Jan 25 23:22:21 Tower emhttpd: spinning down /dev/sdc Jan 25 23:37:59 Tower emhttpd: read SMART /dev/sdc Jan 26 00:00:13 Tower emhttpd: read SMART /dev/sdb Jan 26 00:01:55 Tower emhttpd: read SMART /dev/sdd Jan 26 00:30:19 Tower emhttpd: spinning down /dev/sdb Jan 26 00:33:24 Tower emhttpd: spinning down /dev/sdc Jan 26 00:33:47 Tower emhttpd: spinning down /dev/sdd Jan 26 02:01:55 Tower emhttpd: read SMART /dev/sdd Jan 26 02:01:55 Tower emhttpd: read SMART /dev/sdc Jan 26 02:18:14 Tower emhttpd: spinning down /dev/sdd Jan 26 02:18:16 Tower emhttpd: spinning down /dev/sdc Jan 26 09:35:11 Tower emhttpd: read SMART /dev/sdd Jan 26 09:50:13 Tower emhttpd: spinning down /dev/sdd Jan 26 14:13:46 Tower emhttpd: read SMART /dev/sdc

I do use CA TurboWrite and its write mode is set to Normal (Read/Modify/Write). Under disk setting I have md_write_method set to auto. I have not thought of disabling turbo plugin until now. Disabled it now. Will report back later, if anything changes.

I have these random smart spinups on RC2 too. I went from stable to RC2 because stable verson did not have drivers for newer intel nics. I do not remember this being a thing on stable. I cannot confirm since the stable was running on different mobo (B450 before, H410 now). I do not run any HBA controllers, just plain mobo sata. The hardware is in its 3rd day so I wouldnt say its dying (faking hopefully right :D).

thank you, it did indeed work.

Hello everyone, I have just now noticed that the newer intel i219-v nics on socket 1200 boards do no work with 6.8.3. My question is, will my config file from the flash drive running 6.8.3 work (problem free) with 6.9 RC2 if I make a new USB? Thanks,

Hello guys, I recently changed my off the shelf router for a pfSense box, and since then when I try to connect to the nextcloud web UI, I get a 504 Gateway Time-out. I only ever use Nextcloud on the local network, I don't have any reverse proxies and other then changing the router, everything else remains the same. How should I go about troubleshooting it? EDIT: Fixed it. The issue was in www/nextcloud/config/config.php, pointing to an old address.

Spaceinvader posted a video about event device passthrough. Have a look at that and see if that helps with the latency issues?

I had a similar issue where everything would lock up and crash unraid. Started out of the blue too. For my case it turned out to be USB controller which wasn't resetting properly. Which device does this part of the XML correspond to? <controller type='pci' index='10' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <alias name='pci.10'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> For my case, the template would always get edited to pcie-to-pci-bridge and the system didn't know what to do with it. If this corresponds to the USB controller, try to remove the usb controller from the VM (and this part from the xml if it remains) and try to boot up.

Just throwing this here; I had to make a new Unraid boot drive which used UEFI boot mode (the old one did not). That however resulted in all my linux VMs not booting up and Windows VM throwing the error code 43 error. Going back to legacy boot mode, fixed it all again. Hope this helps someone.