limetech Posted March 18, 2016 Share Posted March 18, 2016 First time using 6.2-beta? please read the Original 6.2-beta Announcement Post first. While every effort has been made to ensure no data loss, THIS IS BETA SOFTWARE.... use at your own risk... 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. 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-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 Management (emhttp): - 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 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: Fix device spindown bug. - unraid: Fix NEW_ARRAY case of Q not set invalid. - unraid: Refinement in 'invalidslot' handling 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 (emhttp): - 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 Link to comment
bigjme Posted March 18, 2016 Share Posted March 18, 2016 Upgraded perfectly. In regards to parity 2, the warnings have gone but i now get the following message on boot: unRAID Parity2 message: 18-03-2016 20:44 Notice [ARCHANGEL] - Parity2 returned to normal operation No device identification () Only as tiny one but hey, its something i noticed Keep up the great work, now to try my VM's out Link to comment
limetech Posted March 18, 2016 Author Share Posted March 18, 2016 Upgraded perfectly. In regards to parity 2, the warnings have gone but i now get the following message on boot: unRAID Parity2 message: 18-03-2016 20:44 Notice [ARCHANGEL] - Parity2 returned to normal operation No device identification () Only as tiny one but hey, its something i noticed Keep up the great work, now to try my VM's out Yes I believe that is an artifact due to the upgrade. I don't think it should happen again, but report back if it does. Link to comment
snazz Posted March 18, 2016 Share Posted March 18, 2016 Wasn't called out as a fix or improvement in beta 19, but UnRaid still hangs on boot on one of my systems unless VT-d is explicitly disabled in bios as was my experience with beta 18. It wasn't an issue on the affected hardware platform with 6.1.9. Link to comment
Dephcon Posted March 18, 2016 Share Posted March 18, 2016 Be careful with using HP RAID/HBAs. I've used a number of older DL380s for ceph development and they suck, either using multiple RAID0 to simulate an HBA mode or on the newer models with an official "HBA" mode. the hpsas drivers/cards are absolute shite on ubuntu in my testing. Link to comment
bigjme Posted March 18, 2016 Share Posted March 18, 2016 Be careful with using HP RAID/HBAs. I've used a number of older DL380s for ceph development and they suck, either using multiple RAID0 to simulate an HBA mode or on the newer models with an official "HBA" mode. the hpsas drivers/cards are absolute shite on ubuntu in my testing. So something newer like a LSI SAS 9300-8e seems to work fine with no issues? (The card is direct HBA) Link to comment
HellDiverUK Posted March 18, 2016 Share Posted March 18, 2016 Wasn't called out as a fix or improvement in beta 19, but UnRaid still hangs on boot on one of my systems unless VT-d is explicitly disabled in bios as was my experience with beta 18. It wasn't an issue on the affected hardware platform with 6.1.9. Try updating the BIOS in the machine. VT-d works fine on the three systems I've tried b18 on. Link to comment
jonp Posted March 18, 2016 Share Posted March 18, 2016 Wasn't called out as a fix or improvement in beta 19, but UnRaid still hangs on boot on one of my systems unless VT-d is explicitly disabled in bios as was my experience with beta 18. It wasn't an issue on the affected hardware platform with 6.1.9. Try updating the BIOS in the machine. VT-d works fine on the three systems I've tried b18 on. That or try setting iommu=nopt in your syslinux.cfg file. Link to comment
jjslegacy Posted March 18, 2016 Share Posted March 18, 2016 For both .18 and .19 the array won't auto start. I have to start manually. Not sure if it's my setup or some config I need to change. Also every time I reboot the weburl takes me to the licensing page - is this expected? I hit DONE and nothing ever happens. Link to comment
jonp Posted March 18, 2016 Share Posted March 18, 2016 For both .18 and .19 the array won't auto start. I have to start manually. Not sure if it's my setup or some config I need to change. Also every time I reboot the weburl takes me to the licensing page - is this expected? I hit DONE and nothing ever happens. Please post your diagnostics. Link to comment
snazz Posted March 18, 2016 Share Posted March 18, 2016 Wasn't called out as a fix or improvement in beta 19, but UnRaid still hangs on boot on one of my systems unless VT-d is explicitly disabled in bios as was my experience with beta 18. It wasn't an issue on the affected hardware platform with 6.1.9. Try updating the BIOS in the machine. VT-d works fine on the three systems I've tried b18 on. That or try setting iommu=nopt in your syslinux.cfg file. Thanks for the suggestions. BIOS is already at the latest revision, and iommu=nopt didn't make a difference. Link to comment
Dephcon Posted March 18, 2016 Share Posted March 18, 2016 All my disks are missing now (all on M1015 IT mode) vault13-diagnostics-20160318-1743.zip Link to comment
sparklyballs Posted March 18, 2016 Share Posted March 18, 2016 All my disks are missing now (all on M1015 IT mode) i've got 2 of those in my server and no issues here. Link to comment
Helmonder Posted March 18, 2016 Share Posted March 18, 2016 For both .18 and .19 the array won't auto start. I have to start manually. Not sure if it's my setup or some config I need to change. Also every time I reboot the weburl takes me to the licensing page - is this expected? I hit DONE and nothing ever happens. same here tower-diagnostics-20160319-0518.zip Link to comment
limetech Posted March 18, 2016 Author Share Posted March 18, 2016 Why do we have to keep asking people to post their diagnostics zip file? We have made every effort to make this easy and sanitize personal info, even the names of your shares. I am going to just plain DELETE WITHOUT WARNING posts that talk about problems that don't also include this attachment (unless the problem doesn't let you get the diagnostics). It is a waste of our time dealing with this, and if you don't want to comply, please don't use beta releases. Link to comment
Furby8704 Posted March 18, 2016 Share Posted March 18, 2016 For both .18 and .19 the array won't auto start. I have to start manually. Not sure if it's my setup or some config I need to change. Also every time I reboot the weburl takes me to the licensing page - is this expected? I hit DONE and nothing ever happens. same here +2 dashboard is still showing a blank 2nd parity drive. also webgui glitch still there when removing docker container in safari probably just needs a gui update nfs is back so thats great! Link to comment
Austin808 Posted March 18, 2016 Share Posted March 18, 2016 For both .18 and .19 the array won't auto start. I have to start manually. Not sure if it's my setup or some config I need to change. Also every time I reboot the weburl takes me to the licensing page - is this expected? I hit DONE and nothing ever happens. same here Same Here. Dual Parity System. Diagnostics attached. tower-diagnostics-20160318-1204.zip Link to comment
jjslegacy Posted March 18, 2016 Share Posted March 18, 2016 Diagnostics attached. I currently haven't added a disk for the 2nd parity slot. mjms-diagnostics-20160318-1726.zip Link to comment
limetech Posted March 18, 2016 Author Share Posted March 18, 2016 For both .18 and .19 the array won't auto start. I have to start manually. Not sure if it's my setup or some config I need to change. Also every time I reboot the weburl takes me to the licensing page - is this expected? I hit DONE and nothing ever happens. same here Same Here. Dual Parity System. Diagnostics attached. Thanks for the log. There is a bug that is causing this because you have a static IP address. Will fix in next release. Edit: a workaround would be to put this line in your 'go' file before 'emhttp' is invoked: sleep 5 (But don't forget to remove it once this bug gets fixed) Link to comment
Dephcon Posted March 18, 2016 Share Posted March 18, 2016 All my disks are missing now (all on M1015 IT mode) i've got 2 of those in my server and no issues here. Super weird. I reverted back to beta18, same deal no disks. I reverted further back to 6.1.9 and my cards were detected then upgraded to beta19 with no issues.... Link to comment
limetech Posted March 18, 2016 Author Share Posted March 18, 2016 Diagnostics attached. I currently haven't added a disk for the 2nd parity slot. Thanks for the diagnostics. See my previous reply - same issue. Link to comment
reapola Posted March 18, 2016 Share Posted March 18, 2016 Same issue here with b19 as 18, flash does not mount and therefore OS doesn't load. I've attached a copy of the log dir which should hopefully highlight the issue. Attached file is .tar.bz2 unraid_6.2b19.No_unRAIDlabel_logdir.txt Link to comment
jjslegacy Posted March 18, 2016 Share Posted March 18, 2016 Added this: # Start the Management Utility sleep 5 /usr/local/sbin/emhttp & rebooted Array still didn't auto start New diagnostics attached if it helps. mjms-diagnostics-20160318-1844.zip Link to comment
reapola Posted March 18, 2016 Share Posted March 18, 2016 In reference to the bug report above, here's the capture from ipmi console. Edit: This is with a freshly formatted usb which was formatted and labelled as per spec using windows epxlorer and not rufus as I was previously using. Reverting back to 6.1.9 fixes the issue so must be kernel or driver related. Motherboard is a SuperMicro X10SL7-F (http://www.supermicro.co.uk/products/motherboard/Xeon/C220/X10SL7-F.cfm) and the usb stick is connected to a USB2 port which is as far as I'm aware connected to an Intel® C222 Express PCH controller. Link to comment
Recommended Posts