Leaderboard

Parity Check Tuning plugin The Parity Check Tuning plugin is primarily designed to allow you to split a parity check into increments and then specify when those increments should be run. It will be of particular use to those who have large parity drives so that the parity check takes a long time and who leave their Unraid servers powered on 24x7. The idea is that you can specify time slots when the increments should be run and these can be chosen to be at times when the Unraid server is likely to be idle. The plugin also support running other long array operations (e.g. Clear, Rebuild) in increments if the user so desires. However since such operations are much rarer the user has to explicitly enable this in the plugin settings. Note that this plugin does not initiate a new parity check (or other array operation) - it only provides facilities for pausing/resuming/restarting them according to the criteria set in the plugin’s settings. If there is no array operation running during the timeslot specified for an increment then this plugin take no action. As an example on my system I have a 10TB Parity Disk and an uninterrupted Parity Check takes about 30 hours to complete. I have my normal scheduled parity checks set to run monthly. By using this plugin to run using 3 hour increments the elapsed time extends to 10 days (10 x 3 = 30) but I do not notice any impact on my normal use as the increments are run when I am not using the system. Once enough increments are run to complete the scheduled parity check then no further increments will be run until the time for the next scheduled check comes around. The plugin also allows other types of long-running array operations to be Paused or Resumed. These are Parity-Sync/Disk Rebuild and disk Clear operations. However since pausing these is less likely to be something the average user wants these can be individually controlled. For those who have problems with cooling on their Unraid systems it is also possible to set array operations to be Paused if the disks reach defined temperature thresholds and then Resumed when they cool down sufficiently. A much better solution is to have your Unraid system set up so that the cooling is sufficient to never let the disks overheat, but for some people this is not always practical. To avoid conflicts that can reduce overall performance you can set the plugin to automatically pause array operations if it detects that either the mover or the CA Backup processes are running and to then automatically resume the array operation when the process it question completes. The plugin will update the standard parity-check log to accurately reflect the duration and speed of parity checks to take into account that the check was run in increments as well as enhancing the information by also recording the number of increments, the total elapsed time and the type of check run. If you are running Unraid 6.9.0 (or later) array operations can be specified to be restated from the point they had reached at the point the reached when the system was shutdown or rebooted (or the array simply stopped/started) rather than from the beginning. This can be of particular use to those who do not want to keep their Unraid system powered on 24x7 (and power off overnight) as with modern large drives an array operation such as parity check can easily take more than 24 hours. The Settings page is added as an extra section to the Settings->Scheduler page (see the screenshot below) in the Unraid GUI as this seemed the most logical place for it to appear. Debug/Testing logging feature If you enable the option for debug logging then you will see additional entries appearing in the syslog about how this plugin is functioning internally. All these entries will include the word DEBUG so It is clear that they have been activated by turning on the Debug logging. This feature is primarily aimed at giving users a sense of what the plugin is doing under the covers for any users interested in such matters. In addition the logging level can be set to TESTING if trying to track down any suspected bugs in the plugin operation. This is primarily used during plugin development but can also help tracking down any issues that might be reported by users. It can be very verbose so users should not normally leave this option enabled. When this option is set to Testing then you are offered an additional option of Hourly for the frequency at which this plugin should pause/resume parity check increments. This was added primarily to help with testing and to help track down any issues that users might experience in using the plugin. Early feedback has suggested that users new to this plugin can use this feature as a way of getting a feel for how the plugin operates. Server Shutdown A feature has been included that allows users to set a temperature threshold for their array and cache drives that if exceeded will force the server to start its shutdown sequence. The prime Use Case for this is seen as protecting the disk drives in the event of the servers cooling failing for some reason. If activated this check runs even when there is no array or cache operation active. Command Line (CLI) options When this plugin is installed it adds the 'parity.check' command to the system which makes the following capabilities available from the command line: Usage: parity.check <action> where action is one of pause Pause a running parity check resume Resume a paused parity check check Start a parity check (as Settings->Scheduler) correct Start a correcting parity check nocorrect Start a non-correcting parity check status Show the status of a running parity check cancel Cancel a running parity check start Start the array stop Stop the array N Built-in Help The settings page for this plugin has very extensive built-in help to describe the meaning of the various settings. You can click on the description text for any particular setting to toggle it on-/off for that particular setting or you can turn it on/off at the page level by using the standard Help toggle in the Unraid GUI. Suggestions for improving the wording or expanding on the provided text are welcomed as it is not intended to produce any separate documentation. Parity Problems Assistant This is an additional option that appears under the Tools menu when the plug-in is installed. it implements Partial parity Checks which can be very helpful when trying to troubleshoot problems with parity after you have encountered errors when running the full parity check. It allows you to run a short check between specified start and end points. The current implementation is quite basic and feedback is welcomed on how it could be improved. Wish List This a holder for "blue sky" ideas that have been expressed for which there is no idea if it is even technically possible. They are kept here as a reminder and for others to perhaps expand on, and even perhaps come up with ideas for implementation.. Auto detect idle periods: The idea is that instead of the user having to specify specific start/stop times for running parity check increments the plugin should automatically detect periods when the system is idle to resume a parity check. This would need the complementary option of automatically detecting the system is no longer idle so that the check can be paused. Stop docker containers during a parity check. The ability to schedule the parity check to stop specified docker containers prior to check running and restart the docker containers after the check is paused or completed. A workaround for this would be to use the User Scripts plugin to do this although an integrated capability would be easier to use. Feedback Feedback from users on the facilities offered by this plugin is welcomed, and is likely to be used to guide the direction of any future enhancements. It will be interesting to hear how useful users find this plugin to be in the normal running of their system. Please feel free to suggest any changes that you think would enhance the experience even if it only rewording of text . Requirements Unraid 6.7.0 or later for the basic capability of running parity checks in increments. Unraid 6.9.0 or later for restarting array operations on next array start, and for using the Parity Problems assistant. Community Applications (CA) plugin. It is expected that this plugin will be installed via the Apps tab (i.e. the Community Applications plugin) and the appropriate template has been prepared to allow CA to handle it tidily. Installation The parity Check tuning plugin is available for installation by using the Community Applications plugin. If you navigate to the Apps tab and search for 'Parity Tuning' this plugin will show up and it can be installed from there. Once the plugin is installed then if you go to Settings->Scheduler in the Unraid GUI you will see an extra section has appeared that allows you to specify the settings you want to be used for this plugin.

