unRAID Server Release 6.2.0-beta23 Available

First time using 6.2-beta? please read the Original 6.2-beta Announcement Post first.

IMPORTANT

[*]While every effort has been made to ensure no data loss, THIS IS BETA SOFTWARE.... use at your own risk...

[*]Your server must have access to the Internet to use the unRAID 6.2 beta.

[*]Posts in this thread should be to report bugs and comment on features ONLY.

HOW TO REPORT A BUG

Think you've found a bug or other defect in the beta?  Ask yourself these questions before posting about it here:

[*]Have I successfully tested this bug with all my plugins disabled (booting into safe mode)?

[*]Can I recreate the bug consistently and have I documented the steps to do so?

[*]Have I downloaded my diagnostics from the unRAID webGui after the bug occurred, but before I rebooted the system?

Do not post about a bug unless you can confidently answer "Yes" to all three of those questions.  Once you can, be sure to follow these guidelines, but make sure to post as a reply on this thread, not as a new topic under defect reports (we track bug reports for beta/rc releases independent from the stable release).

INSTALLING AND UPDATING THE BETA

If you are currently running previous 6.2-beta release, clicking 'Check for Updates' on the Plugins page is the preferred way to upgrade.

Alternately, navigate to Plugins/Install Plugin, copy this text into the box and click Install:

https://raw.githubusercontent.com/limetech/unRAIDServer-6.2/master/unRAIDServer.plg

You may also Download the release and generate a fresh install.

RELEASE NOTES

This releases includes fixes for bugs found in -beta22, refer to Change Log below.

Here are the notes for -beta22:

Several package updates and bug fixes, including fix for a deadlock case in the md/unraid driver.  If you have experienced this issue and solved it by increasing the "Tunable (md_num_stripes)" setting, you can now set back to default (set the field to blank and click Apply).  If you happen to see a "hang" which may be attributed to this (still), please type this command:

mdcmd dump

and then post your system log.  This command will cause a few lines of driver debug info to be written into the system log.

In addition we have integrated bonienl's advanced networking configuration.  This is an extremely nice piece of work that brings the ability to configure physical interface segregation as well as VLAN support (including VLAN tagging) -  [glow=red,2,300]thank you![/glow]

updated  Here is a set of slides bonienl put together to show some possible VM use cases.

unRAID Server OS Change Log
===========================

THIS IS BETA SOFWARE
--------------------

While every effort has been made to ensure no data loss, **use at your own risk!**

Version 6.2-beta23 2016-06-11
-----------------------------

Linux kernel:

- added Mellanox config options per user request:
  - MLX5_CORE: Mellanox Technologies ConnectX-4 and Connect-IB core driver
  - MLX5_CORE_EN: Mellanox Technologies ConnectX-4 Ethernet support
  - MLXSW_CORE: Mellanox Technologies Switch ASICs support
  - MLXSW_PCI: PCI bus implementation for Mellanox Technologies Switch ASICs

Management:
  - fix: ensure hwdb is updated for lsusb descriptions

webGui:
  - Fixed regex validation for IPv4 (e.g. 208.67.220.220 now works)
  - Fixed eth0 port status detection and port up/down execution
  - Fixed display on dashboard when parity is invalid
  - VM Manager: add 'virtio-win-0.1.117' and 'virtio-win-0.1.118' to VirtIO-ISOs list
  - VM Manager: add LibreELEC to the template list

Version 6.2-beta22 2016-06-08
-----------------------------

Base distro:

