I'm on the latest RC, I would confirm that however I just grabbed that yesterday.

I am currently computing Parity - 3 days to complete (sheesh wth.. 15mb/sec -- yes PCI eStata connection to 8 drives).

 

I don't think I can just reboot the server and parity will continue where it left off - I'm about a day into the parity rebuild.

 

I have docker container (Plex) stopped, and a VM I have stopped

 

I was checking status on the main page, and yes refreshed over and over, being impatient -- and then did it pretty quick 3+ times in a row.. the WebGUI stopped responding.

 

Nothing I do -- killall emHttp  - starting it back up as the Go script does -  allows me to bring back the WebGUI.

 

Any help - don't want to reboot and loose progress on parity.

Emhttp can not be restarted. If you killed it, the only way to get it back is to reboot.

Is there any way to get the webGUI to "reset" if it does hang?

 

I've experienced this now a few times while setting up my unRaid initially.

 

It "feels" like if I go too fast, too many quick requests, it hangs.

Do you mean you have one eSATA going to an external enclosure with 8 drives? You should consider redesigning your hardware.

Do you mean you have one eSATA going to an external enclosure with 8 drives? You should consider redesigning your hardware.

 

First please keep this on topic - I'm trying to receive feedback on my issues, not on my hardware setup. But... since you did here:

 

I already stated that I know parity computation will be slow, I have a RocketRaid 622 dual port card that goes to a Sans Digital TowerRaid TR8M +B which I have setup as jbod. 1) 4 drives per esata connection 2) this is going into a small Gen 8 Micro Server from HP 3) Accessing content the way I do -- I NEVER read from multiple disks at the same time, not running VMs one Shares, only media files. 4) I do not mind the extra time it takes to compute parity for right now on the initial parity sync -- afterwards - I have to see what the speed is like. 5) I'm getting right around 100MB per second to one drive while doing the initial copy - dropping to about 80mb at the lowest.. That is plenty fast for a single disk access for me -- again 99% of the time that is all this server will be doing.

 

I just have a lot of files.

Tools - Diagnostics

Here are the diagnostics

unraid-diagnostics-20150813-1907.zip

Just a quick comment, you don't want to refresh the screen any more than absolutely necessary when running a parity check or build or drive rebuild, because it stops the process, resets some values, and greatly slows it down.  It's much more than a browser page redisplay.  I wouldn't refresh more than once a minute, unless you *want* it to go slow!

Thanks Rob on that note.

 

I will say I actually let it compute parity since Sunday, and unfortunately (in a different thread) my web gui crashed. I just let it go, and basically finally today no drive activity - When the Web GUI crashes -- I can only shutdown and start it back up to get it back.

 

When it had NOT crashed, I had waited hours if not a full day, and it was still only 7-15mb on speeds.

 

I also just tried one disk + one parity ... and got only about 25mb