October 7, 200718 yr Download. This is the first "patch" of a final release. The only changes between 4.2 and 4.2.1 are: - use Samba version 3.0.26a - change version string from "4.2" to "4.2.1" This should hopefully fix the problems reported in this thread. Please post in this thread if this release fixes those problems. unRAID Server 4.2.1 Release Notes Upgrade Instructions (Please Read Carefully) -------------------------------------------- If you are currently running unRAID Server 4.2-beta1 or higher (including 4.2 'final'), please copy the following files from the new release to the root of your Flash device: bzimage bzroot If you are currently running unRAID server 4.0 or 4.1, please copy the following files from the new release to the root of your Flash device: bzimage bzroot syslinux.cfg menu.c32 memtest This can be done either by plugging the Flash into your PC or, but copying the files to the 'flash' share on your running server. The server must then be rebooted. If you are currently running unRAID Server 3.0-beta1 or higher, please follow these steps to upgrade: 1. Referring to the System Management Utility 'Main' page, make a note of each disks's model/serial number; you will need this information later. 2. Shut down your server, remove the Flash and plug it into your PC. 3. Right-click your Flash device listed under My Computer and select Properties. Make sure the volume label is set to "UNRAID" (without the quotes) and click OK. You do NOT need to format the Flash. 4. Copy the files from the new release to the root of your Flash device. 5. Right-click your Flash device listed under My Computer and select Eject. Remove the Flash, install in your server and power-up. 6. After your server has booted up, the System Management Utility 'Main' page will probably show no devices; this is OK, navigate to the 'Devices' page. Using the model/serial number information gathered in step 1, assign each of your hard drives to the correct disk slot. 7. Go back to the 'Main' page and your devices should appear correctly. You may now Start the array. If you are installing this release to a new Flash, please refer to instructions on our website at: http://www.lime-technology.com/wordpress/?page_id=19 Changes from 4.2 to 4.2.1 ------------------------- Bug Fix: use Samba version 3.0.26a
October 7, 200718 yr Brilliant stuff. Just a small note. Due to the bug i the first versions of the Memtest i am not sure the upgrade instructions are actually correct for versions ... "If you are currently running unRAID Server 4.2-beta1" i.e. it would be safer to follow the full upgrade to be sure. Trivial point.
October 7, 200718 yr Thanks Tom, Downloaded and currently running on 4.2.1 as of this morning. I've been stress testing it for 7 hours, so far, ftp'd a 5 Gig Iso image to an unRaid share, while using bittorrent to download Slackware 12 ISO DVD ;D ;D I've seen no problems at all. ;D ;D I know this smbd bug was hard to duplicate, and never even showed itself to some, but it made the server unusable for myself and many others under certain conditions. Looking at the release notes for smbd 2.0.25, 2.0.26 and 2.0.26a it looks like a few more memory leaks were plugged in addition to fixing a security issue. The smbd development team actually made a lot of fixes. Although the security issue would probably never be encountered, a memory leak would eventually cause a problem. Thanks for putting out 4.2.1 so quickly after 4.2. Joe L.
October 7, 200718 yr Author Man that's great news and has saved us a lot of time. Thanks for you help in tracking this problem down!
October 7, 200718 yr I upgraded to 4.2.1 this morning and tried to copy a gig of data and it was painfully slow. About 1-2% utilization on a 100Mb connection. Went back to 4.2 and utilization peaked at 90%.
October 7, 200718 yr I too wish to extend my thanks to Joe, for helping in finding the problem/cause, and to Tom/Lime, for implementing it so quickly. I had only experienced it once, but it was quite annoying
October 7, 200718 yr I upgraded to 4.2.1 this morning and tried to copy a gig of data and it was painfully slow. About 1-2% utilization on a 100Mb connection. Went back to 4.2 and utilization peaked at 90%. We'll need a list of your hardware, and an attached copy of a syslog after booting 4.2.1 and doing the same slow copy, and perhaps a copy of a syslog after booting 4.2. It would be better though to start a separate thread, rather than mix your support posts into this announcement thread. unRAID 4.2.1 is working fine for me.
October 8, 200718 yr We'll need a list of your hardware, and an attached copy of a syslog after booting 4.2.1 and doing the same slow copy, and perhaps a copy of a syslog after booting 4.2. It would be better though to start a separate thread, rather than mix your support posts into this announcement thread. unRAID 4.2.1 is working fine for me. Thanks RobJ, I'll gather all that information and start a thread when time allows. I'm sure it's probably my hardware... specifically my Marvell 88E8001 network chipset
October 8, 200718 yr I too wish to extend my thanks to Joe, for helping in finding the problem/cause, and to Tom/Lime, for implementing it so quickly. I had only experienced it once, but it was quite annoying I did not find the solution in the SAMBA mailing list, "wanton" did. I only posted links to pre-compiled binaries of smbd versions 3.0.24 and 3.0.26a and described how to work around the buggy version of smbd once it was identified. Many others should get the credit for reporting and working through this bug... or at least the bulk of it. Joe L.
October 8, 200718 yr I just upgraded over the internet using xp remote desktop... that was real easy. I love unRAID.
October 8, 200718 yr For some reason, setting up the root password in Safari result in an immediate crash, and any further access to the interface yield the same result. I'm safe with Firefox, is it an extra level of security for dedicated Mac users
Archived
This topic is now archived and is closed to further replies.