Stable Releases

I am seeing a bug in v6.7.1's Dashboard, under the "Array" section.  Clicking on any of the "SMART" thumbs-up icons brings up a menu of options: Attributes, Capabilities, Identity - but all the links actually lead to the same page.  Looks like the HTML anchor ("#") link is broken, I always get the top of the page... Attaching a screenshot.  Please let me know if you need any further info.

Creating a certificate_bundle.pem in /boot/config/ssl/certs and using a wildcard certificate will result in a Nginx configuration error in /etc/nginx/conf.d/emhttp-servers.conf   It looks like that the common name of the cert is being used in the configuration, around like 40, in this section:   # # Redirect http requests to https # listen *:80 default_server; listen [::]:80 default_server; return 302 https://*.example.com:443$request_uri;   Cha

Please see this thread for more information.  I've seen the same behavior since 6.6 and now on to 6.7.  Also with 2 completely different servers (completely different hardware).    

All docker containers show 'Update available' if no internet is present when checking for updates in 6.7.0 . This probably should be fixed.

Hi   As the graph show above, I set the warning threshold as 56degrees and it still warn at 46degrees, however I checked every disks settings in main page, it shows the same setting with the hard drive setting in setting page.

Try to upgrade from 6.6.7.  Once rebooted after upgrade to 6.7.0, the server has no active ethernet port. Logs show a call trace then constant resetting of adapter (Intel i211.) It happens if booted in safe mode with no plugins + GUI and when booted normally. If restored to 6.6.7, all issues disappear and the server has normal network access. I have tried install 6.7.1-rc2 and same results: call trace and network eth0 is down. Any ideas? Thanks unraidtoo-diagnostics-20190614-0413.zi

I do believe there is an inherent bug somewhere that possibly does not like my hardware. I've been using unraid since the beginning of V5 or even before that. When V6 first came out things were good. After a couple of revisions is when these copying issues started. I always would get 100MB/sec on copy speeds using a Windows workstation on the network and even faster using the terminal and midnight commander. My server box is a simple norco 4224 box. I have a 1000 watt power supply which has been

Hello,   I'm currently using time machine just fine on my current iMac. However I've bought a new one recently and at the time of installing or restoring the system I'm not getting the Time Machine volume. Not entirely sure how to debug but on one machine I can see it and use it perfectly and on the other it's not even showing up   Is there any steps I can take to try to see what's going on? Both machines are over ethernet and connect to the network (can see both)  

I have ESXi running in qemu. When editing the VM settings, the network adapter type keeps changing from e1000 to virtio. ESXi doesn't support virtio and ONLY supports e1000. I have to make this change in the XML which is not a huge deal, but every time I go into edit, I have to make the same change. Please make this respect the changes AND add a way to edit the network adapter type into the simple VM config view.

I noticed this sometime ago, but I wasn't sure exactly what was happening.  About a month ago I noticed 128 errors after a parity check was completed but saw it only after a week or so had already passed.  All SMART reports were good.  I ran my monthly parity check several days ago and the exact same number of 128 errors occurred.  All SMART reports were again good with zero anomalies on all drives.  The syslog showed a spin down an hour or so after parity check was started (FYI, my disk setting

I stopped the array and set "Enable user shares" to no. I proceeded to start the array without user shares.  When I went to stop the array it will not stop.  Sorry I didn't write down the exact language but it was along the lines of retrying to disable user share in the bottom left corner of the main screen.  Eventually it did allow me to reboot or power down.  Since I had my array on Auto start I had to boot into safe mode and set "Enable user shares" to yes and then restart.  I am currently ru

This bug likely exists for some time, guess it's a corner case, but an user ran into it today.   How to reproduce:   Say you have all 2TB data disks, upgrade parity to a larger disk, e.g. 3TB, start the array and cancel the parity sync, stop the array and replace the 3TB parity with a 2TB disk, start array and parity sync will start again but will still show the old 3TB size for total parity size (not the disk itself), then it will error out during the sync when it runs past

