Stable Releases

While setting up some backup schedules with crond and checking the log I just noticed on both of my servers that there are at lot of log spams like these:   atd[1260378]: Userid 0 not found - aborting job 6 (a0000601b9b9fa)   While there are reports here to be found related to samba I did a lot of trying to bug fix this (the usual stuff including giving world access permissions too). So naturally I moved to my backup server, because that has almost nothing installed - let alone c

After the update, I experienced the following: When looking at the Main page, the array was shown stopped. I then clicked the start button. Unraid, however, reported an error in that a disk was missing. I checked my array and noticed that my original array of 3 slots (2 Data + 1 Parity disks) had somehow changed to an array of 4 slots of 2D+2P where the 2nd parity was (obviously) unassigned. Expectation: Unraid should have left the array configuration alone during the update and not c

The above prompt appears when querying the hard disk ID through the command I'm not sure what this red warning means. But there is no problem with detecting the hard drive through unraid, and the hard drive is also functioning normally during use.   After opening some virtual machines for a few minutes, all CPU threads experience high load. After experiencing high load, UNRAID cannot shut down and restart normally. Only force the power button to complete the shutdown  

Basically the day after the migration all the pass-through devices to a vm (2 network card) stopped working   Unraid 7 after migration: didn't work, or worked for a day Unraid regresion to 6.12.14: didn't work either Restore unraid 6.12.14 from backup previous to migration: didn't work (same logs with errors) Over the above unraid flash restore, I replaced the libvirt.img and It works instantly, no more error logs. Attached in this post diagnostics of Unraid working.

Hello Unraid,   1. Problem: After upgrading to Unraid version 7.0.0, the system stopped mounting a ZFS raidz2 pool consisting of 4 drives and an SSD cache drive during the array startup from the UI. The pool is functional and can be mounted manually via the command line, but Unraid displays the error: "Unmountable: wrong or no file system." To mount & validate the pool manually via CLI: zpool import <myPoolName> zpool get all <myPoolName> Then navigate to t

Main issue: Cannot restart VM manager, once it was stopped. Get the error: "Libvirt Service failed to start." Side issue: USB device changed port after upgrade to 7.0.0   Steps how to reproduce (at least steps that broke it for me): I have VM (windows 11). It had USB device assigned via USB plugin in 6.12.14 version. After upgrade to 7.0.0 started the same VM, but the USB device was not visible in the Windows VM (Aqua_Computer_GmbH___Co._KG:QUADRO) - it changed Port from "2-s

Unraid v7.0.0 - if I open the servers dashboard web page, I'll see the list of notifications pop up. I hit 'Close notifications' (or similarly worded). But, the notification indicator remains lit up. Click that and the same notifications that I just closed are still there. Hit 'Close notifications' again and this time they go away. Small, but annoying, bug.

- Jellyfin and Plex are unable to play any media and throw no errors.  I have first noticed this problem when I upgraded to UNRAID 7.0.0.  I then reverted to 6.12.10, problem persists except the ssh session didn't freeze.  I then upgraded again to UNRAID 7.0.0 since I made some DNS changes in my network that fixed a really slow response in the UNRAID web application (updated several of my Pi-Hole instances and add a new instance).   `Fix Common Problems` used to freeze on the `Rescan` but since

I just updated to 7.0.0 this morning and after reboot the parity check started right away, then after about 30% it slowed down drastically, under 1MB/s.  The log showed a lot of problems with ATA 4, so i shut down the server and used another port on the motherboard and another sata cable, but it is still really slow. Any idea what is going on? plexworm-diagnostics-20250118-2038.zip

I have Unraid running as a VM under Proxmox and its been running great until I tried to upgrade to 7.0 rc2 and 7.0 Final.     After upgrading to 7.0 the system fails to boot with the following error. Notice the dev mapping of the USB stick - sdi       If I remove a drive from the system it will boot under 7.0, the drive will be recognized as sdh. But I am of course down a disk.  I can then boot into Unraid and downgrade to 6.   A

Running Home Assistant in a VM.   I have a snapshot of the VM but I am unable to delete it I get the error "Image currently active for this domain"   Turning the VM Off makes no difference.   marters-unraid-diagnostics-20250115-2017.zip

I just upgraded to 7.0.0. and want to try the snapshot function. I can create one. but I cannot see all the snapshots I have saved or how to restore my snapshot from the "VMS" tab? 

The FTP server is enable by default and enable after every restart. Is there a way to keep it disable? I think this was and old "bug" that was already fixed, but doesn't work for me.

