Important: If you want to report an issue, please start a new topic in this board.

 

UEFI support (-rc4)

A new directory is included on the USB flash boot device called 'EFI'.  The presence of this directory along with its contents, and along with some

additional linux kernel options permit UEFI boot.  This is done in such a way that you could choose either BIOS (legacy) or UEFI to boot off your USB flash device.

 

If you update your server using Check for updates on the Plugin page, the EFI directory and files will be automatically created on your USB flash boot device.  If you prepare a new USB flash using this release, the EFI directory and files will also be included.  If you use the "manual" method of updating by copying the bz* files from the release zip, beware you will need to manually also copy over the EFI directory (and modify the first line of syslinux.cfg and copy it to EFI/boot directory).

 

As a consequence of being able to use either boot method, the 'syslinux.cfg' file needs to be maintained in two places:

• syslinux/syslinux.cfg
• EFI/boot/syslinux.cfg

When a  webGui operation modifies syslinux/syslinux.cfg it also copies it to EFI/boot/syslinux.cfg.  Hence the syslinux/syslinux.cfg is considered the "master" copy independent of the actual boot mode.  Normally this is of no consequence but if you manually edit this file you should be aware of this behavior.

 

Note: some motherboards may present a strongly worded warning along the lines of "The system found unauthorized changes on the firmware, operating system or UEFI drivers."  In this case look for a "Secure Boot" BIOS setting and change to "Other OS".

 

Improved shfs/mover (-rc1)

 

The LimeTech user share file system (shfs) has been improved in two areas.  First, we now make use of FUSE read_buf/write_buf methods.  This should result in significant throughput increases.  Second, the mover script/move program no longer uses rsync to move files/directories between the cache pool and the parity array.  Instead the move program invokes a new shfs ioctl() call.  This should result in complete preservation of all metadata including atime and mtime.

While this function has been fairly extensively tested, please keep an eye on mover activities - there shouldn't be any data loss, but it's a fairly significant code change.

Also note: the /mnt/user0 mount point is no longer needed and has been removed.

 

nginx http server (-rc1)

We now use the nginx webserver as the front-end to the unRAID OS Management Utility (aka, webGui).  The emhttp process has been changed to a daemon (emhttpd) listening at a unix socket.  Incorporating nginx provides several features:

• Multi-threaded access, though emhttpd is still single-threaded.
• https (SSL) support.  At present unRAID OS will generate a self-signed certificate.  https works but you will get a scary warning from your browser about not being able to verify the certificate.  No worries.
• nchan (websocket) support.  We have only just begun the process of converting many of the browser javascript polling functions to an event-driven websocket paradigm.  This opens the door for  us to create something like a process manager where we can have several background operations in process, all monitored in real-time via webGui dashboard.

 

enabling https (-rc3)

To enable https support it's necessary to edit your 'config/go' file on your USB flash boot device.  Use the -p option to specify the port(s) and optionally include the -r option to redirect http request from your browser to using https.  Here's the detailed usage:

# Usage:
#   emhttp [-r] [-p port [,sslport]] [OPER]

# OPER is start or stop.  Default is start.
# By default nginx will be setup to listen only at port 80 (http).
# The -p option may be used to define different listening ports and/or setup nginx
# to listen at a specified port for https.  The -r option may be used to setup
# nginx so that any http request is redirected to https (this requires that both
# ports have been specified with -p option).  For example, to have nginx listen
# at both standard ports but redirect all http to https use:
#   emhttp -rp 80,443
# To listen at only port 443 use:
#   emhttp -p ,443

# Note: the stop operation is only "safe" if the array has already been stopped
# (this will be fixed).

 

linux 4.11 kernel (-rc1) - should provide better Ryzen support among other improvements.

 

IPv6 support (-rc1)

We want to again, give a big "thank you" to bonienl who has greatly improved unRAID OS networking with the addition of IPv6 support.  Give it a try and report any issues.

 

Other (-rc1)

• Two new webGUI themes: Azure and Gray.  Again, thanks to bonienl.
• Expanded driver support (QLogic) and more hardware monitoring support.
• Kernel modules and firmware are left on the Flash in a squashfs loopback and loaded into RAM on demand.
• Many more misc. improvements

 

Version 6.4.0-rc4 2017-06-17

Linux kernel:

