Leaderboard

Popular Content

Showing content with the highest reputation since 02/21/17 in Reports

  1. Welcome (again) to 6.9 release development! This release marks hopefully the last beta before moving to -rc phase. The reason we still mark beta is because we'd like to get wider testing of new multiple-pool feature, as well as perhaps sneak in a couple more refinements. With that in mind, the obligatory disclaimer: Important: Beta code is not fully tested and not feature-complete. We recommend running on test servers only! That said, here's what's new in this release... Multiple Pools This features permits you to define up to 35 named po
    30 points
  2. As always, prior to updating, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Besides bug fixing, most of the work in this release is related to upgrading to the Linux 5.9 kernel where, due to kernel API changes, it has become necessary to move device spin-up/down and spin-up group handling out of the md/unraid driver and have it handled entirely in user space. This also let us fix an issue where device spin-up of devices in user-defined pools was executed serially instead of in parallel. We should also now be able
    22 points
  3. Since I can remember Unraid has never been great at simultaneous array disk performance, but it was pretty acceptable, since v6.7 there have been various users complaining for example of very poor performance when running the mover and trying to stream a movie. I noticed this myself yesterday when I couldn't even start watching an SD video using Kodi just because there were writes going on to a different array disk, and this server doesn't even have a parity drive, so did a quick test on my test server and the problem is easily reproducible and started with the first v6.7 release c
    22 points
  4. EDIT (March 9th 2021): Solved in 6.9 and up. Reformatting the cache to new partition alignment and hosting docker directly on a cache-only directory brought writes down to a bare minimum. ### Hey Guys, First of all, I know that you're all very busy on getting version 6.8 out there, something I'm very much waiting on as well. I'm seeing great progress, so thanks so much for that! Furthermore I won't be expecting this to be on top of the priority list, but I'm hoping someone of the developers team is willing to invest (perhaps after the release).
    19 points
  5. tldr: If you require hardware support offered by the Linux 5.x kernel then I suggest you remain on 6.8.0-rc7 and wait until 6.9.0-rc1 is published before upgrading. The "unexpected GSO type" bug is looking to be a show stopper for Unraid 6.8 using Linux kernel 5.3 or 5.4 kernel. We can get it to happen easily and quickly simply by having any VM running and then also start a docker App where Network Type has been set to "Custom : br0" (in my case) and I've set a static IP for the container or toggle between setting static IP and letting docker dhcp assign one. There are probably a
    18 points
  6. New in this release: GPU Driver Integration Unraid OS now includes selected in-tree GPU drivers: ast (Aspeed), i915 (Intel), amdgpu and radeon (AMD). These drivers are blacklisted by default via 'conf' files in /etc/modprobe.d: /etc/modprobe.d/ast.conf /etc/modprobe.d/amdgpu.conf /etc/modprobe.d/i915.conf /etc/modprobe.d/radeon.conf Each of these files has a single line which blacklists the driver, preventing it from being loaded by the Linux kernel. However it is possible to override the settings in these files by creating the directory 'config/modprobe.d' on
    15 points
  7. Welcome to 6.9 beta release development! This initial -beta1 release is exactly the same code set of 6.8.3 except that the Linux kernel has been updated to 5.5.8 (latest stable as of this date). We have only done basic testing on this release; normally we would not release 'beta' code but some users require the hardware support offered by the latest kernel along with security updates added into 6.8. Important: Beta code is not fully tested and not feature-complete. We recommend running on test servers only! Unfortunately none of our out-of-tree drivers wil
    13 points
  8. As always, prior to updating, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Hopefully spin-up/down sorted: External code (docker containers) using 'smartctl -n standby' should work ok with SATA drives. This will remain problematic for SAS until/unless smartmontools v7.2 is released with support for '-n standby' with SAS. SMART is unconditionally enabled on devices upon boot. This solves problem where some newly installed devices may not have SMART enabled. Unassigned devices will get spun-down according t
    12 points
  9. Back in the saddle ... Sorry for the long delay in publishing this release. Aside from including some delicate coding, this release was delayed due to several team members, chiefly myself, having to deal with various non-work-related challenges which greatly slowed the pace of development. That said, there is quite a bit in this release, LimeTech is growing and we have many exciting features in the pipe - more on that in the weeks to come. Thanks to everyone for their help and patience during this time. Cheers, -Tom IMPORTANT: This is Beta software. We recommend runni
    12 points
  10. It's easy for us to get overwhelmed by new issues, especially coinciding with new features and new kernel releases. Our lack of immediate reply does not mean your report is being ignored. We very much appreciate all hints, testing results, etc. Remember, for very odd issues, please reboot in "Safe Mode" to ensure no strange interaction with a plugin.
    11 points
  11. New in Unraid OS 6.7 release: New Dashboard layout, along with new Settings and Tools icons. Designed by user @Mex and implemented in collaboration with @bonienl. We think you will find this is a big step forward. Time Machine support via SMB. To enable this feature it is necessary to first turn on Enhanced OS X interoperability on the Settings/SMB page. Next, select a share to Export for Time Machine in the share SMB Security Settings section. AFP support is deprecated. Linux kernel 4.19. This is the latest Long Term Support kernel. We will go with t
    11 points
  12. Changes vs. 6.9.0-beta29 include: Added workaround for mpt3sas not recognizing devices with certain LSI chipsets. We created this file: /etc/modprobe.d/mpt3sas-workaround.conf which contains this line: options mpt3sas max_queue_depth=10000 When the mpt3sas module is loaded at boot, that option will be specified. If you add "mpt3sas.max_queue_depth=10000" to syslinux kernel append line, you can remove it. Likewise, if you manually load the module via 'go' file, can also remove it. When/if the mpt3sas maintainer fixes the core issue in the driver we'll get rid of thi
    10 points
  13. New in Unraid OS 6.8 release: The unRAIDServer.plg file (update OS) still downloads the new release zip file to RAM but then extracts directly to USB flash boot device. You will probably notice a slight difference in speed of extract messages. There is still a 'sync' command at the end, which causes each device to spin up serially as Linux kernel syncs each device (why does kernel do this serially? I have no idea). I am tempted to remove this because a Reboot of course spins everything up in parallel, but I'm concerned about users out there who might just hit Reset button and US
    10 points
  14. 6.9.0-beta24 vs. -beta22 Summary: fixed several bugs added some out-of-tree drivers added ability to use xfs-formatted loopbacks or not use loopback at all for docker image layers. Refer to Docker section below for more details (-beta23 was an internal release) Important: Beta code is not fully tested and not feature-complete. We recommend running on test servers only! Multiple Pools This features permits you to define up to 35 named pools, of up to 30 storage devices/pool. The current "cache pool" is now simply a pool named "cache".
    9 points
  15. A fairly large kernel update was published yesterday as was a new WireGuard release and I thought it important to update and sanity-check. We'll let this bake over the weekend and if no new big issue shows up we'll publish to stable. Then we can move on to the 5.4 kernel in Unraid 6.9. -rc9 summary: Update kernel to 4.19.88. Update to latest WireGuard release Other package updates. Specific changes in [-rcN] are indicated in bold below. New in Unraid OS 6.8 release: The unRAIDServer.plg file (update OS) still downloads the n
    9 points
  16. Mainly bug fix to address "slow transfer to xfs-encrypted array disks" issue. Version 6.7.0-rc4 2019-02-15 Base distro: docker: version 18.09.2 (CVE-2019-5736) qemu: version 3.1.0 (rev 2) patched pcie link speed and width support Linux kernel: version: 4.19.23 md/unraid: version 2.9.7 (setup queue properties correctly) Management: webgui: Syslog: added viewer webgui: Dashboard: table right adjustment in two columns view webgui: Dashboard: table adjustment in three columns view webgui: Diagnostics: dynamic fil
    9 points
  17. Please report only issues/bugs which are new in the prerelease. We've been holding back on this release a few days waiting for updated Intel ixgbe (10Gbit) OOT driver which builds correctly with 4.18 kernel. But no update yet so this release uses 4.17.19 kernel. Every major subsystem has been updated. In addition @bonienl has added some really cool features and update the default themes to match our new branding. Release notes: Version 6.6.0-rc1 2018-08-31 Base distro: aaa_base: version 14.2 (rev 5) aaa_elflibs: version 15.0 (rev 2)
    9 points
  18. -rc7 tldr: Updated kernel and Intel microcode which was released just after -rc6. Revert libvirt from 5.9.0 to 5.8.0 because 5.9.0 has bug where 'libvirt_list_domains()' returns an empty string when all domains are started instead of a list of domains. Fixed md/unraid crash resulting when bringing cleared array device online (bug introduced in multi-stream support). Don't let backslash be included in share names and vdisk paths. Misc. webGUI fixes. Other package updates. Specific changes in [-rcN] are indicated in bold below. New i
    8 points
  19. tldr: Updated kernel. Fixed sqlite db corruption issue. Removed "vega 10 reset" patch. Removed "navi reset" patch. Reverted qemu. Fixed shfs bug. Fixed handling of quotes in passwords. Misc. webGUI fixes. Other package updates. Announce /mnt/user0 is deprecated and will be removed in 6.9 release. Note: if your VM's won't start you need to click on Edit in the VM context page and then just click Update. This is because of reverting qemu. Specific changes in [-rcN] are indicated in bold below. New in Unraid OS
    7 points
  20. More bug fixes. More refinements to webGUI, especially check out latest Community Apps plugin! Other highlights: Parity sync/Data rebuild/Check pause/resume capability. Main components in place. Pause/resume not preserved across system restarts yet however. Enhanced syslog capability. Check out Settings/Nework Services/Syslog Server. Special thanks once again to @bonienl and @Mex. Version 6.7.0-rc3 2019-02-09 Base distro: jq: version 1.6 oniguruma: version 5.9.6_p1 php: version 7.2.14 Linux kernel: ver
    7 points
  21. -rc8 summary: Revert kernel to 4.19.87 for reasons described in this post. Update Intel 10Gbit (ixgbe) to out-of-tree driver version: 5.6.5 Update to latest WireGuard release Other package updates. Misc. webGUI fixes. Specific changes in [-rcN] are indicated in bold below. New in Unraid OS 6.8 release: The unRAIDServer.plg file (update OS) still downloads the new release zip file to RAM but then extracts directly to USB flash boot device. You will probably notice a slight difference in speed of extract messages. [-rc2] The '
    6 points
  22. There is a known issue with v6.8 where parity syncs can be slower than before, mostly but not limited to faster and/or very wide arrays. Although this isn't an urgent issue by any means this thread is meant to make it easier for LT to track the problem, also to have a better idea of how many users are affected and if there is a typical server configuration where the slowdown starts to be more noticeable. This issue results from changes made to the md driver and tunables to fix the "writes starve reads" problem with v6.7 and based on my testing there's a general slowdown
    5 points
  23. 6.9.0-beta25 vs. -beta24 Summary: fixed emhttpd crash resulting from having NFS exported disk shares fixed issue where specifying 1 MiB partition alignment was being ignored (see 1 MiB Partition Alignment below) fixed spin-up/down issues ssh improvements (see SSH Improvements below) kernel updated from 5.7.7 to 5.7.8 added UI changes to support new docker image file handling - thank you @bonienl. Refer also to additional information re: docker image folder, provided by @Squid under Docker below. known issue: "Device/SMART Settings/SMART controller t
    5 points
  24. Misc. bug fixes and more changes to try and track down source of 'SQLite DB Corruption' issue. Specific changes in [-rcN] are indicated in bold below. New in Unraid OS 6.8 release: The unRAIDServer.plg file (update OS) still downloads the new release zip file to RAM but then extracts directly to USB flash boot device. You will probably notice a slight difference in speed of extract messages. [-rc2] The 'sync' command at the end has been replaced with 'sync -f /boot'. Forms based authentication If you have set a root password for your server, u
    5 points
  25. 9/17/2019 Update: may have got to the bottom of this. Please try 6.7.3-rc3 available on the next branch. 9/18/2019 Update: 6.7.3-rc4 is available to address Very Slow Array Concurrent Performance. re: Trying to get to the bottom of this... First we have not been able to reproduce, which is odd because it implies there may be some kind of hardware/driver dependency with this issue. Nevertheless I want to start a series of tests, which I know will be painful for some since every time DB corruption occurs, you have to go through lengthy rebuild process. That said
    5 points
  26. Please open a new report for each issue/bug you find unique to this version. Bug fixes, improvements, and moving to linux 4.18 kernel. Release notes: Version 6.6.0-rc2 2018-09-06 Management: rc.nginx: added locations for robots.txt and js/css versioning this plugin: if legacy dynamix.plg file exists, delete it Linux kernel: version 4.18.6 removed OOT Intel ixgbe and ixgbevf, restored in-tree drivers: CONFIG_IXGBE: Intel(R) 10GbE PCI Express adapters support CONFIG_IXGBEVF: Intel(R) 10GbE PCI Express Virtual Fun
    5 points
  27. Likely related to this bug but this one is more serious, any new multi device pools created on v6.7+ will be created with raid1 profile for data but single (or DUP if HDDs are used) profile for metadata, so if one of the devices fails pool will be toast.
    4 points
  28. The ui is broken on the dashboard for docker & VM's on chrome browser. Does nothing when you click on icon's and it's only showing 1 vm of the 3 i have running. All fine if you go into docker tab and vm tab all works as it should.
    4 points
  29. tldr: Starting with 6.8.0-rc2 please visit Settings/Disk Settings and change the 'Tunable (scheduler)' to 'none'. Then run with SQLite DB files located on array disk shares and report whether your databases still become corrupted. When we first started looking into this issue one of the first things I ran across was this monster topic: https://bugzilla.kernel.org/show_bug.cgi?id=201685 and related patch discussion: https://patchwork.kernel.org/patch/10712695/ This bug is very very similar to what we're seeing. In addition Unraid 6.6.7 is on the last of the 4.18 k
    4 points
  30. -rc6 tldr: Updated kernel and Intel microcode for yet another hardware vulnerability. Update to latest qemu stable patch release: 4.1.1 Support UD passphrase-encrypted volumes. Misc. webGUI fixes. Other package updates. Specific changes in [-rcN] are indicated in bold below. New in Unraid OS 6.8 release: The unRAIDServer.plg file (update OS) still downloads the new release zip file to RAM but then extracts directly to USB flash boot device. You will probably notice a slight difference in speed of extract messages. [-rc2] The 'sync'
    4 points
  31. This is continuation of this original issue report. There is some conflicting information in that topic and, therefore, with your help, we want to try and get to the bottom of this. We have several test servers running trying to reproduce this problem, so far hasn't happened. The first thing we want to definitively establish is whether the problem is isolated to only those cases where /config inside the container is mapped to: /mnt/user/appdata vs. /mnt/cache/appdata or /mnt/diskN/appdata Note: it does not matter what the "Default a
    4 points
  32. Hello, I have some cron jobs running during the night and morning every day. None of my cron job has run over the night, upgraded to 6.6.4 yesterday. No mover, no added backup script (using User Scripts), no daily trim and no Backup / Restore from CA. cat /etc/cron.d/root # Generated docker monitoring schedule: 10 */6 * * * /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php check &> /dev/null # Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated mover schedule: 0 3 *
    4 points
  33. Can I please ask everyone when you mark an issue as "urgent" to obey these conditions: 1) The problem is reproduceable 2) Diagnostics and other relevant information are attached in the post We (the receiving side) get alarm bells ringing and act asap, but need info as much as possible to find and resolve the issue. Thank you.
    4 points
  34. Just noticed that on the Dashboard one cpu at a time goes to 100%. Running top shows wsdd taking 100% (I am assuming that means 100% on one processor). It jumps around to both regular and HT processors, all of which are not pinned to a VM. It does not seem to be impacting any function or performance; I have not seen this before upgrading to 6.8.0. I do not see any issues in the system log.
    3 points
  35. Oct 12 03:35:17 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 1357, hdr_len 1411 Oct 12 03:35:17 Storage kernel: tun: 13 e4 3d f7 10 86 b8 9e 87 b1 5f 81 d9 7a 98 c9 ..=......._..z.. Oct 12 03:35:17 Storage kernel: tun: 26 fa 2d 78 50 03 f2 b2 22 55 bc 68 29 75 83 46 &.-xP..."U.h)u.F Oct 12 03:35:17 Storage kernel: tun: 04 35 d4 e4 71 d8 5c 04 e3 e2 a2 6d 4e 1f 22 9d .5..q.\....mN.". Oct 12 03:35:17 Storage kernel: tun: 6f 97 72 60 c9 63 2b dc f4 ec c7 4f 68 60 66 9e o.r`.c+....Oh`f. Getting the above message repeated over and over again in the log whenever a docker tries to a
    3 points
  36. @Valerio found this out first, but never received an answer. Today I found it out, too. But this is present since 2019 (or even longer). I would say it's a bug, as: it prevents HDD/SSD spindown/sleep (depending on the location of docker.img) it wears out the SSD in the long run (if docker.img is located here) - see this bug, too. it prevents reaching CPU's deep sleep states What happens: /var/lib/docker/containers/*/hostconfig.json is updated every 5 seconds with the same content /var/lib/docker/containers/*/config.v2.json is updated e
    3 points
  37. Hi, while i was trying to test the new WSL2 feature it seems nester VM feature is not working anymore. Unraid 6 8 3 VM Windows 10 pro what have i done disabled all VMs, disabled VM Manager, unraid shell modprobe -r kvm_intel modprobe kvm_intel nested=1 edited VM xml template with the following entry under <cpu> section <feature policy='require' name='vmx'/> tried starting VM Manager, no way, always ended in <LIBVrt service failed to start> after some digging and results only showed check pathes
    3 points
  38. Lots of base package updates, other fixes. Hopefully one of the last -rc's before stable release. Version 6.7.0-rc6 2019-03-25 Base distro: adwaita-icon-theme: version 3.32.0 at-spi2-atk: version 2.32.0 at-spi2-core: version 2.32.0 atk: version 2.32.0 bash: version 5.0.003 ca-certificates: version 20190308 coreutils: version 8.31 curl: version 7.64.0 (CVE-2019-8907, CVE-2019-3822, CVE-2019-3823) dhcpcd: version 7.1.1 dnsmasq: version 2.80 docker: version 18.09.3 e2fsprogs: version 1.45.0 ethtool:
    3 points
  39. As explained here there was a pretty significant flaw introduced way back during Linux kernel 4.19 development having to do with page caching. The most obvious effect with Unraid was to cause spin-up of drives not involved in large transfers due to cached device top-level directory i-nodes getting reallocated prematurely. The latest kernel patch release (4.19.24) fixes this issue. More webGUI refinements are also included. Version 6.7.0-rc5 2019-02-22 Linux kernel: version: 4.19.24 Management: update smartmontools drivedb and hwdata/{pci.ids,us
    3 points
  40. After updating to 6.9 Final the HDD's (sata) no longer go into standby (after 30 min), no spin down. I also set the delay to 15 minutes but the HDD's just don't go into standby. I have not changed any system settings before, only when I tried to solve the problem (uninstalled plugins etc.). Before the update, on 6.8.3, the spin down worked fine. I hope that you can help.
    2 points
  41. If an extended SMART self test takes longer than the configured spin-down delay for the array disk, then the disk spins down and the self test is aborted. This behaviour is different from previous versions, where spin-down was temporarily suspended until after the self-test had completed. The message "SMART self test in progress" appears but the spin-down prevention doesn't operate. pusok-diagnostics-20210120-0317.zip (I know the unassigned Hitachi disk is totally shot!)
    2 points
  42. When I try to use Veeam as a backup target using NFS, I always have to reboot my Veeam Backup server before starting the job or I will have errors about stale file handles in the Veeam logs and the job failes. The options provided on the forum with the tunables didn't work. The best possible solution would be to implement a newer version of NFS (4.x) so we can finally get rid of all these old time errors for multiple users. I'm running beta25 at the moment (latest at the time of posting)
    2 points
  43. This is more a request than a bug report, newer kernels support btrfs raid1c3 (3 copies) and raid1c4 (4 copies), currently a pool converted to raid5 or raid6 by using the GUI options will use raid1 for metadata (and rightly so since it's not recommended to use raid5/6 for metadata), the problem for a raid6 pool is that redundancy won't be the same for data and metadata as warned in the log: kernel: BTRFS warning (device sdb1): balance: metadata profile raid1 has lower redundancy than data profile raid6 i.e., data pool data chunks can support two missing devices but metadat
    2 points
  44. I installed RC1 and it booted fine. Dockers & VM's running. Hit the Stop button to bring down the array so I could change a SMB setting to disable netbios. The status bar kept reporting that it was retrying to unmount. Unable to pull up the syslog via the GUI so I telnetted in and tailed the syslog. Received the following over & over. Oct 15 01:17:30 NAS emhttpd: Retry unmounting disk share(s)... Oct 15 01:17:35 NAS emhttpd: Unmounting disks... Oct 15 01:17:35 NAS emhttpd: shcmd (250): umount /mnt/cache Oct 15 01:17:35 NAS root: umount: /mnt/cache: target is busy. O
    2 points
  45. Hi, I've posted this already, but into an incorrect forum where it remained unnoticed. So sorry for the x-post. Symptoms: Plex HW transcoding does not work with Docker on unRAID 6.7.x (0 through 2), although it is working fine when downgrading to 6.6.7 without any change in unRAID or Docker container configuration. go file: #!/bin/bash #Setup drivers for hardware transcoding in Plex modprobe i915 chmod -R 777 /dev/dri #Start the Management Utility /usr/local/sbin/emhttp & syslinux.cfg untouched as i915 support is included OOB fo
    2 points
  46. This is not a big deal and has been reported before on the general support forum, when a custom controller type is used for SMART you can see all the SMART attributes including temp, but for some reason temp is not displayed on the GUI or dash, other user was using the HP cciss controller and the same happens to me with an LSI MegaRAID controller, so looks like a general issue when using a custom SMART controller type. Note, I'm using two disks in RAID0 for each device here, so I can only choose SMART from one of the member disks
    2 points
  47. Q: -rc3? what happened to -rc2? A: we thought a setting resulted in disabling auto-logout but instead made it happen almost immediately - sorry about that. Changes in [-rc2] are indicated in bold below. New in Unraid OS 6.8 release: The unRAIDServer.plg file (update OS) still downloads the new release zip file to RAM but then extracts directly to USB flash boot device. You will probably notice a slight difference in speed of extract messages. [-rc2] The 'sync' command at the end has been replaced with 'sync -f /boot'. Forms based authentic
    2 points
  48. So, after getting into RC2, I was trying to optimize my pinning using the new interface. I looked up my NUMA boundaries in the process: numactl --hardware available: 2 nodes (0-1) node 0 cpus: 0 1 2 3 4 5 6 7 16 17 18 19 20 21 22 23 node 0 size: 32040 MB node 0 free: 256 MB # <<< Make note of this value node 1 cpus: 8 9 10 11 12 13 14 15 24 25 26 27 28 29 30 31 node 1 size: 32243 MB node 1 free: 19974 MB node distances: node 0 1 0: 10 16 1: 16 10 I'm currently running two VMs as of this command. VM 1: 16gb RAM, CPUs 4-7, 20-23 (So, numa node 0,
    2 points
  49. Changes in [-rc2] are indicated in bold below. New in Unraid OS 6.8 release: The unRAIDServer.plg file (update OS) still downloads the new release zip file to RAM but then extracts directly to USB flash boot device. You will probably notice a slight difference in speed of extract messages. [-rc2] The 'sync' command at the end has been replaced with 'sync -f /boot'. Forms based authentication If you have set a root password for your server, upon boot you'll now see a nice login form. There still is only one user for Unraid so for username enter root. Thi
    2 points
  50. Please open a new report for each issue/bug you find unique to this version. Version 6.6.0-rc4 2018-09-16 Linux kernel: version 4.18.8 Management: webgui: System devices: fixed display of ACS override warning message webgui: Correction in custom parity schedule webgui: VM edit corrections create image when new vdisk is added keep sound card selection included fix add/remove of network interfaces webgui: CPU pinning: preserve "emulatorpin" entry
    2 points