Happened several times to me, since Terminal was included, this one is from v6.5.0, at some point Terminal crashes and stops working, only reboot fixes it.   I believe these are from when it stopped working:   Mar 17 18:54:19 Tower1 nginx: 2018/03/17 18:54:19 [error] 5672#5672: *698426 recv() failed (104: Connection reset by peer) while proxying upgraded connection, client: 192.168.1.130, server: , request: "GET /webterminal/ws HTTP/1.1", upstream: "http://unix:/var/run/ttyd.s

This is a continuation of an older thread: see here. I updated to Unraid 7 and wanted to open a new ticket.  Unraid seems like its functioning fine until suddenly it just suddenly drops off the network. It doesn't show up on my router or when I run arp-scan or anything. The only solution is to power cycle unraid via IPMI. This seems to be random and is not reproducible. There's two log files, so I'm attaching both.   I'm running a SuperMicro X9sri board with a Xeon E5-2620 and 64GB RAM

[7.0.0] Mover still moving but "Mover" button is clickable and Mover doesn't say it is running to the right of the button.   My Mover is scheduled to start early in the am each day.   Have Parity tuner plugin installed and set to pause parity check if mover starts.   So do not think this plugin is the cause.   Have PhotoStructure Docker installed and set to leave photos where there are on the Media share in the Photos folder but use the .PhotoStructure folder to sav

Hello. Not a super knowledgeable user, but I've been using Unraid for a bit over a year. This is a problem I've had several times, but not documented until now. I think it happened under 6.12.12 as well).   Unraid seems like its functioning fine until suddenly it just suddenly drops off the network. It doesn't show up on my router or when I run arp-scan or anything. The only solution is to power cycle unraid via IPMI. This seems to be random and is not reproducible. There's two log fil

after upgrade I am unable to edit VM's with the Linux icon (Penguin) the others i've tried seem to work fine so not 100% whats going on. I've rebuilt the vm with a couple icons and it works and rebuilt with the same icon and wont work. I've tried to see if I could provide logs however, it seems like the icon link for the drop down menu is just broken.

2 issues as I had to replace some disks in a btrfs pool.   1) Unraid does not calculate the size of the pool with mismatched disk sizes correctly for some RAID levels (eg: raid1c3). In this tested example it uses a simple algorithm of total RAW space * 33% which only works if all disks are the same size.   For example if you have a pool of 4 disks, 500gb, 1000gb, 1000gb, 2000gb, the total usable space reported by unraid in the GUI is ~1500gb. The actual usable space is howeve

How to reproduce: - Open Terminal and type docker login - Login using any credentials that work. Personally i used login name + personal access token (read-only, not public repo read-only) - Use the UI to pull the image and run the container It will show the version as being not available. Switching the repo to public then deleting the container + image and pulling + run again switches the version to up-to-date. Switching to private again makes it not available any

I have (2) containers (SAB / NZBGet) that I run through a specific VLAN.  After upgrading to 7.0, neither one of those containers will start.  Both containers do not have a network option for the VLAN. I noticed there was no network route for the VLANs any longer. I re-created the VLAN and the route was still not created. I manually created a route and there still is no option for the VLAN in the container config. plexopolis-diagnostics-20250113-1509.zip

[7.0.0] Update Failure, Assistance needed   Howdy Folks,   After updating to 7.0.0 I have the ‘Wrong Pool State, invalid expansion’ issue HOWEVER I cannot solve it as per the pinned post.   On Main, I do not have an option to “Remove Pool”   Under flash/config/pools/cache.cfg I can see my pool details   On Main, if I try to create a new pool called “cache” I get a pool already exists with that name error.   I’ve attached diagnostics.

Hi,   i'm using NoVNC 1.5 on an unraid server 7. NoVNC is used to manage a W10 VM. Everything works fine (ie "azerty" keys are ok) except : Keys are not sent to the VM OS when combined with ALT+GR With a physical French keyboard, this is a problem, as it's the only way to do the \ or @ or | keys.   According to NoVNC creator, it seems to be a problem in Unraid and not with NoVNC : Please check this issue for more informations : https://github.com/novnc/noVNC/issu

VM Manager Issues Post-Upgrade Description of the Issue: After upgrading Unraid to the latest version, I encountered several critical issues with the VM Manager: 1. Existing VMs Not Visible: None of my previously created VMs are listed in the VM Manager. However, the virtual disk files for the VMs still exist in their respective storage locations. 2. Error When Creating New VMs: Attempting to create a new VM results in the following error pop-up: Internal error: Failed

For 4Kn drives I have noticed that if you add a new drive to the array and let it format it as xfs, the sector size in xfs is set to 512 instead of 4096.   If you do the same via the pool, the sector size is 4096, great.   If you format the drive via the cli with mkfs.xfs, the sector size is 4096, great.   Please can explain why the 4Kn drives in the array seem to format with a default 512 sector size using xfs?   Here is my tests, ignore the fact these ex