unRAID Server Release 4.6-rc3 Available


limetech

Recommended Posts

Download

 

For -rc3:

 

o Added updated hdparm, smartmontools, and memtest.  See release notes below.

o 3rd Party Add-On Developers.. please ensure your existing add-ons work with this release.

 


 

This is a maintenance release to fix a "kernel oops" (ie, crash).

 

First, sorry about the ill-fated 4.5.7/4.5.8 releases.  I am committed to maintaining backward compatibility with 3rd party add-ons insofar as possible, and am now taking the advice of many here by producing "release candidates" prior to releasing a "final" version.

 

So for this "do over", I decided to increment the minor number, hence 4.6-rc1.  In addition, 4.5.7/4.5.8 have been taken down from the Download page.  [if you downloaded 4.5.7 or 4.5.8, it's ok to keep running with those (your data is safe), but you may see some "anomalies" in the system log and/or user interface, especially with some 3rd-party add-ons.]

 

Should you eventually update to 4.6 "final"?  Yes, since the "kernel oops" bug fix, though not seen by vast majority of h/w configs, can occur, so I suggest you update.

 

The release definitions are now:

- A "beta" release will have a "-betaN" suffix.  As features are implemented for a new release, they are "phased in" as a series of beta releases.  At some point, once all planned new features are implemented, the release changes to a "release candidate".

- A "release candidate" will have a "-rcN" suffix.  A release candidate is essentially a "feature freeze" of the code.  Users in the Community are encouraged to try out release candidates in an effort to eliminate lingering bugs.  At some points, the "latest" release candidate will have only the version identifier changed, and will become the "final" version.

- Only "final" versions are shipped by Lime Tech in server products.

 

I will monitor this thread, along with the old 4.5.8 thread for bug/incompatibility reports.  So a question to the Community: how long should a release candidate go without new issue reports before becoming a "final" version?  I would like to close out the 4.x series by this Friday, 19 Nov., but perhaps not wide enough window?

 

unRAID Server 4.6-rc3 Release Notes
===================================

Changes from 4.6-rc2 to 4.6-rc3
-------------------------------

Other:
- More unRaid driver/3rd part add-on backward-compatibility fixes.
- Update 'hdparm' to version 9.27
- Update 'smartmontools' to version 5.39.1
- Update 'memtest' to version 4.10 [Note: you will need to move the file 'memtest' from the zip file to the root of your Flash device]


Changes from 4.6-rc1 to 4.6-rc2
-------------------------------

Other:
- Restore "diskNumber" and "rdevNumber" driver vars.


Changes from 4.5.6 to 4.6-rc1
-----------------------------

Bug fixes:
- Fix for kernel oops of the following type:
  "Tower kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod]"

Other:
- Make unRaid driver "status" command a no-op and patch '/root/mdcmd' script to properly handle a "status" command for backward compatibility.
- Restore backward-compatibility with 4.5.6 in regards to 3rd party add-ons.


Changes from 4.5.5 to 4.5.6
---------------------------

Sorry, the 4.5.5 release package got built wrong which resulted in bugs listed below.

Bug fixes:
- Fixed problem with restoring timezone setting upon reboot.
- Fixed missing reiserfsprogs.


Changes from 4.5.4 to 4.5.5
---------------------------

Bug fixes:
- Fixed 'Mover logging' control in webGui.

Other:
- Added better timezone support.
- Increase supported array width from 20 to 21 drives.
- Add 'Are you sure?' prompt to the 'initconfig' command.
- Added IPMI support, I2C support, and Intel 82801 support.
- During parity-check, the first 20 sync errors are output to the system log.
- If directory named 'extra' exists in root of Flash, invoke 'installpkg' on all files found there before invoking the 'go' script.
- Add 'removepkg' and 'explodepkg'.
- Added 'bzip2'.
- Upgrade reiserfsprogs to version 3.6.21


Changes from 4.5.3 to 4.5.4
---------------------------

Bug fixes:
- Fix (another) problem where formatted data disks could appear 'unformatted' immediately following array start.  This one was due to race condition where md devices could possibly not exist before management utility issues 'mount'.

Other:
- Generate additional logging information during 'mount'.
- Added additional "safeguards" in the code handling 'format' operations.
- Removed 'Restore' button from webGui, replacing with new shell command called 'initconfig'.
- Updated mc (midnight-commander) utility to slackware's 2010-02-06 version.


Changes from 4.5.2 to 4.5.3
---------------------------

Other:
- Update linux kernel to 2.6.32.9
- Enable SMT (Hyperthreading) scheduler support in kernel.
- Update linux udev subsystem to 1.41.
- Fix problem reading USB Flash device model & serial number with some motherboads.
- Added USB FTDI Single Port Serial Driver per user request.


Changes from 4.5.1 to 4.5.2
---------------------------

Bug fixes:
- Fix problem where device assignment via webGui could fail if device identifier is too long.

Other:
- Added SCST subsystem (see http://scst.sourceforge.net) in order to support Marvell 88SE63xx/64xx/68xx/94xx SAS controller-based cards.
- Added 'COPYING' file in release that includes text of the GPL version 2.


Changes from 4.5 to 4.5.1
-------------------------

Bug fixes:
- Fix javascript bug checking valid settings on the Settings page.
- Fix bug where a disk can appear 'Unformatted' immediately after array Start.
- Change unmount polling rate from 1 second to 5 seconds when Stopping the array when external extensions still have a disk or use share mounted.

Other:
- Updated linux kernel to version 2.6.31.12
- Updated Samba to version 3.4.5
- Added Areca driver.
- Added Marvell legacy PATA support.
- Added USB printer support.


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

In addition to below, if the Change log indicates 'memtest' version upgrade, please copy the following file from the new release to the root of your Flash device:
    memtest

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.

Link to comment
  • Replies 67
  • Created
  • Last Reply

Top Posters In This Topic

So I assume that newbies like me should wait until the grown ups have decided that this release is okay to run with?. I have 4.5.6 installed and have had no issues but it would be nice to get rid of the HDIO..nonsense on the log.

 

Fixes the HDIO_GET_IDENTITY errors with Supermicro SAS controller.

 

 

Link to comment

Upgraded to get rid of the HDIO_GET_IDENTITY errors.  With the new version, my ability to access the fan control device has disappeared.  The  /sys/class/hwmon directory (and everything under it) is not there with the upgrade.

 

What version were you running before where /sys/class/hwmon was present?

Link to comment

I have been running 5.0b2 and tried to move to 4.6rc3 in order to confirm myMain works with 4.6rc3.  After boot, the emhttp GUI is prompting for a password.  I cannot telnet into the server, as root appears to have a password (which it should not). 

 

I never did run the big permissions script (instead used Samba shares with the security settings that let me access my disks), so thought I would be able to move back.

 

Is there a way I could move back to a pre 5.0 version?

 

 

Link to comment
4.5.6.  Downgrading back to 4.5.6 brought back fan control.

 

You may need to modprobe the it87 driver.... some newer mobos have partial compatibility with it87, but really need a newer driver, and if it87 is built into the kernel, you can't unload it, so a request was mode to leave the instrumentation drivers like it87 as modules, so you need to modprobe them.

 

 

Link to comment

Hello I just upgraded to RC3 and I Get this line in the LOG. I don’t know if it is good or bad but I have never seen this with other versions.

 

Nov 23 20:21:00 Dragon-Tower atd[1665]: Exec failed for mail command: No such file or directory

 

I have attached a syslog.

 

Besides this everything is good so far.

 

You are probably invoking something via "at" and it is attempting to send status mail saying it ran.  unRAID does not have an e-mail command.  The message has been there for a very long time, you probably did not notice it.
Link to comment

I would like to close out the 4.x series by this Friday, 19 Nov., but perhaps not wide enough window?

 

It's already 23 November and Friday it is the 26 of November or I'm missing something?

That was a copy and paste from last week.

 

Ah, ok. I started to doubt myself.

Link to comment

4.5.6.  Downgrading back to 4.5.6 brought back fan control.

 

You may need to modprobe the it87 driver.... some newer mobos have partial compatibility with it87, but really need a newer driver, and if it87 is built into the kernel, you can't unload it, so a request was mode to leave the instrumentation drivers like it87 as modules, so you need to modprobe them.

 

 

 

So I ran  sensors-detect and got:

# sensors-detect revision 5337 (2008-09-19 17:05:28 +0200)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no): YES
Probing for PCI bus adapters...
Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.
Sorry, no supported PCI bus adapters found.

If you have undetectable or unsupported I2C/SMBus adapters, you can have
them scanned by manually loading the modules before running this script.

To continue, we need module `i2c-dev' to be loaded.
Do you want to load `i2c-dev' now? (YES/no): YES
Module loaded successfully.

We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.

Next adapter: SMBus I801 adapter at 0400 (i2c-0)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x18
Probing for `Analog Devices ADM1021'...                     No
Probing for `Analog Devices ADM1021A/ADM1023'...            No
Probing for `Maxim MAX1617'...                              No
Probing for `Maxim MAX1617A'...                             No
Probing for `Maxim MAX1668'...                              No
Probing for `Maxim MAX1805'...                              No
Probing for `Maxim MAX1989'...                              No
Probing for `Maxim MAX6655/MAX6656'...                      No
Probing for `TI THMC10'...                                  No
Probing for `National Semiconductor LM84'...                No
Probing for `Genesys Logic GL523SM'...                      No
Probing for `Onsemi MC1066'...                              No
Probing for `Maxim MAX1618'...                              No
Probing for `Maxim MAX1619'...                              No
Probing for `National Semiconductor LM82/LM83'...           No
Probing for `Maxim MAX6654/MAX6690'...                      No
Probing for `Maxim MAX6680/MAX6681'...                      No
Probing for `National Semiconductor LM64'...                No
Client found at address 0x1a
Probing for `Analog Devices ADM1021'...                     No
Probing for `Analog Devices ADM1021A/ADM1023'...            No
Probing for `Maxim MAX1617'...                              No
Probing for `Maxim MAX1617A'...                             No
Probing for `Maxim MAX1668'...                              No
Probing for `Maxim MAX1805'...                              No
Probing for `Maxim MAX1989'...                              No
Probing for `Maxim MAX6655/MAX6656'...                      No
Probing for `TI THMC10'...                                  No
Probing for `National Semiconductor LM84'...                No
Probing for `Genesys Logic GL523SM'...                      No
Probing for `Onsemi MC1066'...                              No
Probing for `Maxim MAX1618'...                              No
Probing for `Maxim MAX1619'...                              No
Probing for `National Semiconductor LM82/LM83'...           No
Probing for `Maxim MAX6654/MAX6690'...                      No
Probing for `Maxim MAX6680/MAX6681'...                      No
Client found at address 0x48
Probing for `National Semiconductor LM75'...                No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Dallas Semiconductor DS1621/DS1631'...         No
Probing for `Maxim MAX6650/MAX6651'...                      No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                No

Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no): YES
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM78-J' at 0x290...     No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No
Probing for `IPMI BMC KCS' at 0xca0...                      Success!
    (confidence 4, driver `ipmisensors')
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): YES
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       Yes
Found `Winbond W83627DHG Super IO Sensors'                  Success!
    (address 0xa10, driver `w83627ehf')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No
Trying family `ITE'...                                      No

Some south bridges, CPUs or memory controllers may also contain
embedded sensors. Do you want to scan for them? (YES/no): YES
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD K10 thermal sensors...                                  No
Intel Core family thermal sensor...                         No
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal and voltage sensors...                       No

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `ipmisensors' (should be inserted):
  Detects correctly:
  * ISA bus, address 0xca0
    Chip `IPMI BMC KCS' (confidence: 4)

Driver `w83627ehf' (should be inserted):
  Detects correctly:
  * ISA bus, address 0xa10
    Chip `Winbond W83627DHG Super IO Sensors' (confidence: 9)

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): NO
To load everything that is needed, add this to one of the system
initialization scripts (e.g. /etc/rc.d/rc.local):

#----cut here----
# You must also install and load the IPMI modules
modprobe ipmi-si
# Chip drivers
# Warning: the required module ipmisensors is not currently installed
# on your system. For status of 2.6 kernel ports check
# http://www.lm-sensors.org/wiki/Devices. If driver is built
# into the kernel, or unavailable, comment out the following line.
modprobe ipmisensors
modprobe w83627ehf
/usr/bin/sensors -s
#----cut here----

If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones! You really
should try these commands right now to make sure everything is
working properly. Monitoring programs won't work until the needed
modules are loaded.

 

issuing:

modprobe w83627ehf

/usr/bin/sensors -s

 

got the fan control working again.  So would I just put those two lines in my go file and be good?  Also, is there any benefit to adding the lines for the IPMI drivers as well?

 

Link to comment

I install rc3 earlier tonight and then started a disk upgrade.  I have upgraded 3 or 4 disks over the past week on earlier revs and was getting around 60Mb/sec for all those rebuilds.  Now I am getting about 23mb/ sec on this new drive.

 

Drive is on the same card, next slot from an identical disk that just finished rebuilding earlier today at double the speed.  Syslog shows no errors, nothing is running in the background...  Anyone else seeing this speed differential with rc3?

Link to comment

I have been running 5.0b2 and tried to move to 4.6rc3 in order to confirm myMain works with 4.6rc3.  After boot, the emhttp GUI is prompting for a password.  I cannot telnet into the server, as root appears to have a password (which it should not). 

 

I never did run the big permissions script (instead used Samba shares with the security settings that let me access my disks), so thought I would be able to move back.

 

Is there a way I could move back to a pre 5.0 version?

 

 

 

5.0 uses 'shadow' password system so you should delete (or move somewhere to preserve) these files one the flash and then reboot:

- passwd

- shadow

- smbpasswd

 

This will drop all your defined users however.

Link to comment

I install rc3 earlier tonight and then started a disk upgrade.  I have upgraded 3 or 4 disks over the past week on earlier revs and was getting around 60Mb/sec for all those rebuilds.  Now I am getting about 23mb/ sec on this new drive.

 

Drive is on the same card, next slot from an identical disk that just finished rebuilding earlier today at double the speed.  Syslog shows no errors, nothing is running in the background...  Anyone else seeing this speed differential with rc3?

 

Nothing that changed accounts for this.  You can try the rebuild under 4.5.6 to see if speed is faster.

Link to comment
Guest
This topic is now closed to further replies.