DogeKitteh007
-
Posts
45 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by DogeKitteh007
-
-
13 minutes ago, itimpi said:
Have you checked Settings->Global Share settings that you have not limited which drives can be part of User Shares?
You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.
Well, you gave me the exact feedback that was needed, so why bother? j/k
I'll remember that if there's a next time. Thanks a lot! Hero of the day!
-
For some reason the newest disk I installed doesn't seem to have been included in the array (Disk 12).
It shows up as a separate disk share, but it's not possible to include it in any of my other shares.
Would I need to do a new config to get it fixed?
-
4 minutes ago, ich777 said:
From what I know it is and back when I created the container it was working fine, it is also in the description from the container:
Yes, because the name in the Docker template overrides the config file.
Shows what I know. Thanks for taking the time to reply.
Some friends wanted a server they could play on asap because of the new update.
-
1
-
-
How can I set a password for the V Rising server?
The file ServerHostSettings.json in save-data/Settings doesn't seem to be it, as the world name doesn't
correspond to the one set in the docker.
I've tried searching for it in this topic, as I guess the question must have been asked before, but didn't find it.
Thanks again for making these fantastic templates!
-
There seems to be a version mismatch between what it says in the changelog and version in the interface.
See attached screenshots:
-
20 minutes ago, JorgeB said:
Thanks! It wasn't added to Unraid OS GUI Mode.
Booted it in GUI mode last time, so there was the issue. Thanks again @JorgeB
-
1
-
-
Noticed I had errors on the server when /var/log turned out to be 100% full.
Wonder if this could be the ol' Areca Raid controller that needs to be retired or something else.
Disks connected to the card are configured as JBOD.
Any advice on what I should do to avoid loss of data?
Diagnostics attached. Thanks in advance.
-
9 hours ago, JorgeB said:
Cache should mount normally after a reboot, backup anything you need, not sure re-formatting will help for this, but it won't hurt.
I ended up just deleting the docker.img and ran a scrub on the cache drive afterwards. It didn't find any errors.
After that I let the CA Backup / Restore Appdata plugin do it's thing and restarted docker.
Seems to be working fine again now.
-
1
-
-
5 hours ago, JorgeB said:
Jul 26 12:51:19 unraid kernel: BTRFS error (device nvme0n1p1): block=230151340032 write time tree block corruption detectedBtrfs went read only because it detected corruption before writing the data to the device, this is usually bad RAM or something else causing kernel memory corruption.
P.S. also saw some macvlan call traces, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right))
16 hours ago, trurl said:Both docker.img and cache are readonly due to corruption. You can recreate docker.img after you fix cache. You may have to copy what you can from cache and reformat it.
Have you done memtest recently?
Wonder what could be causing this.
The RAM checked out fine and everything is running stock speeds.
Cache disk also seemed to be ok.
I like it better if a specific component just dies. At least then I know what the cause is! 😅
So, in conclusion:
- Copy what I can from cache drive if it is accessible after startup (appdata is most important here)
- Recreate docker.img on a separate ssd this time
- Reformat cache drive(?) and try using the same drive since the hw-tests came out OK
- Switch to ipvlan (thanks @JorgeB)
-
Update:
I've done two full rounds of memtest. Result: PASS
Run all basic tests on the nvme-drive in question with Seatools X. Result: PASS
What could be the reason behind this corruption and do you have any advice on how to proceed from here?
-
Had to download the latest image from memtest86+ and make a USB.
I'll leave it on and check on it later tonight.
For some reason, every time I selected the MemTest option in the unRaid menu, it just rebooted and I was right back where I started.
Thank you for taking the time, @trurl. 👍
-
2 minutes ago, trurl said:
Both docker.img and cache are readonly due to corruption. You can recreate docker.img after you fix cache. You may have to copy what you can from cache and reformat it.
Have you done memtest recently?
No, I'm afraid not.
I was just about to RMA the drive, but I'll see about forcing a reboot and doing that memtest instead.
Don't have ECC-memory on the server unfortunately.
-
Some extra info: I noticed it because suddenly none of my dockers were responding, and in the logs it said there was corruption in the image.
Sorry about not posting the complete diagnostics btw.
-
Just now, trurl said:
attach diagnostics to your NEXT post in this thread
-
Hello,
I haven't rebooted the server yet, but it seems to be stuck on "Array Stopping•Retry unmounting disk share(s)..." when attempting to stop the array.
Could be I have a dead nvme drive on my hands?
Seems like unraid is having a hard time getting it to respond.
Attached syslog and docker logfiles.
-
2 hours ago, rikki said:
am getting the same any one have any advice
On 7/19/2021 at 8:15 PM, tomwhi said:OH MY GOSH - I've just worked out why my Home Assistant couldn't talk to my Phoscon/Deconz app.... They weren't on the same docker network... DOH!!
My HA was on "host" because there was too many ports to map across, and my Phoscon was on br0 (also as shown in SIO's instructions but made the most sense because it needs it's own IP for things to find it on tcp/80 and tcp/443.
I found out by going into the console of the HA container and trying to ping my Phoscon IP - it failed! So the "Api key couldn't not be whatever" is utter bullsh!t from an error message.
I also realised it couldn't talk to Pi-hole (which I was less worried about, but equally as annoyed with not working) - and for anyone else who lives and breaths the SIO videos - it's also on br0!!
So once my HA was moved onto the br0 network everything worked - well - not everything, now it can't talk to the host, so I can't get Sonnar or Raddar data into my HA setup but that really is the lowest of the low priorities and now I've worked this out I'll try and work out how to get it talking to both br0 and host networks.
Tried this solution?
-
1 hour ago, rikki said:
am getting the same any one have any advice
No issues like that on my setup.
Docker images:
Homeassistant (linuxservers image) br0 with fixed IP
deconz (SpaceInvaderOne image) br0 with fixed IP
-
On 6/9/2022 at 7:19 PM, Mustard_Tiger said:
I'm having similar issues connecting my Conbee II into the HA integrations, I'm still getting the error - "Couldn't get an API key", this is after pressing authenticate app button within the Phoscon app. Deconz recognizes my host address but that's about as far as I can get. I suspect it's something to do with how my containers are configured on the network. I have tried changing the networks within each container, HA or Deconz but with some options I cannot access the webui to complete the integration. Hope this makes sense.
Any help would be greatly appreciated 👍
Have you fixed the issue?
-
@SpaceInvaderOne
As I'm posting this question I would like to take the opportunity to thank you for your excellent tutorials on Youtube!
Learnt a lot about unraid, VM's and Docker from those. Also like your chill way of presenting stuff.I hope you keep making content for many many years to come. You rock, sir!
Now, as for my question/request. 😄
Would it be possible to update this docker image? I believe the current version of deconz is 2.17.01, but this docker image is running 2.13.01?Thank you again.
-J
-
3 hours ago, SimonF said:
Have a look at this thread for solution to pci errors
Thank you for linking this!
-
1 hour ago, DogeKitteh007 said:
Also: Does the order matter when assigning the drives with files on them?
I'm blind.
"You can (optionally) re-order the data drives at this point but be aware this will always invalidate parity2"
Thanks for your help. I'll probably mark this as solved soon. 👍
-
Did some homework on the forums and found the relevant guide. 😊
I haven't tried to mount any disks in read-only mode with the Unassigned Devices Plugin yet, but can I assume that the one in the image is the parity drive?
Also: Does the order matter when assigning the drives with files on them?
-
Hm, everything seems to work with the newly made flash drive.
Apart from the error about PCI device spamming the logs that is.
I think it's the onboard SATA-controller? Was there before installing the Areca card too.
Installed the Areca controller card and the Dynamix SCSI plugin.
All the drives show up and SMART-status shows as "passed" on all of them in Unraid GUI.Looks ok in the Areca UI as well.
Assuming that the problem somehow happened when updating unraid on the other flashdrive.
However.. how do I go about restoring the array now? I do have access to the old unraid flashdrive and its files.
I don't have a picture or anything showing the assignments of each harddrive, unfortunately.
Guess I also need to get a hold of Limetech to register this flashdrive on the Pro licence instead.
Attached: Diagnostics with all hardware connected running 6.10.3 w/SCSI plugin
-
Updated unraid on the eval flash drive to latest version 6.10.3.
Diagnostics so far attached.
I'm going to try adding the controller card again so that all drives are connected.
[Support] ich777 - Gameserver Dockers
in Docker Containers
Posted · Edited by DogeKitteh007
Added image of attempt to add variables
First of all, thank you for the awesome docker containers!
How would I best add these variables, so that I can install the public test of Ashlands?
I tried adding the variables like in the attached image, but no luck.
Edit:
Solution: put "-beta public-test -betapassword yesimadebackups" (without quotes) in the GAME_ID field after the numbers.
Also added the environment variable PUBLIC_TEST=true, but don't know if that is necessary.
@ich777