ZerkerEOD
-
Posts
50 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by ZerkerEOD
-
-
1 minute ago, primeval_god said:
Are you backing up your snapshots as well as you filesystem? You should probably just exclude your snapshots from your backup.
An I missing an option, the exclude that I see is only for the GUI. I don't see anything that excludes the backups from the snapshot.
-
I am having issues and broke my setup. I had flaws in it and using duplicacy to back up as it was creating excessive amount of storage. My 300 gig backups turned into 2TB because it was archiving everything due to the prefix changing file structure. Each backup had a YYYYMMDD style tag behind it. So now I am trying to only maintain 1 backup with the plugin and have everything backed up with duplicacy once a day that maintains version and revision control. So not instead of having 7 days of backups I changed it to 1.
That isn't working through, it creates a snapshot but then keeps telling me that it exists already, how can I have a static names backup file such as just appdata that is deleted and then created for the new one each time?
-
12 minutes ago, ich777 said:
I use most of the times nano or connect through SMB or SFTP to the server and change the necessary files with gedit <- but that would also work with the default Editor or Notepad++ (...and yes, I'm a pure Linux user <- Debian to be precise and even use to play games on it...
TBH I have Windows installed on a external drive too for VR and 3D modelling in Fusion 360).
My work laptop is straight Manjaro Linux and I love it. My desktop though will stay Windows for the sole fact of gaming until more games or all the games I want to play are compatible with Linux. My laptop will run Arch though I think, not sure just waiting to get it in first.
-
4 minutes ago, ich777 said:
What editor do you use to edit the files?
Please also make sure that the files stay on the cache and are not moved to the Array if you are using the path .../mnt/cache/appdata/...
Please also read this post for more information on the /mnt/cache path:
Other than that, on what Unraid version are you?
Sweet, I don't use my cache drive except to cache. I have a separate drive that I keep all my appdata on and I forgot to change the path. Changing the path to mine /mnt/user/appdata/palword fixed my issues. Looks like it was trying to find the file inside appdata but was looking on the cache drive which didn't have it. I am good to go now, I use VS Code, but if you know a way to open and edit ini files inside unraid I would love to know. Would make life way easier in the future to make quick updates.
-
Yes, I stop the container then I upload the new config (don't know of a way to update it inside unraid, then start the server again. It keeps telling me it can't find the config.
-
@ich777 I just installed the server and updated the settings in the /Pal/Saved/Config/LinuxServer/PalWorldSettings.ini and they are not being detected. Each time I start the server, it tells me my public IP isn't located in the ini and then gets it again and none of my changes such as server name and updated passwords work. Any tips?
-
On 12/11/2023 at 10:52 PM, Anon_me said:
I have a similar situation but uncertain if it's the same as yours @ZerkerEOD. Were you able to confirm if it was indeed 6.12 or if it was scrutiny? Also, when you downgraded did you go fully back to 6.11? I started fresh on 6.12 with my new build and it would be odd to have to go back to 6.11
Scrutiny was causing issues but I haven't restarted it since downgrading and upgrading again. I'm not sure how a fresh install handles it, I would assume it should have been fine but you can try downgrading and then upgrading again to see if it fixes it
-
Seems to be an issue with Unraid. I will keep an eye on it. I saw people mention that it was happening on 6.12 and a downgrade and upgrade fixed it for them. So I downgraded and then upgraded and it appears to be working right now. Why hasn't this been fixed? Also, it looks like Scrutiny app will keep them spun up as it is testing the devices. Turning it off helped.
-
Update, I think that my issue is Hardware related as I found a couple other posts saying that their HBA did not allow drive spin downs. I just bit the bullet and bought an LSI 9211-8i card which apparently comes highly recommended for way to much money and when it comes in later this week, I look forward to setting it up and seeing if that fixes my issue. I think it is hardware related though because I turned off Docker completely, VM's off completely and yet they still slowly started spinning up.
-
Help everyone, I'm going crazy here. I've tried looking online and saw to get the file activity plugin which would help me identify what keeps causing my disks to spin up. My server starts at using 200 Watts and I'm trying to find a way to cut it down, but with 8 or 9 drives it gets to be excessive power usage when most are not in use.
After downloading that I found a next cloud log on disk 7 and after some research find a way to fix it that didn't work, so while I try to figure that out I'm still trying to figure out why the rest of my drives spin up, so I turned next cloud off. Then I saw some with deluge due to a couple being moved from the cache to the array that were incomplete, but those were in disk 6 and 7. So I turned that off also and kept looking.
Now nothing shows up under the file activity, but I can watch all my drives slowly start back up over about a minute or two. I realized I had my data director setup with NFS and a proxmox server mounting the data share. So I disabled it also. But still all my drives slowly spin right back up after I do a force spin down. Any help would be greatly appreciated.
-
I thought that my docker image was corrupted last time and I deleted it and started new but it kept happening. If I reboot the server everything comes back perfectly even with an unclean shut down. It could be a ram issue but then I would expect that Proxmox would also have issues and it doesn't. I am virtualizing unraid on proxmox and have been for ever a year with no issues, the issues just started after about a month or two ago.
-
Hello all, I am having an issue and I can't figure it out. For some reason (this isn't the first time) my instance just decides it is done... I woke up this morning to an error and I am just able to get to it (emailed to me) that my docker file is unwritable and I couldn't access any of my docker instances. Come back and most of them are offline and I don't know why (I have auto update turned off for all dockers right now). The ones that showed online, I couldn't reach the web UI for any. Usually to fix this, I have to do a full reboot and most the time Unraid hangs and I have to do an unclean power down. I tried stopping docker and then restarting it and I get an error "Docker Service failed to start (Couldn't create socket: [2] No such file or directory." I uploaded the logs for before I do my reboot in hopes that someone could have some answers as to what is happening. I am sure it is something I am doing wrong or a setting that I might have over looked messing everything up but hope that someone more experienced can help me pin point what it is.
-
27 minutes ago, SimonF said:
Retention removes snaps. The function not implemented is to remove on a remote host of send was used. Maybe need to hide that field
What counts as a remote or local one then? I have mine set to a send location on another disk that is then backed up.
I have my settings to keep 7 days and remove snaps/sends local. I don't technically have a remote share, just another disk on the same system (which I may just get rid of because I can back it up from its current location just as easily). I originally started sending it locally because I had issues with the appdata and needed to recover a couple times and having it locally in a backup folder made it easier.
But I just removed about 50 that went into my Cache drive.
Also I just noticed that I had my domains set to send to cache/Backup and my system to do the same and only appdata is getting sent.
-
Does this still not have the ability to remove snaps on a schedule also? I am on the most up to date version it looks and it still says function not implemented.
-
@itimpi thanks again and really appreciate the help. I think I have most everything working. Looks like I might have lost some appdata file for PostgreSQL, but I am restoring from backup right now.
-
44 minutes ago, itimpi said:
What plugin?
It was for the mover tuning. But I think I have mostly figured out. Hopefully last question and I really appreciate all the help, what is say I did something stupid like copy from /mnt/user/appdata to /mnt/vmstorage/appdata. How would I fix individual files showing as both on vmstorage and on disk4 now?
-
1 hour ago, itimpi said:
That will always fail as /mnt/vmstorage/domains is part of /mnt/user/domains so you are telling Unraid to overwrite files with themselves. In fact in a worst case it will end up destroying the contents of the 'domains' share by truncating files to 0 length. You must never mix user shares and physical drives in the same command as it can cause data loss. If you must move files manually use the Dynamix File Manager as it will protect you against this doing this and getting data loss as a result.
You probably need to set the VM and Docker services to be disabled in settings to allow this share to be operated on by mover as is the case with the 'system' and 'appdata' shares.
They are still disabled. When I change the mover direction I lose the option of move now. How can I disable a plugin without uninstalling it?
-
18 minutes ago, itimpi said:
You need to set the pool as Primary storage (i.e. the location where new files get put) , and then the array as secondary storage. Then set the mover direction to be array->cache.
When I do that I can't run Mover on the share anymore. I also when trying to move files manually I get
mv /mnt/user/domains /mnt/vmstorage/domains mv: cannot remove '/mnt/user/domains/images/102': Directory not empty mv: cannot remove '/mnt/user/domains/images/103': Directory not empty mv: cannot remove '/mnt/user/domains/images/104': Directory not empty -
@itimpi I was able to finally get everything moved. I had to delete my snapshot directory because the snapshots were readonly. But I had them backed up offsite anyway. My issue now that I have the new drives in and everything is on the array, when I try to change the settings so that mover will move from array to vmstorage, the option isn't there. If I change Primary storage Array where everything is at, it won't let me select either my cache or vmstorage drives for secondary storage. So mover won't do anything. Do you know anything about this?
-
Just now, itimpi said:
That requires the docker and VM services to be disabled in Setting as they keep files open that will stop files being moved.
Both of them are disabled, I did that first because I wanted to move appdata. I have VM's on them that are off but they are managed through proxmox with the NFS connection (NFS is disabled now too). So VM is always off since I don't run VM's straight from unraid. Sounds like I will move each share manually until I see one that just freezes.
-
5 minutes ago, itimpi said:
The diagnostics shows that there IS a mover process running.
However it also shows that you are using the Mover Tuning plugin so you might want to try removing (or disabling) this in case it is causing problems in some way/
I disabled it after and it didn't do anything. I found another topic that told me how to stop mover. I already reenabled it, but I was able to start the mover on a single share. So I am going to manually start the mover from the share menu until I find which one was causing issue. Can the System share be moved or does that require any special methods?
-
I am at my wits end. I have been trying to run mover for a couple hours. I have disabled VM's and Docker and it wasn't moving stuff from the cache to the array. I upgraded to 6.12.3 and the same issues persists. I thought it could be because some of the shares have NFS attached so I disabled them. I rebooted a couple times. I also enabled the logging through scheduler (and unless I am missing other logs) there are no errors. I made all my shares yes:cache or yes:vmstorage trying to move them off of them so that I can swap out the NVMe drives with new ones, but they won't move.
Just to add with the new version under share it sows everything should move to the array but nothing is moving. I see where mover starts and every hour mover tries to start again and says that it is already running but it isn't. All my drives spin down after so long and I have forced them back on a couple times.
Diagnostics attached and I hope someone can help out.
-
3 minutes ago, jj9987 said:
Postgres doesn't change the permissions, unless it is run the first time (when it needs to initialize the data directory) even then it sets them to 775. 600 might not be enough for PostgreSQL data directory anyway.
https://github.com/docker-library/postgres/blob/master/14/bullseye/docker-entrypoint.sh
The owner can be unknown, because it is configured for the user ID that Postgres image runs as within the container. Just because host doesn't know the UID, doesn't mean it's broken. But it needs to match the userID, that the postgres process in Docker runs as.
PUID and PGID don't do anything, they are specific to Linuxserver images, not Docker in general.It feels like something else is changing the permissions.
It was the docker container or some process with the container. I removed the container completely and brought it back and it did it. I could change my permissions to 777 owner nobody:users and it would stay that was for hours until I manually started the postgresql container, then it instantly failed and the permissions were changed and the owner was unknown and the docker image refused to fully start up and would crash and burn. Looks like I found some other issue that the postgresql appdata CANNOT run from a user share even if it is set to only use a specific drive. Changed the mount point from /mnt/user/appdata/postgresql to /mnt/vmstorage/appdata/postgresql and it booted right up. Something about how unraid handles the file system and postgresql docker image not playing nice. Not sure why it ran for months without issue and then nothing but issues, but oh well.
-
1
-
-
On 11/8/2021 at 9:05 PM, Jase said:
Hi, I too have just stumbled across this permission issue. When the docker container is restarted, the 'postgres' app data folder loses the correct permissions. I'm able to correct this by running chmod -R u-x,go-rwx,go+u,ugo+X '/mnt/user/appdata/postgres' then chown -R nobody:users '/mnt/user/appdata/postgres' but after I restart the container, the permissions are gone. Any help would be appreciated as this was not an issue before.
Did you get this fixed by chance? This is happening to me every time my container tries to start and then it crashes.
TBH I have Windows installed on a external drive too for VR and 3D modelling in Fusion 360).
[Support] ich777 - Gameserver Dockers
in Docker Containers
Posted
What are the "Game parameters" used for in the Enshroud server. I can't really find anything about it