Application: PostgreSQL @ https://www.postgresql.org/ DockerHub: https://hub.docker.com/_/postgres/ GitHub: - Version 10: https://github.com/juusujanar/unraid-templates/blob/master/PostgreSQL10.xml - Version 11: https://github.com/juusujanar/unraid-templates/blob/master/PostgreSQL11.xml - Version 12: https://github.com/juusujanar/unraid-templates/blob/master/PostgreSQL12.xml - Version 13: https://github.com/juusujanar/unraid-templates/blob/master/PostgreSQL13.xml - Version 14: https://github.com/juusujanar/unraid-templates/blob/master/PostgreSQL14.xml This template uses the official Postgres Docker image to quickly set up a relational database according to your configuration. If you have any issues/questions/suggestions regarding this Docker or the template, feel free to contact here. CHANGELOG (5th November 2021): - BREAKING CHANGE: Database volume paths now include version tag, e.g. `/mnt/cache/appdata/postgresql10` so you can run multiple instances with different versions at the same time. - BREAKING CHANGE: PostgreSQL 10 template got changed, this could have broken stuff on old users. I am not familiar with the template changes on older versions. - Added PostgreSQL 12, 13 and 14 templates. - Container names changed to lowercase and includes version, e.g. `postgresql14`. This should make it easier for using in custom networks. - Brought the templates up to date with current schema version. Previous changelogs:

Hahaha I'm dumb. I swear it used to be that little play/stop icon, but clicking the logo works.

ok, i never managed it, nvm, offtopic here ... the card seems to work as it looks like, he could try tvheadend just to make sure card is ok.

Disk 2 or disk 5? The command will move that from disk 5 to disk 6. In case you are not planning to replace disk 5, you now have an array with one less disk. So you have to create a new config and rebuild parity. https://wiki.unraid.net/index.php/FAQ_remove_drive

Yes, the link between the expander and the HBA is based on the link speed of the devices, each link has 4 lanes, so it's 4 x disk link speed. LSI SAS3 HBAs and expanders get around this with Databolt technology, where you can get close to full SAS3 bandwidth when using SAS2/SATA3 devices, more info here:

There is also the fact that if a card you get is reasonably mainstream and the Linux driver is not included already in Unraid it is quite likely that requesting it will get it added to a future Unraid release.

Ordered a Frosted Glass Mug (2019-03-29), summer "frostie" drinks coming up

Thanks, but I've got it under control. As an aside, the last release of CA (2019.02.21) also didn't work correctly with FF. I know exactly where the problem is, and will be pumping out an update tonight. You would think that javascript is javascript, but while Chrome, Edge, and Brave all think that 2+2=4, Firefox seems to believe that 2+2=5???

