CS01-HS

I think a cache drive is optional and if so, no, they can run from the array. Here are instructions for replacing your cache pool but they may not be current so search to confirm: https://wiki.unraid.net/Replace_A_Cache_Drive

I haven't tested enough to confirm it's related but some time after installing the GUI plugin my syslog server started logging to syslog-127.0.0.1.log rather than syslog-<my unraid server's IP>. After uninstalling it it's back to normal. Strange.

I have no experience with 10K SAS drives but RAID 0 or RAID 5 will be faster than the array which is limited by the speed of a single drive, so you're better off with docker apps in the RAID pool. I forgot to mention in my other post - no reflashing. You format the pool as BTRFS and set the RAID level with the web GUI (software.)

I've run 3 drives in a secondary RAID 5 pool since about beta-25, so far so good. It shows as protected on the Shares page. I'd worry about speed with appdata. Doesn't hurt to try? *Sometimes it hurts to try.

Thanks but I meant a console command (I'm trying to script something.)

hdparm seems to work but is there a better way (that might update the WebGUI's activity "LED") ?

Makes sense. I thought maybe I misunderstood AVR or my unit had a substandard implementation. Thanks. Sorry OP for the tangent.

My Cyberpower's AVR only kicks in when voltage drops down from 120V to 104V. That rarely happens so why's it important the drop's supplemented by circuitry rather than battery? The more common case (total power loss) is handled by battery entirely.

Same. In my case multiple simultaneous transcodes maxed out the RAM drive.

I've never seen a file that size. Mine are few MB each. The large size suggests it's being continuously written to in which case my script deleting it may cause whatever's writing it to fail...

Emby doesn't intelligently manage temporary transcoding files and can fill your drive in some scenarios. This is especially a problem if you're transcoding to a RAM drive with limited space as described here (the specified command is added to template's Extra Parameters.) Update: I've switched from tmpfs (outlined here) to /dev/shm I solved this with a helper script stored on a share accessible to the Emby container and called from within it. Create it as transcoding-temp-fix.sh and run chmod a+x on it. Here's the script: #!/bin/sh # User Settings TRANSCODE_DIR="/transcode/transcoding-temp" PERCENT_LIMIT=70 BATCH_SIZE=10 if [ -d "${TRANSCODE_DIR}" ]; then percent_full=`df "${TRANSCODE_DIR}" | awk '{print $5}' | tr -dc '0-9'` echo "Directory limit: ${PERCENT_LIMIT}%" echo "Directory utilization: ${percent_full}%" while [ $percent_full -gt $PERCENT_LIMIT ]; do echo "(${percent_full}%) exceeds limit (${PERCENT_LIMIT}%), deleting oldest (${BATCH_SIZE}) files" # DEBUG: Uncomment to print list of deleted files #ls ${TRANSCODE_DIR}/*.ts -1t | tail -${BATCH_SIZE} | xargs ls -lh ls ${TRANSCODE_DIR}/*.ts -1t | tail -${BATCH_SIZE} | xargs rm percent_full=`df "${TRANSCODE_DIR}" | awk '{print $5}' | tr -dc '0-9'` done else echo "${TRANSCODE_DIR} (TRANSCODE_DIR): directory doesn't exist" fi This assumes you're mounting the RAM drive at /transcode (as described in the linked post) which you've set as the Transcoding temporary path in Emby: The script deletes the oldest ts files in batches of 10 (BATCH_SIZE) until it reaches a safe usage percent (PERCENT_LIMIT). I call it every 30s with the following entry in the template's Post Arguments && docker exec EmbyServer sh -c 'watch -n30 "/system-share/transcoding-temp-fix.sh" 2>/dev/null > /transcode/transcoding-temp-fix.log &' NOTE: The full host path to the script is /mnt/cache/system/emby/transcoding-temp-fix.sh where system-share is a mapped path variable I've added to the template: Its execution can be monitored with the following command from the unraid console: docker exec EmbyServer sh -c 'tail -f /transcode/transcoding-temp-fix.log' It works well so far with standard transcoding but I don't use batch conversions or live TV so YMMV. NOTE: I'm piping results to rm so use at your own risk (and feel free to post improvements.) You may want to test the commands individually before running the full script.

Any plans to include iHD for QSV in addition to i965? Otherwise does anyone know of a docker that will convert to HEVC with hardware support for encode AND decode? Handbrake works but no HW decode support.

I removed the Trim plugin (on RC2) but now Fix Common problems is warning me that it's not installed - should I ignore it?

Updated with miscellaneous reliability and display tweaks and switched shutdown trigger from battery level to time-on-battery.

Anyone encoding h265 with quick sync mind sharing their settings? Mine (defaults except for 192kbps audio) practically doubled the size of the h264s it converted.

Glad it was helpful. Actually I've updated it with misc reliability tweaks and a shift from battery level-based shutdown to timer-based shutdown. I was holding off until I had a few natural power outage/shutdowns to test with but I'm reasonably confident it's an improvement.

Are you sure it's random? If e.g. it's reset on startup you can save the good version to your boot drive and copy it over in config/go (which I'm pretty sure runs after plugins are installed)

As long as you're happy with 6.8.3. 6.9.0 dropped AFP support.

Wow that's comprehensive. It's unfortunate Apple chose to deprecate it. I was surprised to see in your tests with small files that Windows wasn't much better than Mac. I assumed Mac was the biggest culprit but this suggests it's SMB itself or unraid's implementation. I guess to narrow that down you could benchmark a non-unRAID SMB share.

I haven't tested enough to gauge the relative effectiveness of each of these tweaks (some may even be inadvisable) but overall my Time Machine backups are working "reasonably" in 6.9.0-RC2 In Samba extra configuration: [global] #Fix for 6.9.0-rc2 Mac client search spotlight backend = tracker # speed tweak nt acl support = No # tweaks from https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X min protocol = SMB2 fruit:metadata = stream fruit:model = MacSamba fruit:posix_rename = yes fruit:veto_appledouble = no fruit:wipe_intentionally_left_blank_rfork = yes fruit:delete_empty_adfiles = yes #Custom include = /boot/config/smb-custom.conf Where smb-custom.conf looks like this: [Time Machine] path = /mnt/fast/Time-Machine comment = browseable = no writeable = no read list = write list = backups valid users = backups vfs objects = catia fruit streams_xattr fruit:time machine = yes fruit:time machine max size = 552000M case sensitive = auto preserve case = yes short preserve case = yes spotlight = yes And fast is a cache-only NOCOW BTRFS RAID 5 pool to which this custom conf allows direct access (bypassing shfs.) More details on that here: Finally, I wiped my previous sparsebundle and started fresh in Big Sur to take advantage of the new APFS formatting. NOTE: The user "backups" in smb-custom.conf is one I created just for time machine (for security reasons from an older guide.)

I assumed Apple was phasing out old model types, in which case it'd make sense for unraid to use a more recent one. But right, maybe they just forgot and plan to fix it.

Based on your own testing or what I reported? Every container with root access seems like a significant security risk. I thought this would get more interest. Am I misunderstanding?

Extract a Single File(s) From a Large Tarball

I set it up as a user script to run hourly but honestly can't remember why. It would make sense to put those lines in config/go so it's run on startup, but maybe that doesn't work because smb.service is overwritten on array start? The fix for that would be to set the user script to run on array start but I didn't do that either, strange.

Confirmed.