Spirevipp

well, i solved it myself....... in the go file i had a custom line to download a custom version of runc for a binhex container... Binhex documentation - github - Scroll down to the bottom of the file curl -o '/usr/bin/runc' -L 'https://github.com/binhex/arch-packages/raw/master/static/x86-64/runc/runc' && chmod +x '/usr/bin/runc' I think i had to add this for some of his containers to work this spring. modified date of the file is back in april this year. removing the line solved everything, the fault had nothing to do with anything in original post.

TLDR: I filled the cache drive 100% when transferring files, ran mover and finished the transfer. after this i did a server reboot as a new docker container would not start. Now none of the containers will start, error OCI runtime create failed (the docker service starts with no errors). Hi, I was transferring some large backup files to a backup share on my server from windows using robocopy. The backup share is set to use cache. I underestimated the size of the files, and this ended with the cache folder getting 100% filled. While this was transferring in the background, i added a new docker container (adguard-home). This new docker container would not start. Note, this container was added while there was at least 100GB free space on the cache drive. I noticed after a while that the cache drive was completely filled, and a few containers had stopped. I then stopped the transfer, ran mover to free up space on cache, and then resumed the transfer. when it was done transferring i ran mover again (yes, i know), then i did a server restart since some containers had stopped and wouldnt start. (adguard-home, overseerr and organizr) After the reboot then none of my containers will start, they all print the same error to log (this is for duckdns): time="2021-10-27T12:45:08.635963389+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2021-10-27T12:45:08.635966512+02:00" level=error msg="stream copy error: reading from a closed fifo" time="2021-10-27T12:45:08.800240194+02:00" level=error msg="04bc6832995f19f166b0652050b9d53ccf603d5bb486a9e111b1ee0e36dee5fa cleanup: failed to delete container from containerd: no such container" time="2021-10-27T12:45:08.800261780+02:00" level=error msg="Handler for POST /v1.41/containers/duckdns/start returned error: OCI runtime create failed: unable to retrieve OCI runtime error (open /var/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/04bc6832995f19f166b0652050b9d53ccf603d5bb486a9e111b1ee0e36dee5fa/log.json: no such file or directory): fork/exec /usr/bin/runc: exec format error: unknown" I searched google, and found a forum thread for an nvidia hardware container (container using nvidia hardware, idunno how to say it) where they got this error after a driver update. the nvidia driver plugin was set to download latest driver, and a new driver was released recently so i tried downgrading, but no luck. This is as far as i have come. I have attached the diagnostics archive, i unfortunately dont have any logs from before i did the first restart (that i know of, maybe they get saved somewhere?) Forgive any weird english, its not my native language. Thank you for any input and help Spirevipp spiretower-diagnostics-20211027-1254.zip

Just FYI, from what i have read and heard, minecraft 1.17 will require Java 16, starting with snapshot 21W19A.

Hey all, I just put together a server for use with Unraid. I installed unraid 6.9.0rc2 in uefi mode, with bios configured for uefi. The reason i chose this version is for the nvidia driver for hw transcode in plex container. It recognizes the usb, and boots unraid, until it hard locks during boot. The last line on screen is: pcieport 0000:05:05.0: can't change power state from D3cold to D0 (config space inaccessible) Attached image of screen. After this nothing happens. I have tried enabling and disabling pcie power saving feature, and switching from uefi to legacy (and re creating the usb for legacy install) Is there any way for me to enable logging? i think it might be a misconfigured bios, so i will try to reset to defaults after posting this, and will update if anything changes. Specs: mobo: AsRock z97 Extreme 6 (no wifi) asrock website: https://www.asrock.com/mb/Intel/Z97 Extreme6/#Support cpu: i7 4790k ram: 32GB hyperx memory gpu: zotac 1060 3gb only gonna be used for hw transcode for plex / handbrake ssd: Kingston 500gb for cache drive hdd: 4x seagate 4tb drives usb: sandisk 16gb usb 3.0 drive bd-drive: asus bw-16d1ht psu: corsair rm750x gpu is in topmost pcie slot. I initially had the monitor connected to the gpu, but i also tried connecting directly to the mobo igpu (also enabling igpu in bios and setting it to primary) cpu, ram and mobo is leftovers from an upgrade to my main rig. Additional info, i used the gpu in another test install on an old asus mobo with an fx8350 cpu. I had no boot issues there, and the nvidia driver also worked fine. Thank you for any input! Spirevipp UPDATE! I disconnected the bluray writer, and now the server boots. Do you know if this bluray writer model is incompatible somehow? link to asus website: https://www.asus.com/us/Optical-Drives-Storage/BW16D1HT/ The drive is connected to the SATA3_A1_A2 sata ports, page 8 (14) in user manual. This is a shared port with the m.2 slot. Could this be the problem? I will try to set it to force sata to see if that helps. Update 2: I tried to force sata mode, and also swap to the SATA3_A3_A4 port, but still the same. But when i connected to another sata port used by a disk drive SATA5 then it worked. From my testing it seems to be some sort of conflict between the asmedia sata controller and the unraid kernel, any debugging or more testing for this is out of my technical skill level. Last test im doing is connecting a drive to the asmedia sata ports to see if its just the bd drive or all sata devices. From testing, it seems like the disk is recognized. I used the ssd. This might be an incompatibility between asus bd writer and the asmedia sata controller, not related to unraid at all. For now i will just connect them this way. If anyone want to follow up on this, please reply. I will be testing and playing around with this server in the coming week, and will be able to assist if anyone wants to fix this issue.