- ca-certificates: version 20160104
- curl: version 7.49.1 (CVE-2016-3739)
- gnutls: version 3.4.13 (CVE-2016-4456)
- kernel-firmware: version 20160601git
- libarchive: version 3.1.2 (CVE-2016-1541)
- libgcrypt: version 1.7.0
- libxml2: version 2.9.4 (CVE-2016-4447, CVE-2016-4448, CVE-2016-4449)
- mesa: version 11.2.2
- mozilla-firefox: version 45.0.2
- ntp: version 4.2.8p8 (CVE-2016-1551, CVE-2016-1549, CVE-2016-2516, CVE-2016-2517, CVE-2016-2518, CVE-2016-2519, CVE-2016-1547, CVE-2016-1548, CVE-2015-7704, CVE-2015-8138, CVE-2016-1550, CVE-2016-4953, CVE-2016-4954, CVE-2016-4955, CVE-2016-4956, CVE-2016-4957)
- openssl: version 1.0.2h (CVE-2016-2108, CVE-2016-2107, CVE-2016-2105, CVE-2016-2106, CVE-2016-2109, CVE-2016-2176)
- php: version 5.6.22 (CVE-2016-3074, CVE-2015-8865, CVE-2016-4073, CVE-2016-4072, CVE-2016-4071, CVE-2016-4070, CVE-2013-7456, CVE-2016-5093, CVE-2016-5094, CVE-2016-5096)
- qemu: version 2.5.1.1 (CVE-2016-3712, CVE-2016-3710)
- samba: version 4.4.4 (CVE-2015-5370, CVE-2016-2110, CVE-2016-2111, CVE-2016-2112, CVE-2016-2113, CVE-2016-2114, CVE-2016-2115, CVE-2016-2118)
- smartmontools: version 6.5

Management:

- allow kernel append parameter 'unraidlabel' to override boot device label (default: UNRAID)
- fix source url in smartmontools drivedb updater script (update-smart-drivedb)
- fix rare deadlock case when there are insufficient free stripes for a large I/O
- support dual-device "swap/disable" function
- Support spaces in docker and libvirt image file paths.

Linux kernel:

- version 4.4.13
- added config options:
  - NIU: Sun Neptune 10Gbit Ethernet support (per user request)
- added VLAN (802.1q) network and bridge support
- updated nbd module option 'max_part' value to 64 (per user request)

webGui:

- docker: bug fix: allow official docker image updates to work
- docker: don't download banner images anymore (banners were removed a while back)
- fix custom setting in Parity Check Schedule
- fix regression error in Browse function
- include year in parity history
- networking: VLAN and multiple ethernet support (Thanks Bergware!)
- numerous cosmetic and typo fixes
- upgraded jQuery to version 2.2.4
- upgraded font-awesome to version 4.6.3
- vm manager: add 'virtio-win-0.1.113' to VirtIO-ISOs list
- vm manager: add '6.0.3' to the OpenELEC versions list
- vm manager: bug fix: don't reset vDisk Location dropdown to 'None' when 'Manual' should be selected
- vm manager: clean up virtio-iso download progress
- vm manager: OpenELEC download folder should default to <domain share folder> if it exists
- vm settings: allow option to remove libvirt image
- vm settings: bug fix: spinning download button

Version 6.2-beta21 2016-04-05
-----------------------------

Base distro:

- at: version 3.1.19
- curl: version 7.48.0
- dbus: version 1.10.8
- glibc-zoneinfo: version 2016c
- kernel-firmware: version 20160401
- libevent: version 2.0.22
- lvm2: version 2.02.148
- php: version 5.6.20
- qemu: version 2.5.1
- samba: version 4.4.0
- sudo: version 1.8.16
- xkeyboard-config: version 2.17

Management:

- Fixed a few bugs in mac version of syslinux
- rc.local: disabled irqbalance service from automatically starting
- Fix container hostpath validation in rc.docker.
- Updated smartmontool drivedb.h
    
Linux kernel:

- added config options:
  - DM_MIRROR: Mirror target (per user request)
- unraid: Fix parity size not checked against size of new device(s) added to existing array.
- unraid: Fix non-present disabled data device size not checked against new parity device size.

webGui:

- Version: 2016-04-05
- VM Manager: add German vnc keyboard choice
- Improved core separation display for AMD cpus on System Devices page
- Fix: Templates not updating
- Fix single line display of non-hyperthreaded cores on Dashboard page
- Make direct link to plugin update optional in notice.  Allows for direct download or redirect to plugin manager
- Show parity history with newest entry at top and oldest entry at bottom
- Add unRAID OS/Dynamix GUI update message in footer
- API for plugins to test and display a new version message
- Force refresh of file when content has changed, and file is viewed in browser
- Check for disk not present in status report
- Group disk types (parity, data, cache) in status report
- Improved core separation on Dashboard page
- Docker: add RO/Slave path option
- Docker: Do not override /config Name or Display for V2 templates
- Docker: remove spaces from container names
- Fixed regression error in Browse function
- vnc viewer: code updates from upstream (Make sure to copy arrays when using render queue)
- Upgraded jQuery to version 2.2.2
- Change min width of navbar items (@anthony0030)
    
