bondoo0

Any other thoughts (in my case the USB is showing up correctly) or things to try?

I am using Unraid 6.1.2 and Firefox 40.0.3. I'm getting the same error. Was there ever any resolution for this? All of my drives show up on the data tab. No changes are saved either on the layout page (for the elements displayed, however the number of rows does save), or the data page. And after the first time, I get the listed error on the layout page.

Wet Yes, at the beginning of the preclear. If it stood still, there's a unknown bug there. I saw similar behavior with a bad download. Check the file sizes in /boot/config/plugins/disk.preclear. if there are any with a size of zero bytes, that's likely the problem. Remove and add the plugin again, verify file size, and that should fix it.

I had the corruption (0 byte files) issue as well. Now it runs, but I'm not sure how to use bjp999's version with the fast post read. Do I just rename the script file, or am I missing something?

Running into an issue with system stats and the tempfs file system. It seems that the log data for system stats (in /var/log/sa) is growing fast enough that it fills up the tempfs file system before it rolls over, so I have to go in and delete the directory so it doesn't fill up the file system. So, given that, a couple of questions, is there a way to change the location of this from tempfs, or is there a way to change the amount of data logged?

Found it, and that seems to have fixed the issue, thanks!

I'm running into an issue with notifications. For some reason I'm not getting any notifications (updates available, parity check running). I've tried both email and browser (having both checked and either/or checked), and nothing shows up under archived notifications either. I have run the test in SMTP, and get the email so I don't think it's a setup thing with my email. I've noticed this on both beta 12 and beta 13, so anything to check to get his working would be fantastic.

One word of caution for using the script on unraid 6 with VM's. I ran into issues where the script ran fine, but when a parity check kicked off, it would cause unraid to freeze (looked like a kernel panic, that others were able to resolve by pinning CPU's to dom0, but that didn't help in my case). As soon as I went back to the default values the problem went away, so I'm guessing something was just pushed too far, and the machine ran out of resources during parity checks.