Hi Guys,

since several beta's and rc's we are waiting for a final release of the 5.0 branch of unRaid.

 

I just would like to know would are the actual problems of the latest RC, which prevent Tom from releasing a final Version?

I guess that, for most of us, RC8a is performing acceptably.

 

Some are still complaining about dropouts when playing media files, some are reporting performance problems particularly during parity checks.  For me, the only significant problem I have is the one I reported four days ago, where write permission is intermittently refused for no apparent reason - here.

 

I am sure that here are several other 'complaints' but it is not always clear whether these are configuration problems/hardware problems or genuine faults/shortcomings in the unRAID code.

RC8a has issues that will require an update to the Samba package to correct.

Tom indicated that he wanted to include a 'plug-in manager' into the initial release of version 5.0.  It could be that this is presenting more issues than he first anticipated.  I have read that some people have encountered issues with the present method of initial plug-in installation where the NIC was not yet on on-line when the plug-in tried to download the files required for installation. 

I have noticed that preclearing drives on RC-8 are very slow at about 500 KB/s.  I have tested preclearing drives on 4.7 with no problem, I am currently trying RC-5.

I have noticed that preclearing drives on RC-8 are very slow at about 500 KB/s.  I have tested preclearing drives on 4.7 with no problem, I am currently trying RC-5.

I would not have thought that the preclearing script should be affected by the version of unRAID you are using.  That script runs at the Linux level outside the normal unRAID system so should run at full speed.  If you have a disk that appears to preclear too slowly I would be suspicious of that disk or its associated power, connectors and controller.

Tom indicated that he wanted to include a 'plug-in manager' into the initial release of version 5.0.  It could be that this is presenting more issues than he first anticipated.  I have read that some people have encountered issues with the present method of initial plug-in installation where the NIC was not yet on on-line when the plug-in tried to download the files required for installation.

 

For a plugin I am working on, I solved the inet issues with this code (which I stole from somewhere) at the beginning of the plg.  It waits until it can ping google successfully before progressing through the rest of the plg.  FYI this was only an issue for me when using a dynamic IP.  Once switching to a static IP, I had no issues.

 

<FILE Name="/tmp/inetwait" Run="/bin/bash">
<INLINE>
<![CDATA[
#!/bin/sh
x=`ping -c1 google.com 2>&1 | grep -i unknown`
COUNT=0
while [ $COUNT -lt 10 ]; do
if [ ! "$x" = "" ]; then
	echo "Waiting for Internet access"
	sleep 2
fi
let COUNT=COUNT+1   
done
rm /tmp/inetwait
]]>
</INLINE>
</FILE>