Andrewj0813

yep I also missed that dashes were necessary, I think after the changes you just merged from me the issue should be fixed for everyone. I'll create a new server tomorrow from the unraid UI just to be sure everything's working correctly. Thanks for merging in those PRs so quickly.

Running into the same issue seems like the startup script is overwriting it with a blank file, doesn't happen to the whitelist though oddly enough. I can't even manually edit the ops.json because it gets overwritten. [21:11:24] [Server thread/INFO] [minecraft/DedicatedServer]: Starting minecraft server version 1.21.1 [21:11:24] [Server thread/INFO] [minecraft/DedicatedServer]: Loading properties [21:11:24] [Server thread/INFO] [minecraft/DedicatedServer]: Default game type: SURVIVAL [21:11:24] [Server thread/INFO] [minecraft/MinecraftServer]: Generating keypair [21:11:24] [Server thread/INFO] [minecraft/DedicatedServer]: Starting Minecraft server on *:25565 [21:11:24] [Server thread/INFO] [minecraft/ServerConnectionListener]: Using epoll channel type After watching the files and the server booting up its happening right after the server itself boots up after all the neoforge loading I think. After a bit more investigating I figured out the issue I think, You're not adding "bypassesPlayerLimit": false to the ops.json file which I think is required now. The server overwrites the file if it isn't there. I made a PR to update your launch.sh command to add this.

UUID: 0cdbaac7-0611-4b09-844d-2f02f46768a0 Scrub started: Fri Aug 11 10:40:31 2023 Status: finished Duration: 0:08:08 Total to scrub: 1.51TiB Rate: 3.17GiB/s Error summary: no errors found Here's a recent scrub. I'm not surprised it hasn't shown any errors I ran a scrub and repair before I shut down for the memtest (which passed atleast after 1 run) I'll keep an eye on the server today. I've installed the script you recommended and I'll update the post if anything happens.

I've noticed this in the drive's smart report. Is this not an issue? Error Information (NVMe Log 0x01, 16 of 63 entries) Num ErrCount SQId CmdId Status PELoc LBA NSID VS 0 2279 0 0x500a 0x4004 0x028 0 0 -

I've run a scrub a few times now and the issue keeps popping up, I'm currently running memtest on the server so I can't run a new scrub at the moment.

Hi I'm getting a lot of errors in my nvme cache pool. Is one of my drives failing? The errors seem isolated to just one drive. I saw this could be a ram issue elsewhere in forums but I would've thought if it was ram I would be seeing errors from both drives. The offending drive is nvme1 the Seagate Firecuda tower-diagnostics-20230811-0105.zip