unRAID Server Release 6.0-beta8-x86_64 Available


limetech

Recommended Posts

Download

 

Disclaimer: This is beta software.  While every effort has been made to ensure no data loss, use at your own risk!

 

UPDATE INSTRUCTIONS: (this is not in the readme.txt file)

 

Putting this first so maybe it will be read....

 

If you are using gfjardim's docker manager plugin from -beta7, please delete its .plg file from /boot/config/plugins.  If you don't then the plugin will install and wipe out all functionality provided by beta8.

 

Next, after Starting array, visit Extensions/Docker.  All you should see is a single section named "Docker settings".  In this section is a field called "Docker image:".  It appears like a greyed-out field - it's not - it's filled with what HTML calls "placeholder" text with an example of what you should enter in here.  Decide where (which disk/share) you want your docker image to exist and what you want to name it, and enter it here.  Examples:

 

/mnt/disk1/docker.img  [docker.img will be created in root of /mnt/disk1]

or

/mnt/disk1/docker/docker.img [directory, aka share, docker must already exist]

 

You don't have to use /mnt/disk1.  Could use /mnt/disk2 or /mnt/cache, etc.

 

You don't have to name it docker.img.  Could be docker1.img or my-docker.img or test-docker.img, etc.

 

You don't have to give it an img extension.  Could give it any extension or no extension.

 

Now click 'Start' to start docker.  Since this is first time starting it will create the image file and mount it at /var/lib/docker.

 

Once you have your new docker volume image set up, you can copy all your existing my-* templates by typing this command:

 

