Leaderboard

Popular Content

Showing content with the highest reputation since 11/06/21 in Report Comments

  1. Since you mention "for others to see", I take it as giving me right to comment (after all it IS in a public forum). So let me comment on this after reading your original post too. 1) Disclaimer: I am not taking the side of Limetech. I don't care. I had my own rough times in the past (with Tom too IIRC)... many years ago. Don't even remember why any more. Back then I "voted" with my decision. I stopped using unRAID for years. Yet I returned because it became what I dreamt it should be before I stopped using it. So being first and foremost a consumer, not a fanboy nor a hater, I just returned. My original Pro license waited for me patiently. 2) Since you are talking about "tone"... Your tone in your first post and this post is quite a Karen. You are only ONE customer. Who made you our representative and the right to speak for us? Who told you we want this removed (even if we don't use it, I don't either). It doesn't bother me. It just stays there, who cares. 3) I don't see any threat whatsoever by LT. Maybe you mean "treat", but still, I don't see an issue. 4) LT is a business, as you said. They make things, we buy them, they support them indefinitely ON the price we originally bought them (no service fees). So why would they be grateful, or would we be grateful? $$$ = product. And I bet you have the product already. It is a transaction - as simple as that. Yet, they stand by their clients all right and do it for years (and this is not proven by removing something nobody else asked to remove than entitled-you). 5) Also, since they are a business, it is in the end their choice if they want to actively promote a new feature (their "cloud" system) if it is not too intrusive. So that login up in the corner and the OPTIONAL plugin, is not what I would call "intrusive". 6) Nobody is forcing you to update unRAID to next version. Stay on the current one. Remove unRAID for all we care. 7) If this login button and menu is (or was) a real problem, I am sure someone will step in with a tiny plugin (like the one that widens the interface for super-wide screens), that removes it. Or you can try making such a plugin. 8 ) Back to tone. I am sure if your original post was something like "this thing on the top right about logging in... could you please make hide-able, maybe by a toggle in the settings in some future version, for us OCD people?". This possibly would get a better reply. Cheers.
    5 points
  2. Below I include my Unraid (Version: 6.10.0-rc1) "Samba extra configuration". This configuration is working well for me accessing Unraid shares from macOS Monterey 12.0.1 I expect these configuration parameters will work okay for Unraid 6.9.2. The "veto" commands speed-up performance to macOS by disabling Finder features (labels/tags, folder/directory views, custom icons etc.) so you might like to include or exclude these lines per your requirements. Note, there are problems with samba version 4.15.0 in Unraid 6.10.0-rc2 causing unexpected dropped SMB connections… (behavior like this should be anticipated in pre-release) but fixes expected in future releases. This configuration is based on a Samba configuration recommended for macOS users from 45Drives here: KB450114 – MacOS Samba Optimization. #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end [global] vfs objects = catia fruit streams_xattr fruit:nfs_aces = no fruit:zero_file_id = yes fruit:metadata = stream fruit:encoding = native spotlight backend = tracker [data01] path = /mnt/user/data01 veto files = /._*/.DS_Store/ delete veto files = yes spotlight = yes My Unraid share is "data01". Give attention to modifying the configuration for your particular shares (and other requirements). I hope providing this might help others to troubleshoot and optimize SMB for macOS.
    3 points
  3. I am adding some logging to UD to show that the NFS mount will not work until NFS is enabled. I also am disabling the Penguin icon when adding a NFS mount with a warning on the dialog when NFS is not enabled. NFS is required to be enabled for NFS clients on Unraid.
    2 points
  4. Thanks to everyone that has already tested and confirmed that the latest beta release of Plex works on the latest Intel processors! Just to follow up on my earlier comment... In Unraid 6.10.0-rc2 (like rc1) there is no need to create config/modprobe.d/i915.conf with with any custom options. If you previously created one, I'd recommend deleting it to get your system back to stock. It is also not necessary to install the "Intel GPU Top" plugin, although if you do install that it allows you to install the "GPU Statistics" plugin, which is handy for confirming that the i915 GPU is actually being used. To pass the i915 to a docker container, edit the container and add a "Device" with name and value of "/dev/dri". Then start the container and adjust any settings needed to get the application to use it. Note that only one container at a time can use /dev/dri. The big news is that the latest version of Plex has been updated to work with these 11th gen Intel CPUs / 12th gen GPUs: So... in Unraid 6.10.0-rc2, passing /dev/dri to the LSIO Plex Container with Plex Pass version 1.25.0.5246 installed and "Use hardware acceleration when available" enabled in Plex settings, Plex's "Now Playing" reports that it is doing hardware transcoding on my 11th Gen i9-11900K. This is further confirmed by the "GPU Statistics" plugin. woot! Jellyfin continues to work in rc2 as well, assuming the Plex docker is stopped and I pass /dev/dri to ich777's Jellyfin docker with "Intel Quick Sync" hardware acceleration enabled in Jellyfin settings. I haven't found a way to confirm that within Jellyfin, but the "GPU Statistics" plugin shows the GPU is in use. So far I have only done basic testing to confirm it works, I can't really speak to the quality of this vs CPU transcoding.
    2 points
  5. If you need a temporary fix while waiting for 6.10, go to Develop (you will have to enable the Develop menu in Preferences) > Experimental Features and turn off WebGL 2.0.
    2 points
  6. Thanks, I made a fix for the next Unraid release.
    2 points
  7. I have a similar issue with Catalina, samba is on and off. Reverted back to rc1 and everything seems to be OK. In my case the connection to the Tower samba shares will drop on a random basis. Not sure how to reproduce this issue.
    2 points
  8. With all due respect, have you addressed the UPC / login option located in the upper right of the webGUI header? Give us an option to take it off, remove it? I don't care to log in, I don't care for the cloud intrusion in my personal life, I don't care to see it, full stop period, regardless of your business case. And I am very unhappy how some of these intrusive feature are being pushed down our throats. I just want it off my GUI header and I don't want anything to do with unraid cloud service as working offline (OFF THE GRID) is my primary priority. Can we have that option?
    2 points
  9. Thanks Maxrad, the 45 drives link offers valuable insights.
    1 point
  10. When these system hangs happen for me (started on 6.9.2 and have continued with 6.10.0 RC), there is nothing meaningful in the syslog around the time of the hang but this is reported in the IPMI log. An OS Stop/Shutdown sounds like a kernel/driver issue to me. It's like the rest of the system is working but the OS just decided to shutdown. FWIW, I have never seen these shutdowns as a result of hardware transcoding.
    1 point
  11. There are bugs in samba version 4.15.0 included in Unraid 6.10.0-rc2 impacting SMB connections from macOS. Bugs noted in samba version 4.15.1 release notes. I have reverted to 6.10.0-rc1 and wait (with calm patience) for a future release of Unraid containing newer samba version. See this post for a bit more info on my experience optimizing Unraid samba for macOS: Unraid 6.10.0-rc1 and Unraid 6.9.2 both seem to provide me with reliable SMB connections for macOS (including Monterey 12.0.1)
    1 point
  12. The mce happened during processor initialization, and is a fairly common occurrence with certain hardware combinations and is quite safe to ignore.
    1 point
  13. It is reported to be. There’s also a workaround- https://forums.unraid.net/bug-reports/prereleases/popup-terminalconsole-unusable-on-safari-610-rc1-r1598/?do=findComment&comment=16463
    1 point
  14. Post the diagnostics, not the syslog when you get back to the computer
    1 point
  15. Nov 14 16:23:38 NIKOS-TOWER kernel: amdgpu 0000:0a:00.0: amdgpu: amdgpu: finishing device. According to the syslog snippet you posted you are loading the amdgpu driver which will prevent the card being passed through to a VM. Either stop loading the amdgpu driver or, if you need it for another AMD GPU, bind your 5700XT card to the VirtIO driver on the Tools -> System Devices page. As mentioned in the release notes, at the top of this page, which would explain the different behaviour.
    1 point
  16. You can actually do that by clicking the little gear icon in the lower right corner in the web player and select "Playback Data" this will bring up a window like: Hope that helps.
    1 point
  17. The original poster marked this as solved after this reply Does that not solve it for you? If not then maybe you don't have Maybe a new report with your diagnostics would be appropriate.
    1 point
  18. It's not about how old the flash drive is. You get one replacement per year regardless of the age of flash.
    1 point
  19. Confirmed: Using the linuxserver container (running 1.25.0.5220) on 6.10.0-rc2 and hardware transcoding works (including tone-mapping).
    1 point
  20. I had a similar thing happen when I upgraded my system with a new mainboard and cpu... 6.9.2 would not boot into the GUI... I was indifferent to it but discovered almost by accident that 6.10 RC1 worked.
    1 point
  21. Thanks! Turns out the file I was trying before wasn't HDR, but I tried one that was and tone mapping also appears to be working just fine. Picture looks correct to me with HDR off on the client and the tone mapping setting turned on on the server.
    1 point
  22. I decided to try 6.10rc2 today and it's been fine for me now. I got my VM up to Q35-6.1 and added a virtual TPM to go to Windows 11. All good now. Guess maybe it was something fixed by the component upgrades in rc2?
    1 point
  23. The internal Unraid nginx is for the GUI only and can't be used for other purposes.
    1 point
  24. Can't really see why it fails. I made a small change to the detection logic, let's see if that works!
    1 point
  25. Sure: root@Z490:~# dmidecode -t4 # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 3.2.0 present. Running cat /proc/cpuinfo does give: model name: Intel(R) Core(TM) i3-10300 CPU @ 3.70GHz I believe that's what was in the CPU info in 6.9.2.
    1 point
  26. Thanks for feedback. I encourage you to take a look at the Purchases section on our policies page and the My Servers wiki linked below. There are a few inaccuracies in your comment. If you have other questions, my DMs are open. https://unraid.net/policies https://wiki.unraid.net/My_Servers#Privacy
    1 point
  27. Thanks... Card seems better in win 10 but still having issues firing up in win 11. Ill try a clean build out at the weekend and report back. T
    1 point
  28. Thank you for reporting. I am making the dev team aware.
    1 point
  29. Update from another who was having the same issue on 6.9.3 After upgrading to 6.10-rc2 - Same result Updated docker settings to use ipvlan instead of macvlan - seems to have resolved the issue. Have not noticed any issues with any of my docker containers as a result of this change. Uptime 3 days, 43 minutes ( Prior to this change, was seeing hard crashes prior to the 3 day mark) Will report back if there's any change.
    1 point
  30. I would strongly recommend to set the DNS Server in unRAID itself to the one from your ISP or better speaking to the IP from your Router or any open DNS Server of your liking. unRAID needs exclusive access to the Internet without any blocking software in front of it.
    1 point
  31. Only if you install the Nvidia Driver plugin, otherwise it is not installed by default. This is already possible, the plugin let you choose between the latest production branch driver, the latest new feature branch driver, maybe the latest beta driver and also the last v470.x driver, But keep in mind that the Nvidia Driver plugin is for another use case and that is if you want to utilize the card in Docker containers. You don't need the plugin if you want to use the card in a VM!
    1 point
  32. Fixed it. The solution was just to upgrade my Win10 VM nvidia driver which was from 2020/09. It turns out that since 465.89 (2021/03) Nvidia has allowed virtual machines. For whatever reason 6.9.2 was allowing me to cheat the old driver and 6.10 wasn't.
    1 point
  33. I think resolved my earlier reported problem of unreliable SMB connections from macOS Monterey 12.0.1 to Unraid 6.10.0-rc2. Removing several user-added parameters (ie added by me several months back) from "Samba extra configuration" seems resolve my problem and I now have reliable SMB connections between macOS Monterey 12.0.1 and Unraid 6.10.0-rc2 (samba: version 4.15.0). My "Samba extra configuration": #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end [global] spotlight backend = tracker [data03] path = /mnt/user/data03 spotlight = yes My configuration adds SMB share point "data03" with support for macOS spotlight search. Unraid 6.10.0-rc2 now working very well for me – thanks for great work! EDIT: I posted success too soon. This (intermittent) problem is not resolved.
    1 point
  34. I would LOVE that, great suggestion mate Such a simple and elegant fix....
    1 point
  35. I sincerely hope that the UPC remains optional. I will not be using this, after the total disaster caused by a similar scheme employed by Ubiquiti. Mandatory signon using their cloud, which was promptly hacked exposing hundreds of thousands of user details. One of the main reasons I use unRAID is so I'm self-sufficient without the need of cloud-based logins, and also so I have as little user data out there as possible.
    1 point
  36. I wont annoy anyone by posting my objection to the UPC again, but in case it makes any difference to the company, for whom I have had great respect and good feelings for about 11 years, this will represent the end of my support. I will not upgrade from my current state. I have ZERO interest in having my servers connected to the internet except for one application on my backup server. There is no need to take any risk whatsoever of allowing some mistake/mismanagement/malicious attack/ whatever at Lime technology and _especially_ over this "for information only" forum. I am stunned that connecting registration on this forum directly to our server license and information was even floated except over a beers. I really can't believe this is being considered. I suppose the modern way of things is subscriptions to gouge every last dime out of customers at a seemingly low price month by month but I am rejecting it from microsoft and will reject it here. I am quite happy with my purchase, have recommended UNRAID uncounted times to others and several friends are now users but that is at an end. I will remain at my current version of unraid that that's that. It sounds like i need also to delete this forum account, unfortunately. I am certain noone gives a rat's but I thought I would clarify my position before signing off of the forum. Why not just charge for version upgrades instead? Is that because people might decide they dont need the current version and you'd like to charge them anyway? At the price of the security of my servers? I just dont understand. I have happily paid for my licenses and was actually considering purchasing a third, but man this will get very expensive very quickly if i pay for it every month. what happens when i stop paying?
    1 point
  37. There is a lot going on in the release, and a lot of good! Some mixed sentiment on the UPC and My Server stuff. Firstly the My Server stuff is fine, an optional additional service people can use to remotely monitor one or more servers. Great stuff useful for those that need or want this. The UPC stuff is a little more complex. I changed my key today, the old way, and it was super simple barely an inconvenience. I'll outline my concerns with this direction, take them as you will. UPC is linking to a forum. It could be that the forum backend is the core authentication system / CRM or the like, but it seems an odd choice to me. If a server is authenticated via UPC an open web socket is maintained. Generally not a big deal, but it's another thing to be exploited and as others have pointed out didn't work out so well for other companies. All information is useful to a hacker, no matter how little data may be captured if there is a breach it is exposing potentially vast configurations, IPs, and so on. On the configuration backups, why a private repo? This seems odd to me, are these encrypted per server? Wouldn't just end to end encrypted file blobs be more secure, regardless of saying "it doesn't include files with sensitive info". No company regardless of design or merit is immune to breaches, hacks, or acquisitions. While it's clear now that if you have a valid key you do not need to authenticate with UPC (forum), this is pretty much how all non-cloud authentications go to die. I've seen, you've seen it... And I get it, from a business perspective, it's easier for you to manage centrally, oversee, and move towards the subscription model. Confidence that a path like this isn't in the future would ease many, especially in the area of data storage where moving is not always trivial. Are you GDPR compliant, or similar data protection schemes (kind of not specific to the release, just generally) Are you ISO27001 and SOC certified such that we can be sure your development pipelines to your infrastructure won't be compromised with active connections to our servers? These are my concerns, the features and functions of Unraid in this release are great. Thanks for the work put into them
    1 point
  38. Agree, no risk like this is acceptable.
    1 point
  39. I can reproduce this and I have reported the issue to Limetech.
    1 point
  40. Thought I'd give an update. My system has an 11th Gen i9-11900K. In Unraid 6.9.2 (based on Linux kernel 5.10.28), I created this file on the flash: config/modprobe.d/i915.conf containing this text to activate the experimental i915 drivers for this GPU: options i915 force_probe=4c8a and Plex was able to do hardware transcoding. In some of the earlier private betas of 6.10, this worked as well. Starting with 6.10.0-rc1 (kernel 5.13.8) Plex was unable to do hardware transcoding on this system (it works on 9th and 10th gen Intel CPUs, just not 11th gen.) Internally today we are up to kernel 5.13.12 and Plex still will not do hardware transcoding on this system. In the 'Plex Media Server.log' it reports: TPU: hardware transcoding: enabled, but no hardware decode accelerator found On the plus side, you no longer need to create an i915.conf file with those custom options, the GPU activates right out of the box. And an interesting data point, this Jellyfin docker does hardware transcoding beautifully on the 6.10 rc's: https://forums.unraid.net/topic/102787-support-ich777-jellyfin-amdintelnvidia/ Now I'm not suggesting that die hard Plex fans need to switch to Jellyfin, I don't intend to. Just saying that the Linux drivers for the latest Intel CPU/GPUs are still in flux and for whatever reason, Jellyfin works with them and Plex does not. I do not know if a future Linux kernel will solve the problem, or if it will take an update from Plex. But I do not have high hopes for the current version of Plex doing hardware transcoding in rc2 on the latest Intel CPUs. Update - For completeness I will add that I am using the LSIO Plex Container: https://forums.unraid.net/topic/40463-support-linuxserverio-plex-media-server/ and Plex itself is currently (as of 8/25/21) version 1.24.1.4931. I have a Plex Pass.
    1 point
  41. I'm stable running on 6.10.0-rc1 with ipvlan for over a week now. An uptime of more than 7 days is a record in the past couple of months.
    1 point
  42. The solution is a lot simpler. Linux (unRaid) is somehow blocking the device on the host. I found out that you can unload the bluetooth drivers and it works now inside the VM. modprobe -r btusb modprobe -r bluetooth If you want that it persistent between reboot, you have to blacklist these drivers. Normally it is /etc/modprobe.d/ but unRaid does not replace the initial root filesystem (initrd / rootfs) with a block device so changes where are not persistent. In some other forum thread a found something like this for unRaid. (not tested because my system is still running) mkdir /boot/config/modprobe.d/ echo -e 'blacklist btusb\nblacklist bluetooth' > /boot/config/modprobe.d/bluetooth.conf If you still need bluetooth on the host for some docker container. It is probably needed to load the drivers again when the VM isn't running. modprobe btusb modprobe bluetooth
    1 point
  43. I wonder if it's as simple as the "bluez-firmware: version 1.2" upgrade in 6.10.0-rc1 causing the issue as the NMBluezManager is a different version on the two logs you've attached?
    1 point
  44. ipvlan seems like an upgrade from macvlan anyways so I didn't even bother with testing my config on macvlan with 6.10.0-rc1. I went right to ipvlan as soon as the update was complete and now at 45 hours with no issue. Generally couldn't make it half that long in 6.9.x when I tried with my configuration before locking up.
    1 point
  45. Thanks for replying, that's reassuring to see I'm not alone -at all- with this long lasting issue, as we have exactly the same UPS, except for the form factor (rack mount for you, tower for me). I should receive the serial cable on Tuesday, and I'll share my findings, of course. I read apcupsd manual again, and the setup should be rather straightforward according to http://apcupsd.org/manual/manual.html#modbus-driver . As i'm not a Linux expert, and haven't played with serial ports for years if not decades, I just wonder how to find the device name. I have an existing /dev/ttyS0 entry, I suppose it is the DB9 serial port of my motherboard, but not 100% sure. I'll keep you informed anyway.
    1 point
  46. This worked for me too, just so folks are clear and don't have to google I did the following: 1) edited /boot/syslinux/syslinux.cfg 2) added 'iommu=pt' to the line containing 'append initrd=/bzroot' 3) in the end it looks like: Thanks for the help this is great, I was freaking out that I was going to have to buy a new card and figure it out on a weekend. Everything seems to mostly be starting up and running fine.
    1 point
  47. Ok forget about the scsi_mod.use_blk_mq parameter, instead try this kernel parameter instead: For Intel-based: iommu=pt For AMD-based: amd_iommu=pt
    1 point