Leaderboard

WOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOHAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA Unbelievable, but finally success. I had given up on having a working AMD gpu reset bug patch on my main system in my OSX Mojave VM with 5700XT passed. Tried every patch on the planet , which either crashed my whole system , or just did not work and required reboots on every VM restart, incl more recently using builds from / with the help of the great ich777 and giganode, but even their help could not beat my stubborn system where others had success using the same builds. So i forgot about it untill today. I just tried to give the Unraid-Kernel-Helper a go and build a kernel myself with just zfs and the the audio-reset branch of the vendor-reset patch. And it is working like a rock. I can do whatever i want with my OSX Mojave VM , even force shutdowns. Zero issue starting it up again. Amazing. Thanks for all the hard work guys !!!!!!

It's included in the Unraid-Kernel-Helper, please delete the Container and redownload it from the CA App (I recommend that because I add and change a lot in the template... ).

No problem, you're welcome! All that counts is that it works now, but more importantly, that everything is fine now!! 😉

I am so sorry buddy i did not react sooner, but had a bit of a bad personal time so was off the radar for a while. And again , thanks for all the help in the past.

It seems that I finally have some good news about those crashes Yes, I have looked up the recommended slots for 2 and 4 modules and always placed them in that way. There is no overclocking enabled as you are totally right about the stability aspect as well. --- I have updated to the latest version 6.9.0-RC1 when it was released, but that did not solve it (so it was not solved by the new kernel - which I hoped would fix it). After that I have done the following, which seems to have solved it: - Upgrade to 6.9.0-RC2 - Disabled IPv6 network for Unraid completely Since then, the server is up and running for 37+ days and no error at the logs at all. (maximum was ~15 days before) I did not restart the server since then, so I hope that it will stay the same for the next (RC3?) release. I believe it is the IPv6 setting that does not make it crash anymore. It might be due to some misconfiguration on my home network - or some Unraid related problem with the Unraid network settings in general. I have also found a topic about a similar problem: - https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-to-dockers/ It seems to be solved by using multiple NICs / setting up VLANs etc.: - https://forums.unraid.net/topic/62107-network-isolation-in-unraid-64/?tab=comments#comment-609082&searchlight=1 As the current state (disabling IPv6 completely) is not what I want, I'll try those solutions in the future. However, my network does not really support VLANs due to my current hardware (FRITZ!Box router). I'll report back as soon as I have done some more testing on those IPv6 and general network-related settings.

Open the config and you will see two lines like below: "proxy_pass $upstream_proto://$upstream_app:$upstream_port; Delete $upstream_app and repalce with IP of HA instance. You'll need to do it for both. proxy_pass $upstream_proto://10.1.1.200:$upstream_port; (For example) Save config and restart SWAG.

Yes, looks normal. I have HandBrake presets that use Intel QuickSync (iGPU) for transcoding and it does reduce the amount of CPU, however, 60% CPU usage even with hardware based encoding can be expected. Handbrake will always decode with the CPU and all audio and subtitles are handled via CPU as well. The latter two aren't a big load, but decoding is.

After a bit more digging found several related posts (after understanding that this is about forcing a user over SMB): Exactly my problem Solution is to add the following lines to your /boot/config/smb-extra.conf [Global] force create mode = 0666 force directory mode = 0777 force user = nobody force group = users create mask = 0666 Marking as solved.

LEaving my solution in case someone is having the same issue as I was. I deactivated all power saving options on my bios and one by one started to enable them until i got a crash. The culprit seems to be C1E options which if i understoop properly will allow for savings in CPU when not doing full load. This took me a month to pinpoint so i hope is useful to someone.

You forgot to add "fast on request"... 😁

glad to here from you... we've had a relatively long private conversation about that issue.. After many successful attempts I wrote you a pn to inform you. Sadly you never asked. I'm happy that we have another success now!!! Exactly. As not even one person failed to use navi cards with the specific branch, they included it in master branch.

its the https://github.com/gnif/vendor-reset but i just include it via the kernel helper docker.

Glad to hear... @giganode is this necessary anymore? I think the master branch should now also work.

I'm unclear about your description. Does the problem occur when running Unraid "bare metal"?