cp /boot/config/plugins/Docker/* /var/lib/docker/unraid-templates

 

After that you can delete /boot/config/plugins/Docker from your flash, or leave it there if you want - it's no longer used.

 

Sorry you will need to re-download all the docker images again.

 

The following is optional, depending on how you set up docker pre -beta8.  It's ok to skip this and deal with it later.

 

Next to get rid of 'docker' directory on cache disk (or btrfs array disk if you did that), it's kind of a pain.  Here's how to do it:

 

(assuming /mnt/cache/docker is your docker volume from beta7)

btrfs subvolume delete /mnt/cache/docker/btrfs/subvolumes/*
rm -r /mnt/cache/docker

 

CHANGES IN THIS RELEASE

 

Besides some bug fixes two main changes:

 

Big change in how docker is managed.  What we're doing is creating "image" files that are formatted using btrfs and loop mounted onto /var/lib/docker.  This is all done by rc.docker.

 

The 'my-template' template files are stored in a directory inside this volume called /var/lib/docker/unraid-templates.  The list of autostarted containers is stored in /var/lib/docker/unraid-autostart.  In other words, not on the flash.

 

When you visit the Extensions/Docker page you will notice a box to enter a Docker image file.  When you click 'Start' the file name you specify will be created and a btrfs file system will be created inside that file.  Next the file is loop mounted onto /var/lib/docker.  You are also able to resize the file (expand only, shrink not supported yet), and scrub (check) the file system.  The default size of "10" (meaning 10GB) seems reasonable to start with.

 

Having separate image files for docker has many advantages.  Let's say you start out and create a 10G image file named, say /mnt/disk1/Volumes/docker.img.  Now you start docker as usual and download all your images, create containers, etc.

 

To backup the entire collection it's only necessary to copy that 10G file somewhere, maybe to /mnt/user/Backups.

 

Similarly you can have a set of image files.  Maybe one where you have everything tweaked just how you want it, and another one that starts out as a copy but maybe you experiment with certain applications.  You can select between these volumes easily through the Docker management page.

 

Other big change you won't see benefit of until -beta9 (or -rc1).  If you visit Extensions/Plugins page you will see now only one 'built-in' plugin named unRAID-OS.  This will be used to update unRaid OS on your flash instead of going through the manual process of downloading zip and copying files to the flash.

 

Soon after this release we will be posting a new webGui github repo that comprises the entire thing.  More on this later...

 

unRAID Server Version 6.0-beta8 Release Notes
=============================================

Please note: THIS IS BETA SOFTWARE.  WHILE EVERY EFFORT HAS BEEN MADE
TO ENSURE NO DATA LOSS, USE AT YOUR OWN RISK.

Summary of changes from 6.0-beta7 to 6.0-beta8
----------------------------------------------
- docker: update to 1.2.0
  docker for unRAID works with loopback mounted btrfs image
  integrate forum user "gfjardim" docker plugin (with permission)
- emhttp: fix handling of blank 'min free space' share setting
- emhttp: use 'mkdir -p' instead of 'mkdir' when creating disk mount points
- shfs: honor cache floor settings for 'unsplittable' paths
- plgMan: support unRAID OS update via Plugins page
- webGui: change Utilities menu to Tools, added Credits, license info


Summary of changes from 6.0-beta6 to 6.0-beta7
----------------------------------------------
- btrfs-progs: update to 3.14.2
- docker: update to 1.1.2
- emhttp: assign any number of slots to array and cache pool
- emhttp: implemented multi-device btrfs cache pool feature
- emhttp: support btrfs, reiserfs, xfs filesystems for array devices
- emhttp: handle multiple key files in /boot/config, but no more keys files in /boot
- emhttp: add indicator for shares that only exist on the cache
- libvirt: update to 1.2.7
- linux: update to version 3.16
  CONFIG_NR_CPUS: changed from 16 to 256
  CONFIG_XFS_FS: include XFS file system
  CONFIG_XFS_POSIX_ACL: include XFS ACL support
  add "pci: Enable overrides for missing ACS capabilities" patch (for KVM vfio/PCI pass-through)
- misc: console coloring for kool kids
- php: update to 5.4.30
  add support for curl, openssl, zlib, bz2 and gmp
- qemu: update to 2.1.0
  add "Enable -cpu option to hide KVM" patch (for Nvidia)
- samba: update to 4.1.11
- shfs: fixed improper handling of cache floor
- slack: added htop-1.0.2
- slack: added xfsprogs-3.1.11
- unraid: correct overlapped I/O logic in driver; remove write-throttling algorithm
- webGui: add "check filesystem" functions on DiskInfo page.
- webGui: several misc. bug fixes

Known issues in this release
----------------------------
- emhttp: removed automatic file system expand when small drive is replaced by bigger drive.
  This will be put back in next release.
- emhttp: certain btrfs pool operations can cause mount to take a looooong time
- slack: bonding driver interaction with dhcpcd is flaky, introduced delay as workaround.
- slack: the time setting "(UTC+10:00) Brisbane" is wrong: Brisbane does not use daylight
  savings time like "(UTC+10:00) Camberra, Melbourne, Sydney".
- slack: no 32-bit executable support (a non-issue?)
- netatalk: update to 3.1.x didn't happen yet
- webGui: help incomplete; a few rough edges remain
- emhttp: any file that is world-readable is accessible via http://Tower/mnt/... (which is to say a
  file can be made non-accessible by making it non-world-readable).


Summary of changes from 6.0-beta5a to 6.0-beta6
-----------------------------------------------
- docker: added support for docker version 1.0.0
- emhttp: support btrfs-formatted cache disk
- linux: update to version 3.15.0
- linux: added more features:
  CONFIG_NR_CPUS: changed from 8 to 16 (number of CPU's supported)
  CONFIG_NUMA: Enable NUMA (Non Uniform Memory Access) support.
  CONFIG_SCSI_MVSAS_TASKLET: Support for interrupt tasklet (improves mvsas performance)
  CONFIG_ALX: Qualcomm Atheros AR816x/AR817x support
  CONFIG_I40E: Intel(R) Ethernet Controller XL710 Family support
  CONFIG_AMD_IOMMU: AMD IOMMU support
  CONFIG_INTEL_IOMMU: Support for Intel IOMMU using DMA Remapping Devices
  CONFIG_INTEL_IOMMU_DEFAULT_ON: Enable Intel DMA Remapping Devices by default
  CONFIG_IRQ_REMAP: Support for Interrupt Remapping
  CONFIG_VFIO: VFIO Non-Privileged userspace driver framework
  CONFIG_VFIO_PCI: VFIO support for PCI devices
  CONFIG_VFIO_PCI_VGA: VFIO PCI support for VGA devices
  CONFIG_CIFS_SMB2: SMB2 network file system support
  CONFIG_NET_9P: Plan 9 Resource Sharing Support (9P2000)
  CONFIG_NET_9P_VIRTIO: 9P Virtio Transport
  CONFIG_9P_FS: Plan 9 Resource Sharing Support (9P2000) 
  CONFIG_9P_FS_POSIX_ACL: 9P POSIX Access Control Lists
  CONFIG_MAGIC_SYSRQ
- slack: updated packages with security advisories:
  curl-7.36.0
  gnutls-3.1.25
  ntp-4.2.6p5
  openssh-6.6p1
  openssl-1.0.1h
  openssl-solibs-1.0.1h
  shadow-4.1.5.1
  libtasn1-3.6
  php-5.4.29
  samba-4.1.6
- slack: added packages:
  btrfs-progs
  libcgroup
  sqlite
- slack: minor fixes in rc.S, rc.M, rc.sshd
- qemu: version 2.0.0 with SeaBIOS 1.7.5
- xen: update to version 4.4.0, with security patches through 6-13-2014.
  Eliminated qemu-system-i386 altogether and now just builds qemu-system-x86-64 (qemu 2.0.0)
  Correct typo in /etc/default/xendomains.


Summary of changes from 6.0-beta4 to 6.0-beta5a
-----------------------------------------------
- emhttp: fix issue generating ini files with single quotes in keys  
- emhttp: support BRSTP variable to enable/disable network bridge STP
- openssl: update to openssl-1.0.1g (heartbleed bug fix)
- php: update to 5.4.26, and
  change search path for php.ini to: /etc/php
  change search path for additional ini files to: /etc/php/conf.d
  in /etc/php/php.ini include this directive:
    auto_prepend_file="/usr/local/emhttp/plugins/webGui/include/local_setup.php"
  local_setup.php defines the timezone and locale so that php scripts don't have to
- slack: initialize /etc/ssl/certs using update-ca-certificates
- sysinfo: added line to display OpenSSL version
- webGui: Network Settings: add control for BRSTP


Summary of changes from 6.0-beta3 to 6.0-beta4
----------------------------------------------
- linux: added more features:
  CONFIG_BLK_DEV_SR: SCSI CDROM support
  DEVPTS_MULTIPLE_INSTANCES: Support multiple instances of devpts
  SCSI_MPT3SAS: LSI MPT Fusion SAS 3.0 Device Driver
  VT_HW_CONSOLE_BINDING: Support for binding and unbinding console drivers 
  CONFIG_SENSORS_F71805F: Fintek F71805F/FG, F71806F/FG and F71872F/FG support
  CONFIG_SENSORS_F71882FG: Fintek F71882FG and compatibles support
  CONFIG_SENSORS_F75375S:  Fintek F75375S/SP, F75373 and F75387 support
- nfs: fixed issue where exported volumes were read-only (needed to explicitly add sec=sys option)
- php: added json support
- samba: update to version 4.0.15 in order to set "acl allow execute always" to "yes" in order to fix 
  windows exe files not executing
- samba: "max protocol = SMB3" is the new default
- slack: added ca-certificates
- slack: added nano editor
- slack: added usb-utils (lsusb command)
- smartmontools: update to version 6.2
- syslinux: remove Xen command line options (user can tune syslinux.cfg via webGui)
- emhttp: fixed bug where blank value for cache 'Min free space' would cause shfs terminate
- emhttp: fixed bug where changing SMB export setting in Active Directory mode caused crash
- emhttp: provide $_GET and $_POST to php scripts
- emhttp: when root password set, only authentiate webGui page access
- emhttp: very simple security for http access to share data (a work in process)
- emhttp: return correct mime type per file extension
- webGui: add syslinux configuration page on 'flash' menu
- webGui: add plugin manager
- webGui: add xen domain manager
- webGui: current list of built-in plugins:
  indexer - Share Browser
  sysinfo - The 'Info' button
  plgMan - Plugin Manager
  vendor - third party utility components
  webGui - the webGui itself
  xenMan - Xen Manager
- xen: update to version 4.3.2


Summary of changes from 6.0-beta2 to 6.0-beta3
----------------------------------------------
- flash: added Xen boot options, multiboot support
- linux: added drivers:
  CONFIG_PATA_AMD: support for the AMD and NVidia PATA interfaces found on the chipsets for Athlon/Athlon64.
  CONFIG_PATA_ATIIXP: support for the ATI ATA interfaces found on the many ATI chipsets.
  CONFIG_PATA_OLDPIIX: support for early PIIX PATA support.
  CONFIG_PATA_PDC2027X: support for Promise PATA pdc20268 to pdc20277 host adapters.
  CONFIG_PATA_VIA: support for the VIA PATA interfaces found on the many VIA chipsets.
  CONFIG_SENSORS_NCT6775: support for the hardware monitoring functionality of the Nuvoton NCT6775F, 
  NCT6776F, NCT6779D and compatible Super-I/O chips.
- linux: fixed issue with hwclock (added RTC support which somehow got left out)
- linux: updated Intel e1000e driver to version 2.5.4
- slack: added more packages, notably python and perl
- slack: added network bridging, including bridge of bonded ethernet NICs
- webGui: added bridge control on Network Settings page
- Xen: version 4.3.1


Summary of changes from 6.0-beta1 to 6.0-beta2
----------------------------------------------
- slack: added missing library: libtasn1
- vsftp: fixed
- webGui: updated to 2014.01.24a to fix issue with updating


Summary of changes from 5.x to 6.0-beta1
----------------------------------------
- linux: version 3.10.24p x86_64 (includes reiserfs 'continuous write' patch)
- linux: include all KVM/Xen virtualization options, including libvirt
- linux: back to using kernel realtek NIC driver r8169
- mailx: version 12.5
- php: upgrade to 5.4.20
- samba: upgrade to 4.0.9
- slack: upgrade to slackware64-14.1
- openssh: version 6.3p1. Host keys are generated and stored in /boot/config/ssh directory. Currently
  configured to allow null passwords (easy to change). telnet still enabled (easy to disable).
- webGui: upgrade to webGui-master


Upgrade Instructions
====================

If you are currently running any previous 6.0-beta
--------------------------------------------------

In general it is only necessary to copy these files from the zip file to the root
of your USB Flash device:
  bzimage
  bzroot
  xen
  readme.txt

Starting in -beta8, docker is configured to make use of a loop
mounted image file for its operation.  This may require you to
re-download your docker containers.

Starting in -beta7, if your Plus or Pro key is located in the root of
your USB Flash device you must move it to the 'config' directory in
order for it to be recognized.


If you are currently running unRAID Server OS release 5.0.x
-----------------------------------------------------------

First backup the content of your USB Flash device to a folder on your PC and then install this
release according to "Installation on a New Flash Device" below.  Before ejecting your flash,
restore the 'config' directory from your back up.


If you are currently running any unRAID Server OS release before 5.0:
---------------------------------------------------------------------

First upgrade to latest 5.x release.  Please refer to upgrade instructions on our wiki:
http://lime-technology.com/wiki/index.php/Upgrade_Instructions


Installation on a New Flash Device
==================================

To make a bootable USB Flash device follow these steps:

If using Windows (XP/Vista/Win7)
--------------------------------
1. Plug your USB Flash device into your Windows PC.

2. Open 'My Computer' (XP) or 'Computer' (Vista/Win7) and right-click your Flash device. Click 'Format...',
   set the volume label to UNRAID and then click 'Start'. Important: the volume label must be set exactly
   to UNRAID (all caps).

3. Click on your Flash device (to open it), click on the zip file (to open it) and drag then entire contents of
   the unRAID Server zip file to the Flash.

4. For Windows XP, click on the file 'make_bootable'.  A DOS window will open and run the 'syslinux' utility on the
   Flash.  For Windows Vista or Windows 7, right-click on the file 'make_bootable' and select 'Run as administrator'.
   The 'syslinux' utility will write the Master Boot Record and create a small hidden file named 'ldlinux.sys' on
   the Flash device, making it bootable.

5. Once again, right-click your Flash device in 'My Computer' or 'Computer' and then click 'Eject'.  Your USB Flash
   device is now ready to boot into unRAID Server OS.

If using Mac OS X
-----------------
1. Plug your USB Flash device into your Mac.

2. Open Disk Utility, select the device and click the Erase tab.  Select Format: MS-DOS (FAT) format, Name: UNRAID
   and then click Erase. Important: the Name (volume label) must be set exactly to UNRAID (all caps).

3. Click on your UNRAID device (to open it), click on the downloaded unRAID Server OS release zip file (to open it),
   click on the un-archived unRAID Server folder that results (to open it), and drag then entire contents
   of the unRAID Server folder to the Flash.

4. Click on the file 'make_bootable_mac' on the device.  A terminal window will open and prompt for your admin
   password.  If the selected device is correct, enter the password and hit return.  The script will proceed to run
   the 'syslinux' utility which will write the Master Boot Record and create a small file named 'ldlinux.sys' on
   the Flash device, making it bootable.  Note: you may see your device disappear and reappear on your
   desktop a few times as the script is running - this is normal.

5. When the script completes, close the terminal window and Eject the device.  Your USB Flash device is now ready
   to boot into unRAID Server OS.

Link to comment
  • Replies 190
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

Okay, but can you please elaborate?

 

Presumably we are still following the instructions to clear out the gfjardm's plg file, but do we need to re-download the docker containers or anything else from Tom's post?

 

Since this is the first updated beta that potentially breaks Docker I want to make sure I understand 100% before I (and others in my situation) take the plunge.

 

 

Link to comment

Great job Tom!

 

One question for you... how are the instructions different for those of us who had a dedicated disk outside of the array for Docker (i.e. not cache drive).

 

Right, if you enter the block device partition (eg, /dev/sdg1) in the field for "Docker image file" it will mount that btrfs partition onto /var/lib/docker.

 

Kept that capability just for you, btw.  Not recommended.

Link to comment

Great job Tom!

 

One question for you... how are the instructions different for those of us who had a dedicated disk outside of the array for Docker (i.e. not cache drive).

 

Right, if you enter the block device partition (eg, /dev/sdg1) in the field for "Docker image file" it will mount that btrfs partition onto /var/lib/docker.

 

Okay, thanks. I will try this tomorrow (it's late and I don't want to f@ck it up right before I am going to bed). :)

 

Thanks for the hard work on getting beta8 out so quickly.

Link to comment

What is the state of automatic file system expansion when a drive is replaced with a larger capacity drive? Is this in beta8 or not until beta9/beta10. Or by release do you mean 6.1?

 

In the posted notes, under 6.0-beta7-x86 64 it states the following.

emhttp: removed automatic file system expand when small drive is replaced by bigger drive.

  This will be put back in next release.

Link to comment

Tom -

 

If a person has a separately mounted btrfs disk (SSD) that currently contains ones Docker containers, you had indicated that the loopback FS would not be required.

 

Please provide direction on installing beta8 for this configuration.

 

Thanks!

Link to comment

All seems to be working great, just re-downloading images now. Thanks!

 

I wasn't 100% sure of the update order but i did the following.

 

Deleted docker plg from plugins.

Updated unraid to beta8 & reboot

Ran btrfs subvolume delete

Started docker and added new img path

Ran  CP for existing template move

Deleted -boot/config/plugins/dockerMan.plg - /Docker-startup.plg  - /dockerMan-2014.08.28.tar.gz

 

 

Link to comment

Sep  1 10:29:38 HomeServer php: /etc/rc.d/rc.docker start
Sep  1 10:29:38 HomeServer php: Creating new image file for Docker:  size: G 
Sep  1 10:29:38 HomeServer php: Not starting Docker: failed to create image file 
Sep  1 10:29:38 HomeServer php: 
Sep  1 10:30:28 HomeServer vsftpd[2653]: connect from 79.182.137.180 (79.182.137.180)
Sep  1 10:30:29 HomeServer vsftpd[2653]: [root] OK LOGIN: Client "79.182.137.180"
Sep  1 10:30:48 HomeServer vsftpd[2656]: [root] OK MKDIR: Client "79.182.137.180", "/mnt/disk1/untitled folder"
Sep  1 10:30:56 HomeServer vsftpd[2656]: [root] OK RENAME: Client "79.182.137.180", "/mnt/disk1/untitled folder /mnt/disk1/docker"
Sep  1 10:31:09 HomeServer vsftpd[2656]: [root] OK UPLOAD: Client "79.182.137.180", "/mnt/disk1/docker/untitled file", 0.00Kbyte/sec
Sep  1 10:31:21 HomeServer vsftpd[2656]: [root] OK RENAME: Client "79.182.137.180", "/mnt/disk1/docker/untitled file /mnt/disk1/docker/docker.img"
Sep  1 10:31:42 HomeServer php: /etc/rc.d/rc.docker start
Sep  1 10:31:42 HomeServer php: Maybe expand image file 
Sep  1 10:31:54 HomeServer php: Not starting Docker: mount error 
Sep  1 10:31:54 HomeServer php: 
Sep  1 10:33:32 HomeServer vsftpd[2656]: [root] OK DELETE: Client "79.182.137.180", "/mnt/disk1/docker/docker.img"
Sep  1 10:33:44 HomeServer php: /etc/rc.d/rc.docker start
Sep  1 10:33:44 HomeServer php: Not starting Docker: /mnt/disk1/docker/ is not a file 
Sep  1 10:33:44 HomeServer php: 
Sep  1 10:37:35 HomeServer vsftpd[2816]: connect from 79.182.137.180 (79.182.137.180)
Sep  1 10:37:35 HomeServer vsftpd[2816]: [root] OK LOGIN: Client "79.182.137.180"

 

Here are some of the important log

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.