I've had an issue twice now since upgrading to 6.7 where the server just hangs. No network activity and nothing on the console if I plug in a monitor to HDMI. The power LED is still lit on the server but nothing else. When I restarted last night it did a parity check and it sent an email report about 4 hours ago, but I just sat down to watch something on plex and server is down again.   Is there any way to get diagnostics in the case of no console/nmo network? I'm guessing not.

This happened last about  8 days ago, I noticed that dockers were not online, then I login to Unraid and I am able to click all of the menu items just fine, but all the screens are blank.  Dashboard shows no dockers and not much info, disks shows no disks (screenshot attached) and well even no Description in top right corner.  If you notice it just says Unraid OS and not Plus like it does normally.  I then reboot the server and everything comes back to normal.     Does

The whole array spins up unnecessarily when starting a VM. iso and domain resides outside the array on ssd.

Upgrade to 6.7.0 broke wake on lan function.  System no longer able to wake from sleep via WOL.

Depending on the exact size of my browser, sometimes, this happens: The third column starts wherever the 2nd column ends, I've folded the 2nd column to hide personal data and also to make the whole thing fit my display. When opened up:

Updated from 6.6.7 to 6.7.0 this morning and rebooted the server. The server never came back up and upon inspecting the screen output I can see the following (however cannot scroll to get more information): I'm not sure what's broken and what the next steps are but it seems to me like a bug with the updater as it's now not in a bootable state after this update was performed.

Hi,   during the re-boot after the 6.7.0 upgrade the machine hung during BIOS boot and needed to be turned off again. When 6.7.0 came up it reported Disk 17 as "Unmountable: No file system" with the following errors in the log:   May 21 12:24:14 SS kernel: XFS (md17): Internal error xlog_valid_rec_header(2) at line 5283 of file fs/xfs/xfs_log_recover.c. Caller xlog_do_recovery_pass+0xc7/0x514 [xfs] May 21 12:24:14 SS kernel: CPU: 2 PID: 14488 Comm: mount Not tainted 4.19

I'm not sure if this is the proper area to post this, but I'm getting this notice from "Fix Common Problems":   Write Cache is disabled on disk1: You may experience slow read/writes to disk1. Write Cache should be enabled for better results. Post your diagnostics for other users to confirm this test and advise. NOTE: If this drive is connected to your server via USB, then this test and the fix may or may not work / be accurate as USB support for smartctl and hdparm is hit and miss

Hi, so updated to 6.7.0, i have what i hope is constructive feedback in regards to the dashboard,  i completely understand this is low priority stuff and hope nobody takes offence, it is all subjective to personal taste.   1 - (dashboard) array free space bar looks wrong, i'm fairly sure its not supposed to look like that, right? screenshot:-     2. (dashboard) the smallest cog icon i think i may of ever seen :-), if it is supposed to be that size then i would like to

Since upgrading to 6.7.0 a couple days ago, I have started seeing the following message in my system log.   May 16 07:00:02 nas kernel: DMAR: [DMA Read] Request device [03:00.0] fault addr ffabc000 [fault reason 06] PTE Read access is not set   Some quick Googling suggests that this is related somehow to IOMMU, though I don't use hardware passthrough for any of my VMs and anyway I've confirmed that IOMMU is reported as enabled by unRAID. The error message is similar to one ra

To reproduce:   Management UI -> Settings -> FTP Server   Set FTP server: Disabled then Apply.   Status in top right should show Status: Stopped   Click Dashboard then Reboot icon.  Proceed.   Once back up, Settings -> FTP Server, Status: Running   System:   Just upgraded to 6.7.0 from 6.6.6.  Still in trial (28 days remaining...), active directory joined, no dockers, plugins, and one user share created.   T

If I zoom in using mobile safari to open notifications menu (green button on the right side), the submenu opens waaaay to far to the left. 

Problem description: Unable to manually start array. Automatic start after reboot works ok. All drives are unencrypted (xfs)   Visual manifestation of the problem: After stopping array manually, the START button on Main screen greyed out, input field below it asks for passphrase, even though there are no encrypted drives in the system.   Temporary solution: Set "Default file system" in Settings > Disk Settings to "xfs" instead of "xfs-encrypted"