Download

 

Please see

readme.txt

in the release zip file for installation/upgrade instructions.

 

Bug fix release.  Hopefully no bugs will be found with the bug fixes and I'll drop the "-rc1".

 

Changes from 5.0 to 5.0.1-rc1
-----------------------------
- emhttp: fix Active Directory, fix join operaiton (winbindd wasn't starting)
- emhttp: for Active Directory, fix assiging initial owner/group (only set once)
- emhttp: for "swap disable" where new disk is factory-cleared, skip clearing remaining space beyond replaced disk size
- emhttp: added missing 'started' event, generated at end of array Start sequence
- linux: upgrade kernel to 3.9.11p (patched)
- linux: added iptables support per user request
- linux: changed frequency scaling drivers from "built-in" to "modules", and added a few more drivers
- other: remove extraneous files in /root and /usr/local/sbin
- slack: fix settings in /etc/rc.d/rc.samba to eliminate 'WARNING: The "idmap backend" option is deprecated'
- slack: add "winbind use default domain = Yes" to rc.samba when setting up Active Directory
- slack: upgrade smartmontools from 5.40 to 5.43 per user request
- slack: upgrade hdparm from 9.37 to 9.43 per user request
- unraid driver: support 64-bit builds (no impact on 32-bit build)
- unraid driver: initialized superblock should start out marked "clean"
- unraid driver: prevent crash if disk partition(s) doesn't exist upon array Start
- webGui: for Active Directory, user may explictitly enter the AD short domain name
- webGui: add confirmation checkbox to enable array Stop button
- webGui: offer "Parity is already valid" checkbox only if parity disk has been assigned
- webGui: fix "swap disable" not being presented correctly

So as a rule of thumb should I wait for the rc to be dropped before installing on my main production server?

Didn't get the "Write corrections to parity disk" checkbox fixed eh? I'll get this installed tomorrow and let you know how it goes!

 

Thanks Tom, good to see progress continuing after 5.0

Thanks, looking forward to testing it out.

 

FYI on smarmontools, that is still too old of a version, you can't get to the new SVN repository to download the lastest HD db

Please update to 6.2 when you get a moment.

 

Date 2013-07-26

Summary: smartmontools release 6.2

-----------------------------------------------------------

- smartctl: Added ATA write cache reordering control using

  '-g wcreorder' and '-s wcreorder,[on|off]' options.

- update-smart-drivedb: Updated for new SVN repository.

- HDD, SSD and USB additions to drive database.

- Areca RAID support: Fixed possible segfault on empty port.

- HPT RAID support: Maximum disk number increased to 128.

- Linux: RHEL 9 compile fixes.

- FreeBSD: Device scanning now skips port multipliers.

- Cygwin: 64-bit compile fixes.

- Windows: Fixed bogus temp file name in smartd_warning.cmd

  (already included in smartmontools-6.1-2.win32-setup.exe).

- Windows: smartd service is no longer installed as interactive.

So as a rule of thumb should I wait for the rc to be dropped before installing on my main production server?

We have it installed on all "production" servers.

Didn't get the "Write corrections to parity disk" checkbox fixed eh? I'll get this installed tomorrow and let you know how it goes!

 

Thanks Tom, good to see progress continuing after 5.0

Yes it is fixed.  The pertinent line is:

 

- unraid driver: initialized superblock should start out marked "clean"

 

Right, should have indicated the bug being fixed instead of what the fix is.

NOOB ALERT:

 

what does "- unraid driver: support 64-bit builds (no impact on 32-bit build)" mean? That this is a 32 bit build but has all the stuff needed to recompile a 64-bit build?

NOOB ALERT:

 

what does "- unraid driver: support 64-bit builds (no impact on 32-bit build)" mean? That this is a 32 bit build but has all the stuff needed to recompile a 64-bit build?

It means that I have unRaid vers 6 in development which is a 64-bit kernel.  There are a handful changes in the unraid driver to make it compile on both 64-bit and 32-bit platforms, and that line in the change log is documenting that those changes got into the code base with release 5.0.1.

 

Edit: I really like your sig 

Thanks for your hard work as always, Tom.

So far so good. Looking forward to the full 64-bit release.

Installed fine for me.  No issues so far

Installed fine for me.  No issues so far

+1

Installed on two systems -- my main server and one test unit -- and both are working just fine.  Ran a bunch of "stress" copies on the test unit and no hiccups at all.

 

A small point - should the thread title not mention 5.0.1 rather than just 5.0?  It is not obvious at first glance without reading the thread that it is about a new release.

A small point - should the thread title not mention 5.0.1 rather than just 5.0?  It is not obvious at first glance without reading the thread that it is about a new release.

Yes, fixed that, thank you.

I think this page needs to be updated for 5.0.1?

http://lime-technology.com/wiki/index.php/UnRAID_Server_Version_5.0-beta_Release_Notes

Main server upgraded OK.  Thank you Tom.

so just double checking everything went well with 5.0.1.. I noticed this:

 

smartctl -a -d ata /dev/sdg (disk1)

smartctl 5.43 2012-06-30 r3573 [i686-linux-3.9.11p-unRAID] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     SAMSUNG SpinPoint F4 EG (AFT)
Device Model:     SAMSUNG HD204UI
Serial Number:    S2H7J1BZA19770
LU WWN Device Id: 5 0024e9 004372475
Firmware Version: 1AQ10001
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 6
Local Time is:    Tue Nov 12 08:05:16 2013 CST

==> WARNING: Using smartmontools or hdparm with this
drive may result in data loss due to a firmware bug.
****** THIS DRIVE MAY OR MAY NOT BE AFFECTED! ******
Buggy and fixed firmware report same version number!
See the following web pages for details:
http://knowledge.seagate.com/articles/en_US/FAQ/223571en
http://sourceforge.net/apps/trac/smartmontools/wiki/SamsungF4EGBadBlocks

 

http://sourceforge.net/apps/trac/smartmontools/wiki/SamsungF4EGBadBlocks

    Problem: If the system writes to this disk and smartctl -a (5.40) is used at the same time, write errors are reported and bad blocks appear on the disk.

 

thankfully I know I've already applied the firmware update, which sadly doesnt change the firmware number.. hence:

    The warning will also be printed when the patch is already installed! 

 

so mainly just a disclaimer to those that do have the drive and never got around to updating

Didn't get the "Write corrections to parity disk" checkbox fixed eh? I'll get this installed tomorrow and let you know how it goes!

 

Thanks Tom, good to see progress continuing after 5.0

Yes it is fixed.  The pertinent line is:

 

- unraid driver: initialized superblock should start out marked "clean"

 

Right, should have indicated the bug being fixed instead of what the fix is.

 

Excellent! Installed OK.

I think this page needs to be updated for 5.0.1?

http://lime-technology.com/wiki/index.php/UnRAID_Server_Version_5.0-beta_Release_Notes

That wiki page is deprecated and I'll soon remove it.

What is the best and safe way to upgrade from 5.0 to 5.01-RC1 ?

The instructions are in here: http://download.lime-technology.com/dnld/beta/unRAIDServer-5.0.1-rc1-i386.txt

 

So what I did on my windows machine was type Run in my search bar from the start button, then connect to the server "\\tower", then opened my flash drive and draged over 'bzimage', 'bzroot', and 'readme.txt' from the release zip file. Then rebooted.

What is the best and safe way to upgrade from 5.0 to 5.01-RC1 ?

Right, sorry, I should have stated in the announcement to look in the readme.txt file in the release zip for install instructions.

NOOB ALERT:

 

what does "- unraid driver: support 64-bit builds (no impact on 32-bit build)" mean? That this is a 32 bit build but has all the stuff needed to recompile a 64-bit build?

 

Like your signature file too.  I like it so much, I am thinking about copying it.  Very cool!