Stable Releases

I have the WebUI open in 2 tabs in a firefox window, i've noticed that sometimes i cannot access terminal or logs if i have another WebUI tab open at the same time. As soon as i close the other tab i can open terminal/logs on the other tab with no issue.   If i have both tabs open and try to open terminal/logs, the popup window will flash open as a blank page for a split second and then close.   I would assume it has something to do with the new log/terminal pop-up windo

After updating to 6.10 today I noticed the left side of my UI now has a scroll bar that is pushing the UI elements to the right, which results in messed up menu buttons.   After talking to people on the discord it was established that this only happens on Firefox (100.0.1 ) with the untabbed Grey UI style.   Please resolve this issue. Thanks a lot

OP in pre-release section by me for Unraid OS 6.10.0 RC8. Since this issue has persisted into the stable release, I am reposting here. Not sure if allowed to have two posts (prerelease/stable) for the same issue. If this is not allowed, feel free to contact me or adjust as needed. I looked at the full release notes and tried to see if the VNC package that Unraid Linux uses was the cause. I could not figure out which library/package it is.   Issue: When editing or creating a

After upgrade reboot all pool devices show as missing. The missing device id is using the longer notation, but the drives I can select from is using the short id.   I matched each drive to the appropriate slot and the array starts but still shows the devices as missing, and says the contents are emulated despite every drive in the pools being in this state. The data is there and shows up just fine, but even after an additional reboot this persists and I have to manually start the array

Hi guys, I have upgraded from 6.10 rc7 to 6.10.0 and immediately got my NVME drive with all docker containers unmountable. Array started, but this drive did not. It says: "Unmountable: wrong or no file system" I tried repairing the Btrfs in the Maintenance mode using GUI, but it also does not work, reporting that it cannot open the file system. Please advise if there is a chance to make it working. I would not like to format the drive and re-install all the dockers. Screensho

The 84°C is not normal. It has low usage and on main tab it shows between 30-35°C. Also that NVMe has a heatsink.

Hey there. While this may be a huge coincidence, but my server was running fine on 6.9.2 with all drives running normally including the cache drive. When I upgraded and rebooted, the system came up, but the cache drive was in read only mode and 1 of my 4 drives was unreadable (btrfs on all of my drives). I also noticed that the /var/log folder filled up (syslog filled the volume). I deleted the file, then rebooted the system again.  When it came back up, Drive 2 was still offline and then t

v6.9.2 When one of the cache disks gets hot, I get notifications in the GUI; usually a few at a time because the disk is under load, so temp is 48C,  temp is 50C, temp returned to normal, etc.   When I click "close all notifications", they disappear then reappear. Clicking the X on each notification makes it disappear, then reappear.   Refreshing the webpage fixes it.  

So I decided to update my unRAID server this morning from 6.9.2. to the newly released 6.10.0. I clicked the Update button in the Update Tool and I received a notification that some plugins needed to be updated and to wait for another notification before rebooting my server. Two hours later, I am still waiting for the reboot notification...   The last notification I received is attached, with my diagnostics ZIP. From what I understand, its checking which plugin from this list I have in

I filed this report for a pre-release of 6.9.2 (I believe), thread below, but it's still broken in 6.10 stable.    

HOW TO REPRODUCE:   Install unRAID 6.9.2 on a multi-CPU machine. View the Dashboard page and scroll to the Memory section.   In my particular instance, my machine has 4 x Xeon E5-4650 CPU's which each have a maximum memory limit of 384GB. This is what is being reported as the maximum memory size for the machine, so it seems to not be taking into account that there might be multiple CPUs. The size should be reported as 1.5TB (4 x 384GB).   Very much cosmetic and

I had a lot of struggles getting quadro (m2000, P4000) graphics cards working in a windows VM. I eventually nailed down the reliable way to get them working. They are not in the first slot, but I only have 1 in my system at a time. I'd expect there to be no issues with passing through a Quadro card.   You just put the VM to sleep, and then resume it and install the drivers. It works every time. Installing, uninstalling, removing, replacing drivers wouldn't fix it. When I

I am doing a parity swap: replacing my old 3TB parity drive with a 4TB drive and replacing one of my data drives with the former parity drive. Currently all my parity data is being copied from the old drive to the new one and the following read/write speeds are being reported: The reported speeds seem to be stuck at the values shown in the screenshot.   The progress on the copy is about 1% every 5 minutes. I am not sure whether this is 1% of 3TB or 1% of 4TB. However the pro