Free Plex, of course, will still do software (CPU) transcoding. Plex Pass is only required for hardware (GPU) transcoding in addition to its other benefits. Your current CPU has a passmark score of less than 1000, so, according to Plex, it is not capable of doing even one 1080p transcoding stream; especially since the recommendation for unRAID is an additional 2000 passmarks for system overhead. If you want a good transcoding experience with Plex, some sort of upgrade is in order. The Ryzen 5 3600 you were considering has a very good 17,000+ passmark score.

I didn't really understand the above using a translator, but there are several ATA errors on multiple devices, suggesting a controller or connection/power problem, just a small example: Jan 28 02:08:39 U3 kernel: ata10.00: exception Emask 0x50 SAct 0x20000000 SErr 0x4890800 action 0xe frozen Jan 28 02:08:39 U3 kernel: ata10.00: irq_stat 0x08400040, interface fatal error, connection status changed Jan 28 02:08:39 U3 kernel: ata10: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch } Jan 28 02:08:39 U3 kernel: ata10.00: failed command: READ FPDMA QUEUED Jan 28 02:08:39 U3 kernel: ata10.00: cmd 60/80:e8:d0:13:13/00:00:00:00:00/40 tag 29 ncq dma 65536 in Jan 28 02:08:39 U3 kernel: res 40/00:e8:d0:13:13/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Jan 28 02:08:39 U3 kernel: ata10.00: status: { DRDY } Jan 28 02:08:39 U3 kernel: ata10: hard resetting link Jan 28 02:08:39 U3 kernel: ata9.00: exception Emask 0x10 SAct 0x6000 SErr 0x4090000 action 0xe frozen Jan 28 02:08:39 U3 kernel: ata9.00: irq_stat 0x00400040, connection status changed Jan 28 02:08:39 U3 kernel: ata9: SError: { PHYRdyChg 10B8B DevExch } Jan 28 02:08:39 U3 kernel: ata9.00: failed command: READ FPDMA QUEUED Jan 28 02:08:39 U3 kernel: ata15.00: exception Emask 0x10 SAct 0x3 SErr 0x1990100 action 0xe frozen Jan 28 02:08:39 U3 kernel: ata9.00: cmd 60/40:68:90:0e:13/05:00:00:00:00/40 tag 13 ncq dma 688128 in Jan 28 02:08:39 U3 kernel: res 40/00:70:d0:13:13/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 28 02:08:39 U3 kernel: ata15.00: irq_stat 0x08400000, PHY RDY changed Jan 28 02:08:39 U3 kernel: ata9.00: status: { DRDY } Jan 28 02:08:39 U3 kernel: ata15: SError: { UnrecovData PHYRdyChg 10B8B Dispar LinkSeq TrStaTrns } Jan 28 02:08:39 U3 kernel: ata9.00: failed command: READ FPDMA QUEUED Jan 28 02:08:39 U3 kernel: ata15.00: failed command: READ FPDMA QUEUED Jan 28 02:08:39 U3 kernel: ata15.00: cmd 60/40:00:90:0e:13/05:00:00:00:00/40 tag 0 ncq dma 688128 in Jan 28 02:08:39 U3 kernel: res 40/00:08:d0:13:13/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 28 02:08:39 U3 kernel: ata9.00: cmd 60/80:70:d0:13:13/00:00:00:00:00/40 tag 14 ncq dma 65536 in Jan 28 02:08:39 U3 kernel: res 40/00:70:d0:13:13/00:00:00:00:00/40 Emask 0x10 (ATA bus error) As for the unmountable disk there's filesystem corruption: Jan 28 01:51:42 U3 kernel: BTRFS warning (device md3): md3 checksum verify failed on 22102016 wanted CB943766 found 565F6860 level 0 Jan 28 01:51:42 U3 kernel: BTRFS warning (device md3): md3 checksum verify failed on 22102016 wanted 7EA49A72 found 222D9443 level 0 and with btrfs not And with btrfs not always so easy to recover, you can see here for some options: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490

In case of Java8... did you try this?: https://code2care.org/howto/install-java-on-macos

If it does you can always revert back, but it would not interfer with you Nvidia card, why should it...