Version 6.2-beta20 2016-03-25
-----------------------------

Base distro:

- aaa_elflibs: version 14.2 
- ethtool: version 4.5
- glibc-zoneinfo: version 2016b
- lvm2: version lvm2-2.02.147
- mc: version 4.8.16
- pciutils: version 3.4.1
- pkgtools: version 14.2
- procps-ng: version 3.3.11
- mozilla-firefox: version 45.0.1
- harfbuzz: version harfbuzz-1.2.4
- utempter: version 1.1.6

Linux kernel:

- version 4.4.6
- added missing firmware: ast_dp501_fw.bin
- use out-of-tree drivers:
  - Intel 10Gbit Ethernet driver ixgbe: version 4.3.13
  - Intel 10Gbit Ethernet driver ixgbevf: version 3.1.2
  - Highpoint Rocket r750: version 1.2.4

Management:

- Add halt_poll_ns=0 to kvm.conf - eliminates high cpu overhead in windows 10 [kudos to Eric S. for this!]
- Fix auto-start array
- Fix upgrade process erroneous reference of /boot/config/domains.cfg to /boot/config/domain.cfg
- Quiet extraneous nfs start messages.
- When necessary to query keyserver, poll up to 45 seconds for a connection.

webGui:

- docker: Add Template Authoring Mode. 
- docker: Add the ability to keep templates in sync with the authors modifications
- docker: Fix: wrong variable name prevents config creation
- docker: Set default port mode to TCP and path mode to RW 
- dynamix: Introduce context-sensitive help
- dynamix: Get rid of SMART db update in monitor
- Do not activate context-sensitive help functionality for Docker and VMs pages yet
    
Version 6.2-beta19 2016-03-17
-----------------------------

Base distro:

- fix NFS mounts and warnings about missing IPv6
- removed obsolete 'apmd' and 'portmap' packages
- acpid: version 2.0.26
- docker: version 1.10.3
- cryptsetup: version 1.7.1
- grep: version 2.24
- gtk+3: version 3.18.9
- htop: version 2.0.1
- libdrm: version 2.4.67
- libnl3: version 3.2.27
- lvm2: version 2.02.145
- mozilla-firefox: version 45.0 (console GUI mode)
- mpfr: version 3.1.4
- nettle: version 3.2
- openssh: version 7.2p2
- p11-kit: version 0.23.2
- pciutils: version 3.4.1
- rpcbind: version 0.2.3
- samba: version: 4.3.6
- xorg-server: version 1.18.2

Linux kernel:

- version 4.4.5
- added config options:
  - AMD_IOMMU_V2: AMD IOMMU Version 2 driver
  - INTEL_IOMMU_SVM: Support for Shared Virtual Memory with Intel IOMMU
  - SCSI_HPSA: HP Smart Array SCSI driver [per customer request for testing, may be removed]
- unraid: Correct sync start/end timestamps.
- unraid: Fix device spindown bug.
- unraid: Fix NEW_ARRAY case of Q not set invalid.
- unraid: Refinement in 'invalidslot' handling

Management:

- Certain mount errors can actually leave device mounted, so un-mount if any error detected.
- Change 'color' status of non-present parity devices from 'red-off' to 'grey-off'.
- correctly handle dual-parity "trust parity" flag.
- fix 'bash' error in /etc/rc.d/rc.6 (shutdown) script.
- Fix disks_mounted event generated after svcs_started.
- Get rid of "Identify" operation.
- Incorporate gfjardim suggestion to mark /mnt "shared" for better Docker integration.
- upgrade process now copies/upgrades bzroot-gui and syslinux/syslinux.cfg-

webGui:

- docker: always show the 'Add another Path, Port or Variable' button
- docker: export ports as variable if Network is set to host
- docker: fix 'WebUI' content menu item now hidden when the web ui link is empty
- docker: removed 'Dry Run' button on create/edit container page
- docker: update pop-in dialogs to look better when using the Dynamix black theme
- Do not display unassigned parity devices when array is Started.
- fix context menu to escape non-safe css selector characters
- fix when disk rebuild is complete, notification reports status "Canceled"
- vm manager: Fix cdrom bus type to use SATA when machine type is Q35

Version 6.2-beta18 2016-03-11
-----------------------------