Apologies if this is a duplicate; I did some searching but didn't turn up anything. However, a lot of these terms are hard to search for 🙂   My Firefox browser updated to version 100 this morning, and now the left-side nav menu using the "azure" setting for "Dynamix color theme" is shifted too far to the left. It doesn't break any functionality, but it does look bad.  I tried downgrading to Firefox 98 (couldn't find an installer for 99) and everything goes back to looking correct.

Hello, since some days I have an error in my unRAID log: Apr 26 09:39:57 Tower kernel: pcieport 0000:00:1c.7: AER: Corrected error received: 0000:00:1c.7 Apr 26 09:39:57 Tower kernel: pcieport 0000:00:1c.7: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Apr 26 09:39:57 Tower kernel: pcieport 0000:00:1c.7: device [8086:a33f] error status/mask=00001000/00002000 This error comes every 1 or 2 hour. In the pcie slot is a DD-TV Card, connected to

tl;dr: It appears to me that Unraid 6.9.2 doesn't honor device-specific temperature notification settings for Unassigned Devices for a straightforward reason that is easily fixed.   Now that I have two unassigned NVME drives in my Unraid server, the annoyance of over-temp notifications that ignore the per-device settings has doubled, so I've come up with what is hopefully a true fix, rather than a workaround, in the form of a small change to the check_temp function in /usr/local/emhttp

So I have a Home Assistant VM with ZHA. I have a Sonoff Zigbee Dongle.   If I plug the dongle into a usb extension cable and boot, all works fine 100%.   If I plug the dongle into the exact same port on the mobo, it recognizes the dongle in the VM, but does not pass info. No devices can connect, no data flows in.   Other USB ports do the exact same thing. And yes, they are all USB 3.0 and so is the extension.   Another issue I can see is it will sometimes

Hoping for some guidance (full context is here  )     I have a weird issue relating to a cache-only drive where files are unable to be deleted - they rather lose permission to windows devices across the network (simultaneously) so all windows  devices see the file as having no owner   if i access the drive direct through cache\sharerather than the user share this problem doesnt exist (again full detail on above thread, trying not to spam here) I can also delet

Hi,   On the Dashboard the Streams counter stays zero on cache only shares even when there is an active stream.       Can this be fixed? The streams counters would be a good indicator when someone using the server.   Thanks, Mark

Expected: - running VM to be hibernated upon restart using GUI. the hibernation state should be preserved after restart - already hibernated VM to preserve hibernation state upon restart using GUI - possibly the same upon start and stop array using GUI   What happens: - When hitting restart using GUI, unknown whether VM hibernates. Either way, hibernation state is not preserved after restart - When stopping and starting array using GUI, either 1) qemu-system-x8

I acknowledge this isn't so much of a bug, but it cost me 20 minutes of resorting all of my dockers.   Clicking anything in a table header should not be destructive.  The icon looks just like the icon generally used to change the table display from icons, grids, details, etc.  I clicked it before the tool tip showed up because again, clicking anything in the header should not be destructive, it just effects the sorting order.  Since there is already a row of buttons below the dockers,

Input a password on the main login screen that is wrong a bunch of times to get locked out It will say that too many attempts happened Input the correct password It will still tell you too many attempts happened and nothing will happen Refresh the page, you are now logged in and at the Unraid menu   This has to be a bug. Basically it seems the login page takes the password even though it spits the message "too many attempts" and you get a cookie which stor

Setup: - Unraid ver. 6.9.2 - Conbee 2 ver 2.05.77, 5/22/2020   Issue description: As presented on below screenshot, Device number is being changed periodically for Conbee2 device only, all other devices are having rather "static" device number. By periodically I mean that sometimes after VM reboot (which is using conbee2), sometimes just without any action. This is getting annoyed, because my all zigbee network is down unexpectedly, whole home automation is not working.

As a long time Unraid user (over a decade now, and loving it!), I rarely have issues (glossing right over those Ryzen teething issues).  It is with that perspective that I want to report that there are major issues with 6.9.2.   I'd been hanging on to 6.8.3, avoiding the 6.9.x series as the bug reports seemed scary.  I read up on 6.9.2 and finally decided that with two dot.dot patches it was time to try it.  My main concern was that my two 8 TB Seagate Ironwolf drives might experience

Issue 1: Editing the WebUI setting for an existing container (via the advanced view) has no effect. The entry does "stick" and will display properly in the Update Container page, but the WebUI link for the container will continue to route to the previous setting.   This can be worked around by setting the WebUI during the initial container creation, rather than editing it after the fact. Note that this issue and workaround were reported as far back as 2015 (!): https://forums.unra