NO, I havent sold my 5700XT yet. my issues are none related to the cards or macOS, my 5700XT works perfect in Catalina and BIG SUR, the problem is that at the moment BIG SUR has no support for JAVA 8 and IF i sell my 5700XT to get a 6800 (which is highly available here in my country) just to have a RESET BUG free experience, then I lose my ability to develop in macOS as 6000 series ONLY works in BIG SUR.. either way im screwed lol.. gonna try the patch and see whats the thing.. I dual monitor one with the 5700XT and macOS and one with ubuntu and a NVIDIA 2070 SUPER (which works FLAWLESS), hope that patch does not cause any issue with my setup

I think this is the appropriate answer: Soon™

I don't wanna argue with you anymore. You simply don't want to understand it. Im out...

Obviously, you're free to do as you wish... but I have to push something that works for everyone. I did some reading of that bug and some stackoverflow posts and it seems that Chrome height percentage values are based on the parent container height. If no absolute height is set to calculate percentage against it defaults to the real height of the image (causing this issue). If we make it auto, it will calculate height based on the calculated width which should easily maintain a nice aspect ratio since all of the images I'm using are square. This will also retain responsiveness for people with larger/smaller font sizes either due to zooming or different resolution desktops.

I think you shouldn't use cache preferred -- you should use cache "yes" then mover will move it over and the df -h command will see the free space on your underlying drives, not the space on the cache. It's working for me with cache "yes". When I log into the docker image I also see the proper space for the mount as well.

Big Navi is basically the 6000 series. For a overview of the cards code names look here: https://github.com/gnif/vendor-reset#supported-devices

Do you see the docker you used if you go under "past apps" (or something like that - going off memory) in the community apps tab? The good thing about that awesome feature is that not only has your apps/docker install history, it also remembers the config you used with it. That basically means reinstalling everything is a one click affair.

Hey guys. Thank you for your thoughts. First of all I found a solution. When navigating to the map network drive prompt (this pc>map network drive) I had been using the "Browse..." button to try to find my share. That is when I was getting the error message. Typing in the IP address of the server then /path allowed me to connect! I'm not a Windows user really, I just have use it for a piece of exam related software (thank you covid). I set up access my shares on the mac by browsing the GUI and on Ubuntu by typing the IP and path. It never occurred to me that windows would have such a problem with the browse function until I watched a Spaceinvader One video (what a legend). He didn't use the "Browse..." button but typed out the path and recommended using an IP address rather than the server's name. FYI, I am using Windows 10 Pro 20H2 (not a VM). I had a lot of issues getting my exam software to run smoothly and had to update to get it working. I have a few windows VM's scattered across my PC's and ran into the same problem, with the same solution. Once again, Big thanks. Richard

No error since re format and restore data. Mark as SOLVED. Thank you.

Yes, but only if the target path is inside of the mapped path. Example: /container/data maps to /host/data Relative link: image.jpg Would target: /container/data/image.jpg which maps to: /host/data/image.jpg Would not work: ../images/image.jpg Would target: /container/images/image.jpg which maps to nothing (it stays inside the docker itself). This would only work if you map /container/images to /host/images as well or if you would map /container to /host for much broader access to the host (which was done in the "Plex example"). Depending to your target it's maybe better to create hardlinks to all the files that should be accessible through the container. But note: hardlinks work only for files. But they allow the following: /host/some_files/image.jpg links to /host/images/image.jpg /host/some_files/texts/text.txt links to /host/texts/2021/01/28/text.txt Now you map /host/some_files to the container and it can only access those files.

Hey, Sorry, I could not update you sooner as I was preoccupied but all I can say as for now its holding and no crashes at all. I will keep monitoring thank you again!

Just used your steps and this worked! Thank you so much for posting this!

root@unSERVER:~# ls -lah /mnt total 16K drwxr-xr-x 13 root root 260 Dec 19 08:43 ./ drwxr-xr-x 20 root root 460 Jan 19 21:27 ../ drwxrwxrwx 5 nobody users 120 Dec 19 08:43 RecycleBin/ drwxrwxrwx 1 nobody users 62 Jan 27 04:40 cache/ drwxrwxrwx 4 nobody users 41 Jan 27 04:40 disk1/ drwxrwxrwx 3 nobody users 27 Jan 27 04:40 disk2/ drwxrwxrwx 6 nobody users 75 Jan 27 04:40 disk3/ drwxrwxrwx 8 nobody users 105 Jan 27 04:40 disk4/ drwxrwxrwt 2 nobody users 40 Jan 2 10:05 disks/ drwxrwxrwx 8 nobody users 91 Jan 27 04:40 fast/ drwxrwxrwt 2 nobody users 40 Dec 19 08:41 remotes/ drwxrwxrwx 1 nobody users 41 Jan 27 04:40 user/ drwxrwxrwx 1 nobody users 41 Jan 27 04:40 user0/ root@unSERVER:~#

