DirtyDarrell

In order to shutdown the array cleanly, you have to stop the array first, and then hit power down. I had an issue similar to this a couple versions back where my server was also doing the automatic parity checks after I would Reboot or Power Off (It registered them as unclean shutdowns). To my understanding, I don't believe there is a way to "Disable" Automatic Parity Checks, but I do think there is a script that helps in unclean shutdowns I.E the use of the power button. I found this article awhile back which helped me tremendously in understanding Unraid Parity Checks. I hope this helps! -Darrell

As I said on another post, I'm not the smartest Network guy. But have you tried basic Network troubleshooting yet like resetting your router or modem? Also, have you tried turning off Docker containers? If so, does the problem still persist? Docker containers are usually a big cause for Network problems and stability issues from what I've experienced so far. Strength & Honor -Darrell

I'm not the smartest network guy, but I had seen here awhile back someone having similar issues as this after upgrading to 6.12.2. I think they had solved it by going into Settings and changing Network to ipv4 only. Like I said, I'm not the brightest when it comes to Networking, but maybe it's worth a shot for now? Also, I was having similar issues after upgrading to 6.12.2 myself from 6.11.5 and I tried this ipv4 step, but it didn't work me (It's worked for several others though). What worked for me was turning off ALL my Dockers and turning them on 1 by 1 every other day until a server crash. I noticed my "Scrutiny" Docker was the source of my server crashes, so I've ended up removing it for now. Hope this helps and wishing you the best, -Darrell

I've had some problems like that in the past where I got entirely different ram than what I had ordered or had to do some type of tinkering to get it to work with the current system. Glad you got it figured out and I'll try to keep my eye here if anything else comes back up. Best, Darrell

Hello erfly7, Hope you are ready for the weekend! I had a similar issue whenever I got started with NordVPN. I'm not the most familiar with Surfshark, but I basically had to add a tunnel/exception for tower.local in order to access the webGUI and the Network shares. Adding a tunnel/exception allows you to access whatever it is without utilizing the VPN. I'm not the smartest network guy, but I hope this helps! Wishing you the best -DD

Hey Raiever, Hope all is well! I'm a little confused (It's the end of week), are you asking basically if you can use your old USB which holds your PRO license in the new setup once you get all of your data moved over? If this is the case, yes. I know you said your old server will be up until you get the new one up and stable. So this new server will essentially replace your old server, correct? If this is the case, you could copy your .key file to from your PRO drive to your trial drive once it's up and all data is moved over. Sorry if this wasn't the answer you were looking for, like I said it's the end of the week so I'm a bit brain-dead anyways lol. Also, check this out.. is this essentially what you're asking? -DD

Still no luck, but will post an update if I find a solution. Any tips or helps is appreciated!

Came back because I'm already set to ipv4 only as well. Also following for any advice

Is your ram overclocked? I had a similar issue awhile back and it was a problem with the OC ram.

Came here because I've been having a similar issue, but mines been going since about 6.11.5. I will try the ipv4 step and see what happens. Thank you!

Hey guys! Firstly, hope everyone had a good weekend and is doing well. I have a super niche issue after updating from Unraid 6.11.5 to 6.12.2. My server is running on an old Alienware Aurora R1 that I've had since release in about 2009. If you are familiar with Alienware products, then you know all the lighting adjustments are done through the Alienware Command Center application (atleast with the older gens like the R4, R3, R2, and R1 from my understanding). Anyways, I can't control the lighting with Command Center through a Virtual Machine because I figured the hardware is being emulated and this older R1 x58 chipset does not support passthrough. So what I've been doing to control the lighting on the Aurora R1 chassis is to boot from an ssd with Win10 and configure everything in the AlienFX panel within Alienware Command Center (I've only done this a few times because I rarely change the lighting effects). I would then restart, boot from Unraid USB, and boom the lighting I applied in AlienFX from the Win10 ssd would be applied while I had my Unraid server up. Since updating to 6.12.2, whenever my server comes up my lighting effects go away. It's basically applying the "Sleep Profile" from within AlienFX where everything lights up as should, except the biggest panel; the side. So the Alien logo and front cover light up as they should, but not the side panel. Like I said, whenever I open AWCC and get within AlienFX I can see the Sleep Mode it is going into, but I am unsure how to make it either not go into this profile all together, or atleast stop it from doing it while Unraid is up. I've been running Unraid for about a year and have never had and issue with this until now when I updated to 6.12.2. This is a super niche issue and I've been hunting every corner of the internet trying to figure out what the problem is but I'm at a blank. I can't find many other people that have a similar setup, but the Unraid forums have saved my booty a couple of times so I figured I'd ask if anyone has some advice here? I apologize if this isn't the place for this, but any helps or tips is appreciated. ❤️ I can post whatever screenshots or logs necessary I was just unsure on how to communicate and approach this issue. HELP ME GET MY LIGHTS BACK! Thank you in advance, -DD