Stable Releases

I removed one of my drives from my array to turn it into a hot spare since I have more protected storage than I needed. I went from nine array drives to eight. One of my shares was set to include Disk9. After I removed one drive, Disk9 no longer existed but the share was still set to include it based on the "Fix common problems" plugin report. The problem is, Disk 9 isn't included in the list of available drives so it couldn't be seen or specifically deselected on it's own. Fixing was si

The new ability to choose your own custom dashboard icon is great and I have used it to great effect. However, sometimes I load the dashboard and the image can't be displayed.  It's still pointing to the file but the file is missing.  I end up having the reselect it locally.   Not sure what's going on here?

After the latest stable release 6.7.2 Hot-Swap does not work.   Example.   Added another drive into an available drive bay but the drive does not show up in Unassigned_Devices. (see 1st image) Rescaned from terminal:  rescan_scsi_bus (see 2nd image) Drive now shows up as an Unassigned_Device (see 3rd image)   Additional information: I also tried to uninstall Unassigned_Devices and Re-install and that did not work either.   The only other thing th

I updated my Unraid server yesterday (not sure which version i had running before). After the reboot all disks wich are connect at my PCIe Adapter aren't available. Tried to reboot, checked the cables and checked the card.   homeserver-diagnostics-20190807-2248.zip

I noted this strange behavior, when I add or remove a user while at the same time transfering files to/from UNRAID the transfer is halted and I get this error message:  

Whenever trying to configure Pushover, Slack, Telegram, or any of the agents within 6.7.2, I enter the respective key/webhook URL and hit 'Apply', then nothing happens. This is after enabling the function also, and upon refreshing the page via. CTRL+F5 it does not save the information and therefore, I can't configure Slack notifications.   Upon refresh it shows then as 'Disabled'.

I am running my Firewall (OPNsense, based on FreeBSD) in a VM on UNRAID using Network Bridges as virtual NICs. Using previous versions of OPNsense (versions <= 19.1.10_1), NICs were recognized correctly, if and only if I set machine to Q35-2.6.   Problem: Using latest Version of OPNsense (Version 19.7), NICs aren't recognized any more, so I had to set my Firewall back to older Version to run (using a Backup of vdisk1.img).   some testing I did: Creating a new VM u

Have a thread going with 13 reports of AMD motherboards that, after upgrade to the latest BIOS, get the following error for Windows 10 VMs with GPU pass-through: vfio: Unable to power on device, stuck in D3 It affects the x300, X400, and the new X570 series mobos.  This has been an issue since March 2019 when AMD motherboard manufacturers began preparing for the AMD 3000 CPUs.  In the thread, I noted during some early research that the same issue plagued the AMD TheadRipper on x399 moth

I had version 6.6.6.  SMTP and emails were working correctly. Upgraded to version 6.7.2.  SMTP settings show correct in Notifications settings.  Use TEST button to send test email.  Button changes to "Test Results" but none shows.  Never receive test email.  Checked SYSLOG but there are no entries referring to SMTP/mail activity at all.  Do not receive daily system status emails. jhblzu1-diagnostics-20190712-1202.zip

Hi all   This issue has been discussed on and off around the forum but it doesn't seem anyone has made an actual bug report post so here we go.   Essentially the issue goes as follows, you pass through an AMD GPU, in my case a Vega 56 and then whenever you shutdown or reboot the VM, it will not turn back on until the unRAID system has been fully rebooted.   Now looking around the forums it appears that the VM or unRAID doesn't release the GPU when the host reboots,

This one has been happening for a long time, but not sure I ever raised it.   Whenever one my my UNRAID servers (have 3, 2x 6.4 and one 6.7) reboots due to a power failure (have been a lot recently as the house is a construction site) then, after coming back up, the domain is never automatically rejoined. The details are in the GUI but status is not-joined. Normally rejoins first or second attempt no problem from settings widget.   I don't think this is a problem in a control

I am having this issue with 2 Adata XPG GAMMIX S5 256GB drives.  Both are seen in the BIOS but I see the following during system start up.   Jul 14 21:56:11 TheWatchtower kernel: nvme nvme1: ignoring ctrl due to duplicate subnqn (nqn.2018-05.com.example:nvme:nvm-subsystem-OUI00E04C). Jul 14 21:56:11 TheWatchtower kernel: nvme nvme1: Removing after probe failure status: -22   Further digging I came across this *NEW* https://lkml.org/lkml/2019/7/15/57   Date:  M

