unRAID Server release 4.5-beta3 available

limetech · March 23, 2009

Several bug fixes.

unRAID Server 4.5-beta3 Release Notes
=====================================

Changes from 4.5-beta2 to 4.5-beta3
-----------------------------------

Known issues:
- The 'reiserfs' file system is built with kernel-option to enable extended attribute support.  This is necessary for Active Directory.  Even if file system is not mounted with extended attributes, reiserfs still creates a hidden file called '.reiserfs_priv' (used to manage extended attributes) in the volume root. This file is harmless and does not appear in any share.

Bug fixes:
- Fixed problem where all Flash files appeared to have Hidden/System/Archive all set.
- Fixed upgrade problem where 'simple security' was not being initialized properly.
- After formatting a new disk, the 'File system type' was not being updated.
- If cache disk present, should allow 'use cache disk' option in creating new share.
- Fixed problem with mover not moving.

Other changes:
- Changed name of samba include file introduced in -beta2 from 'boot/smb.extra' to 'boot/smb-extra.conf'.
- Upgrade Samba to (patched) version 3.3.2.  The patch is a bug fix that prevented windows client from removing Read-only attribute (previous versions of samba 3.3.x fail with 'Access denied').
- If security model is not Active Directory don't mount the data disks with acl & extended attributes enabled.
- Prevent recording (ie, writing) 'last access time' when directories and files are read on the Flash.
- Added 'lsof' command.
- Include 'Hardware Monitoring' in the linux kernel build along with this device support:
  AMD Athlon64/FX or Opteron temperature sensor
  Intel Core (2) Duo/Solo temperature sensor
  ITE IT87xx and compatibles
  Winbond W83627HF, W83627THF, W83637HF, W83687THF, W83697HF
  Winbond W83627EHF/DHG


Changes from 4.4.2 to 4.5-beta2
-------------------------------

New features:
- Support Active Directory Service (ADS).  This lets an unRAID server join an Active Directory (AD) domain.
- System Management Utility will now use a CSS style sheet file on the Flash (config/style.css) if present.
- May now read syslog directly via browser by referencing 'http://tower/log/syslog' (substitute 'tower' with your server name).  Actually any 'file' in the /var/log directory can be read via 'http://tower/log/file'.
- May now read arbitrary files on disk and user shares via http protocol by referencing URL 'http://tower/share/<diskN>/...' or 'http://tower/share/user/<sharename>/...' (substitute 'tower' with your server name).
- Samba configuration now 'includes' the file on the Flash 'config/smb.extra' if present.  This is included at the end of the 'global' section just before the share definitions.  This may be used to customize the Samba configuration.
- Added control to enable/disable 'mover' logging.

Bug fixes:
- With user mode security enabled, would not accept 'root' share login until password was set at least once.
- Fixed problem in 'mover' script where mover would attempt to move objects in a top-level directory staring with a '.' character.  These would all fail and cause excessive syslog messages.
- Fixed bug in 'logrotate' which would prevent syslog from rotating.

Other changes:
- Part of adding AD support: Removed "User security [enabled/disabled]" control from Shares page, and added "Share security [simple/User Level/Active Directory]" control to Settings page:
  unRAID 'Basic' (free version) supports only 'Simple' share security model;
  unRAID 'Plus' supports 'Simple' and 'User Level' share security models only;
  unRAID 'Pro' supports all share security models ('Simple', 'User Level', and 'Active Directory').
- Removed System Management Utility control for setting SMB ports; this can be done via 'config/smb.extra' if desired.
- Change spin-down logic to account for external programs spinning drives up/down.
- Per user request, added '/usr/lib/libstdc++.so.6.0.9'
- Upgraded to linux kernel 2.6.28.4.
- Upgraded to samba 3.3.0.


Upgrade Instructions (Please Read Carefully)
============================================

