Hi,

 

I don't know if this is platform specific, but if I refresh the main unRaid page using the browser refresh button (control +R) instead of the unRaid refresh button unRaid will shutdown instead of refreshing leading to a parity check when restarting. This is using Safari on OS X. This is not what one expects to happen. Refreshing should be the same if using the browser refresh button or unRaid's refresh button

 

Roland

Hi,

 

I don't know if this is platform specific, but if I refresh the main unRaid page using the browser refresh button (control +R) instead of the unRaid refresh button unRaid will shutdown instead of refreshing leading to a parity check when restarting. This is using Safari on OS X. This is not what one expects to happen. Refreshing should be the same if using the browser refresh button or unRaid's refresh button

 

Roland

What version of unRAID are you running??  Tom has been trying to address this, but it has only been reported by a few users.

 

In the current 4.4-beta2, the "Refresh" button issues a  call to this JavaScript

<script language="javascript">
function disable_form_elements() {
  for(i=0;i<top.window.document.forms.length;i++){
    var formObj = top.window.document.forms[i];
    for(j=0;j<formObj.elements.length;j++){
  if (formObj.elements[j].type.toLowerCase() != "hidden")
        formObj.elements[j].disabled = true;
}
  }
}
function refresh() {
  disable_form_elements();
  parent.location=parent.location;
}
</script>

The actual button HTML for refresh looks like this:

<input type="button"  value="Refresh" onclick="refresh();">

 

You can see that the "Refresh" button in the screen does far more than the refresh button in the browser.  It first disables each of the button on the form and then sets the "parent.location" to be itself.

 

It looks like Tom is thinking that actual issue to be that your browser is submitting to unRAID a "cached" version of the form when you press the "Refresh" button. (the one you you last used to stop the server)

 

His code does not get invoked when you press the "refresh" button (on the browser toolbar) or "Control-R" (the keyboard shortcut)

 

The above code, while ingenious, is not the final answer as I'm not sure the current form (with the disabled form elements) is even "submitted" to the unRAID web-server at all when you press the button on the web-interface.

 

I do agree with you, the "refresh button on the unRAID form should not do anything more than "Control-R" or the browser toolbar refresh button.

 

In the meantime, I suggest you install the unmenu.awk management web-server and view your day-to-day status there.  Its main screen has NO buttons at all, shows more data than the stock page, and adds features some have found useful.  It even auto-refreshes its main page every minute. (or you ca use Control-R, or browser refresh button)

 

You can find it in this thread: http://lime-technology.com/forum/index.php?topic=2595.0

 

Joe L.