I've got an old laptop drive that I can format as APFS and send to you. If you want to contact me by PM with the details on where to send it to, I'll add it to my trip to the post office this week.

...oben in der Liste war doch das Nanoxia 1 revB, nicht das 4 😇 Ja, sorry, hatte nicht richtig gelesen. Ich habe dieses Nanoxia 1. Habe oben geedited. In dieser Konfiguration sind es 11x 3.5 HDDs. Wenn man am linken Einschub 2.5 statt 3.5 HDDs nimmt, dann sind es denke 5x 2.5 + 8x3.5. Mit dem sind es dann noch +3x 3.5. Ich hoffe mal das reicht bis 2025 - zumindest sind die ersten beiden Platten schon 50% voll. 😅 Übrigens, von Euch weiß nicht zufällig jemand wie man in unraid absolute path symlinks in relative path symlinks umwandelt, oder? Post hier.

Each additional disk requires more ports, more power, at some point more license. And at some point really should have dual parity so yet another disk. Larger disks perform better simply because of data density. Perhaps most importantly, each additional disk is an additional point of failure.

That worked. Thanks @JorgeB

First of all, they did not refuse. Instead gnif and amd had a few conversations and with others on reddit etc. as well.. Secondly they fixed the issue on big navi cards... So they definetly heard what the costumers said. Can't tell you if or when Big Sur will run with 6000 cards.. @derpuma told me that they is already something in big sur that belongs to big navi.. Nevertheless my 5700xt just runs fine in Big Sur...

No, you always can download the default bz* images and replace the custom built ones from the Unraid-Kernel-Helper on your USB Boot device and you will be back to stock Unraid since the images are the main things that makes Unraid, well Unraid... No problem, just asking.

Went back to Beta35 - not a single unwarranted spin-up in two full days. Meanwhile not a day went by without multiple random spin-ups of my drives.

If the container does not establish a connection to the VPN then the UI will not load. Sent from my CLT-L09 using Tapatalk

Hi All, i have found a recovery for my jitsi install when it became unusable after a update. Broadly speaking all you have to do is follow SpaceinvaderOne's video and install jitsi again with a small change... 1. Backup your old jitsi install (/mnt/user/appdata/jitsi) or just rename the folder. 2. Remove the jisti containers using portainer (delete). The container stack will be recreated in the video guide. 3. Start following the video guide till 8:52, right after the git clone command to pulldown the docker. 4. Goto /appdata/jitsi/github/docker-jitsi-meet and open the docker-compose.yml file in a text editor. 5. Change the version of the docker container which is pulled for the installation to an older version! I used build 4416 which was released around the time when the installation video was posted. Note: for reference goto: "https://hub.docker.com/search?q=jitsi&type=image" Then search for jitsi, there is a tab called "Tag" that shows all available container build versions. Modify the docker-compose.yml. Within the file there are 4 sections corresponding to each container: image: jitsi/prosody:latest replace the part after image: with jitsi/prosody:4416 image: jitsi/jicofo:latest replace the part after image: with jitsi/jicofo:4416 image: jitsi/jvb:latest replace the part after image: with jitsi/jvb:4416 image: jitsi/web:latest replace the part after image: with jitsi/web:4416 Once done, save the file and exit the editor. 6. Continue and finish the install following the guide in the video. Hope that helps to recover broken installs. It worked for me. Feel free to re-install and test any newer version of jitsi until your install breaks The latest version as of today had issues for me... Thanks.

The "latest versions" of these plugins are most likely for the latest version of Jellyfin (10.7.x). Download the last version of the plugin and it should work. Example: Version 6.0.0 for TMDB Collections = 10.6.X while version 7.0.0 is for version 10.7.x.

Just went through with my Silverstone DS380 build and modifications, let me know what you think. the temps and airflow are improved greatly after some real trial and error (could not have been done without you guys). Here are some pics (gimme a little time to add them) to answer most of the questions.

