Dalarielus

Kind of an odd one - while a backup is running I can see the files being created in my backup folder using Windows File Explorer, but when it completes they all disappear. I can still see them using the file browser on the Unraid web interface and they're definitely still there. What might cause this?

Potential bug - During my first scheduled run, no log was generated. While the backup was running, the status/log tab indicated that the backup was not running, and the abort button was inactive. On attempting to share a debug log, it returned `Your debug log ID: Logfile does not exist!` Also, is it possible to exclude all files with a certain extension? Is it as simple as adding `*.ext` to the excluded folders/files list? Thanks!

After brief experimentation, it looks like it's not possible. I tried `/mnt/user/appdata/binhex-plexpass/Plex\ Media\ Server/Media/localhost/*.bif` and just `*.bif` as exclusions, and both produced a backup that included the bif files >.<

I wonder if that's recursive. The way Plex stores it's metadata is odd, or at least not very human friendly. I have a folder called /appdata/binhex-plexpass/Plex Media Server/Media/localhost/ which contains a serial numbered folder for each object in my Plex library, each one containing several files - including the bif file that I don't want to backup. Obviously it wouldn't be possible to exclude each numbered folder individually. My only worry is that declaring `/appdata/binhex-plexpass/Plex\ Media\ Server/Media/localhost/*.bif` as an exclusion would only exclude bif files located in /.../localhost and not anything deeper. Hmm. Time to experiment! Edit: Escaped my spaces

My Plex folder alone, not including other AppData is approximately 300GB - this is because of the *.bif files used for video preview thumbnails. I don't see the need to back them up, because they will be regenerated as a scheduled task if needed, and not including them in backups would save me about 270GB of disk space, and 40mins of time on each backup. There is literally no need to back them up - they aren't user generated content and my system can replace them in about three days if I ever had to restore. @KluthR - The ability to exclude certain filetypes would be an *extremely* useful addition. Even moreso if you can exclude certain filetypes on a per-folder or per-tree basis! Edit: Spelling.

Is it possible to exclude files of a specific type from appdata backups? I don't see the need to backup my Plex video thumbnails, which are all stored as *.bif files, but they're mixed in with the other metadata (non *.bif files) - I'd like to exclude only *.bif files from my backups, without excluding the whole metadata folder.

Is anyone having issues with the latest update? My pages aren't rendering properly, and are taking a very long time.

Would it be possible to request that the NestyBox SysBox Container Runtime be added as a package? https://github.com/nestybox/sysbox It would make it a lot easier and safer to experiment with Docker in Docker setups

UnRAID 6.10.2 appears to partially break iotop. After updating, I reinstalled my packages (and had to install python2 to be able to open iotop again), but am now seeing the following warning; CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO % Running; echo 1 > /proc/sys/kernel/task_delayacct appears to fix the issue, but it seems like a bit of a hacky workaround.

I know this is resurrecting an old thread, but just wanted to say thanks and point out that the solution mentioned here is still very much relevant. I was attempting to run an LSI 9201-8i in IT mode with the p20 firmware on an ASUS Z170M-PLUS motherboard. With the HBA inserted, the system would not boot. On connecting the card to another motherboard and erasing the HBA BIOS, the HBA now boots and runs perfectly - in fact it's currently preclearing my new parity disk

I cancelled it in the usual manner from the Unbalance WebUI, but at one point the interface became unresponsive for a few minutes. When it terminated, the file that had been in the process of moving was corrupted (literally cut in half). At the time, I simply replaced the file and moved on, though in hindsight this is the first parity check that has been run since then.

Further update: File integrity check completed without errors. I'll run memtest while I'm at work tomorrow. At this point I can only assume either a memory error, or some kind of parity mistake caused by cancelling an incomplete job on Unbalance while I was still figuring it out?

I have been running it, but somehow it managed to completely escape my mind! When the file integrity check finishes, I'll be running memtest.

Update: Second parity check completed without errors. Scheduled parity checks have been changed to NOT update parity in the event of errors. I'm now going to run a scan with the File Integrity plugin.

Perhaps a scan with the File Integrity plugin?