• version 4.11.6
• added EFI kernel options:
  • CONFIG_EFI: EFI runtime service support
  • CONFIG_EFI_STUB: EFI stub support
  • CONFIG_EFIVAR_FS: EFI Variable filesystem
  • CONFIG_FB: Support for frame buffer devices
  • CONFIG_FB_EFI: EFI-based Framebuffer Support
  • CONFIG_FB_VESA: VESA VGA graphics support
  • CONFIG_FRAMEBUFFER_CONSOLE: Framebuffer Console support
• changed several components from built-in to module:
  • CONFIG_9P_FS: Plan 9 Resource Sharing Support (9P2000)
  • CONFIG_BLK_DEV_NBD: Network block device support
  • CONFIG_CIFS: CIFS support (advanced network filesystem, SMBFS successor)
  • CONFIG_EXT4_FS: The Extended 4 (ext4) filesystem
  • CONFIG_HFSPLUS_FS: Apple Extended HFS file system support
  • CONFIG_NFSD: NFS server support
  • CONFIG_NFS_FS: NFS client support
  • CONFIG_NFS_V2: NFS client support for NFS version 2
  • CONFIG_NFS_V3: NFS client support for NFS version 3
  • CONFIG_REISERFS_FS: Reiserfs support
  • CONFIG_VMXNET3: VMware VMXNET3 ethernet driver
  • CONFIG_XEN_BLKDEV_FRONTEND: Xen virtual block device support
  • CONFIG_XEN_NETDEV_FRONTEND: Xen network device frontend driver
  • CONFIG_XFS_FS: XFS filesystem support
• other:
  • CONFIG_PMIC_OPREGION: PMIC (Power Management Integrated Circuit) operation region support

Management:

• added syslinux EFI boot files; update plugin to create populated EFI directory upon upgrade
• mover: there are legit reason we cannot rmdir, so do not log these cases
• php-fpm: change log_level from default (notice) to (warning) to quiet down "child exited with code 0" messages
• webgui: Revert uppercase to boldcase in themes AZURE and GRAY
• webgui: Fixed regression error in display of custom banner introduced in rc3
• webgui: Added theme support in popup windows; other 6.4 related theme changes
• webgui: copy changes to /boot/syslinux/syslinux.cfg to /boot/EFI/boot/syslinux.cfg (keep them in-sync)

Version 6.4.0-rc3 2017-06-14

Linux kernel:

• version 4.11.5
• md/unraid version: 2.8.1
  • bug fix: replacing "invalid" parity device does not check that size of new device is large enough

Management:

• emhttp: by default have nginx listen only a port 80 (http); added -r option to redirect http to https
• emhttpd: fix mover logging enable/disable
• emhttpd: start nginx before docker and libvirt
• webgui: Add generation of custom icon in header (sidebar) for themes AZURE and GRAY
• webgui: Fixed IP address check and VLAN support in Docker service creation
• webgui: Enhanced Read/Write operations for easy cloning of user shares and disk shares
• webgui: More refinements in User shares and Disk shares
• webgui: Removed hardcoded width in share-edit
• webgui: Correction and update of clone functionality, now also available for AFP and NFS
• webgui: Fixed potential misbehavior of input element in themes AZURE and GRAY

Version 6.4.0-rc2 2017-06-04

Management:

• emhttpd: fix mover invokation

Version 6.4.0-rc1 2017-06-04

Base distro:

