bk101

Quick question, if we want to follow the following steps do we do them BEFORE updating to 6.12.4 or AFTER updating? "For those users, we have a new method that reworks networking to avoid this. Tweak a few settings and your Docker containers, VMs, and WireGuard tunnels should automatically adjust to use them: Settings > Network Settings > eth0 > Enable Bridging = No Settings > Docker > Host access to custom networks = Enabled"

My Unraid box was running completely fine, no errors no issues with disks. I spun the array down to disable SMBv1 as per some security advice I've seen. Anyway while my array was powered down I noticed that my cache pool has 4 slots, I only have 2 cache SSDs and 2 empty slots. I thought oh lets reduce the available slot size to 2 as I probably wont add another 2 drives in the future, as soon as I did this the drive status went blue and it says "All existing data on this device will be OVERWRITTEN when array is Started" I don't want my data to be deleted so I changed the amount of slots back to 4 however it's still blue and says my data will be overwritten. How do I fix this? I don't want to power on my array in case it deletes data. My hunch is to change slots to 2 and do a new config keeping all existing settings but I'm not certain and don't want to cause another issue on top of this. Any help would be appreciated as I can't start my array without knowing what's going to happen I've noticed in cache.cfg it's references 2 additional SSDs that where in the pool in the past. This pool used to be 4 SSDs but I reduced it to 2 maybe a year ago and it's had 2 empty slots since then and working fine. Not sure if this is related. edit: Diagnostics added edit2 : I went for the new config, selected all and then checked parity is valid on start everything is back... panic over

This worked for me! thanks

I see, I guess my unraid doesn't need to access it. I just remember turning this on when setting up Swag. I could always turn it off and test if it breaks anything and then go from there. Edit: Actually found host access to custom networks is already turned off, I have "Preserve user defined networks" turned on.

Will this break my Swag proxy?

@JorgeB@trurl Thanks for checking and posting me those links, just want to confirm that the 3 crashes were all linked to Macvlan issue? so by defaulting back to bridge mode and disabling pihole for the time being should have solved my issue? The 3 crashes were from 14th April 21:00, 24th April 21:00 and 2nd May 18:20.

@codefaux@trurl@Frank1940 Thank you for responding, sorry about my first post being so vague, I was at my wits end trying to figure out what was going on. I've had a server lock up maybe once every 7-9 days. The web ui becomes unresponsive and then there will be a bunch of Kernal messages on the server monitor and I would have to restart the server to fix it. The logs I posted were from roughly the time of the crash, I had read up about syslog server after the first server crash as I noticed there were no logs kept after the restart. So the 2 logs I posted before hand were of roughly the time of the crash, I've attached the diagnostics to this po st and the logs from the Syslog. I also learnt about the Macvlan, unsure if this was the only issue. I had set most of my docker containers to use static IPs, since this post I have reverted them back to using bridge with the exception of PiHole, unfortunately I noticed some further errors in the log and managed to restart teh server before it locked up, I have now disabled pihole to see if the issue really is macvlan error, I currently have no docker containers with a static IP. Hoping you can take a look at the logs and tell me if it could be something else? I haven't really made many hardware changes recently, however this is a recently put together build. I think the errors that cause the crash look like this: Please let me know if I can post anymore info and thank you for your time.

Anyone able to assist?

I've been experiencing some server crashes where the server becomes unresponsive and I have to reboot, can someone please take a look at the following log info and help me understand what may be causing it?

Ok, no worries. They're still under warranty so will contact manufacturer to arrange a replacement.

SDG and SDI are identical disks both brand new 8TB drives

Anyone able to take a look please?

Attached, thanks. It seems like the pre-read is finally done, but it took 3-4 times longer than another identical disk. It's like it gets slower towards the end. It's currently zeroing at normal speeds, but will be interesting to see if it slows down towards the end again. This disk was actually my parity drive before and didn't have any issues with the first parity build but later on when it did a parity check it was this slow towards the end as well.

Recently jumped hard on to the UNRAID bandwagon and I'm loving it so far, learnt a lot since first starting to use it, I've run in to an issue and was hoping someone could help. I'm running preclear on a few drives and one is currently at 97% (pre-read) but going as slow as 1mbps every so often, there appears to be no SMART errors or any indication as to why, I've tried to have read through the logs but I'm not familiar enough to spot the issue, nothing obvious jumps out. Could someone please help me out? The slow speeds is on a brand new 8TB Toshiba drive device SDG I know SDI has some CRC errors which I believe is due to the HBA, waiting for these preclears to finish before I further investigate that Also SDO has 4632 current pending sectors, which I believe means the drive is failing. Can someone confirm? I've attached the syslog.