Followed on Twitter by @s_panky

Just followed on Twitter with the handle rctneil . Love Unraid and considering purchasing a mug shortly!

I remember reading somewhere/sometime that limetech have plans for user logins. I'll wait for that implementation 😁 👍

Hey team. I'm finally coming off my 350 hour project at work. Will finally start to see more free time to work on unmanic. I appreciate the patience. Since January I've been working overtime and have not had a chance to do any of my personal projects. I have not even logged into steam for months. But finally that's coming to an end. Over the next fortnight I'll take a look at everyone's suggestions and start coming up with a plan of attack for getting unmanic to a point where its useful for everyone. Thanks again. Sent from my ONE E1003 using Tapatalk

Good thing @CHBMB wasn't involved as something would have been deleted then 😜 Thanks for the fix.

the net-define command already makes it persistent. run virsh net-autostart lab-network to make the corresponding bridge auto start

I did not, but it did it for me. Everything was cleared, including any OC Profile you may have had saved. So you'll have to modify back all your settings. Using custom settings on the Smart Fan curve is a real pain. 😐

@mattz Glad it worked out. Did you wipe the CMOS after the downgrade?

@tw0884 - that Flash Tool worked like a charm with the older (v14) BIOS! I recommend you do the mobo BIOS downgrade. Updating to rc5 didn't help me at all with my problem. Maybe the Linux Kernel bump they brought in on rc6 will help, but I wouldn't bet on it... Maybe for a bigger upgrade I would try again. I have successfully booted into my Windows 10 VM with the GPU pass-through! I am ecstatic. Sucks that the only solution is to use an unofficial flash tool to downgrade the BIOS to get this working... but good enough for me!