Changes vs. unRAID Server OS 6.1.9.

Base distro:

- switch to 'slackware64-current' base packages
- avahi: version 0.6.32
- beep: version 1.3
- docker: version 1.10.2
- eudev: version 3.1.5a: support NVMe
- fuse: version 2.9.5
- irqbalance: version 1.1.0
- jemalloc: version 4.0.4
- libestr: version 0.1.10
- liblogging: version 1.0.5
- libusb: version 1.0.20
- libvirt: version 1.3.1
- lshw: version B.02.17 svn2588
- lz4: version r133
- mozilla-firefox: version 44.0.2 (console GUI mode)
- netatalk: version 3.1.8
- numactl: version 2.0.11
- php: version 5.6.19
- qemu: version 2.5.0
- rsyslog: version 8.16.0
- samba:
  - version: 4.3.5
  - enable asynchronous I/O in /etc/samba/smb.conf
  - remove 'max protocol = SMB3' from /etc/samba/smb.conf (automatic negotiation chooses the appropriate protocol)
- spice: version 0.12.6
- xorg-server: version 1.18.1
- yajl: version 2.1.0

Linux kernel:

- version 4.4.4
- default iommu to passthrough (iommu=pt)
- kvm: enabled nested virtualization
- unraid: array PQ support (dual-parity)

Management:

- Trial key now supports 6 devices, validates with limetech keyserver
- Pro key supports max 30 array devices, unlimited attached devices
- add 10Gb ethernet tuning in /etc/sysctl.conf
- add tunable: md_write_method (so-called "turbo write")
- array PQ support (dual-parity)
- do not auto-start parity operation when Starting array in Maintenance mode
- libvirt image file handling
- stop md/unraid driver cleanly upon system poweroff/reset
- support NVMe storage devices assignable to array and cache/pool
- support USB storage devices assignable to array and cache/pool
- system shares handling
- misc other improvements and bug fixes

webGui:

- all fixes and enhancements from 6.1.9
- added hardware profile page
- added service status labels to docker and vm manager settings pages
- docker: revamped docker container edit page (thanks gfjardim!)
- docker: now using docker v2 index/repos
- docker: updating a stopped container will keep it stopped upon completion
- dyanmix-6.2: version 2016-03-11
- reverse the negative logic in docker and libvirt image fsck confirmation
- support user specified network MTU value
- vm manager: usb3 controller support, improved usb device sorting and display
- vm manager: integrated virtio driver iso downloader
- vm manager: support nvidia with hyper-v for windows guests
- vm manager: added auto option for vdisk location
- misc other improvements and bug fixes

Wow that was quick installing now

libreelec VM was in beta22, just saying.

 

- added Mellanox config options per user request:

  - MLX5_CORE: Mellanox Technologies ConnectX-4 and Connect-IB core driver

  - MLX5_CORE_EN: Mellanox Technologies ConnectX-4 Ethernet support

  - MLXSW_CORE: Mellanox Technologies Switch ASICs support

  - MLXSW_PCI: PCI bus implementation for Mellanox Technologies Switch ASICs

 

Does this mean Unraid is  now supporting 10GB networking over Mellanox cards?

 

- added Mellanox config options per user request:

  - MLX5_CORE: Mellanox Technologies ConnectX-4 and Connect-IB core driver

  - MLX5_CORE_EN: Mellanox Technologies ConnectX-4 Ethernet support

  - MLXSW_CORE: Mellanox Technologies Switch ASICs support

  - MLXSW_PCI: PCI bus implementation for Mellanox Technologies Switch ASICs

 

 

Does this mean Unraid is  now supporting 10GB networking over Mellanox cards?

The user who requested inclusion of these drivers was not using 10Gb interfaces, but if these same drivers support 10Gbit, then yes (can you verify?).  We already do support Intel 10Gbit.

 

- added Mellanox config options per user request:

  - MLX5_CORE: Mellanox Technologies ConnectX-4 and Connect-IB core driver

  - MLX5_CORE_EN: Mellanox Technologies ConnectX-4 Ethernet support

  - MLXSW_CORE: Mellanox Technologies Switch ASICs support

  - MLXSW_PCI: PCI bus implementation for Mellanox Technologies Switch ASICs

 

 

Does this mean Unraid is  now supporting 10GB networking over Mellanox cards?

 