I have Problems with ConBee II USB Stick (worked fine on my Raspi). Here are the Logs:  tower-syslog-20190714-0637.zip

I had a weird failure a while back when I tried to add a second drive to my cache pool, but I didn't have a chance to really track it down until today.  The initial symptom was that I stopped the array, added the (blank) drive to the cache pool, and after starting the array, the main page of the web interface reported that both drives were in a pool, but no balance operation was happening, and no IO was happening with the new drive.   My existing cache volume was /dev/sdh1, and I was t

Moving from 6.6.7 to either 6.7.0, 6.7.1 6.7.2 all have the same issue. Everything works correctly, except starting a VM that has a GPU passed through.  When starting this VM the system crashes.   I've attached diagnostics from both versions (6.6.7 and 6.7.2), just before starting the VM.   Nothing was changed in the configuration between runs.   There is another VM running fine in both cases.  It has nothing passed through.   Also attached is the xml config of the probl

Hi,   Lately my Unraid install has been crashing/unresponsive.  That means no response from webui/ssh/ping, and the attached display connected to the actual server is frozen.  I am attaching the diagnostics zip as well as the /var/log/syslog I was able to capture with a remote syslog server, hopefully that is helpful but I'm unable to find anything telling me what happened.   The last recorded log was @     Jul 07 07:52:45 shoebox kernel: mdcmd (66): spindown 1 And then

I have two SSDs in btrfs raid0. I've been fiddling around with my box lately, and I guess the cables were loose on one my drives, because the drive dropped while the mover was running. It came back after reboot and no data was lost, but there were some very preventable corruption issues.   Bug #1:  After one disk dropped, the files on the raid0 cache remained visible to the UI (but not readable through the UI). Good, I guess. But the mover kept on going and wrote corrupted files t

I just removed a disk1 from my array using the guide on the wiki. The guide included emptying the disk to remove, and setting all shares to only include other disks.   I only got 2 disks in (+cache), and after my change I will have 1 disk+cache.   After using the new config function I removed disk1 as I wanted, and then set disk2 as disk1. Setting disk2 to disk1 caused some problems. All shares were still set to use only disk2, but I didn't have the option to change

It's gotta be software at this point.  I've had this issue since 6.6.7 and was convinced it was hardware.  Alas, I have replaced every single piece of hardware and still get kernel panic NF_NAT IPTables about once a week.  I'm not sure where to go from here. I don't have a log file of the kernel panic as once it panics and you reboot, the logs are gone.   I'm attaching a diagnostic file, and will await instruction on what to do next.     tower-diagnostics-20190705-0148.z

This happened last time I upgraded, to 6.7.1. And it happened exactly the same way this time. I stopped the array, made a backup of /boot, ran update assistant, upgraded the OS, and it kernel panics on boot. From what I can tell, the update is breaking EFI. But I'm sure that comments here will tell me that its normal and not fix it. Going back to 6.6.7.

Hi...   Some of the services on unRAID in 6.7.X do not seem to have access to the Internet. For example, "Community Applications" works and pulls things down, yet the simple SpeedDisk Tool nor any of my dockers have access.  The server itself seems fine as it will download the UnRAID version upgrade and seems well.   Had seen a "similar issue" reported in another thread that really did not have a resolve.  I even asked if it was resolved in 6.7.1 and then seen there was a 6.7

The setting is here  , but it still warning at 46degree, and notify return to normal in 1-2 seconds. 6.7

When creat a home assistant VM, change the xml file clock set to local time will casued hass.io no ip addres after running half hours

Is it only me every single upgrade from 6.7.0 has seen my server not connect to the App Store  or pull any update it keeps banging on about DNS, it set to static on the router and on the server but when ever I upgrade it doesn’t work, when I down grade it works but I think I’m truly stuffed now as I can’t see the previous OS to downgrade now, so server is a massive paper weight 🤦🏾‍♂️ Nics are built into the board which has 3 not all three are being used though help please.   zeus

Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) after updating to 6.7.1 from 6.6.2 Also not being able to roll back an update and boot the old image is a bug too IMO. Same condition and description as this reddit post.