Leaderboard

Popular Content

Showing content with the highest reputation on 03/20/17 in all areas

  1. You can boot to windows with a passed through NVMe without using clover at all. I've been doing this for a while since the first 6.3 RC. Bear in mind this assumes you're doing a fresh install. The only reason you cant do this natively is that Unraid ships with an older OVMF bootloader for VMs which is before it started supporting NVMe devices. We will just be downloading a referencing a different bootloader so we add support for direct NVMe booting. So basically, build the VM (dont start it yet) and pass through the NVMe device: IOMMU group 41 [144d:a802] 81:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM951/PM951 (rev 01) would be: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x81' slot='0x00' function='0x0'/> </source> </hostdev> Download OVMF firmware from here https://www.kraxel.org/repos/jenkins/edk2/. You want the edk2.git-ovmf-x64-x-xxxxxxxx.xxxxx.xxxxxxxx.noarch.rpm file open with 7zip and drill down until you get to the edk2.git\ovmf-x64\ folder and pull out the OVMF-pure-efi.fd and OVMF_VARS-pure-efi.fd files and put them on an accessible share somewhere. Preferably on a cache only share (be sure to do both). in the xml below, Ive put them in /mnt/user/VMData/Windows10VM. reference the new files in XML (replace the default values): <os> <type arch='x86_64' machine='pc-q35-2.7'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/user/VMData/Windows10VM/OVMF-pure-efi.fd</loader> <nvram>/mnt/user/VMData/Windows10VM/OVMF_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> Boot the VM and go to the boot menu. Change the boot order to the DVD drive as top, NVMe as 2nd. Save and boot from the windows installation ISO. the NVMe drive should show as an available installation target in windows setup. Run through the installation as you normally would and you're done
    2 points
  2. Download Clicking 'Check for Updates' on the Plugins page is the preferred way to upgrade. If the new version does not appear, you can manually update by selecting the Install Plugin tab, paste this URL and click Install: https://raw.githubusercontent.com/limetech/unRAIDServer/master/unRAIDServer.plg Please also read the unRAID OS version 6 Upgrade Notes for answers to common issues that may arise following upgrade. This is another bug fix and security update release: - update openssl - update linux kernel - other small fixes, see below. In addition, we now provide per-share control of OS X fruit optimizations. This setting is located in the SMB Security Settings for each share. The default is "No". If you access shares using SMB with OS X, Finder directory listings can be significantly improved by enabling this optimization. unRAID OS 6.3 is an extensive security and package update release. In particular, we have made numerous changes to harden the unRAID OS webGui against XSS and CSRF vulnerabilities. PREVIOUS unRAID OS RELEASES ARE VULNERABLE TO CSRF/XSS ATTACK AND WE STRONGLY RECOMMEND ALL USERS UPGRADE TO 6.3 Plugin Authors: as posted earlier, your plugin may not function properly depending how how POST requests are handled, see: http://lime-technology.com/forum/index.php?topic=55986.0 Plugin Users: please post issues you find in the appropriate Plugin Support topic. And to reiterate: true plugins (not Docker containers) run as the root user and have full access to everything on your server: Install 3rd party plugins at your own risk. Bugs: As always, if you are reporting a bug new in this release, please attach your diagnostics.zip file downloaded via Tools/Diagnostics unRAID Server OS Change Log =========================== Version 6.3.2 2017-02-16 ------------------------ Base distro: - kernel-firmware: 20170210 - openssl: version 1.0.2k (CVE-2017-3731, CVE-2017-3732, CVE-2016-7055) Linux kernel: - version 4.9.10 - accraid: version 1.2.1-53005 - added Chelsio Ethernet support (user request): - CONFIG_NET_VENDOR_CHELSIO: Chelsio devices - CHELSIO_T1_1G: Chelsio gigabit Ethernet support - CONFIG_CHELSIO_T1: Chelsio 10Gb Ethernet support - CONFIG_CHELSIO_T3: Chelsio Communications T3 10Gb Ethernet support - CONFIG_CHELSIO_T4: Chelsio Communications T4/T5/T6 Ethernet support - CONFIG_CHELSIO_T4VF: Chelsio Communications T4/T5/T6 Virtual Function Ethernet support - added F2FS support (user request): - CONFIG_F2FS_FS: F2FS filesystem support - CONFIG_F2FS_FS_XATTR: F2FS extended attributes - CONFIG_F2FS_FS_POSIX_ACL: F2FS Access Control Lists Management: - emhttp: fixed regression passing ampersands in querystring - update hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt} - webGui: Fix regression adding or changing user account images - webGui: provide per-share "vfs_fruit" optimization control under SMB security settings - webGui: reorganize how the device ids are displayed on the System Devices page Version 6.3.1 2017-02-08 ------------------------ Base distro: - apcupsd: version 3.14.14 (rev2 -- added modbus usb support) - gd: version 2.2.4 (CVE-2016-9317, CVE-2016-6912) - libusb-compat: version 0.1.5 - qemu: version 2.7.1 - samba: version 4.5.5 Linux kernel: - version 4.9.8 Management: - emhttp: fixed spurious "ioctl(SIOCGIFHWADDR): Bad address" appearing on Console - smb: permit NTLMv1 authentication - webGui: Add lsusb info to diagnostics - webGui: Fix regression assigning slots and devices - webGui: Fix regression generating SMART files for diagnostics Version 6.3.0 2017-02-02 ------------------------ Management: - emhttp: added 'svcs_restarting' event - emhttp: include "vfs objects =" line for each share named in generated /etc/samba/smb-shared.conf file - webGui: Fix regression changing display banner - webGui: Fix regression with 'Compute All' on Share page Version 6.3.0-rc9 2017-01-27 ---------------------------- Base distro: - add pv: version 1.6.0 - docker: version 1.12.6 (CVE-2016-9962) - containerd: version 0.2.5 - glibc-zoneinfo: version 2016j - gnutls: version 3.5.8 (CVE-2017-5334, CVE-2017-5335, CVE-2017-5336, CVE-2017-5337) - libpng: version 1.6.27 (CVE-2016-10087) - mozilla-firefox: version 51.0 (CVE-2017-5375, CVE-2017-5376, CVE-2017-5377, CVE-2017-5378, CVE-2017-5379, CVE-2017-5380, CVE-2017-5390, CVE-2017-5389, CVE-2017-5396, CVE-2017-5381, CVE-2017-5382, CVE-2017-5383, CVE-2017-5384, CVE-2017-5385, CVE-2017-5386, CVE-2017-5394, CVE-2017-5391, CVE-2017-5392, CVE-2017-5393, CVE-2017-5395, CVE-2017-5387, CVE-2017-5388, CVE-2017-5374, CVE-2017-5373) - openssh: version 7.4p1 (CVE-2016-10009, CVE-2016-10010, CVE-2016-10011, CVE-2016-10012) - php: version 7.0.15 (CVE-2016-10161, CVE-2016-10162, CVE-2017-5340, CVE-2016-7479, CVE-2016-10158, CVE-2016-10160, CVE-2016-10159) - samba: version 4.5.3 (CVE-2016-2123, CVE-2016-2125, CVE-2016-2126) - update hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt} Linux kernel: - version 4.9.6 - added CONFIG_DRM_I915: Intel 8xx/9xx/G3x/G4x/HD Graphics (but blacklisted to prevent auto-load) Management: - libvirt: disable nested virtualizaton by default - shfs: correct return value of system.LOCATION extended attribute to eliminate bash "warning: command substitution: ignored null byte in input" - webGui: Add BTRFS file system checking notifications - webGui: Avoid wget to cache plugin files and postpone plugin updates - webGui: Capitalize method name in plugin operations. - webGui: Natural sorting of user share names - webGui: Save docker, VM and libvirt logs as .txt files in diagnostics - webGui: Disable filesystem selection when data-rebuild is pending - webGui: Add cache pool BTRFS info (if existing) to diagnostics - webGui: added new Europe/Saratov timezone - webGui: additional XSS and CSRF hardening Version 6.3.0-rc6 2016-12-07 ---------------------------- Base distro: - inotify-tools: version 3.14 - mozilla-firefox: version 50.0.2 (CVE-2016-9078, CVE-2016-9079) - ntfs-3g: version 2016.2.22 - rsyslog: version 8.23.0 Linux kernel: - version 4.8.12 (CVE-2016-8650) Management: - network: must set forwarding delay before setting stp 'on'; need 1 sec delay between stop/start in restart - samba: move OS X "vfs_fruit" optimization from 'global' to individual share settings - shutdown: increase default shutdown delay from 60 to 90 sec; eliminate extraneous console messages - update: hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt} smartmontools/drivedb.h - webGui: add Hibernate option to VM context menu Version 6.3.0-rc5 2016-11-25 ---------------------------- Base distro: - bash: version 4.4.005 - grep: version 2.26 (rev2) - kernel-firmware: version 20161118git - libvirt: version 2.4.0 - mozilla-firefox: version 50.0 - ntp: version 4.2.8p9 (CVE-2016-9311, CVE-2016-9310, CVE-2016-7427, CVE-2016-7428, CVE-2016-9312, CVE-2016-7431, CVE-2016-7434, CVE-2016-7429, CVE-2016-7426, CVE-2016-7433) Linux kernel: - version 4.8.10 (CVE-2016-7039) Management: - add btrfs_check script to facilitate btrfs file system check - bug fix: firefox correctly connects to emhttp port number - samba: include OS X vfs_fruit optimizations by default - shutdown: bug fix: overall shutdown timeout read from wrong cfg file - shutdown: bug fix: saving shutdown timeout value - shutdown: add config setting for overall VM shutdown timeout - update: hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt} smartmontools/drivedb.h - webGui: add filesystem Check for btrfs volumes in Maintenance mode - webGui: add vm shutdown time-out option - webGui: generate VM xml with cpu topology as single-threaded when host cpu is AMD - webGui: special text aside new disks to clear - webGui: split out Europe/Istanbul as its own timezone Other: - make_bootable_linux: use readlink instead of realpath since it is more compatible Version 6.3.0-rc4 2016-11-11 ---------------------------- Base distro: - curl: version 7.51.0 (CVE-2016-8615, CVE-2016-8616, CVE-2016-8617, CVE-2016-8618, CVE-2016-8619, CVE-2016-8620, CVE-2016-8621, CVE-2016-8622, CVE-2016-8623, CVE-2016-8624, CVE-2016-8625) - docker: version 1.12.3 (CVE-2016-8867) - glibc-zoneinfo: version 2016i - grep: version 2.26 - kernel-firmware: version 20161001git - libusb: version 1.0.21 - libX11: version 1.6.4 (CVE-2016-7942, CVE-2016-7943) - libXfixes: version 5.0.3 (CVE-2016-7944) - libXi: version 1.7.8 (CVE-2016-7945, CVE-2016-7946) - libXrandr: version 1.5.1 (CVE-2016-7947, CVE-2016-7948) - libXrender: version 0.9.10 (CVE-2016-7949, CVE-2016-7950) - libXtst: version 1.2.3 (CVE-2016-7951, CVE-2016-7952) - libXv: version 1.0.11 (CVE-2016-5407) - lvm2: version 2.02.166 - mozilla-firefox: version 49.0.2 - mpfr: version 3.1.5 - nano: version 2.7.1 - php: version 7.0.13 - samba: version 4.5.1 Linux kernel: - version 4.8.7 (CVE-2016-7042, CVE-2016-8630, CVE-2016-8633) - md/unraid version: 2.7.1 - make the 'check' command "correct"/"nocorrect" argument case insensitive - mark superblock 'clean' upon initialization Management: - emhttp: add API command cmdStopMover and API status variable shareMoverActive (yes/no) - emhttp: ensure disk shares have proper permissions set even if not being exported - emhttp: fix detecton of unclean shutdown to trigger automatic parity check upon Start if necessary - emhttp: fix mac address not set in avahi afp share advertisement (regression introduced in -rc2) - emhttp: unmount docker/libvirt loopback if docker/libvirt fail to start properly - mover: add start/stop/status subcommands (experimental) - mover: dereference files on user shares to get st_dev/st_ino instead of from shfs stat structure - shfs: eliminate 'use_ino' option dependency (fixes NFS issue on buggy clients) - update: hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt} smartmontools/drivedb.h - webGui: combine PCI Devices and IOMMU Groups on Sysdev page; Sort IOMMU and USB Devices properly - webGui: correct button positions on confirmation dialogs - webGui: correct handling of unclean shutdown detection - webGui: fixed device passthrough for Docker - webGui: fixed Docker/VMs tab stay visible when array is stopped - webGui: fixed some help text typos - webGui: update to font-awesome 4.7.0 Version 6.3.0-rc3 2016-10-22 ---------------------------- Linux kernel: - version 4.8.4 (CVE-2016-5195) Management: - shutdown: additional logging in event of cmdStop timeout Version 6.3.0-rc2 2016-10-19 ---------------------------- Base distro: - docker: version 1.12.2 - containerd: version 0.2.4 - runc: version 1.0.0_rc2 - libseccomp: version 2.3.1 - libvirt-php: 0.5.2 (+ latest from git) - php: version 7.0.12 - usbredir: version 0.7.1 - spice: version 0.12.8 - spice-protocol: version 0.12.12 - imlib2: version 1.4.9 - gd: version 2.2.3 - rsyslog: version 8.22.0 - libfastjson: version 0.99.4 - reverted OVMF firmware back to the version in 6.2 due to user reported issues Linux kernel: - version 4.8.2 - r750: version 1.2.10-16_10_13 - md/unraid: kernel 4.8 API changes; support FUA and SYNC write operation flags Management: - bug fix: Samba listening on the wrong interface in a VLAN-enable config - emhttp: added starting/stopping docker/libvirt events - emhttp: removed 'reboot', 'shutdown', 'changeNetwork' API calls; eliminated emhttp-managed network vars - shutdown: save diagnostics in event of cmdStop timeout - vm manager: add 'virtio-win-0.1.126-2' and 'virtio-win-0.1.126-1' to VirtIO-ISOs list - webGui: Added "Join" notification agent - webGui: Add support for "Notify My Android" notifications - webGui: Fixed: Windows unable to extract diagnostics zip file - webGui: Increased password length to 128 characters - webGui: Interactive Reboot and Shutdown directly invokes '/sbin/reboot' and '/sbin/poweroff' Version 6.3.0-rc1 2016-10-05 ---------------------------- Base distro (primary packages): - btrfs-progs: version v4.7.2 - netatalk: version 3.1.10 - openssl: version 1.0.2j - php: version 5.6.26 - qemu: version 2.7.0 - samba: version 4.5.0 Base distro (secondary packages): - apcupsd: version 3.14.14 - bash: version 4.4.0 - curl: version 7.50.3 - diffutils: version 3.5 - e2fsprogs: version 1.43.3 - etc: version 14.2 - file: version 5.28 - fuse: version 2.9.7 - gawk: version 4.1.4 - gdbm: version 1.12 - glib2: version 2.46.2 - glibc: version 2.24 - glibc: version zoneinfo - glibc-solibs: version 2.24 - gnutls: version 3.4.15 - jemalloc: version 4.2.1 - kmod: version 23 - libtasn1: version 4.9 - libxml2: version 2.9.4 - lvm2: version 2.02.161 - nano: version 2.7.0 - network-scripts: version 14.2 - nfs-utils: version 1.3.4 - openssl-solibs version: 1.0.2j - pkgtools-14.2-noarch: version 13 - reiserfsprogs: version 3.6.25 - util-linux: version 2.28.2 Base distro (desktop GUI packages): - freetype: version 2.6.5 - harfbuzz: version 1.3.0 - libXfont: version 1.5.2 - mesa: version 12.0.2 - mozilla-firefox: version 49.0.1 - xkeyboard-config: version 2.18 - xorg-server: version 1.18.4 Linux kernel: - version 4.7.6 - aacraid: version 1.2.1-52011 - intel 10Gbit ethernet: revert to in-tree drivers - r750: version 1.2.9-16_09_27 - md/unraid: Fix bug where case of no data disks improperly detected. Management: - bug fix: For file system type "auto", only attempt btrfs,xfs,reiserfs mounts. - bug fix: For docker.img and libvirt.img, if path on /mnt/ check for mountpoint on any subdir component - bug fix: During shutdown force continue if array stop taking too long. - bug fix: Handle case in 'mover' where rsync may move a file but also return error status. - webGui: Add "Shutdown time-out" control on Disk Settings page. - webGui: bug fix: Cannot manually specify virtIO iso in VM settings - webGui: other changes: refer to github commit log
    1 point
  3. <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/virtualisation/vm/unraid-vm/disk1.img'/> <target dev='hdd' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> That's what I'm using.
    1 point
  4. SMART for that disk looks OK. So did you try to rebuild the disk as it instructs in that wiki? That is the way to get it enabled again.You can rebuild it to itself. https://lime-technology.com/wiki/index.php/Troubleshooting#Re-enable_the_drive
    1 point
  5. OOM errors started when the mover ran, I had a similar one recently and from what I've read they are quite common with kernels 4.8 and 4.9, apparently fixed on kernel 4.10, but unRAID is still on 4.9. Since then I decreased my RAM cache and so far no more OOM errors, you could try the same, manually or using the Tips and Tweaks plugin. Values to change are vm.dirty_background_ratio and vm.dirty_ratio, default is 10 and 20, I set mine to 1 and 2 just to see if it would help and for now they are still like that.
    1 point
  6. Also, while I agree with your first statement, that SSL is an improvement for local security, I really don't see a good reason to expose the admin UI to the internet without a VPN, even when we get SSL. Security is hard to get right, we have to be perfect all the time and the bad guys only have to get lucky once. The more layers the bad guys have to penetrate to get to my private data the better. A good VPN is just good security practice.
    1 point
  7. In my experience restarts such as these are caused by a power supply that is either going or overloaded, but can be other items also. I would start by shutting down all dockers and VM's and see if that brings stability to your system. If it does bring one back at a time to test for stability until you find the culprit. As for the power supply, what type and voltage is it, and the 12V rail amperage? Do you have any maintenance scheduled to occur that would spin up your disks (mover ect.)prior to the computer restarting? Looking through your smart reports you have around 3 disks that have reported errors. I haven't spent time educating myself on these yet, but they look like they happened a while ago. I have know idea on the call trace, and nobody cared found on your server means.
    1 point
  8. Sorry...but that is starting to no longer be a valid excuse.
    1 point
  9. Oh, I'm very familiar with OpenVPN on Android, use it all the time. But you clearly haven't met Mrs CHBMB who wouldn't quite see it as "It's only an app to open"
    1 point
  10. I get the same message with the same mobo and cpus. I don't see any issues with USB, so I'm not too worried either... Also, there are no stable Bios updates available. asRock has sent me a few beta bioses to try and fix a false CPU critical temp sensor event (to no avail), but I believe the message still appears in my log.
    1 point
  11. It's USB related, if all is working normally it should be mostly harmless, look for a board bios update, it can help.
    1 point
  12. After successfully bricking the Fujitsu D2607 by downflashing it I'm proud to be able to contribute to this thread and hereby report: LSI MegaRAID with SAS2008 chipsets 3) DELL Perc H310 as well as H200 Flashed successfully to LSI9211-8i IT (P20) 3TB Drive Support with this card: YES (UPDATE: 5.0Beta7 added 3TB Drive support) Drive Spin Down support: YES (UPDATE: Added as of 5.0Beta7) Drive Temp Readings: YES Toolset_PercH310 to LSIMegaraid.zip (DOS, via bootable usb key) http://www45.zippyshare.com/v/51016808/file.html (for some reason I can't embed the link...) MD5:80174075959fb7d1ff8c6362f7241bfe Update on 06.08.2014 Included the P19 firmware http://www21.zippyshare.com/v/9541812/file.html Update on 01.12.2014 Possible issues with P20 firmware! See this post and this. Update on 23.10.2015 There is an new version of Avago (former LSI) P20 (20.00.04.00) which seems to be OK with unRAID. See this post. Update on 15.09.2015 User opentoe found out that the DELL IT firmware is also working with unRAID. It's your decision what to flash. Flashing DELL firmware is easier and supported by DELL! opentoe's verdict on DELL IT or Avago (former LSI). Update on 07.06.2016 There is a new firmware from Avago. P20.00.07.00 The toolset has been updated accordingly. First impressions. http://www3.zippyshare.com/v/xZKIOHaz/file.html https://www.mediafire.com/?8f82hx4c032a929 MD5: 24f7d428292e00f9dee6f715d8564202 Update on 30.12.2016 Firmware is still P20.00.07.00 Switch to RUFUS for bootdisk creation. Added alternative ways to extract controller info if MegaCli is not working. https://www.mediafire.com/?9cbklh4i1002n23 MD5: 7d90f84c831e8b939c5536d9eb03ba81 Update on 23.02.2017 Firmware is still P20.00.07.00 Uses sas2flsh through the whole process. Tested on a "backflashed" H200, to be confirmed on a stock H200 card and on H310's. Card backup is now dumping the full flash. This can be used to restore the initial condition of the card. Added script for automatic SAS address extraction. No reboot necessary any more. https://www.mediafire.com/?0op114fpim9xwwf MD5: 2fbe3d562846e493714a9e8ac3f15923 Due to missing UEFI environment, no changes nor testing with UEFI shell. Update on 30.03.2017, v2 Firmware is still P20.00.07.00 Spiced up the routines with some checks to automatically select the right tool if one is not working. Tested on a stock H310 as well as a H200 - works for me. Post your experience in the forum. https://www.mediafire.com/?6b77v4s7czluvs2 MD5: 6cb92336ff537aeb838085a028aa6601 Update on 11.04.2017, v3 Firmware is still P20.00.07.00 Added files for use in an EFI environment. Untested due to missing hardware. Post your experience in the forum. https://www.mediafire.com/?9ovj2rxuaf43wv4 MD5: t.b.d. Update on 17.04.2017, v4 <--- this is the latest, use this one! Firmware is still P20.00.07.00 Corrections for EFI environment. Untested due to missing hardware. Post your experience in the forum. https://www.mediafire.com/?py9c1w5u56xytw2 MD5: t.b.d. If you experience the "failed to initialize PAL" error somewhere in step 5, you have to boot from UEFI shell and try again or use another mainboard. See here how to use UEFI shell (Kudos 2 Maglin). Make sure you read and understand the __READMEFIRST.txt before starting! If you experience troubles or something is not clear, don't hesitate to ask for help. You can help improving the howto by doing so. Chances are small but you can brick the controller!
    1 point