If you are currently running unRAID Server 4.2-beta1 or higher (including 4.2.x '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, by 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

NAS · March 23, 2009

wiki updated

Update: Please could you bring back the equivalent of the "0" setting for highwater that used to exist in older versions i.e. "0 - do not allow highwater to create new folders at all"

marcusone · March 23, 2009

Looking good... great work, thanks!

A couple of things:

1. Any ETA on enabling cache disk support for other versions that the Pro?

2. A quick "how to" for "Hardware Monitor"?

thanks again!

SSD · March 23, 2009

I installed this version. Here are my preliminary comments ...

1. I installed and booted. Worked great.

2. I had some issues with Samba with the prior release which caused me to revert to 4.3.3. This version resolves those issues.

3. I setup the custom samba configuration (smb-extra.conf). It includes both a usermap and a series of custom shares. All working great.

4. There is a slight mistake in the release notes -

instead of ...

- Changed name of samba include file introduced in -beta2 from 'boot/smb.extra' to 'boot/smb-extra.conf'.

should say

- Changed name of samba include file introduced in -beta2 from '/boot/config/smb.extra' to '/boot/config/smb-extra.conf'

5. I re-ran my performance test (copying a 1G file from Windows to unRAID server via Samba)

w/ queue_depth at default (31): 2:09

w/ queue_depth set to one: 1:24

Anyone using this version should set queue_depth to 1 in go script.

6. I'll keep an eye on the syslog for that strange burst of log entries. It happened twice under 4.5b2. One was attributed to a bad memory stick, but then it recurred after bad memory stick was removed. Both times happened after about 2 days of uptime.

NLS · March 23, 2009

5. I re-ran my performance test (copying a 1G file from Windows to unRAID server via Samba)
w/ queue_depth at default (31): 2:09

w/ queue_depth set to one: 1:24

Anyone using this version should set queue_depth to 1 in go script.

Maybe you should spell us how? (or is it in the wiki already? sorry didn't look - I am in a training lab and in fact had a "quicky" look in the forum)

marcusone · March 23, 2009

5. I re-ran my performance test (copying a 1G file from Windows to unRAID server via Samba)
w/ queue_depth at default (31): 2:09

w/ queue_depth set to one: 1:24

Anyone using this version should set queue_depth to 1 in go script.

Maybe you should spell us how? (or is it in the wiki already? sorry didn't look - I am in a training lab and in fact had a "quicky" look in the forum)

There are a number of spots, but I'll put it here for quick reference:

echo 1 > /sys/block/sdX/device/queue_depth #where X = drive letter you are setting. You can also 'cat' this file to see the current setting

Joe L. · March 23, 2009

5. I re-ran my performance test (copying a 1G file from Windows to unRAID server via Samba)
w/ queue_depth at default (31): 2:09

w/ queue_depth set to one: 1:24

Anyone using this version should set queue_depth to 1 in go script.

Maybe you should spell us how? (or is it in the wiki already? sorry didn't look - I am in a training lab and in fact had a "quicky" look in the forum)

There are a number of spots, but I'll put it here for quick reference:

echo 1 > /sys/block/sdX/device/queue_depth #where X = drive letter you are setting. You can also 'cat' this file to see the current setting

On my server, the queue_depth is already set to a 1 for all my sdX devices. I did not need to do anything... (and I just loaded the 4.5-beta3 version a few hours ago)

Joe L.

root@Tower:# for i in /sys/block/sd*; do echo $i `cat $i/device/queue_depth`; done

/sys/block/sda 1

/sys/block/sdb 1

/sys/block/sdc 1

/sys/block/sdd 1

/sys/block/sde 1

/sys/block/sdf 1

Romir · March 23, 2009

Most people are probably using IDE mode and not AHCI, which will already have it set to 1.

SSD · March 23, 2009

Maybe you should spell us how? (or is it in the wiki already? sorry didn't look - I am in a training lab and in fact had a "quicky" look in the forum)

Here is a post by RobJ in which he includes an easy to use script to report on and set the queue depth.

Most people are probably using IDE mode and not AHCI, which will already have it set to 1.

There have been several recommendations to set the SATA in AHCI mode. If I remember right, setting to IDE mode has each pair of SATA drives emulate an IDE channel. An IDE channel can either be in read or write mode. Thus having SATA drives in IDE mode come with some baggage that can cause accesses to be unnecessarily delayed. Also, NCQ certainly sounds like a good idea, and is only available in AHCI mode (setting queue_depth to 1 basically turns this off, however). But it was based on those reasons, I set all my drives in AHCI mode.

In 4.4.2 copying a 1G file with queue_depth at 31 took about 6 minutes, versus 1:30 with queue_depth set to 1. This version took just over 2 minutes with queue_depth at 31, and 1:24 with queue_depth set to 1. Maybe in a few versions the queue_depth of 31 will be neck and neck with the queue_depth at 1 (with the added advantage of NCQ when there are multiple pending accesses). For now, though, set it to 1 manually to get the benefit of faster write performance. Note that I have seen no impact on read performance with queue_depth changes.

rhinoman · March 25, 2009

I'd made the move to 4.5b2 and now have my permssions all messed up. I cannot delete or rename the old bizimage bizroot to install the new one. Could someone tell me what, how to do this please.

Thanks

John

marcusone · March 25, 2009

I'd made the move to 4.5b2 and now have my permssions all messed up. I cannot delete or rename the old bizimage bizroot to install the new one. Could someone tell me what, how to do this please.

Thanks

John

Take the USB stick/drive to your normal PC and move/setup the files there. then you can put it back into your unRAID box and boot into the "new" version.

marcusone · March 25, 2009

Sensors: well, I installed the lm_sensor pack (lm_sensors-3.0.3-i486-1.tgz) and all is well!

did > installpkg lm_sensors-3.0.3-i486-1.tgz

then > sensors

and get:

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +37.0 C  (high = +86.0 C, crit = +100.0 C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +37.0 C  (high = +86.0 C, crit = +100.0 C)

it8718-isa-0290
Adapter: ISA adapter
in0:         +1.22 V  (min =  +0.00 V, max =  +4.08 V)
in1:         +1.78 V  (min =  +1.28 V, max =  +1.68 V)   ALARM
in2:         +3.44 V  (min =  +2.78 V, max =  +3.78 V)
in3:         +3.01 V  (min =  +2.67 V, max =  +3.26 V)
in4:         +3.02 V  (min =  +2.50 V, max =  +3.49 V)
in5:         +0.00 V  (min =  +0.58 V, max =  +1.34 V)   ALARM
in6:         +1.22 V  (min =  +1.04 V, max =  +1.36 V)   ALARM
in7:         +3.01 V  (min =  +2.67 V, max =  +3.26 V)
in8:         +3.07 V
fan1:       1366 RPM  (min =   10 RPM)
fan2:       2265 RPM  (min =   10 RPM)
fan3:          0 RPM  (min =   10 RPM)  ALARM
temp1:       +21.0 C  (low  = +127.0 C, high = +63.0 C)  sensor = thermal diode
temp2:       +28.0 C  (low  = +127.0 C, high = +112.0 C)  sensor = thermistor
temp3:       +23.0 C  (low  = +127.0 C, high = +112.0 C)  sensor = thermistor
cpu0_vid:   +0.000 V

Not sure why I'm getting "ALARM" showing (one of the voltages is at 0 apparently, one is above, and the other appear to be in range, according to sensors anyways). The system is running great and stable for the last few days (though i don't use it heavily all day long).

marcusone · March 25, 2009

Found a bug?

When I click "Spin Up" on the main page of the web GUI, I get this in syslog, and the drives go back to sleep:

Mar 25 11:46:13 RCNAS emhttp: Spinning up all drives...

Mar 25 11:46:29 RCNAS emhttp: shcmd (62): /usr/sbin/hdparm -y /dev/sde >/dev/null

Mar 25 11:46:30 RCNAS emhttp: shcmd (63): /usr/sbin/hdparm -y /dev/sda >/dev/null

Mar 25 11:46:31 RCNAS emhttp: shcmd (64): /usr/sbin/hdparm -y /dev/sdd >/dev/null

Mar 25 11:46:32 RCNAS emhttp: shcmd (65): /usr/sbin/hdparm -y /dev/hde >/dev/null

Mar 25 11:46:32 RCNAS emhttp: shcmd (66): /usr/sbin/hdparm -y /dev/hdf >/dev/null

The only drive missing (as I have 6 total) is one that is being accessed (so is awake already). a 'man' on hdparm says that that '-y' paramater sets the drive to low power

Force an IDE drive to immediately enter the low power consumption standby mode, usually causing it to
spin down. The current power mode status can be checked using the -C flag

trueimage · March 25, 2009

I just installed this beta and powered on the server. I see a bunch of "FATAL" errors looks like to do with NFS

I've attached my syslog

EDIT: I just rebooted and re-attached the syslog, I don't see the FATAL error in there (on either copy) but it was on the screen, after the login prompt showed up.

I'm gonna test the NFS connection to see if it is still working properly.

limetech · March 27, 2009

Found a bug?

When I click "Spin Up" on the main page of the web GUI, I get this in syslog, and the drives go back to sleep:

Mar 25 11:46:13 RCNAS emhttp: Spinning up all drives...

Mar 25 11:46:29 RCNAS emhttp: shcmd (62): /usr/sbin/hdparm -y /dev/sde >/dev/null

Mar 25 11:46:30 RCNAS emhttp: shcmd (63): /usr/sbin/hdparm -y /dev/sda >/dev/null

Mar 25 11:46:31 RCNAS emhttp: shcmd (64): /usr/sbin/hdparm -y /dev/sdd >/dev/null

Mar 25 11:46:32 RCNAS emhttp: shcmd (65): /usr/sbin/hdparm -y /dev/hde >/dev/null

Mar 25 11:46:32 RCNAS emhttp: shcmd (66): /usr/sbin/hdparm -y /dev/hdf >/dev/null

The only drive missing (as I have 6 total) is one that is being accessed (so is awake already). a 'man' on hdparm says that that '-y' paramater sets the drive to low power

Force an IDE drive to immediately enter the low power consumption standby mode, usually causing it to
spin down. The current power mode status can be checked using the -C flag

Those 'hdparm' commands are indeed used to spin drive down.

I can not duplicate this problem. Can you make this happen again? If so, please capture syslog and post. Thanks!

limetech · March 27, 2009

I just installed this beta and powered on the server. I see a bunch of "FATAL" errors looks like to do with NFS

I've attached my syslog

EDIT: I just rebooted and re-attached the syslog, I don't see the FATAL error in there (on either copy) but it was on the screen, after the login prompt showed up.

I'm gonna test the NFS connection to see if it is still working properly.

What are you using for the NFS export string for your shares being exported by NFS?

marcusone · March 27, 2009

Found a bug?

When I click "Spin Up" on the main page of the web GUI, I get this in syslog, and the drives go back to sleep:

Mar 25 11:46:13 RCNAS emhttp: Spinning up all drives...

Mar 25 11:46:29 RCNAS emhttp: shcmd (62): /usr/sbin/hdparm -y /dev/sde >/dev/null

Mar 25 11:46:30 RCNAS emhttp: shcmd (63): /usr/sbin/hdparm -y /dev/sda >/dev/null

Mar 25 11:46:31 RCNAS emhttp: shcmd (64): /usr/sbin/hdparm -y /dev/sdd >/dev/null

Mar 25 11:46:32 RCNAS emhttp: shcmd (65): /usr/sbin/hdparm -y /dev/hde >/dev/null

Mar 25 11:46:32 RCNAS emhttp: shcmd (66): /usr/sbin/hdparm -y /dev/hdf >/dev/null

The only drive missing (as I have 6 total) is one that is being accessed (so is awake already). a 'man' on hdparm says that that '-y' paramater sets the drive to low power

Force an IDE drive to immediately enter the low power consumption standby mode, usually causing it to
spin down. The current power mode status can be checked using the -C flag

Those 'hdparm' commands are indeed used to spin drive down.

I can not duplicate this problem. Can you make this happen again? If so, please capture syslog and post. Thanks!

Same thing... as soon as I click the "Spin Up" button on the GUI, i get those 'spin down' commands in my syslog for all drives that currently show to be 'sleeping'.

I'll do a reboot to get a "clean" full syslog of this happening and send it to you.

RobJ · March 27, 2009

I'll do a reboot to get a "clean" full syslog of this happening and send it to you.

It would be good to also include the contents of the disk.cfg file from the config folder of your flash drive.

marcusone · March 28, 2009

I'll do a reboot to get a "clean" full syslog of this happening and send it to you.

It would be good to also include the contents of the disk.cfg file from the config folder of your flash drive.

# Disk configuration
spindownDelay=1
parity=pci-0000:00:1f.2-scsi-1:0:1:0
disk1=pci-0000:02:00.0-scsi-0:0:0:0
disk2=pci-0000:00:1f.2-scsi-1:0:0:0
disk3=pci-0000:00:1f.2-scsi-0:0:0:0
disk4=pci-0000:00:1f.1-ide-0:0
disk5=pci-0000:00:1f.1-ide-0:1
diskSpindownDelay.0=-1
diskSpindownDelay.1=-1
diskSpindownDelay.2=-1
diskSpindownDelay.3=-1
diskSpindownDelay.4=-1
diskSpindownDelay.5=-1

not sure what that will tell ya, but here.

RobJ · March 28, 2009

not sure what that will tell ya, but here.

It just helps ensure there is nothing unusual about the global and individual spindown settings. Yours are at the default values.

NAS · March 30, 2009

Tom please add system beep to the next beta if you find the request acceptable.

It has been discussed many times over the last year such as:

http://lime-technology.com/forum/index.php?topic=2447.0

However it has alot of potential uses.

WeeboTech · March 30, 2009

Tom please add system beep to the next beta if you find the request acceptable.

It has been discussed many times over the last year such as:

http://lime-technology.com/forum/index.php?topic=2447.0

However it has alot of potential uses.

I would vote a +1 for the kernel driver and command line tool.

I do think that it has merit for user based monitor tools for headless machines.

Biggy2872 · March 30, 2009

Tom please add system beep to the next beta if you find the request acceptable.

It has been discussed many times over the last year such as:

http://lime-technology.com/forum/index.php?topic=2447.0

However it has alot of potential uses.

+1 here...

Cheers,

Matt

JarDo · March 31, 2009

I'd really love to see kernel drivers in support of VPN added so that we can run Hamachi etc...

You can download the slackware package from an Italian site here:

http://www.slacky.eu/index.php?option=com_content&task=view&id=4759&Itemid=56

I haven't tried this - but if you get it to install but it complains of missing libraries, let me know

http://lime-technology.com/forum/index.php?topic=477.msg13028#msg13028

http://lime-technology.com/forum/index.php?topic=477.msg27591#msg27591

Having a secure way to access my files remotely would add a tremendous amount of value to my server.

stephenm00 · March 31, 2009

Fixed

Edited April 21, 2017 by stephenm00

unRAID Server release 4.5-beta3 available

Recommended Posts

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation