guyonphone

I am running a game server in a container, I was thinking about how it would be nice to be able to give someone else the ability to login and perform a restart of a container, and then I got to thinking that UnRaid could have a full User Permission system, which could be handled via the GUI. (CLI too of course) Imagine a world... Where you could assign users granular permissions to VM's, Containers, plugins and other permissions. Users with limited rights would only see GUI access for objects they have rights to view. Containers: Permission to Manage\edit a specific container or multiple containers. Permission to add a new container. Permission to stop\restart a container. Permission to see container logs. Virtual Machines Permission to Manage\edit a specific VM or multiple VMs. Permission to provision a new VM. Permission to stop\restart a VM. Permission to see VM logs. Plugins: Permission to install plugins Permission to remove plugins. Unraid Settings: Granular user permissions to allow the ability to manage the array. Start/Stop the array. Essentially extend user permissions past the file system into every aspect of Unraid. Etc, so on and so forth. Now tell me why my idea is a horrible one and I should have never had it

I feel a feature request coming on :). I appreciate the suggestion. Posted one here:

As the title suggests I would like to create a user who's only ability is to reboot a container, is this possible?

@acozad1 I downgraded from 6.11.1 to 6.11.0 and then re-updated back to 6.11.1. Unfortunately this did not fix my issue and I am still having the issue. I am noticing that I am having odd issues where I am unable to rename some directories via windows SMB.

I too am having this issue, going to try the downgrade and re-update method mentioned above to see if that works.

I actually got this figured out, and was totally caused by my own issues. First this is absolutley the correct directory to copy the mod to: '\Empyrion - Dedicated Server\steamapps\common\Empyrion - Dedicated Server\Content\Scenarios' My issue was that I was trying to change the scenario on an already existing save game. So once you boot the container the first time and allow it to download all the game files, you then need to turn the server back off and do the following: Navigate to "Empyrion - Dedicated Server\steamapps\common\Empyrion - Dedicated Server\Saves\Games" and rename 'DediGame' to 'DediGame.old' Copy the Scenario you subscribed to and downloaded using your client computer From: '\Steam\steamapps\workshop\content\383120\2550354956' To: '\Empyrion - Dedicated Server\steamapps\common\Empyrion - Dedicated Server\Content\Scenarios' Rename the folder '2550354956' to 'Reforged Eden' Modify the 'dedicated.yaml': Change the field 'Srv_Name' under Server Config from 'DediGame' to anything of your liking. changing the 'CustomScenario:' field from 'Default Multiplayer' to 'Reforged Eden' (Without the quotes) Power the server back on, this time it should load 'Reforged Eden' and create a new save game folder. This is what fixed it for me.

Hello fiR3W4LL, I am running the Empiryon docker container, and I am also interested in installing a scenario mod called 'Reforged Eden'. I have subscribed to the mod and downloaded the files on my game client and then tried to copy the files to the server in this location '\Empyrion - Dedicated Server\steamapps\common\Empyrion - Dedicated Server\Content\Scenarios' I then have modified the 'Dedicated.yaml' file with the new name 'Reforged Eden' for the scenario value. When the mod is installed on my client machine it installs it to '\Steam\steamapps\workshop\content\383120\2550354956' I am unsure where to copy the files and was wondering if you had any pointers or ideas on why it's having issues. Thanks!

Hey @JorgeB, Just want to say I was able to pop both of my previous 8TB drives back into my array, did what you suggested and it worked! I was able to restore my array, thanks a ton dude!

Thank you, i will do this and report back

The data on the array has changed. Could you help me by sharing the steps to put in my last drive so that I only loose the data that was on disk 7? Thanks!

Yes I do

Hi Jorgeb, unfortunately I can't, the array doesn't see the drive, it shows as missing. Basically the behavior I see by the drive is that it spins up, is seen by the bios in post but then becomes unresponsive when the os loads. Happens in windows too. I can see the disk in disk manager after I boot as uninitialized disk, but then I do a rescan, and It disappears.

Hello, Please forgive me I posted another post but deleted it thinking I had found the issue I had a drive fail on me lets call this (Drive B), while rebuilding parity on another drive (Drive A). Drive A was being rebuilt due to a size upgrade from 8tb to 14tb. I still have the old 8tb drive A. I would like to know the best way to fix my issue with as little data loss as possible. I am pretty much resigned to the fact that I am going to lose data. Thanks unraid-diagnostics-20210411-1008.zip