• acpid: version 2.0.28
• adwaita-icon-theme: version 3.24.0
• apcupsd: version 3.14.14 (rev2, added modbus-usb support)
• at-spi2-atk: version 2.24.0
• at-spi2-core: version 2.24.0
• atk: version 2.24.0
• btrfs-progs: version 4.10.2
• cairo: version 1.14.8
• coreutils: version 8.27
• cryptsetup: version 1.7.5
• curl: version 7.54.0 (CVE-2017-7468, CVE-2017-2629)
• dbus: version 1.10.16
• dejavu-fonts-ttf: version 2.37
• dhcpcd: version 6.11.5
• docker: version 17.05.0-ce
• dosfstools: version 4.1
• e2fsprogs: version 1.43.4
• etc: version 14.2 (rev10)
• ethtool: version 4.10
• eudev: version 3.2.2
• file: version 5.30
• flex: version 2.6.4
• fontconfig: version 2.12.1
• freetype: version 2.7.1
• gd: version 2.2.4
• gdbm: version 1.13
• gdk-pixbuf2: version 2.36.6
• glibc: version 2.25
• glibc-zoneinfo: version 2017b
• glib2: version 2.52.1
• gnome-themes-standard: version 3.22.3
• gnutls: version 3.5.10 (CVE-2017-5334, CVE-2017-5335, CVE-2017-5336, CVE-2017-5337)
• gptfdisk: version 1.0.1
• grep: version 3.0
• gtk+3: version 3.22.12
• harfbuzz: version 1.4.6
• hdparm: version 9.51
• htop: version 2.0.2
• iproute2: version 4.10.0
• iptables: version 1.6.1
• irqbalance: version 1.2.0
• jemalloc: version 4.5.0
• kernel-firmware: 20170330
• keyutils: version 1.5.10
• kmod: version 24
• libarchive: version 3.3.1
• libcroco: version 0.6.12
• libdrm: version 2.4.80
• libedit: version 20160903_3.1
• libepoxy: version 1.4.2
• libevdev: version 1.5.6
• libevent: version 2.1.8
• libgcrypt: version 1.7.5
• libgudev: version 231
• libjpeg-turbo: version 1.5.1
• liblogging: version 1.0.6
• libnetfilter_conntrack: version 1.0.6
• libnftnl: version 1.0.7
• libnl3: version 3.2.29
• libpcap: version 1.8.1
• libpciaccess: version 0.13.5
• libpng: version 1.6.29 (CVE-2016-10087)
• libpthread-stubs: version 0.4
• librsvg: version 2.40.17
• libseccomp: version 2.3.2
• libssh2: version 1.8.0
• libtasn1: version 4.10
• libusb-compat: version 0.1.5
• libvirt: version 3.2.0
• libX11: version 1.6.5
• libXfont2: version 2.0.1
• libXi: version 1.7.9
• libXpm: version 3.5.12
• lvm2: version 2.02.170
• lz4: version 1.7.5
• mc: version 4.8.19
• mesa: version 17.0.5
• mozilla-firefox: version 53.0.2 (CVE-2017-5031, CVE-2017-5433, CVE-2017-5435, CVE-2017-5436, CVE-2017-5461, CVE-2017-5459, CVE-2017-5466, CVE-2017-5434, CVE-2017-5432, CVE-2017-5460, CVE-2017-5438, CVE-2017-5439, CVE-2017-5440, CVE-2017-5441, CVE-2017-5442, CVE-2017-5464, CVE-2017-5443, CVE-2017-5444, CVE-2017-5446, CVE-2017-5447, CVE-2017-5465, CVE-2017-5448, CVE-2016-10196, CVE-2017-5454, CVE-2017-5455, CVE-2017-5456, CVE-2017-5469, CVE-2017-5445, CVE-2017-5449, CVE-2017-5450, CVE-2017-5451, CVE-2017-5462, CVE-2017-5463, CVE-2017-5467, CVE-2017-5452, CVE-2017-5453, CVE-2017-5458, CVE-2017-5468, CVE-2017-5430, CVE-2017-5429)
• nano: version 2.8.2
• ncurses: version 6.0
• netatalk: version 3.1.11
• nettle: version 3.3
• nfs-utils: version 2.1.1
• nginx: version 1.12.0
• ntfs-3g: version 2017.3.23
• ntp: version 4.2.8p10 (CVE-2017-6464, CVE-2017-6463, CVE-2017-6458, CVE-2017-6460, CVE-2016-9042, CVE-2017-6462, CVE-2017-6451, CVE-2017-6455, CVE-2017-6452, CVE-2017-6459)
• openssh: version 7.5p1 (CVE-2016-10009, CVE-2016-10010, CVE-2016-10011, CVE-2016-10012)
• openssl: version 1.0.2k (CVE-2017-3731, CVE-2017-3732, CVE-2016-7055)
• pango: version 1.40.5
• pciutils: version 3.5.4
• php: version 7.1.4
• procps-ng: version 3.3.12
• qemu: version 2.9.0 (CVE-2017-2615, CVE-2017-2630)
• rsyslog: version 8.26.0
• samba: version 4.6.4 (CVE-2017-7494, CVE-2017-2619) + patch for Time Machine fullsync support
• sed: version 4.4
• sessreg: version 1.1.1
• shadow: version 4.2.1 (rev2) (CVE-2017-2616)
• shared-mime-info: version 1.7
• sqlite: version 3.16.2
• sudo: version 1.8.19p2
• util-linux: version 2.29.2 (CVE-2017-2616)
• wget: version 1.19.1
• xauth: version 1.0.10
• xf86-input-evdev: version 2.10.5
• xf86-input-keyboard: version 1.9.0
• xf86-input-mouse: version 1.9.2
• xf86-input-synaptics: version 1.9.0
• xf86-video-mga: version 1.6.5
• xfsprogs: version 4.10.0
• xorg-server: version 1.19.3
• xterm: version 327
• xz: version 5.2.3
• zlib: version 1.2.11