The user who requested inclusion of these drivers was not using 10Gb interfaces, but if these same drivers support 10Gbit, then yes (can you verify?).  We already do support Intel 10Gbit.

Was looking at the drivers for Mellanox ConnectX-2 EN

Not sure if the drivers will work with this card or not.

 

- added Mellanox config options per user request:

  - MLX5_CORE: Mellanox Technologies ConnectX-4 and Connect-IB core driver

  - MLX5_CORE_EN: Mellanox Technologies ConnectX-4 Ethernet support

  - MLXSW_CORE: Mellanox Technologies Switch ASICs support

  - MLXSW_PCI: PCI bus implementation for Mellanox Technologies Switch ASICs

 

 

Does this mean Unraid is  now supporting 10GB networking over Mellanox cards?

 

The user who requested inclusion of these drivers was not using 10Gb interfaces, but if these same drivers support 10Gbit, then yes (can you verify?).  We already do support Intel 10Gbit.

 

Was looking at the drivers for Mellanox ConnectX-2 EN

 

Not sure if the drivers will work with this card or not.

The kernel config options reads, "Mellanox Technologies 1/10/40Gbit Ethernet support".  As long as it does not rely on an out-of-tree (proprietary) driver, it should work 

Was looking at the drivers for Mellanox ConnectX-2 EN

 

Not sure if the drivers will work with this card or not.

 

The kernel config options reads, "Mellanox Technologies 1/10/40Gbit Ethernet support".  As long as it does not rely on an out-of-tree (proprietary) driver, it should work 

I believe the driver for the ConnectX-2 has been included for a while:

https://lime-technology.com/forum/index.php?topic=39813.0

https://lime-technology.com/forum/index.php?topic=48402.0

oh, no fix for the "pending updates" docker bug

oh, no fix for the "pending updates" docker bug

I believe I saw aptalca mention some specifics about it elsewhere, but I don't think those specifics have been posted here in the beta threads or as a Defect Report.  I've only seen rather abstract mentions here, and some of the mentions appeared to be a container related issue, not necessarily a system bug.

oh, no fix for the "pending updates" docker bug

 

I believe I saw aptalca mention some specifics about it elsewhere, but I don't think those specifics have been posted here in the beta threads or as a Defect Report.  I've only seen rather abstract mentions here, and some of the mentions appeared to be a container related issue, not necessarily a system bug.

it's affecting a container of mine, a couchpotato docker that i wrote.

it's pushed as a complete docker image to dockerhub from my jenkins server.

the docker shows blue as needing an update on restart and when manually checking for updates as well as scheduled checking.

only started doing it with beta22.

oh, no fix for the "pending updates" docker bug

 

I believe I saw aptalca mention some specifics about it elsewhere, but I don't think those specifics have been posted here in the beta threads or as a Defect Report.  I've only seen rather abstract mentions here, and some of the mentions appeared to be a container related issue, not necessarily a system bug.

 

it's affecting a container of mine, a couchpotato docker that i wrote.

it's pushed as a complete docker image to dockerhub from my jenkins server.

the docker shows blue as needing an update on restart and when manually checking for updates as well as scheduled checking.

only started doing it with beta22.

log attached covers the sequence involved.

docker show update ready, click update , nothing is downloaded , check for updates again, shows update is ready.

unraid-nas-diagnostics-20160612-0348.zip

oh, no fix for the "pending updates" docker bug

 

I believe I saw aptalca mention some specifics about it elsewhere, but I don't think those specifics have been posted here in the beta threads or as a Defect Report.  I've only seen rather abstract mentions here, and some of the mentions appeared to be a container related issue, not necessarily a system bug.

 

it's affecting a container of mine, a couchpotato docker that i wrote.

it's pushed as a complete docker image to dockerhub from my jenkins server.

the docker shows blue as needing an update on restart and when manually checking for updates as well as scheduled checking.

only started doing it with beta22.

 

log attached covers the sequence involved.

docker show update ready, click update , nothing is downloaded , check for updates again, shows update is ready.

Yup, I'm getting it with my jdownloader container. It is built on docker hub from the dockerfile. Gui shows an update, but when you hit update it downloads 0 bytes.

cant remember were i read it in the forums but some said that the author  rebuilds the docker on git hub it then works

EDIT