@mattz, No problem for the tool. Fix with second GPU: I also found this to be the case with a Gt710 and I never actually got it working with unRAID ( didn't need it once I got the VM working) I have since booted into windows 10 from the MSI boot menu as I had W10 installed on a passed through NVME (was accessible by bare metal and VM).All was well within my W10 NVME and it ran fine. Launching through unRAID VM interface caused my unRaid to go haywire again( unmount cache drive, showing 4 trillion writes to cache) and the VM hung, not allowing unRAID to be restarted. I think my initial problems with the docker page was due to some docker files being moved from cache (speculation). I ran mover and docker is now responsive again. I'm pretty tempted to update to rc6 for a fix but may try the downgrade first...let me know how this turns out as I cannot run unRAID and W10 concurrently ATM.

No need to remove and re-add the docker image. Jst edit your docker, change the repository and then hit apply. Job Done.

@tw0884 - Sorry to hear you are also having problems. But it also makes me feel good I'm not just crazy and someone else sees it. I'll bet there are a lot more ppl noticing the problem as the update. Awesome find on that downgrade tool! I am going to give that a try... hope I don't brick my mobo but so hungry for a fix for the VM. FAILED - I bought a $40 video card and tried using it to no avail: 1) The mobo has no way to specify that card as the primary unless I move it to the top physical slot and 2) when I have a second card, the PCI-E goes from 16x lanes down to 8x lanes. I am not sure how big of an impact that may have, but I am not a fan of losing half the lanes. FAILED - I also tried using the Flashback+ built into the BIOS with no luck. I put in the flash drive with a "MSI.ROM" for the v14 BIOS, the computer powers on for 1 second, powers off, then the Flashback+ LED flashes 3 times and stays on. I guess that indicates an error with the flash process. I hit the power button and the computer boots up with the current BIOS v18. I have read that it is very particular about USB sticks, so I could go out an buy a few other brands but... Blah. I am going to load Windows 10 natively on an old SSD I have to see if everything boots OK. And then try out the MSI downgrade BIOS tool (thank you tw0884!). And then, the more desperate move, I will look to buy a new motherboard, different brand. MSI said I could start the RMA process, but if I have to disconnect everything and be out a motherboard for a week (or 2??), I am going to bail on MSI--the same problem will happen anyway once the BIOS is updated. I do worry, though, that it's not exclusively an MSI problem but linked to how Ryzen 2 talks to the sysytem... That means that the Linux Kernel(??) would have to get changed (maybe it's fixed in v5?) or... something else? But I don't want to sit idly by for it. However, since it was only the latest BIOS update where I had this problem, hoping other brands completely avoided causing this issue.

Hey mattz, Just wanted to chime in that I'm having the same issues with my MSI b450 gaming carbon Ac after updating my bios to the same version you did( 7B85v16). Same two errors on W10 VM Start, same CPU pairings changing after update. Running 6.7.0 rc4. GPU stubbed and unable to pass through to VM. Cheers Running: ryzen 2600 Sapphire Rx 580 MSI B450 gaming carbon Ac. Note: I did find a tool that is supposed to be able to downgrade the MSI BIOS here.

I had the same problem and this fixed it! Maybe we should stick it somewhere more prominent! Thanks to @aptalca

That's right, open the container settings and modify the repository entry (which is the docker image)

PSA. It seems openvpn pushed another broken bin, tagged 2.7.3 I get the same error with it as I did with the previously pulled 2.7.2 While they/us try to figure it out, you can change your image to "linuxserver/openvpn-as:2.6.1-ls11" and it should work

You know, I really don't get it. It seems like this is a Threadripper / Ryzen 2 issue from over a year ago. Some pretty ingenious folks on reddit posted a fix for it. However, the final fix was a BIOS update to x399 mobos. My CPU is a Ryzen 2 2700x... And it only broke with this error message on the _LATEST_ BIOS update. I have emailed MSI's tech support, but I am not getting much help from them... They still think I need to reinstall Windows to make it work. 😕

im on it guys, looks like there has been a switch to .net core which requires changes to the code which ive now done, new image now building

This will have very low priority in my life since I do it on my limited free time.

I just installed on my server. I'm trying to get a good client configuration. If I configure with Adaptive compression my Mac complains that LZO compression is deprecated but works fine on both Mac and my iOS devices. If I select LZ4 compression it works fine on my Mac but my iOS devices connect but can't seem to communicate. If I select no compression iOS works fine but my Mac Tunnelblick complains that the ovpn file has unrecognized options or missing parameters. What to do? I'm actually switching from linuxserver.io's Docker. In that configuration I have compression disabled but it works fine.

Here's my list of instructions.... Use them at your own risk..... If upgrading to v12 please see here: ##Turn on maintenance mode docker exec -it nextcloud occ maintenance:mode --on ##Backup current nextcloud install docker exec -it nextcloud mv /config/www/nextcloud /config/www/nextcloud-backup ##Grab newest nextcloud release and unpack it docker exec -it nextcloud wget https://download.nextcloud.com/server/releases/latest.tar.bz2 -P /config docker exec -it nextcloud tar -xvf /config/latest.tar.bz2 -C /config/www ##Copy across old config.php from backup docker exec -it nextcloud cp /config/www/nextcloud-backup/config/config.php /config/www/nextcloud/config/config.php ##Now Restart docker container docker restart nextcloud ##Perform upgrade docker exec -it nextcloud occ upgrade ##Turn off maintenance mode docker exec -it nextcloud occ maintenance:mode --off ## Now Restart docker container docker restart nextcloud Once all is confirmed as working ##Remove backup folder docker exec -it nextcloud rm -rf /config/www/nextcloud-backup ##Remove Nextcloud tar file docker exec -it nextcloud rm /config/latest.tar.bz2

As you know, 7200rpm drives will run a bit warmer than slower drives; and the HGST is known to run a bit warmer than some others, even at the same rpm. Nevertheless, it should not hit 50 => I wouldn't be concerned about mid-40's (44-46 or so) during continuous usage (pre-clears, parity checks, etc.) ... but if it's getting warmer than that you need to look at the airflow you have for the drive. By the way, the picture you posted for the temps during a parity check is essentially useless => that's a parity check that was just started. It can take an hour or so for temps to stabilize during a parity check ... let it run for 60-90 minutes and THEN look at the temps => that will be a much more useful data point.

You should keep some perspective on this, 41 is not hot, 50's and 60's are hot. You might be surprised by the manufacturers specs. I did a quick spot check, and found the max operating temp to be 55 for WD Blacks, 60 for Seagates and WD Blues and Greens, and 65 for WD Reds (couldn't find temps for HGST). It's been awhile since the Google hard drive study, but if I recall right, they did not see issues with drives that reached higher temps, but did see a few problems with cold drives. I personally have my drive temp warnings set to 45 for 'Warning' and 55 for 'Critical'. I consider 45 a good temp to inform me, as it's higher than I expect, and let's me know I may have a dead fan or other issue. At the same time, I too would wonder why one drive is rather different, would probably spend a little effort looking for a reason, but wouldn't worry too much about it. Your pic though shows that drive had done a LOT of work recently, and I wonder if it had had time to cool down yet.