Linux kernel:

• version 4.11.3
• added IPv6 support
• added QLogic Ethernet support:
  • CONFIG_BNA: QLogic BR-series 1010/1020/1860 10Gb Ethernet Driver support
  • CONFIG_QLA3XXX: QLogic QLA3XXX Network Driver Support
  • CONFIG_QLCNIC: QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support
  • CONFIG_QLGE: QLogic QLGE 10Gb Ethernet Driver Support
  • CONFIG_NETXEN_NIC: NetXen Multi port (1/10) Gigabit Ethernet NIC
• added squashfs to support mounting /boot/bzmodules, /boot/bzfirmware
• additional config options:
  • CONFIG_BLK_DEV_PCIESSD_MTIP32XX: Block Device Driver for Micron PCIe SSDs
  • CONFIG_BNXT: Broadcom NetXtreme-C/E support
  • CONFIG_CMA: Contiguous Memory Allocator
  • CONFIG_MTD: Memory Technology Device support
  • CONFIG_NUMA_BALANCING: Memory placement aware NUMA scheduler
  • CONFIG_NUMA_BALANCING_DEFAULT_ENABLED: Automatically enable NUMA aware memory/task placement
• expanded set of included hwmonitor modules
• md/unraid version: 2.8.0
  • accommodate kernel 4.11 api changes
  • bug fix: if one disabled disk and another invalid disk, should not be able to unassign third disk
• modules now compressed with XZ

Management:

• create ntp and avahi users if missing
• replace cpuload daemon with websocket endpoint
• firmware now loaded on-demand from 'bzfirmware' file located on USB boot device
• force correcting-fsck on USB boot flash before mounting
• integrate nginx http-server including php-fpm and nchan support
• modules now loaded on-demand from 'bzmodules' file located on USB boot device
• support https with auto-generated self-signed certificates
• update smartmontools drivedb and hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt}
• emhttp: detect "unraidsafemode" boot and prevent array autostart if set
• emhttp: eliminate "/mnt/user0" shfs mount point.
• emhttp: fix 'btrfs check' running status not detected correctly
• emhttp: if valid old key on same usb flash device as Trial key, offer to replace key
• emhttp: invoke emhttpd daemon listening on local unix socket
• shfs: Full atim/mtim preservation.
• shfs: implement ioctl() functions to move objects
• shfs: utilize FUSE read_buf/write_buf methods
• mover: use shfs ioctl() instead of 'rsync'
• webGui: added new themes 'Azure' and 'Gray'
• webGui: allow custom IP addresses for individual Docker containers
• webGui: changed screen width to automatic with minimum of 1080
• webGui: networking now allows multi bonds and multi bridge groups
• webGui: new watchdog service with websockets instead of ajax polling
• webGui: utilize pubsub/cpuload nchan websocket endpoint to update cpu load info
• webGui: IPv6 networking and routing table management
• webGui: correct case of cache device assignment not being preserved across array restart
• webGui: Upgrade tooltipster to version 4.2.3
• webGui: Fixed file read errors when system is started but array is stopped
• webGui: Fixed persisting the show banner value after applying disk settings
• webGui: Fixed regression error in erroneous display of disk table on Dashboard
• webGui: Registration page refinements

 

Edited June 18, 20179 yr by limetech
Add note re: secure boot

Updated without issue, my entire system seems to be a little quicker booting as UEFI which is interesting. I had a SeaBios VM that when ever i booted it up it would cause mouse jittering and extreme lag on my other VM's (OVMF), that behavior seems to have stopped entirely just with that update...

Good morning:  

 

I have been using the RC versions since you started releasing them.  Everything seems to be working correctly however I have discovered that I can no longer drill down on the disks on the main page to make changes to the individual disks.  I can not also click on the folders on the main page to see what is on each disk. For example, when I highlight the disk icon I see the command browse mnt/disk/1 but it no longer browse's.  I can right click on the icons and choose open in new tab and they will pop a new tab..