I have this issue with DelugeVPN and also had it with one of my personal dockers. I did a rebuild on docker hub for mine and it fixed the issue, so possibly if binhex forces a rebuild at docker hub might fix it.

In Friday morning, I upgraded from 6.0b21 to b22

On Saturday morning, I found that 2 disks  (Disks 13 & 14) had been disabled

As I had 2 disks disabled, and was worried about lossing data, I replaced disk 13 with a new WD Red 3TB disk, and the array reconstructed itself OK.

On the former disk 13 I ran HGST diagnostics with no faults found, I also run HD Tune which also found no faults. Thereafter I completely erased the disk.

This monring (Sunday), I have updated to b23, and replaced the disabled disk 14 with the former disk 13, however it is disabled as soon as I stop the array.

I guess an a  panic, I have also replaced disk 14 with a new WD Red 3TB disk, and the array is currently rebuilding Ok

I am currently running HD Tune on the former disk 14, which is half way through and showing no errors. I also ensured reseated alll SATA connections

I appreciate that you get the occassional disk red balled, and in the past I have carried out diagnostics on redballed disks, formated them, found no SMART errors and put them back in use in the array.

I don't understand why I have have got 2 disks (of the same make and model) fail at the same time, yet they prove OK using HGST dianostics & HD Tune? I wonder if this a bug with Toshiba (former HGST drives)?

Diagnostics and screenshot to follow, when I work out how to get them below the 192KB limit

Please see attached screenshot

I can't get my diagnostic file (which is over 300KB) below 192KB

Please find attached syslog files I have found within the diagnostic zip file

syslogs.zip

I can't get my diagnostic file (which is over 300KB) below 192KB

 

Please find attached syslog files I have found within the diagnostic zip file

I have managed to get the zip file below 192KB now, I had 2 duplicate syslogs for some reason?

tower-diagnostics-20160611-1105.zip

 

- added Mellanox config options per user request:

  - MLX5_CORE: Mellanox Technologies ConnectX-4 and Connect-IB core driver

  - MLX5_CORE_EN: Mellanox Technologies ConnectX-4 Ethernet support

  - MLXSW_CORE: Mellanox Technologies Switch ASICs support

  - MLXSW_PCI: PCI bus implementation for Mellanox Technologies Switch ASICs

 

 

Hi, i can confirm the intel card i'm using is working fine and for the first time i/m able to allocate IP and set up different nic's  properly via the GUI!! 

many thanks to bonienl for the hard work and LT Team for bringing this headache to an end.

 

here is the screenies ive done this morning on release.  Will be testing the mellanox card in a bit.

 

I was able to quickly set up the new card on unraid and static the IP of both nic's  (dual card-  intel x520da-2  sfp+)

 

 

loving the new network settings GUI!    this is how i set up my 10gb nic, note the ixbe  being seen.

 

https://www.dropbox.com/s/0mraqjjzhifenw5/unraid%2010gb%20settings.jpg?dl=0

 

ping test to check the settings

https://www.dropbox.com/s/f663zhif02911qh/unraid%206.23%2010gb%20ping.jpg?dl=0

 

First test after setting up the share on unraid and on pc.

 

from my gaming PC , an SSD drive (samsung 850evo)  to the UNRAID server via the DAC cable  = 450-70mbps. 

https://www.dropbox.com/s/i6ywk2sdf8p9vjb/unraid%20ssd%20test.jpg?dl=0

 

 

 

RAM deisk test from PC to unraid.

 

https://www.dropbox.com/s/jzj3c8l39egg2ut/unraid%206.23%2010gb%20transfer.jpg?dl=0

 

 

