noraa

@QuarantineDrive Sorry I am just seeing this as I actually just started to get them again... I am not entirely sure what is causing them either 😧, I had swapped the cables and everything has been fine for 2+ months and now all of a sudden they are back. I am again worried about losing data and wondering if I should just get rid of the drive at this point. I really am stuck on what to do here haha.. I am curious though, have you found a solution to the problem? Would really appreciate it if you could share the solution if so. Sorry again for not seeing this reply originally 😧

Ok I think I am going to try to swap the cables positions and if the errors come up on the drives that I swapped to its safe to say its a cable issue? The errors are back again (on the same drives) and seem to be climbing slowly. Checked syslog and there is this, but don't think it really tells me anything I didn't already know. md: disk4 read error, sector=4571643616 I don't have a spare PSU at the moment, although if I suspect that is the issue I have no problems grabbing a new one, just don't want to lose any data. Thank you for the suggestions JorgeB, I appreciate it!

Hmm ok, what would be the best way to diagnose a power problem? I haven't made any changes to my setup. although I assume the power supply could be going bad or something along those lines? not too sure. I took out my GPU a few months ago and installed the MediaSonic Probox with an eSata card, I doubt that's causing any issues as the drives are powered by the Probox and the impacted drives aren't in the Probox, but thought I'd mention it. I was thinking about running xfs_repair on the impacted drives and seeing what it returns but not too sure if that is worth doing or not, Pretty lost at this point haha.. Thank you for the help JorgeB, I appreciate it!

Hello JorgeB, So the UDMA CRC errors as far as I know were caused by a faulty SFF -> SATA Cable, I had picked up an HBA a couple years ago now I wanna say and one of the cables I had grabbed wasn't working properly and would spit out the UDMA errors. I replaced the cable back then and as far as I know, the errors haven't gone up. I have been keeping an eye on the numbers as well. I can try replacing the cable and see if that solves the issue if you suspect that it is causing the issues, Just thought i'd mention that I did in fact have issues with the cable at one point but replaced it back when I first installed the HBA. Thanks again!

Hello as the title says, I am wondering / worried that I have some discs that are corrupt / failing in my array. The following errors are the ones in question. Aug 23 16:04:55 Tower kernel: I/O error, dev sdc, sector 406173464 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 And Aug 27 14:16:53 Tower kernel: I/O error, dev sdb, sector 1169562704 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 2 I ran a SMART extended test on /dev/sdc and it completed with no errors, although these errors keep appearing. Not too sure what additional information is required. I have attached my diagnostics as well. I appreciate any help / feedback. Thank you! tower-diagnostics-20240827-1850.zip

Not too sure if anyone else is having this issue however, the broadcast command for RCON seems to not be working.. I am able to do everything else (save, showplayers, info etc) with no issues but am getting an "unknown command" return when trying to broadcast a message using "timeout 1 rcon -a 192.168.20.5:25576 -p password broadcast Saving..." Any help would be greatly appreciated i'm sure it is something silly. Thanks in advance.

Possibly NAT Reflection? I am not 100% sure tho and am just spitballing but it could be you don't have it enabled for Port Forwarding under Firewall->NAT (At least on OPNSense). However, If you have other stuff forwarded with no issues then I am very wrong. Good luck!

Here you are sorry about that, I deleted all folders except Pal and started the container up and it is running v0.1.4.0 now. Any reason you suggest to skip pi hole for unraid? i’ve never had any issues with it but if it is known to cause issues then i’ll gladly disable it. Thanks for your help!

Hey thanks for the fast reply! I ran the above command and attached what it returned. I do have PiHole running i’ll watch the logs to see if it’s blocking anything. Thanks again Edit - Deleted everything but Backups and Pal folder, everything updated and seems to be good now. I would like to update the container properly by restarting it but I’m really not sure what the issue could be.

Hello, I am having issues trying to update the server to the latest version. Currently I've tried restarting the container, deleting steamapps folder as well as restarting without my steam credentials. None of which seemed to work Here is a screenshot of my paths if that helps at all, any help would be appreciated. Thank you!

I am stuck on getting RCON enabled even with the steps above, I haven't touched the default template at all, I have enabled RCON in my config etc. and typing rcon -H machine ip -P 25575 -p password doesn't work it just hangs. Just wondering if there is a step I am missing? Will provide whatever info is needed. Thanks in advance.

So I put a file container the folders / paths I would like to exclude from the 'Mover' process My ignore-files.txt is located in '/mnt/user/backups/' inside of the file I have the directories / folders listed like so /mnt/cache_downloads/data/usenet /mnt/cache_downloads/data/usenet/incomplete and so on, unfortunately it doesn't seem to be working, any help would be greatly appreciated. Thank you! Attached picture of my 'Mover' Settings.

As the title says I am having issues with my Plex docker container, I checked the logs and I get the error "Connection timed out" multiple times, and the media then becomes unavailable on Plex until the container is Restarted. I post.d another issue I am having over in the General Forums, where none of my container are pulling updates. I am not too sure if the 2 are related, Plex works perfectly fine once the container restarted, until the error happens again which at least once a day at this point. Any help would be greatly appreciated. Thank you!

Hey, I used to run this Docker with no issues but have recently re-installed it and am getting the following error "No profiles are available; check internet connectivity and refresh the profile list." I do have a pfsense Box but can't seem to find any information on why it wouldn't work? I have tried updated the WebUI and re installing the Node packages etc. Any help would be appreciated, thank you!

I am also getting this error. I have disabled my autodl for now. I think the git repo might have changed their URL?, not too sure but I think this is an issue with autodl in general not just you or your setup but I am talking out of pure speculation.