Leaderboard

The only way issues like yours get resolved is if you post here, include your diagnostics, and work with folks in the community to resolve. There are literally thousands upon thousands of users leveraging Unraid as a full server and don't have these problems. It sounds likely your issues are either container or configuration specific. A good example is if a container is writing to RAM instead of writing to actual storage. This can happen if your configuration for the container isn't right. I can definitely appreciate the frustration when things don't work as expected, but please refrain from blaming the solution before even giving us a chance to review and make it right. Sent from my Pixel 3 XL using Tapatalk

What controller is this disk connected to? It sounds like you might be using a controller that cannot handle disks greater than 2TB in size?

system and appdata shares exist only on cache

If you are talking about Plex as a docker in unRAID (and not running on a Windows VM), Plex cannot even use a discrete video card for transcoding. If you have an Intel CPU in your unRAID server with an iGPU and support for Quick Sync Video, the Plex docker can use that for hardware transcoding (reduces the load on the CPU). If your CPU does not have an iGPU which supports QSV, the Plex docker will transcode in software. For 1080p transcodes, this requires a CPU with about 2000 passmarks per simultaneous Plex stream. Software transcoding is much more CPU intensive than hardware transcoding but results in better quality at lower bitrates.

If you leave it blank it defaults to {path to your Plex folder in appdata}/Library/Application Support/Plex Media Server/Cache/Transcode If your appdata share in on an SSD, it will transcode on the SSD. If you have created a transcoder volume mapping in the Plex docker, then enter the specified container path as your Transcoder temporary directory.

@off topic here sorry cant help myself. But do you guys and girls thinkit would come with the slogan: Version 6.6.7 one step ahead of the devil! ? Sent from my SM-G955F using Tapatalk

There's this children's book my son likes called "Waiting is not easy" We should read it.

🖕

It's a btrfs limitation with raid5/6, used spaced will show correctly, available space will not account for parity, but since it still decreases with used space not much of a problem, also note that while you can use raid5/6, I use it myself, it's still less stable than other profiles, and a UPS is strongly recommended because of the the write hole issue that affects most raid5/6 implementations.

Added to Unraid 6.7

I've done this a few times now but recently my High Sierra refused to allow me to activate iMessage (only later I realised it was to do with the network card ordering mentioned below). I ended up just rebuilding the VM from scratch. The best guide I have found is here:- https://www.tonymacx86.com/threads/an-idiots-guide-to-imessage.196827/ If you use a fresh VM then you need not do all the clearing of the library folders, otherwise clean out the ones mentioned in the article. Having a proper serial number and board UUID is also required, the guide takes you through it. You need one that Apple says is invalid as it just means it hasn't been registered yet (a good thing). Ensure if using an existing VM you have signed into iCloud with that you remove it from your list of devices via Find my device on the iCloud site. One thing is *really* important and that is that the ethernet connection it set as eth0. If you only have the virtual network adapter then it should be fine but if you have a wifi card as well for handoff then sometimes it can get mixed up. Also remember that using UI mode in unRAID causes manual edits to disappear from the XML. I sometimes forget this and then waste a few hours before realising. If you follow the steps in that article though it should be fine...

Just a note for anyone that is trying to get Wallabag - I have finally had some luck with the official docker repository getting setup on unRAID. https://hub.docker.com/r/wallabag/wallabag/ For smaller installs, the basic version running on SQLite is quite nice. However, configuring it for me took some learning. When importing the container through CA, I mapped two different locations which were noted on the dockerfile: /var/www/wallabag/data was mapped to /mnt/user/appdata/wallabag/data Also /var/www/wallabag/web/assets/images was mapped to /mnt/user/appdata/wallabag/data Then I had CA create the container. Finally, I came up to a huge hurdle with the initial release of Wallabag 2.3.1 - it kept loading with no CSS - essentially unformatted text only on the screen. It turns out that they may have made a mistake in how your individual URL for Wallabag gets populated in the screen. So, I noticed that you can set that variable by editing the container. In the Wallabag container, click "Advanced Options", then in the "extra parameters" section, I added this line as it was mentioned in the Repo Info: -e SYMFONY__ENV__DOMAIN_NAME=https://my.wallabag.url As I'm using Wallabag behind a reverse proxy, I found that I needed my domain/name rather than IP address in that new parameter. Additionally, I had to change the "WebUI" to match the same address. Finally, it worked! Official Wallabag repo on unRAID, all nice and pretty. A little note of caution here as this post may exist for awhile, I totally feel like the DOMAIN_NAME issue is a simple mistake as the current docker build is only 8 days old as of this post. Changing that may not be a requirement in the future, but having to work around it was a great learning experience!

Type it in manually like plex/cache comma separated

I wrote this script that I tell user.scripts to fire off every morning at 7AM-11AM to back up some stuff from my Mac #!/bin/bash #Start Docker docker start resilio-sync #Delay before issuing Stop sleep 4h #Stop Docker docker stop resilio-sync

Hi Guys. I have made a video about setting up and configuring Duplicati on unRAID for cloud and network backups.

I thought this might be a good FAQ entry, so created it: What is "Boot GUI mode", and how do I change to it? Feel free to edit it, or suggest changes.

Is this likely to work on unRAID? ## Create an image file to your preferred size fallocate -l 50G /data/security/patio.img ## Format the image file as ext3 mkfs -t ext3 -q /data/security/patio.img -F ##Add the NFS mount to your FSTAB to mount the image at your NFS location (/etc/FSTAB) /data/security/patio.img /data/security/patio ext3 rw,loop,usrquota,grpquota 0 0