wherzwaldo93

Unfortunately, I did not. Now that it's been more than a year since posting this, my guess would be to make a User Script that runs on every startup?

I was using my server and some of the docker containers weren't working correctly and had a hard time accessing the server in general. I ended up having to do a restart of the server, after which it resumed working normally to my knowledge. I'm not sure why this error came up because I should have plenty of RAM for my usage. Any help would be appreciated. origin-diagnostics-20230312-1740.zip

This solved my issue completely, thanks!

I did some research on how to create permanent aliases, as typing "ls -l" etc. every time is getting annoying. I researched the topic and made a txt file which I referenced in the go file. However, I couldn't get this to work on startup. Is there a way to do this?

I've gone through many forums to get qBittorrent set up correctly with nordVPN. I've checked and qBittorrent is using the same IP that nordVPN is using/setting. Great. I've also configured qBit to have its TCP and UDP ports controlled by nordVPN, but I believe this is may be where my problem is? My downloads start for about a second or two and seems like it finds seeders and peers and status will be "Downloading", but after that second or two the status is "Errored". Also checked nzbget and it's not downloading nzb file. container overview: nordVPN configuration template: nzbget error messages:

I've gone through many forums to get qBittorrent set up correctly with nordVPN. I've checked and qBittorrent is using the same IP that nordVPN is using/setting. Great. I've also configured qBit to have its TCP and UDP ports controlled by nordVPN, but I believe this is may be where my problem is? My downloads start for about a second or two and seems like it finds seeders and peers and status will be "Downloading", but after that second or two the status is "Errored". Also checked nzbget and it's not downloading nzb file. container overview: nordVPN configuration template: nzbget error messages:

Currently going through this process and tried everything I found in many different forums but nothing seems to work. Finally have qBit passed through nordVPN and can even get the UI to open now, but all downloads error out at start.

(Maybe needed) Context: I accidentally pulled out my parity at some point while my array was still on... which I'm sure is very bad. I was going through and turned the array off and on a couple times to play with to do this and forgot to turn it off before taking it out once unfortunately. The parity drive was disabled and I had to reboot, restart the array, and rebuild the parity drive to get it enabled again. Upon rebuilding the parity drive, I got the Machine Check Event error. Is this because I took out the hardware while the array was still on? origin-diagnostics-20221002-1211.zip

Thanks a ton, that worked. Oh damn I guess it's good I'm moving the data then. On a similar note, I thought a major benefit of having a cache pool was to facilitate faster transfers of data? Yet, all the forum posts that I read about large/fast transfers of data instruct turning cache setting to no. Why is this?

I was transferring data from an external hdd to a share I created using sonarr preferred formatting: /mnt/user/data/media/... At some point, the data transfer grinded to a halt around 7mbps and was stuck around that. I left it like that for a couple days but read about ways to optimize this speed and saw a couple that I implemented... while the transfer was still taking place. Bad move. I turned share settings from cache prefer to cache no and changed disk setting tunable (write_md_method) from auto to reconstruct write. I believe it was when I changed the cache setting that the move of data stopped with error, and the entire user directory is now gone including all the shares that were there within. I'm brand new to unraid so apologies if I'm not explaining this well. Any help understanding what happened or how to remedy this problem would be extremely apprciated. origin-diagnostics-20221001-0213.zip