Stable Releases
Bug reports for stable releases.
2506 reports in this category
-
I'm getting this error recently after updating to the latest version of Unraid, but after trying to downgrade to the previous, issue is still getting triggered. alexandria-diagnostics-20240906_2232.zip
- Solved
- Urgent
- 738 views
-
Following an upgrade to 6.12.13, some issues were experienced when copying files using rsync and after a restart the Cache drive remains unmountable. Have unassigned the drive, started the array, stopped the array and reassigned to no avail. Submitting bug report before attempting a downgrade. whitewitch-diagnostics-20240903_2119.zip
- Closed
- 529 views
-
i posted in general topic last week. but i see i not only one. my experience is server locks up 100% you can only ping the server... the hard drive light is running but non of the array or USD drive lights are accessing so i guessing its the unraid files either the flash or the system, appdata which is on an nvme thats taking 100% or what not you loose gui smb... i have poor smb copying. i should get close to 500mb/s going from SSD to SSD i get like 30mbs and thats using window
- Minor
- 297 views
-
This has happened each time I've attempted to upgrade to 6.12.XX The upgrade completes successfully after a reboot. I then attempt to manually start the Windows 10 VM. The VM attempts to start but is never successful. I am now unable to do anything in Unraid. I cannot shut down the server properly. I must power off the server and restart, and therefore begin a parity check. Prior versions of 6.12.XX that I have upgraded to did allow the Windows 10 VM to start. But s
- Minor
- 242 views
-
After upgrading from 6.11.5 to 6.12.3 all my shares from unassigned drives went missing. My system is now raising errors below: WARNING Directory: \\Nas\d1_st12000vn0008-2j\ does not exist. WARNING Directory: \\Nas\d2_wdc_wd121\ does not exist. WARNING Directory: \\Nas\d4_toshiba_mg07aca1\ does not exist. WARNING Directory: \\Nas\d5_wdc_wd141kfgx-68\ does not exist. WARNING Directory: \\Nas\d6_wdc_wd141kfgx-68\ does not exist. WARNING Directory: \\Nas\d7_wdc_wd140efgx-68\ do
- Closed
- 222 views
-
Not sure if this has been reported before (search didn't turn up anything), user shares on a RAID0 striped ZFS pool will show as protected (with a green orb) in the Shares tab. Some might argue a striped pool is even more at risk for catastrophic failure than any single disk, so this might lead to a false sense of security and feels wrong somehow.
- Minor
- 247 views
-
Hello. (excuse my bad english, I am native german). I made an update from 6.12.11 to 6.12.13. (I did miss the 6.12.12 and cant find it anywhere to download). I use Win10VM in unraid and I transfer Files with TotalCommander from/to the VM. In 6.12.13 I can't transfer Data > 1MByte per smb to external QNAP NAS or real Win11 PC. I can download from those external SMB Shares with no problem in to my win10 VM C : . (I made Diagnostics with 6.12.13. attached)
- Solved
- Urgent
- 516 views
-
Updated from 6.12.10 to 6.12.13. I have a VM with W10 installed Filezilla Server installed and working. IP, Port Forwading, Firewall everything seem OK an most important everything worked find until the upgrade. After the Upgrade even FTP connects from the internal network slowed down close to 10 to 0 kbps. Downgraded to 6.12.10 and everything is working smoothly again with several MB/s nasng-diagnostics-20240827_0017.zip
- Minor
- 1211 views
-
CPU kernel lockup in 6.12.11? - kernel: general protection fault, probably for non-canonical address
August 29th Had some kind of full lockup - maybe CPU kernel error at 4am ish eventually the machine locked up around 6/7am with all drives spinning so had to do a forced reboot. Worth noting there is no scheduled tasks for that time. Anyone had similar on .13 vs .11 ? Could be anything but have downgraded to .11 to be safe. Aug 29 04:00:25 Moulin-rouge kernel: general protection fault, probably for non-canonical address 0xfbffea00417fcd- Minor
- 933 views
-
The release notes for 6.12.13 has broken links for the link to release notes of 6.12.12. The link goes to: https://docs.unraid.net/go/release-notes/6.12.12, which seems broken. Also if I go to the update os page (https://account.unraid.net/server/update-os), the link to release notes for 6.12.12 goes to https://account.unraid.net/server/6.12.12.md, which is also broken.
- Solved
- Minor
- 414 views
-
Since these devices are 4K and the file system is created as 512B, you are unable to mount these file systems outside of the unraid array. If I just click mount via unassigned devices: Apr 29 09:25:42 Tower unassigned.devices: Mount drive command: /sbin/mount -o rw,noatime,nodiratime '/dev/mapper/HGST_HUH721010AL4200_direct' '/mnt/disks/HGST_HUH721010AL4200_direct' Apr 29 09:25:42 Tower kernel: XFS (dm-8): device supports 4096 byte sectors (not 512 Here is me doing
- Minor
- 1683 views
-
Aug 26 08:26:50 Cube smbd[3120]: [2024/08/26 08:26:50.226852, 0] ../../lib/util/fault.c:183(smb_panic_log) Aug 26 08:26:50 Cube smbd[3120]: =============================================================== Aug 26 08:26:50 Cube smbd[3120]: [2024/08/26 08:26:50.226861, 0] ../../lib/util/fault.c:184(smb_panic_log) Aug 26 08:26:50 Cube smbd[3120]: PANIC (pid 3120): assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in 4.17.12 Aug 26 08:26:50 Cube smbd[3120]: [2024/08/26 08:26:50.227231,
- Minor
- 364 views
-
Hi I performed a in-place upgrade from 6.12.10 to 6.12.11 using the in-built wizard. Upon reboot i noticed my docker containers were missing as the service had failed to start. Looking at the logs i can see the error message "Homeserver root: '/mnt/user/system/docker/docker.img' is in-use, cannot mount" -> see attached '6.12.11' Dx Log. Downgrading my system back to 6.12.10 has fixed my docker issue -> see attached '6.12.10' Dx Log.
- Minor
- 306 views
-
Hi, I'm running unraid in a proxmox VM and yesterday I upgraded from 6.12.11 to 6.12.13. Today my unraid was not accessible and looking at the console it was in this state: I want to mention that I never faced such issue before, it was 100% stable. I'm downgrading to 6.12.11. Regards.
- Minor
- 588 views
-
Upgraded to 6.12.12 from 6.12.11 - my Win11 - VM start to have strange behavior: - the shares inside the VM pointing one to a synology and another to internal unraid share (NVME) stop responding after 10-20 Mbytes written on share - qbittorent who use one of the shares for temp downloading freeze (after 10-20Mbytes downloaded) Tried: - Upgraded virtio to last one 0.1.262-2 No changes Extra: after i stopped the VM manager in settings and tried to r
- Annoyance
- 657 views
-
On one machine I have (backup -- diagnostic attached) the coretemp CPU temperature sensor is no longer available fan is no longer detected, unless I set to PWM minimum 80 fan speed is detected between 800 and 23000 RPM, when on, and it's seemingly random (note: it's a 600~1600RPM fan) Back to 6.12.11 and everything is normal again. On 6.12.12: On 6.12.11 (what's expe
- Closed
- 1388 views
-
hi, I created a new [01 Music] under the [Disk_Media] folder of disk2 and there is no [01 Music] folder in disk3. I selected [Manual: do not automatically split directories], but the files were still written to disk3, and in The [01 Music] folder is automatically created under the [Disk_Media] folder of disk3.
- Annoyance
- 707 views
-
I got 2 VM's installed: 1. Windows 10, runs at 12 cores, 16Gb memory. 2. Debian 12.6, runs at 4 cores, 4Gb memory. Both installed on fast cache SSD, both has selected it's own logical CPU cores. If started alone they both runs smooth and fast. But If I got Windows VM running, starting Debian takes almost endless amounts of time (15-20+ mins) and everything goes very slow with it, I'm getting error messages in console while it's loading about locking cpu by
- Urgent
- 492 views
-
Good Day I am experiencing issues with the the web UI under docker for release I upgraded to 6.12.11. Has anyone else experienced this issue. Is there a work around?
- Urgent
- 276 views
-
After upgrading to 6.12.1 from 6.12.0, NFS does not seem to come up. I am using a custom exports file within exports.d but 'exportfs -rv' isn't throwing any errors on a config issue. Dropping back to 6.12.0 seems to work as expected. I don't see anything in the changelog that changed NFS or its underlying dependencies? root@Bakery:~# showmount -e clnt_create: RPC: Program not registered Jun 20 14:57:26 Bakery rpc.statd[28411]: Failed to read /var/lib/nfs/state: Suc
- Retest
- Minor
- 6414 views
-
My server will randomly go offline and I will have to reboot to get online. I was using the network port on the motherboard and I read that certain network cards had issues with the update to 6.12.11 so I installed a new network card (not Realtek) and still having the same issues. alfred-diagnostics-20240814_1154.zip
- Minor
- 480 views
-
There is a very minor spelling typo in the tooltip in Wireguard "Local server uses NAT:" tooltip. "Addressess" should be "addresses". Again, very minor When NAT is enabled, the server uses its own LAN address when forwarding traffic from the tunnel to other devices in the LAN network. Use this setting when no router modifications are desired, but this approach doesn't work with Docker containers using custom IP addressess. When NAT is disabled, the server uses the WireGu
- Minor
- 279 views
-
WebUI showing info incorrectly in Chrome (Edge is OK) Some data, such as scrubbing info, boot menu edit showing incorrectly in Chrome. Attaching Chrome screenshots vs Edge screenshots. Unraid version: 6.12.10, but the problem is the same in different version as well (7 beta, 6.12.9 etc). Boot menu seems messed up in Edge as well as in Chrome, attaching nano screenshot of nano /boot/syslinux/syslinux.cfg
- Annoyance
- 307 views
-
When you deploy a docker container that is the same as an existing one, but differs only in casing, the template file for the already existing container is overwriten by the new one. For example make a container called "HandBrake", then make another one with different settings (like same image but another var, other path, ...). Unraid will make the 2nd one but overwrite the on disk config of the already existing container. Now when clicking edit on either container goes to the same
- Minor
- 370 views
-
Each parity check process restarts the server after a variable interval - 1 to 60 minutes - following the last update from 6.12.10 to 6.12.11. Previous parity checks were all successful. No HW change was made to the server between versions. I'll revert to 6.12.10 and if the parity check still fails, I'll start looking into the hardware (change PS first and so on) tower-diagnostics-20240802_1633.zip
- Closed
- 346 views
