itimpi

No idea I am afraid. That part of the scheduling is handled by the core Unraid system and not by the plugin. Maybe you need to raise a feature request/bug about this?

Have you rebooted since doing the update? Just asking as this might clear up some ‘debris’ state information by an earlier release. if you DO get after rebooting then to determine why I would need the testing mode active in the plugin settings and then diagnostics taken after the reboot and when this notification has been displayed.

I found it can be an external link to the User Manual, but that it loads into the tab that is currently displaying the GUI. That was why I asked about a way to force a new tab. I now need to decide if the value of displaying the relevant manual page out-weighs the downside of the user now having to reload the Unraid GUI into another tab.

If that was the case then I would consider returning them - they are obviously not new.

You can get to it from the forum - no need to have a working server.

Any way to get the link to open in a new page and/or tab? I was wanting to set up a link that goes to a section of the online documentation and it would be better if this left the current GUI page unchanged.

You did not include a copy of your system's diagnostics zip file which might have been a good idea? I would suggest adding them next time around to see if we can spot anything. Just a thought - go into the config/shares folder on the flash drive and see if there are any .cfg files there that do not correspond to shares you think you should have and if so then delete them just in case one of those is causing problems as your screenshot of the User Shares page looks a bit strange with what look like empty share names.

Never heard of the power on hours being wrong in this way. Were these meant to be new drives or second-hand ones? Where did you purchase them from?

you cannot rebuild a drive and add an additional drive in 1 step which is what I think you are trying to do here? If so it needs to be done as 2 separate steps.

If you have the key file then you put in the ‘config’ folder on the flash drive.

It would also be worth checking that all fans are spinning OK as the reboot could be due to CPU overheating causing a thermal shutdown.

Post your system's diagnostics zip file.

Looks like the issue is your licence key file as the log contains: Sep 8 12:01:25 UnraidPredator emhttpd: error: get_key_info, 565: Invalid argument (22): stat: /boot/config/key.key Sep 8 12:01:25 UnraidPredator emhttpd: Unregistered - missing key file (ENOKEYFILE2)

Delete the 'parity.tuning.restart' and 'parity.tuning.scheduled' files from the plugins folder - it looks like this is left over from the previous issue! They would probably have been automatically tidied up if you had rebooted but it looks like this did not happen?

That is the wrong command as you have omitted the partition number (e.g. /dev/sde1) so no point in continuing.

Running from the command line is notorious for getting the command slightly wrong which results in the bad superblock message. It is always a good idea to post the exact command you used so we can check it was valid. it is very rare after a successful run via the GUI for the drive to remain unmountable which was why I was checking on what exactly had happened.

Are you sure you ran without the -n option as both sets of output you posted said -n was used. note also that it will continue to say unmountable even after a successful repair until you stop the array and restart it in normal mode.

That is currently intended behaviour (I think I discussed it earlier) with the recent releases if it happens during an array operation. It is only the pause/resume related ones that are currently being controlled by the plugin's settings. I thought this could well be useful information for most users so they can see if those tasks running coincides with possible performance issues. Making it unconditional for the time being will mean I get some feedback to see how many want it vs. do not want it. The questions that arise are: Is having this notification useful even when not using the pause/resume options for background tasks. Should there be a setting to control it? I could possibly add it as one after the options to pause/resume for background tasks in the current plugin settings with the default being to set it on.

Fair enough. I guess it is just a case of waiting until either someone else confirms it works for them, or at least no new reports of a problem like this.

Just checked my server running 6.12.4 and I do not see a new window popup. Instead an edit area opens up on the current page.

I am ging to change the default pause setting for increments to be 7:30 instead of the current 3:30. The options to temporarily pause while move or a backup are running seem to now be working as expected which means it is no longer so relevant to not allow the parity check increment time to overlap their running times. This is allowed for. It is not unusual for users to start late in the evening but before midnight.

As far as I know you are the only one experiencing this issue, although I do not see what could be causing it.

You should enable the syslog server with the option to mirror to flash set so we can get a syslog that shows what was happening in the lead up to the crash/freeze. The syslog of interest will then end up in the 'logs' folder on the flash drive.

With those settings you should end up with a syslog file in the 'logs' folder on the flash drive. This will be the one to post after a crash to show what was happening in the lead up to the crash although it is a good idea to post the current diagnostics as well so we can see more about your system.

This would be the way to go. Have you checked that the new USB drives DO have a unique GUID? When you update to a new release of Unraid then the latest blacklist will take effect.