1471

Hi @Squid, appreciate you must be very busy but is there any chance you could take a look at this plugin, again, and see if it's possible to fix in 6.12.XX Issue is around changing the order of folders and containers, useful video in the post above showing whats wrong.

Hope this can be fixed too, one of the most useful plugins for Unraid!

Ok, thanks for the update / info.

Migrated to the new authentication and spotted two minor missues, though it'd share incase it effects others etc: 1) My accounts profile picture has dissappeard from the 'my servers' plugin: 2) My accounts now showing as having two servers with the same name?

Stumbled across this plugin when watching THIS video on reducing power usage, works well! As others have mentioned, should get its added to the CA store so its easier to find as really good!

All sorted. Thank you very much for your help, really appreciated.

Thanks, its an encrypted volume so had to go via the GUI, followed a helpful guide from Spaceinvader One. Ran the XFS recovery (had to use -L flag) and rebooted th eserver. I'm still getting the disk error (see screen shot below), but now the disks being emulated and can access the data. Just to add, there arent any SMART errors on the disk, so don't think thats the issue. Do you know what the process would be to fix from here? Remove the disk from the aray, format and rebuild from parity? I've created a new share NOT using the faulty disk and backing up everything from the faulty disk to that, just in case. New diagnostics attached if that helps unraid-server-diagnostics-20221017-0634.zip

Looking for a bit of help! I've got a disk marked as "Unmountable: Wrong or no file system". I have two parity disks in my array, the GUI seems to suggest that the disk is being emulated, however the data on the disk is missing: I have the option to format the disk, but don't want to do that as the data isn't being recreated from parity, so think doing this would loose the data: Is there anything I can do? I've tried a reboot and same issue. I have all my important files backed up, but hoping I dont need to go through the hassle or working out whats missing etc. Running 6.11.1 - Diagnostics attached. unraid-server-diagnostics-20221016-1418.zip

Similar issues as above since updating to Unraid 6.11.1. Looks like all the other controls have gone and can only see for Docker? Checked my Grafana dashboards and looks like the datas not being collected for VM's etc Looking at the logs, getting: Cannot read properties of undefined (reading 'children') Get VM Details for ip: 10.112.1.80 Failed

Thank you, all sorted for me with the update.

Yup, same for me too. Rolling back worked.

Just a heads up, looks like the linux server image is deprecated as well now. From the github page: ---------------------------- This image is deprecated. We will not offer support for this image and it will not be updated. We recommend the official images: https://github.com/AnalogJ/scrutiny#docker ---------------------------- The AnalogJ image is available through CA, using that without any problems

Thank you @Squid for fixing this plugin and the dashboard too

Thanks, that fixed things for me.

Nothing useful to add but have the same problem but with filerun: 220306 21:58:55 mysqld_safe Logging to '/config/databases/9deadb462a43.err'. 220306 21:58:55 mysqld_safe Starting mariadbd daemon with databases from /config/databases Haven't had a change to look into the problem, but glad to know i'm not the only one.

Thanks, appreciate the quick reply! Sorted, was a clash with linuxserver/unifi-controller container.

Hi, looking for a bit of help getting the alturismo/xteve container up and running, installed via community applications. I can't get the container to start, from the logs: [ERROR] listen udp4 224.0.0.0:1900: bind: address already in use () - EC: 0 If I run the following command from Unraid - sudo netstat -pna | grep 1900 - I get: upd 0 0.0.0.0.0:1900 0.0.0.0.* 24583/docker-proxy The containers running in host mode as per the template. Any idea's what i'd doing wrong?

... although i'm having issues updating to the latest version from tne new container. Needs to be done by regestering then updating from the Filerun GUI. Info HERE.

Yup, moved over to filerun/filerun with the old container retired by the looks of it. Major update, info on the forum post HERE.

Thanks for that. Yup having the same problem since updating, changing to telegraf:1.20.2-alpine worked for me too.

Hey, did you have any luck getting sorted?

Nothing to add other than I get the same error

Well, I haven't had any problems since so looks like adding a PUID and PGID to containers with those variables missing worked. Still not sure what container was causing the problem but all good now

There are a few good use cases for root shares, Space Invader One has a recent video on it: Unraid & Moving Data (Part 4) RootShares And also covered in this older video with lots of other useful tips and tricks with SMB shares: Unraid Shares in Depth - PT1 Windows and SMB __________________________________________________________________________________ Thanks for the reply. Yes that was my first though, however permissions for most other folders and files in the share are being changed too, so harder to track down as have lots of container mapped to the whole array. I can at least narrow it down to container that have access to the share though. There were a few containers without a PUID and PGID variable, so added those, but that didn't fix the problem. Think the next step is to look at umasks, I've ssh'd into each container and they've all running under 0022. Had some good advice in the unraid subreddit, sounds like changing umasks to 002 or 000 where supported might work? Not sure if the permission changes are something that would show up in the logs? If so, any idea what I should be looking for?

I've got a odd problem with file and folder permissions changing every few days. I Imagine this this is a container with the wrong permissions or something, however I've only been using Unraid for a few weeks and would appreciate pointing me in the right direction to find whats wrong. I have a fair few containers and a Server2019 VM, with shares mapped via a root share. This works well but every few days the permissions change and no longer have edit rights to the shared folder. This is the same when mapped to the share in my VM or connecting from ym Macbook. Running the tool 'docker safe perms' fixes the permissions but they keep reverting. I've run ls -al before and after fixing the permissions so can see whats being changed, see attached screen shot. I've also attached my servers diagnostics for info. If it's relevant, these are my root share settings: [root share] path = /mnt/user comment = browseable = no valid users = olly-share write list = olly-share vfs objects = #hide files veto files = /._ds*/.DS_Store/ hide files = /$*/ hide dot files = yes #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end Any idea how I can find whats changing the permissions? I've had a look through the logs, but not really sure what i'm looking for. I've been through my containers and found a few that didn't have a PUID or PGID set, so i've added those variables to see if that makes a difference, but not entirely confident in what i'm doing when it comes to docker permissions to be honest. unraid-server-diagnostics-20210604-1123.zip