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

Mine is also an rsync to an nfs share - an unassigned mounted drive on another unraid server.

40 minutes ago, slimshizn said:

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 336.72 kB · 0 downloads

You have the cache dirs plugin installed.  Be sure you set it to include only the shares you want it to operate on.  If you don't set up include shares, it will cache all shares including UD and cause issues like this.

21 minutes ago, dlandon said:

You have the cache dirs plugin installed.  Be sure you set it to include only the shares you want it to operate on.  If you don't set up include shares, it will cache all shares including UD and cause issues like this.

Thanks, just disabled it for now.

I don't have that plugin myself......

I can cause these issues by running an rsync to an unassigned mounted nfs disk to another unraid server.

Any other time they dont happen.

Not a memtest issue.

On 3/25/2024 at 1:51 PM, dlandon said:

You have the cache dirs plugin installed.  Be sure you set it to include only the shares you want it to operate on.  If you don't set up include shares, it will cache all shares including UD and cause issues like this.

Thanks this post really helped me! Disabled while transferring between servers stopped this.
Using the guide to use Luckybackup moving TB of data 

Dont know why that dir cache plugin is still online, it never helped me not spinning up drives

Disabled the dir cache plugin but still keep getting errors

 

I am copying between servers using the guide from SPX Labs

 

And it works great, but seems I only get these errors when running a copy?
Sofar its not crashing.....

 

diagnostics-20240329-2326.zip

I guess we just hope a future release/kernel fixes this.

Same issue here and system hangs with a few cores peged. 

unraid-diagnostics-20240602-0742.zip

Been dealing with this issue for months.  

On 6/21/2023 at 8:24 AM, trurl said:

For anybody still piling on this thread

I started having this error. I did a memtest found errors bought a new set of RAM tested it in this server as well as another PC previous to installing it. I fixed some minor corruptions. Checked for errors had none. Started having these a few days later. I have tried a separate known working pcie NIC  then replaced the motherboard previous to the memory replacement. Now I'm piling on here.

Just now, ctsdad said:

I started having this error. I did a memtest found errors bought a new set of RAM tested it in this server as well as another PC previous to installing it. I fixed some minor corruptions. Checked for errors had none. Started having these a few days later. I have tried a separate known working pcie NIC  then replaced the motherboard previous to the memory replacement. Now I'm piling on here.

Thought I should mention I tested the cable and specific port it's connected to. The issue is random I will get speeds up to 110 MB's on a download the watch as it goes down to bits per second and then the entire server goes "offline" where your connection to it freezes and I am unable get to anything. Then shortly it will come back.

Unraid version 6.12.4

I have the same issue. My situation seems similar to SpeedyB

Recently I installed a second cache ("cache_shares", see attached img) with 2 TB SSD. I wanted to speed up some write Operations.

• 1. I wanted my download clients to download on the cache ("downloads" share).
  • 1.1 (*In some cases, the file (or some files of a torrent) has been moved back to array from the mover if it hasn't downloaded fast enough)
     
• 2. Then sonarr moves the downloaded file to media library. ("MediaShares" share)
  
  The issue starts at this step, and I have noticed the download speed of my download clients (qBittorent and deluge) goes from 10MiB/s to 40KiB/s. The deluge sometimes crashes as well and restarts itself.
  
  Other issues I have noticed is the Unraid UI crashes (someone else also posted the same issue) and high CPU usage
   
• 3. Then Tdarr picks up the file for transcode (transcode on "tdarr" share).
   
• 4, And last, the mover will move the file to Array

Can't say I am happy with this config 😅 but definitely the errors appeared when I introduce the second cache

My old config looked like this:
I had only one cache 2TB Nvme.
No, Cache to Array shares.
One download client.
Only Tdarr transcoded in the cache.

So, I it feels something is wrong with the read and write operations on the new cache

here is an img of my "shares" config.


If you can spot anything wrong with this config, please let me know.

Edited July 18, 20241 yr by Lachanophobia

I'm facing the same: https://discord.com/channels/216281096667529216/780505064816246834/1283025269430550579
I guess it somehow related to any network activity (even if it is low)

Did anybody tested it on 7x version? It has been here for about 2 years and still no fix. Maybe it is fixed in 7.x beta? Anybody?

 

Hi all, just thought to chip in with my experience, I too had an error of this nature and turned out to be that I had a SMB mount via a tailscale tunnel which when that mount was not reachable I got this error. When unmounting the unreachable share the errors stopped. 

I could reproduce this by having that drive available and mounting it, then turning off that drive on the remote end and the error started again. 

I understand this may not be the case in all of the above but it may help some who are getting this error in this use case. 

On 9/10/2024 at 1:32 PM, IrQ said:

Did anybody tested it on 7x version?

I just started experiencing this with version 7, after having upgraded to it a few days ago after running the betas for a little while. The whole web UI went haywire too and be barely usable. It first started with the Apps page not loading, then the whole UI randomly reloading and returning to Main, where it would show all my drives popping out and back in over and over again. I think it started when I updated the Community Apps Application earlier today. There was a second update that seemed to fix it for a short while but then made it worse.

 

A restart brought the system back to a usable state, showing three errors upon startup:

 

```

Jan 15 20:50:07 STower24 kernel: traps: mongod[24128] general protection fault ip:151b7d0c79a2 sp:7ffc5eab0230 error:0 in libc.so.6[151b7d0c7000+188000]

Jan 15 20:50:09 STower24 kernel: traps: mongod[25705] general protection fault ip:1493b20eb9a2 sp:7fffe9d1d0f0 error:0 in libc.so.6[1493b20eb000+188000]

Jan 15 20:50:12 STower24 kernel: traps: mongod[27290] general protection fault ip:1473acfef9a2 sp:7ffe7bbe1420 error:0 in libc.so.6[1473acfef000+188000]

```

 

Will soon swap the mainboard as that seems to possibly be wonky (threw some NIC errors that made me use a PCIe x1 NIC for now).

Edited January 15, 20251 yr by DesertCookie

19 minutes ago, DesertCookie said:

mainboard as that seems to possibly be wonky

start with memtest

9 minutes ago, trurl said:

start with memtest

Ran for over a day without any issues. Now, that's half a month ago already, but I hope it's not gone bad since then. But I will retest it before and after I swap the mainboard.