slimshizn

This one's on me, to make sure I just did a SMART extended self-test and had some errors. Time to replace that disk. Sorry for that.

Updated to the recent version this afternoon, am getting these in the logs now. ``` Oct 14 18:46:55 Azeroth kernel: sd 7:0:3:0: [sde] tag#2475 Sense Key : 0x1 [current] [descriptor] Oct 14 18:46:55 Azeroth kernel: sd 7:0:3:0: [sde] tag#2475 ASC=0x18 ASCQ=0x4 Oct 14 18:46:57 Azeroth kernel: sd 7:0:3:0: [sde] tag#2545 Sense Key : 0x1 [current] [descriptor] Oct 14 18:46:57 Azeroth kernel: sd 7:0:3:0: [sde] tag#2545 ASC=0x18 ASCQ=0x4 Oct 14 18:47:00 Azeroth kernel: sd 7:0:3:0: [sde] tag#2546 Sense Key : 0x1 [current] [descriptor] Oct 14 18:47:00 Azeroth kernel: sd 7:0:3:0: [sde] tag#2546 ASC=0x18 ASCQ=0x4 Oct 14 18:47:07 Azeroth kernel: sd 7:0:3:0: [sde] tag#2433 Sense Key : 0x1 [current] [descriptor] Oct 14 18:47:07 Azeroth kernel: sd 7:0:3:0: [sde] tag#2433 ASC=0x18 ASCQ=0x4 ``` Odd thing is, this isn't even a UD. Any reason why the update would start to cause those logs? Thanks!

Yeah I figured out how to update within the container. Thank you.

I didn't, it still happens but doesn't seem to do anything other than fill up the logs.

Seems to be related to NFS.

Anyone seeing this, it is a NFS issue. Verify permissions. If permissions are not set, then it is a NFS bug. Seems to not hurt anything, but fills logs ( which can eventually cause issues ).

Any chance this could be updated to the recent version? Thank you.

Thanks, just disabled it for now.

Had this start happening after I was transferring data off of my Unraid server onto my TrueNAS server to change out the Unraid FS setup. It was coupled with some RAM errors at the same time that the server had not had before. I'm transferring over NFS. azeroth-diagnostics-20240325-0808.zip

Hello, Trying to figure out where these logs came from after a recent update, and how to stop them. Thank you. Searched before posting, and found two posts that were not answered. azeroth-diagnostics-20240322-1624.zip

@NotAZombie Did you end up figuring this out? This started happening to mine.

Hello, I'm on version 6.12.4 now after being on 6.10.3 for a long time. I had two crashes since moving over and I believe it's due to macvlan. Unfortunately due to the crashes I've had a disk failure, so I'm trying to figure out the root cause and enabled syslog mirroring, but am starting here: https://docs.unraid.net/unraid-os/release-notes/6.12.4/ I have a UDM Pro, so I'm following the part after "However, some users have reported issues with..." Does this require both ipvlan enabled in "Docker custom network type" and the network changes, or does it just require changing the network settings, and keeping the Docker custom network type on macvlan? Thanks in advance.

Yes Stop all of your containers using mysql, then open a mariadb console, then enter the following, followed by your password.

I tried this yesterday, and the YouTube links were removed. I came back here and saw an edit saying they were no longer needed as it was natively installed. The command still didn't work so I had to install the following packages with un-get. the following are already on the latest unraid version 6.11.5 afterwords and reboot the server. (following SpaceInvaderOne's video of course)

Following, Staying on previous 2.1.1-1-02 until further notice. Another reason for everyone to turn off auto updates when everything's working, provided you had them on.