I've successfully setup ONLYOFFICE to work in my self hosted Nextcloud instance. Like many others here I use NginxProxyManager to setup reverse proxy and get a certificate from Let's Encrypt for my subdomains. As already mentioned here you don't need to create any config files and copying certificate and private key to a newly created folder certs in appdata ...... I think anyone who added at least one proxy host to NginxProxyManager with SSL certificate from Let's Encrypt pointing to the newly created subdomain will be able to configure OnlyOffice Document Server to work properly with Nextcloud. If not I will gladly provide some assistance. My main intention here is creating a brief HOW TO in order to restrict the access to ONLYOFFICE Document Server (for security reasons and data integrity) with encrypted signature, known as Secret Key. Let me emphasize that I don't own the credit for this tutorial, I'm just posting something found among user comments in @SpaceInvaderOne YouTube video tutorial How to Install and Integrate Only Office with Nextcloud. Many, many thanks to @SpaceInvaderOne for providing great tutorials for us "nerds" and make our experience with unRAID easier. HOW TO add and configure Secret Key in ONLYOFFICE: Stop the OnlyOffice Document Server container. In the "edit" option for the OnlyOffice Document Server docker, do "+ Add another Path, Port, Variable, Label or Device". Config Type: Variable Name: JWT_ENABLED (can be whatever you want to see in the UI, I used the key) Key: JWT_ENABLED Value: true Description: Enables use of Secret key [press ADD] Then add another variable: Config Type: Variable Name: JWT_SECRET (same thing, up to you) Key: JWT_SECRET Value: [WhateverSecretKeyYouWantToUse]. You can use the following command in Terminal (without quotes) to create a random Secret Key: "openssl rand -base64 48" and press Enter Description: Defines the Secret key value [press ADD] [press APPLY] Start OnlyOffice Document Server container. Go to Nextcloud > Settings > ONLYOFFICE page. Enter the Secret Key and click Save (you should get the message: Settings have been successfully updated ..... No restart of the Nextcloud docker was needed.

Der Vollständigkeit halber will ich kurz erwähnen, das das Problem gelöst wurde. Dazu verlinke ich kurz zum englischsprachigen Teil des Forums https://forums.unraid.net/topic/84601-support-spaceinvaderone-macinabox/?do=findComment&comment=912934

Thanks for the help in this post, works fantastically. TL;DR of original, here's a step by step guide for creating a mount on VM creation (as of unraid 6.8.3). In the "Unraid Share" section, select the unraid folder that you want to make mountable. This can be an individual share or a parent directory of the share for multiple. e.g `/mnt/user` In the "Unraid Mount tag" section, enter a tag name, this can be anything and will be passed to the VM. e.g `myMountTag` Complete VM setup, power on and install your VM OS or normal. The following steps require root/sudo user. Make a backup copy of fstab in case you mess up your configuration `sudo cp /etc/fstab /etc/fstab.orig` Create a target mount directory where you want to mount your share e.g. `sudo mkdir /path/to/myMountedDir` Edit `/etc/fstab` config by adding the following line to the end of the file, (change tag & path to your needs) `myMountTag /path/to/myMountedDir 9p trans=virtio,version=9p2000.L,_netdev,rw 0 0` Save fstab file and run `sudo mount -a` to check your mount works (there should be no output for on success) You should now have a mounted share in your VM Futher detail For anyone new to unraid, looking for an explanation as to what the fstab values are, here is an explanation <device>: myMountTag <mount point>: /path/to/myMountedDir <file system type>: 9P (The protocol that QEMU uses for a VirtFS) <options>: trans=virtio,version=9p2000.L (our transport for this share will be over virtio, and we specify the 9P version (2000.L) because the default for QEMU is 2000.U. "L" has better support for ACLs, file locking and more efficient directory listing, deletion edge cases etc) _netdev (tells the system that this mount relies on the network, and to delay the mount until a network is enabled) rw (mount as read/write) <dump>: 0 (disables backup via the dump command) <pass num>: 0 (disable any error checking) Cheers!

Try: sudo -u abc php /config/www/nextcloud/occ maintenance:mode --off EDIT - path was incorrect before, fixed it. You can also change the maintenance value variable in config.php located at /appdata/nextcloud/www/nextcloud/config/ and reboot the docker.

Do the following to let docker rebuild the networks rm /var/lib/docker/network/files/local-kv.db /etc/rc.d/rc.docker restart