i am a little confised as it achived either score from the transfer,  as i havent set up a cache on the unraid server, and at the moment its currently sitting with 2 disks in the array (1x 500gb wd blue for iso's etc)  (1x 3tb wd red for media share)  both in XFS.  I noticed the other drives that are freshly wiped and ready for the server are 3x 3tb wd reds, and those are unformated as the new beta wants them at btrfs??? hmm

 

surely the 1 wd red can't pull off reads/writes that high?

 

 

 

 

 

The user who requested inclusion of these drivers was not using 10Gb interfaces, but if these same drivers support 10Gbit, then yes (can you verify?).  We already do support Intel 10Gbit.

Was looking at the drivers for Mellanox ConnectX-2 EN

 

Not sure if the drivers will work with this card or not.

 

The kernel config options reads, "Mellanox Technologies 1/10/40Gbit Ethernet support".  As long as it does not rely on an out-of-tree (proprietary) driver, it should work 

 

I believe the driver for the ConnectX-2 has been included for a while:

 

https://lime-technology.com/forum/index.php?topic=39813.0

https://lime-technology.com/forum/index.php?topic=48402.0

here is the ConnectX-2  working,  i got the same transfer speeds from my previous test on intel x520-da2.

In Friday morning, I upgraded from 6.0b21 to b22

 

On Saturday morning, I found that 2 disks  (Disks 13 & 14) had been disabled

 

As I had 2 disks disabled, and was worried about lossing data, I replaced disk 13 with a new WD Red 3TB disk, and the array reconstructed itself OK.

 

On the former disk 13 I ran HGST diagnostics with no faults found, I also run HD Tune which also found no faults. Thereafter I completely erased the disk.

...[snipped]...

I don't understand why I have have got 2 disks (of the same make and model) fail at the same time, yet they prove OK using HGST dianostics & HD Tune? I wonder if this a bug with Toshiba (former HGST drives)?

clevoir, it's natural to feel that when drives happen to fail at the same time we upgrade, the upgrade is suspicious (I assume that's why you're posting here?).  But any time 2 drives fail at the same time, the chances are *extremely* small that it's the drives themselves.  Plus, I can't think of any way that a software upgrade could possibly cause a drive to fail.  By far, the cause is going to be a hardware component common to both drives, such as a common controller, power supply, power splitter, SAS breakout cable, or backframe (can't think of any others).  (By the way, that means the drives themselves are fine!  Not their fault!)  So in my opinion, this is a support issue, confusingly coincident with the upgrade.  Rare, but it happens.

I have managed to get the zip file below 192KB now, I had 2 duplicate syslogs for some reason?

There should have been a syslog.1, or both a syslog.1 and a syslog.2.  What we want is the first 500KB of the syslog with the highest number.  If you have syslog files in /var/log that are named that way and they are huge, run the following command on the largest (adapt as needed for the correct file name, e.g. syslog.1) -

  truncate -s 3M /var/log/syslog.2

That's a small s and a capital M.  Once truncated, grab the diagnostics again.

i am a little confused as it achieved either score from the transfer,  as i havent set up a cache on the unraid server, and at the moment its currently sitting with 2 disks in the array (1x 500gb wd blue for iso's etc)  (1x 3tb wd red for media share)  both in XFS.  I noticed the other drives that are freshly wiped and ready for the server are 3x 3tb wd reds, and those are unformated as the new beta wants them at btrfs??? hmm

 

surely the 1 wd red can't pull off reads/writes that high?

In both cases, you were writing TO the unRAID server.  The Linux kernel automatically caches using all available RAM.

Edit: so your faster result was pure network, RAM to RAM.  The slower test was local disk to RAM, over the network.

Was looking at the drivers for Mellanox ConnectX-2 EN

 

Not sure if the drivers will work with this card or not.

 

The kernel config options reads, "Mellanox Technologies 1/10/40Gbit Ethernet support".  As long as it does not rely on an out-of-tree (proprietary) driver, it should work 

 

I believe the driver for the ConnectX-2 has been included for a while:

 

https://lime-technology.com/forum/index.php?topic=39813.0

https://lime-technology.com/forum/index.php?topic=48402.0

 

here is the ConnectX-2  working,  i got the same transfer speeds from my previous test on intel x520-da2.

I just knew... needed to wait for the first one to show 6 interfaces AND 10G, nice

Some correction was made to MTU handling and there is now proper support for jumbo frames when using VMs and dockers.

I am using a MTU size of 9000 on my internal network and this is working great for me.

Just upgraded from Beta 22 to beta 23 with no issues, all dockers are fine, vms booted and are working as expected

One a side note i've noticed my memory usage has settled a little with this build - on beta 21 and 22 i was noticing my VMs using a lot of extra memory (12gb vm was using 18gb or more) but in this build things seem less drastic with my 12gb vm using 15GB

Is this sort of VM overhead to be expected still or is there perhaps something going wrong? All in my VMs have 22gb allocated to them and are using 28gb (over 3vms, i have included my diagnostics if its useful)

Jamie

archangel-diagnostics-20160612-1339.zip