Still working for me.

 

Have you tried to clear your browser's cache?

 

8 hours ago, limetech said:

UEFI support (-rc4)

 

I did the update through the plugin page and when I rebooted, I got a red background message from the BIOS that there was some issue with the booting process due to the

UEFI support and the default choice was 'OK'  (Wish I had taken a photo of it!), picked that default choice, and the boot proceeded normally from that point.  Is this going to happen every time I reboot from now on or it is a one time event?

1 minute ago, Frank1940 said:

 

I did the update through the plugin page and when I rebooted, I got a red background message from the BIOS that there was some issue with the booting process due to the

UEFI support and the default choice was 'OK'  (Wish I had taken a photo of it!), picked that default choice, and the boot proceeded normally from that point.  Is this going to happen every time I reboot from now on or it is a one time event?

 

Can you try rebooting again now to find out?

14 minutes ago, BRiT said:

 

Can you try rebooting again now to find out?

Stupid on my part and I did it.  Same problem and here is the picture:

 

EDIT:  This is the my Test Bed server.  Just pushing the Enter key and the boot proceeded normally.  Not a big issue for this server but my Media server is in another part of the house....

Edited June 18, 20179 yr by Frank1940

By hitting OK, it proceded to the next boot device (which was probably the non-UEFI version)

3 minutes ago, Squid said:

By hitting OK, it proceded to the next boot device (which was probably the non-UEFI version)

So how does one fix it?  (I might be able to figure it out but it would be a help for all of the other follks who are going to be having the same problem!)

 

UEFI boot from the flash drive worked fine for me.  Maybe you need a bios firmware update?

Noticing the following in my log:

 

Jun 18 17:48:47 Tower kernel: ACPI: Early table checksum verification disabled
Jun 18 17:48:47 Tower kernel: floppy0: no floppy controllers found
Jun 18 17:48:47 Tower kernel: ata6.00: READ LOG DMA EXT failed, trying unqueued
Jun 18 17:48:48 Tower rpc.statd[1596]: Failed to read /var/lib/nfs/state: Success
Jun 18 17:48:48 Tower ntpd[1630]: bind(21) AF_INET6 fe80::3023:16ff:fe1a:70bf%12#123 flags 0x11 failed: Cannot assign requested address
Jun 18 17:48:48 Tower ntpd[1630]: failed to init interface for address fe80::3023:16ff:fe1a:70bf%12
Jun 18 17:48:52 Tower ntpd[1630]: bind(24) AF_INET6 fe80::225:90ff:fe78:d55b%11#123 flags 0x11 failed: Cannot assign requested address
Jun 18 17:48:52 Tower ntpd[1630]: failed to init interface for address fe80::225:90ff:fe78:d55b%11
Jun 18 17:49:03 Tower avahi-daemon[12738]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Jun 18 17:49:24 Tower ntpd[1630]: bind(27) AF_INET6 fe80::42:aeff:fe4d:fef4%13#123 flags 0x11 failed: Cannot assign requested address
Jun 18 17:49:24 Tower ntpd[1630]: failed to init interface for address fe80::42:aeff:fe4d:fef4%13
Jun 18 17:49:24 Tower ntpd[1630]: bind(27) AF_INET6 fe80::7464:faff:fe47:3818%15#123 flags 0x11 failed: Cannot assign requested address
Jun 18 17:49:24 Tower ntpd[1630]: failed to init interface for address fe80::7464:faff:fe47:3818%15

 

tower-diagnostics-20170618-1918.zip

This is the NTP service complaining about the IPv6 link-local address not being assignable. As far as I have tested there are no side-effects and you can ignore the warning.

 

Thanks !


Verzonden vanaf mijn iPhone met Tapatalk

So how does one fix it? 

Maybe by disabling secure boot on your bios?

