trurl

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

Any top level folder on cache or array is automatically a user share. You must have configured something with a path like /mnt/user/jDownloader or /mnt/cache/jDownloader or something like that. The best way is to delete all files and folders from the share, then delete the share from the webUI. That way Unraid knows to remove the share. But, if you just delete the folder, simply stopping and starting the array should be all that's needed to get it to reload the shares based on the disk contents, because if the folder doesn't exist when the array starts, it isn't a user share.

And just in case there is still some confusion. DO NOT update Unraid if what you want is Unraid NVidia. ONLY update Unraid NVidia.

Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post.

Unraid Nvidia IS a custom build of Unraid. You must use the Nvidia plugin to update to a new Nvidia build. If you just update Unraid you just get Unraid. All this is explained many times in the Nvidia thread.

The diagnostics you posted earlier indicate parity was invalid. You said you were checking parity, but if parity is invalid then I assume you hadn't built parity yet. So instead of checking parity you were building it. Is that correct? Is that syslog after a crash? Doesn't look like any parity disk was assigned.

Shouldn't this thread be moved to Docker Containers? Let me know and I will do it.

All the information you put in those screenshots could have been better given to us with just the Diagnostics. Probably would have made it more obvious what was going on and there wouldn't have been 2 threads. You should assume that if you need help, we need your diagnostics.

I have merged your threads. Please don't start multiple threads for the same issue. It makes it impossible for us to coordinate our responses.

I assume you mean you renamed it to UNRAID.

@Squid Isn't this thread supposed to be locked? I posted to it after it was but I am a moderator and I'm pretty sure I wouldn't have unlocked it to post to it. I will lock it again if you want.

Has absolutely nothing to say about parity, since parity doesn't know anything at all about files. Every disk is just a bunch of bits as far as parity is concerned, and every bit of every disk is included in parity, whether or not those bits are even part of any files. You could have parity errors with no file problems, and those errors could still affect a rebuild that would result in file problems.

Yes, I wouldn't be surprised if that isn't what he is comparing to. He didn't specifically mentioned that, just said no cache. And we often recommend doing the initial data load before adding the parity disk.

I don't know of any that get that speed, with or without reconstruct write, with commonly used HDDs. If you read that link you can see why writes to the parity array cannot be as fast as writes to a single disk. Write speed isn't the primary focus of the Unraid design. Unlike RAID, there is no striping, but there is parity, which has to be maintained in addition to any write to a data disk. But, the fact that there is no striping means each data disk can be read independently on any Linux, and different sized disks can be used, and drives can be easily replaced or added without rebuilding the entire array. Storage in the parity array is often write-once, read-many, archived data and media files. Cache pool allows for faster access and redundancy for those other cases where that is needed.

This plugin is much newer than that. Don't know if it's compatible or not.

Since you had this discussion going in 2 different threads I have split the posts from that other thread into this one. Please keep things together so we can coordinate responses.

/mnt/user is the user shares. Any folder created there will create a user share, and Unraid will choose a disk for it on the array since it will have default settings.

By this do you mean you restored the appdata from the backup? Did you also reinstall plex using the Previous Apps feature on the Apps page, or did you just reinstall it without using the Previous Apps feature? Have you corrected whatever caused you to fill cache?

Not really recommended to continually write syslog to flash. That should only be done for specific troubleshooting purposes. Even better is to have it stored somewhere else if you are running syslog server.

You sure that molex wasn't plugged in backwards (yes, people have done that)? Or maybe it was wired up wrong. My guess is the power to the drive was at fault.

The array is not started in those diagnostics. Get us new diagnostics after starting the array.

Unraid is slackware so likely way more packages needed than you realize, if it is even possible. I think it is unlikely this will get much traction.

Have you made it work at all? If so, you can use the User Scripts plugin to reinstall those packages at boot time.

Unraid IS NOT RAID, and RAID controllers are NOT recommended. Unraid has parity that provides redundancy, but it isn't truly any standard RAID implementation. In many ways, it is actually better than RAID. Since each data disk in Unraid is independent (no striping) speed of disk access can only be as fast as the single disk. Somewhat slower than that for writes for parity updates. But, since each data disk in Unraid is independent, you can mix different sized disks, easily replace a disk, and easily add disks. See this Overview from the wiki and you will be in a better position to ask better questions: https://wiki.unraid.net/UnRAID_6/Overview

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post. Also, setup Syslog Server so your syslog will be saved from before the crash: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601 Have you done memtest?