Company > Announcements
unRAID Server Release 5.0-rc5 Available
limetech:
Download | Release Notes
Please post issues in the unRAID OS 5.0-rc Board
Here's the current state of 5.0 along with what still needs to be done for "final" release. First some known issues:
- NFS stale file handles when accessing user shares. This is not fixed in -rc5, but finally I know what the problem is. Until this is solved I recommend not using NFS to access user shares. I'll add more info about this in a sticky...
- mvsas driver issues. This is also not fixed in -rc5, but I can reliably reproduce some failure cases. Note, all issues with this driver appear to be related to bug(s) in error processing. If your h/w is working properly, there is no problem and data I/O is reliable. In addition, most errors are handled correctly. I'll add more info about this in a sticky.
- media playback stutter. Earlier the idea of creating a fully preemptable kernel might alleviate some of these issues, but in my testing I have not found this to be the case. In addition, it cuts parity-sync rate almost in half. So this is not going to be a productive path to follow. This will require more testing to get to the bottom of it.
Here is additional functionality to be implemented:
- add configurable location for saving the netatalk database
- enhancements to avahi: programmable service names, enable/disable controls
- plugin manager
Might make it into 5.0 final, if not, will wait for 5.1:
- lighty (lighttpd) front-end for emhttp
- move webGui code to github as a public repository
Another issue someone has brought up is (again - sigh) the Realtek NIC drivers. It turns out that Realtek's "r8168" driver compiles ok with our kernel, so I will produce a -rc5-r8168 release for those affected to test out. The r8168 project is GPL2 and why Realtek just doesn't take ownership of this driver under linux and get rid of r8169 is a mystery to me.
WingmanNZ:
I can confirm that manually compiling the 8168 driver for RC4 and replacing the r8169.ko fixes my issues with my RTL8111D NIC, using r8169 under RC4 however gives me network issues when streaming multiple streams from the unRAID box.
I can also confirm this by rolling back to b12a which includes the r8168 driver.
I would love to test "-rc5-r8168" and report back with logs etc.
thanks
- WingmanNZ
PeterB:
--- Quote from: limetech on June 23, 2012, 04:23:24 PM ---- NFS stale file handles when accessing user shares. This is not fixed in -rc5, but finally I know what the problem is. Until this is solved I recommend not using NFS to access user shares. I'll add more info about this in a sticky...
--- End quote ---
Are you issuing this advice because the fault can, potentially, corrupt data? Is there any reason that rc5 should be any worse in this respect than rc4, or earlier?
tyrindor:
--- Quote ---mvsas driver issues. This is also not fixed in -rc5, but I can reliably reproduce some failure cases. Note, all issues with this driver appear to be related to bug(s) in error processing. If your h/w is working properly, there is no problem and data I/O is reliable.
--- End quote ---
I just built 2 systems, each using 3x SAS2LP-MV8 cards for a total of 6. I fixed all my problems by disabling PCI-E OPROM for all slots in BIOS. I made a thread but fixed the issues before I got a reply. They are now running RC5, and still no problems. I don't know if this is related to the issues you are talking about, but I know some people wanted to know about SAS2LP-MV8 support and they are working perfectly fine after a few BIOS tweaks for me.
EDIT: Had to go back to B14. MVSAS error definitely exists on the 2nd gen version of the cards too.
--- Quote ---- plugin manager
--- End quote ---
;D
limetech:
--- Quote from: PeterB on June 23, 2012, 04:45:57 PM ---
--- Quote from: limetech on June 23, 2012, 04:23:24 PM ---- NFS stale file handles when accessing user shares. This is not fixed in -rc5, but finally I know what the problem is. Until this is solved I recommend not using NFS to access user shares. I'll add more info about this in a sticky...
--- End quote ---
Are you issuing this advice because the fault can, potentially, corrupt data? Is there any reason that rc5 should be any worse in this respect than rc4, or earlier?
--- End quote ---
This issue should not result in data corruption, and behavior should be the same in all releases.
Navigation
[0] Message Index
[#] Next page
Go to full version