Is there any way to switch the sidebar display of the tabs to the tab display under the banner (like in the 'White' and Black' color themes) for the Azure color scheme.  I realize that location of the tabs is a very subjective one but each of us are entitled to our preference.  I prefer the Azure color scheme but the White layout for the location of the tabs.  I was hoping that perhaps there could be a option to select either on the 'Display' page. 

1 hour ago, Frank1940 said:

Stupid on my part and I did it.  Same problem and here is the picture:

 

EDIT:  This is the my Test Bed server.  Just pushing the Enter key and the boot proceeded normally.  Not a big issue for this server but my Media server is in another part of the house....

 

50 minutes ago, dlandon said:

UEFI boot from the flash drive worked fine for me.  Maybe you need a bios firmware update?

 

OK.  I did get it fixed for this server.  I went into the BIOS and went to the 'BOOT' tab of the BIOS.  There were two choices for my boot USB drive.  One was for the UEFI partition on the drive and the other did not have UEFI mentioned in its short description.  The UEFI was the current first choice and so I changed it to the other USB option and that worked. 

 

 

19 minutes ago, johnnie.black said:

Maybe by disabling secure boot on your bios?

 

@Johnnie.black, I didn't try your suggestion as didn't see it until after I had made the change.  But I don't recall having seen an option to disable secure boot but I wasn't looking for it at that point.

 

I am not sure that the whole issue has been really resolved yet.  I was kind-of hoping that LimeTech might jump in and provide us with some insight as to why the change was made and what changes (or potential changes) might be required as a result of it. 

15 minutes ago, Frank1940 said:

why the change was made

 

What change are you referring to?

14 minutes ago, Frank1940 said:

@Johnnie.black, I didn't try your suggestion as didn't see it until after I had made the change.  But I don't recall having seen an option to disable secure boot but I wasn't looking for it at that point.

 

I am not sure that the whole issue has been really resolved yet.  I was kind-of hoping that LimeTech might jump in and provide us with some insight as to why the change was made and what changes (or potential changes) might be required as a result of it. 

 

There's a secure boot option for sure on your bios, that's optional when booting uefi, windows supports secure boot, pretty sure unRAID doesn't, hence the error.

2 minutes ago, johnnie.black said:

pretty sure unRAID doesn't, hence the error.

 

Blame Torvalds:

https://arstechnica.com/information-technology/2013/02/linus-torvalds-i-will-not-change-linux-to-deep-throat-microsoft/

I had the same problem booting with a freedos stick created by Rufus into efi until I disabled secure boot

Sent from my LG-D852 using Tapatalk

Yeah, it's not a problem, it just needs to be disabled, maybe add a warning to the release notes that to boot unRAID with uefi secure boot needs to be disable (if the board has that option).

1 hour ago, johnnie.black said:

maybe add a warning to the release notes

 

Good idea, done.

3 hours ago, limetech said:

 

What change are you referring to?

 

This is the change that I was referring to:

 

13 hours ago, limetech said:

UEFI support (-rc4)

A new directory is included on the USB flash boot device called 'EFI'.  The presence of this directory along with its contents, and along with some

additional linux kernel options permit UEFI boot.  This is done in such a way that you could choose either BIOS (legacy) or UEFI to boot off your USB flash device.

 

 

I think the issue has probably been laid to bed now and folks who now encounter the problem will be able to quickly find the solution.  Just remember to have the note ----

13 hours ago, limetech said:

Note: some motherboards may present a strongly worded warning along the lines of "The system found unauthorized changes on the firmware, operating system or UEFI drivers."  In this case look for a "Secure Boot" BIOS setting and change to "Other OS".

 

--- predominately displayed in the first post of the release thread for 6.4.0.  or there will probably be far more folks with the problem who are not use to handling these types of issues as well as the folks who use betas and rc's.  

This may be a little off topic, but perhaps someone could explain to the less enlightened (me) what the advantage is to using UEFI. Tried google but just got a bunch of articles describing how to enable it in Windows.

bios is legacy, it was never supposed to last as long as it did.. but programmer kept finding tricks to squeeze more into it..  uefi is like its own mini os, it can connect to the internet/supports the mouse/etc.. has a ton more bells and whistles when it comes to making things more user friendly and do all sorts of stuff when it comes to overclocking/updating/etc.

 

for more info: https://www.howtogeek.com/56958/htg-explains-how-uefi-will-replace-the-bios/

 

now for it relates to unraid.. its mainly to how the hardware is initialized.. which may work better as everything is heading away from legacy bios.

also perhaps unraid one day will be offered as a standalone appliance with unraid as the bootloader (there own drobo type of thing?):

https://superuser.com/questions/496026/what-is-the-difference-in-boot-with-bios-and-boot-with-uefi

 

Edited June 18, 20179 yr by zoggy