I pulled the drive from the array, and plugged it into a desktop, and it seems to spin up (for some reason the drive isn't being detected by the server) at this point I think that there is some other issue such as a cable or port problem and not actually a failed drive.

Hello, I replaced an 8TB Drive with a 14tb drive, and while rebuilding, a separate 14tb drive failed on me. I am pretty much resigned to the fact that I'm probably going to lose data, what would be the best steps to resolve this situation with as little data loss as possible? My hope is that I can put the 8TB i had back into the array, and use the drive I was going to use as an upgrade to now instead replace the newly failed 14tb drive, but im unsure if this is possible. Thank You unraid-diagnostics-20210411-1008.zip

Thank You, I ended up rolling back to a previous version and its working now. Must be an issue with the release.

Hi, After updating to 1.22.1.4228-724c56e62 I appear to be unable to play files in firefox or edge. I am able to navigate plex, and click into the info screens for items, but I cannot play an item. I click play and nothing happens. It looks like the browser registers the click but nothing changes. Chrome works just fine with no issues. I have tested on multiple computers. Any ideas, I have removed all ad blockers, and cleared my cookies, etc.

Hello, I am receiving the following error after updating the plex docker to the latest build after upgrading Unraid to 6.9.1. docker: Error response from daemon: Unknown runtime specified nvidia I am running the nvidia driver plugin Any assistance would be appreciated. EDIT: It looks like it was the driver version which was causing the issue. I downgraded the nvidia drivers back down to v455.45.01 and Plex is working again.

Hello Hoopster, Just want to close the loop and let you know that your advice absolutely worked, I have upgraded unraid to 6.9 and confirmed plex is working with hardware decoding after the upgrade. Huge Thank You 😀

Hello, I am a user of the Linuxserver.io Unraid Nvidia Plugin which now appears to have been deprecated and has a locked thread. I am currently on Unraid 6.8.3 From what I remember it was not safe to just apply an upgrade of Unraid while having this Plugin installed. You needed to make sure you updated the OS via the plugin with another Nvidia Unraid OS build, or use the plugin to revert to a non-nvidia os build of Unraid, prior to using the embeded "Update OS" option in the Unraid GUI. I would like to upgrade to the Nvidia Unraid build to 6.9, however my linuxserver.io Nvidia plugin seems to be broken. Can anyone share with me the proper way to go about upgrading to the Nvidia 6.9 build of Unraid OS.

Just want to give an update. After putting the 6TB back in, and rebuilding parity, i booted the array to maintenance mode, and ran an 'xfs_repair -n' I received a notice that the drive had valuable journal logs that need to be written back to the array and that I should try to mount the drive first. I tried and the drive would not mount. Therefore I ran an 'xfs_repair -L' and zeroed the log. I then was able to mount the drive, it doesn't look like i suffered any/much corruption. Once my array was healthy I then replaced the 6TB drive with a 14TB drive and it's rebuilding. As for my CPU temps. I took out the ol' air compressor w/ moisture trap and hit the fins with 120PSI this cleaned the heatsync honestly it wasn't that dusty (no build up between the fan and the fins) I think my heatsync just isn't really up to the task of properly cooling this CPU (it's a low profile noctua heatsync/fan) i will look into getting a beefier heatsync. Thanks for your help Johnnie Black, turl!

Ok, my problem has come back so let me try to explain in the best way possible to solve this issue. Originally: I had some issue which corrupted my filesystem on drive md19. I hadn't fully realized this and I pulled the drive to replace it with a larger drive. After this my array showed I lost a bunch of files. I stopped the rebuild, pulled the new drive (14tb) put the old drive back in (6tb), did a new config, and started the rebuild back. All my files suddenly returned that were lost on that drive. Now: My drive is rebuilding using the original drive(6TB) which was in md19. I checked my system and I now see that I have lost a bunch of files again. It looks like this is the culprit: May 22 06:39:46 Unraid kernel: XFS (md19): xfs_do_force_shutdown(0x8) called from line 439 of file fs/xfs/libxfs/xfs_defer.c. Return address = 00000000e39b5244 May 22 06:39:46 Unraid kernel: XFS (md19): Corruption of in-memory data detected. Shutting down filesystem May 22 06:39:46 Unraid kernel: XFS (md19): Please umount the filesystem and rectify the problem(s) My array is currently rebuilding parity. What is the best method to continue forward without losing my data? 1. Should I allow the array the time to finish rebuilding and then try an XFS repair? Currently if I look at MD19 it shows empty no files. But the array sees that it is full of data. or 2. Should I stop the array rebuild and try to run an XFS repair on an emulated disk? or 3. Should I stop the rebuild pull the drive, see if I can copy data off the drive using some sort of third party tool to pull the data? I know Tee-Tee Jorge said I should backup the data and format the drive, and I want to do what he says, but what's complicating things for me is the array rebuild. Other Questions: Why is Corruption of in-memory data happening? Looks like the answer to this is just XFS corruption, not RAM. Will the XFS corruption cause issues with the Array rebuild? My guess is no, since the parity is raw values? unraid-diagnostics-20200522-1305.zip

Ha Ha! Ive been around on the forums for a while. Not necessarily advanced in the Unraid Technical sense. Right now I have a minimum free setting of 15GB usually 20GB, what can I say, i trim it down when im running out of space to squeeze the most out of things as I can. Drives are expensive. However 20GB even 50GB in relation to a 14TB drive is going to show 100% full, when you've filled the drives up to that level. Currently the disk i have with the least amount of free space is 6GB.

Hello Constructor, What is the correct amount of capacity to have free to safely write to my array? Thanks

Hi Tee-Tee Jorge, Im NOT having corruption over and over on the same drive, it's been different drives every time. First it was my docker image on my cache drive. Then it was my cache drive running XFS. And now it says md19 is having this issue which is emulated and in the process of being rebuilt as we speak. I am receiving the following in my logs May 21 17:35:52 Unraid emhttpd: error: get_fs_sizes, 6412: Input/output error (5): statfs: /mnt/user/lost+found I have noticed I now have missing data from my array. You helped another user with these issues of which I appear to be having the exact same issues. I am going to put the old disk back in and perform a new config. I have attached my current logs for you to look over if you would look them over I would appreciate it as I don't know how to correctly determine what is happening. unraid-diagnostics-20200521-1739.zip