Nexal

Bump... any idea why this might be happening or what I can do about it? Thanks!

Please let me know if there is anything else you need. Thanks! nas-diagnostics-20250106-1347.zip

I am trying to organize my media so that certain files are on certain drives. For example: Movies: Disk 1 TV: Disk 2, Disk 3 Anime: Disk 4 Music: Disk 5 Misc files (downloads): Disk 6 However, I am finding that when I acquire new media, it tends to stay on the drive where it was initially downloaded which is causing the download disk to get full before everything else. I am currently using Unbalanced to migrate the files to the correct disk when it becomes an issue, but is a slow and manual process; something I am trying to understand how to avoid going forward. I am using nzbget as my downloader and my completed downloads directory is on drive 6. I believe the reason for this is because bullet point #2 in the behavior outlined in this post: My question is: How can I configure my server to automatically put the files on the correct disks so that manual intervention via unbalanced isn't necessary? I have checked my nzbget and *arr settings and haven't seen any options to set a per category 'incomplete' InterDir directory for storing the download parts. My research has shown that as long as the InterDir is specified, nzbget unzips of these files within the 'incomplete' InterDir directory and them moves (mv) them to completed DestDir directory specified via the category. Additionally, I haven't seen any settings for these applications to copy then delete the files out of the downloads directory. Am I missing these critical settings? Or do I need to re-evaluate how I am storing my data? Curious if anyone has gotten a setup similar to this working. Any guidance would be very much appreciated. Edit: Grammar, spelling, & additional context.

Sorry for the delay, work picked up before I had to go out of town. I've finally had a chance to do some experimentation and so far extremely long file names and file names that end in spaces and so far after transferring with SMB neither has yielded the garbage names. Will continue to keep an eye out though for more circumstances where it occurs though.

Hmm seems like a possibility as I do use SMB. I’ll do some experiments the next time I am at my computer. Unfortunately, if this is what causes the issue, I am guessing the previous directory names would lost to history. But would be satisfied to at last understand this behavior better so thanks for sharing! Will update tomorrow morning as soon as I’m able on any findings

Great question! I have clicked through three or four directories and picked a random sample of files from each, and each appeared to be completely intact.

Interesting idea. Though the files are still accessible in the renamed folders and I haven't found any location that the original name with encrypted contents. I assume these encrypted files would be located in the same location? 🤔

I haven't manually started a repair, but is this something unraid does automatically on a periodic basis?

@KilrahThey are in the expected location. What do you mean by a filesystem check? Like a parity check or something else?

Hmm. I almost never use windows with this unraid server so I would be surprised if it came from there. I asked ChatGPT and it said: However, when I was trying to learn more about 'sparse subdirectory names' there was practically no additional information which made me think that ChatGPT was likely making the name up. But not sure, to be honest, which is why I thought I'd ask real humans who likely would know a more accurate answer. It is possible that these file names were quite long, maybe >80 characters. But I can't see their original directory names to confirm so this is just a guess. When I manually create longer file names they don't get renamed within the observation period. So it's got me stumped.

Apologies in advance as I am sure this has been asked before, but I have been unable to locate any previous posts due to not knowing this behavior's name. I have been noticing that many of my directories have been renamed to so something like the following when I do `ls` in the command line: AWSVI4~U/ AWT44A~A/ AWTG9Q~4/ AWVBVQ~S/ AWWPW5~4/ AX1FG1~5/ AX4ROW~G/ AX6IG2~B/ AX9N8N~T/ AXEAWT~X/ AXGKR7~X/ AXTZHE~6/ AXX89X~Q/ AXXQ3N~1/ AXY21M~3/ AXYEMA~B/ AY6IL5~G/ AY9CO0~Y/ AYDVWF~W/ AYGYF6~S/ AYHK2F~4/ AYICEK~E/ AYKN8G~5/ AYP24I~B/ AYVCSJ~D/ AYXEJE~4/ AYZZUR~4/ AZ7DOQ~D/ AZ8GE5~V/ AZB27W~Y/ My array is using XFS. It doesn't seem like corruption because the files within these directories are still accessible and the renaming is so uniform. So a few questions: - What system or feature is causing this (so I can read more about it)? - What causes some directories to be renamed and other to not be renamed? - How can I disable this renaming and restore my directories to their original names? Thanks in advance!

Thanks for all the wonderful responses. I have replaced the CPU and the error seem to have gone away. Will continue monitoring but I haven't seen these error in the 12 hours since the CPU was replaced.

It was only on the screen for less than a second, but I might have just seen a similar kernel error when trying to boot into proxmox. If so, then it's likely not a software error... Could it be my CPU? Never heard of a brand new CPU being bad. But what else could cause these issues if the mobo and ram have been replaced and the issue persists?

I am extremely dismayed to report that the new motherboard and RAM did not resolve the kernel errors I have been seeing and reporting. I am at a complete loss at what to do next. This makes me think that the issue wasn't hardware related. If it's not hardware related, that means it has to be software related. Starting to wonder if I need to find another solution other than Unraid. Not my preference, but I am not seeing how else to get a stable system... Any thoughts would greatly appreciated.