Joop

Just wanted to double check the next steps I start by unassigning the data drive. Shutdown and replace the drive. Start Unraid, preclear and assign the new drive to the parity slot. Assign the old parity drive to the data drives slot that is currently in a disable state This should show blue indicators and a copy buttons should become visible. Once the new parity drive is in place i can repeat the process for the data drive? Unassign, shutdown, replace, start and assign in order for it to rebuild?

Hello all, I've been getting a read error on 1 of my Data Disks. On all 3 drives (Parity + 2 Data) an extended SMART test has been preformed and both Parity and Data disks show the read error. The data disk is currently in a disabled state and the other passed the test and is operational. There are also 3 cache drives which don't present any error. Important data has been backup to another system and i've ordered 2 replacement disks. Now my questions is if this is a failing drive or potentially false positive due to bad cables. Hoping someone can point me in the right direction as i want to start replacing the bad disk today but not sure if it will work when the parity drive throws in a read error. Is the read error on the parity drive coming from the disabled disk or is that disk also dying. And if so how would i recover the data when the parity drive is also dying. Should i be follow the guide below to start the rebuild of the potentially dying drive or are the other steps i should take first. Data Recovery Attached is the syslog and SMART results of the 3 drives. Thanks for having a look at my issue. syslog.txt ST4000LM024-2AN17V_WCK4KPLE-20230209-1212 parity (sdb).txt ST4000LM024-2AN17V_WFF16ZDR-20230209-1212 disk1 (sdc) - DISK_DSBL.txt ST4000LM024-2AN17V_WFF17DZJ-20230209-1212 disk2 (sdd).txt

Just made another one fresh and all is good now :P. No idea what caused the issue because it is basically the same. Kept the folder but removed and readded the docker seemed to solve the issue. Thanks for thinking and sharing your info. Really appreaciate all of your work that you have been doing. Keep it up, my guys are enjoying your work

As i mentioned before i tried searching in steam on all 3 ports. No response on any, and also tried local IP which gave the same results. In the docker area you change the GAME_PORT to what i want to use2466. You remove the current UDP entry and add in a new Port Entry correct? And i add it in like below? 2466-2468 on both sides.

No i was not able to find it in the list, the old one that is running default is appearing in the list. When searching for myip:port, tried 2466-2467-2468 but none of these come back as responding. And ingame i can't find it except the original game on the standard ports. Router ports

It should be up for an hour or so but still doesn't show up. Normally when i reboot the server that is working it appears within 5 minutes. Feels like i'm either missing something or the Docker is not using the given ports.

I've tried the above by changing the GamePort to 2466 and removed and created a new line for UDP 2466-2468. Opened the port on the router but it doesn't appear in the server list. Both ingame and steam. Any other tips i could try?

I would love to add rocket.chat to the reverse proxy of linuxserver.io The certificate is in there but i haven't figured out to add rocket.chat to it. Anyone had any luck setting that up?

I can't seem to get https to work for OwnCloud. Do you have any guidance or instruction on how to get it running?