Kokopelli13

Thanks for letting me know, I'll give it a go with the beta later!

Unraid 6.8.3 Hello, I have been running my unraid server on a i5-9400 with a B365M Pro4 for a while now with no issues. I recently got my hands on a 10900 (non k) to play around with and thought I might try it in my unraid server, so I installed it with a H470M Pro4. Strangely it seems as though the NIC is nowhere to be found in unraid. I have double checked the BIOS and the adapter is definitely turned on. I even did a BIOS network update so I know it's working. It also appears to be the same NIC used on the B365M board I was using before, so I'm hesitant to believe that it's a driver issue. Wondering if it might be some strange incompatibility issues I installed a fresh copy of unraid onto a flash drive only to be met with the same problem. I have looked through the diagnostics myself but can't find anything noteworthy. Attached below is the diagnostics. Hopefully someone with more experience and knowledge than myself might be able to see or suggest something I haven't thought of. Cheers EDIT: My friend suggested seeing if it showed up in lspci and indeed it does. I don't know why it's not getting configured in unraid but if anyone knows how I could go about doing that I'd appreciate it tower-diagnostics-20200611-0235.zip

Hello, Yesterday the power at my house went down and unfortunately I do not have a UPS setup yet (it was on my list...but now I'm going to get one today). At the time sabnzbd was downloading a file and so the shutdown occurred during a disk write. Upon restart unraid started a parity check and has since finished finding 4773 sync errors. I have read through similar threads and it is my understanding (correct me if I am wrong) that you cannot exactly tell whether the parity itself is incorrect or the data that was being written was corrupted as a result. The parity check itself was non correcting so I need to correct this somehow. I believe because of the nature of NZBs being multipart rar files that if the data itself is corrupt sabnzbd should see this when I restart it as it attempts to finish downloading/extracting the file-- although I don't know if the shutdown could have affected other files in the process. I wanted to ask some people who know more than me what the proper course of action would be in this case before I run a correcting parity check. Is it possible to see exactly what data/file the errors are located in, because if so it would not be a problem to reacquire them. I have attached the diagnostics here mercury-diagnostics-20190118-1702.zip. Please let me know if you have any suggestions, thank you!

Thanks I really appreciate it, I will definitely make a new post when there is an update. Also that sounds like good idea with the notifications..l probably set them up to go to my phone. I changed the schedule to monthly and nothing has happened yet, so fingers crossed it sticks this time.

If anyone has any ideas it would be greatly appreciated... it just started another parity check last night.

Hello, I've recently been setting up my new unRAID server and at the moment I have the parity check scheduled for every week on Sunday at 12:30am (00:30). It does trigger correctly on sundays and start the parity check, however a couple of times it has seemingly started out of nowhere on the wrong day. Today I got on to check and noticed a parity check was running and upon further inspection it appears to have started at 12:30am this past night, a Tuesday. Thinking back I believe the rouge parity checks also started late at night and I'm thinking they most likely followed this pattern. Does anyone know why this might be happening? Or perhaps it is a bug? Thanks Edit: So I let the parity check finish and it reported that it was successful with no errors. Just a few minutes ago I restarted the server for an unrelated reason but now it is saying the last check was incomplete... interesting.. Edit2: added unRAID version to title and uploaded diagnostics mercury-diagnostics-20181023-2319.zip Just updated to 6.6.3, I'll see if that fixes it

Teracopy looks like a great upgrade from the windows copy utility-- I will also check out Midnight Commander. To copy the files directly I imagine that I should just disable to cache for the share while I complete the transfer, unless there is a more elegant way? Anyways thank you for the help!

Hello, I'm just getting started with unRAID so please forgive me. I recently set up my server with 3 8TB drives and a 250GB cache SSD and just started to transfer my media collection from my computer. There are a lot of big files-- 4K remuxes upwards of 90GB each. Initially I had windows telling me that there wasn't enough free space so I did a little googling and concluded that I needed to change the min space available on my cache drive to be larger than my largest file. After changing it and running the mover just to be sure, I copied over some more files without any trouble. However I just started copying a new batch and am getting the same error from windows. I can click "try again" and the transfer continues, but then it seems to just pop up again later. Am I doing something wrong, or missing a clue? If you have any advice it would be much appreciated. Cheers. Edit: I just noticed that unRAID is giving me cache utilization warnings in conjunction with this. Could the mover not be clearing the cache fast enough?

If I use both sabnzbd and deluge, is the best solution to let each connect to my VPN independently (two different connections)? In this case I would just use Privoxy on one of them and then point sonarr/radarr to that? Apologies if this has been asked before I wasn't able to find an answer