cpshoemake

Is there any way to get the syslog collector to work?

Great work GuildDarts! I'm not sure "Docker Folder" does it justice. The organization is great, but the real feature is the ability to stop and start groups of dockers. I'm doing so much less clicking now. Feel free to put up a donate button. I'd be happy to throw a few bucks your way for this.

My sqlite database was getting pretty big so I just muddled through migrating to a PostgreSQL11 database. Here are the steps, for posterity, if anyone is interested. Backup your /appdata/quassel-core directory in case something goes wrong Install the Postgres11 container from postgres. Change the POSTGRES_PASSWORD variable to whatever password you like. The rest are fine at default, unless you have a port conflict or want to change your storage path. Hit "Apply" to start the container. Open a console on the new container. Enter the following commands: # psql -U postgres psql (11.7 (Debian 11.7-2.pgdg90+1)) Type "help" for help. postgres=# CREATE USER quassel ENCRYPTED PASSWORD 'yourpassword'; CREATE ROLE postgres=# CREATE DATABASE quassel WITH OWNER quassel ENCODING 'UTF8'; CREATE DATABASE Open a console to your Quassel container. Enter the following commands: # quasselcore --configdir=/config --select-backend=PostgreSQL [Info ] SQLite storage backend is ready. Schema version: 31 [Info ] Database authenticator is ready. Default values are in brackets Username [quassel]: <-- Leave this at default (just hit Enter) Password []: <-- Enter the password you used for the quassel database Hostname [localhost]: <-- Enter your Unraid IP address Port [5432]: <-- Leave default unless you changed the port Database [quassel]: <-- Default At this point I got a bunch of errors, but everything worked out anyway. You will now see the window start to fill with asterisks as your old database is migrated. This could take awhile depending on the size. Once the asterisks stop and you get a prompt back, restart the Quassel container. Connect to your core and make sure all your settings and data are intact. If everything is good, you can now delete the /appdata/quassel-core/quassel-storage.sqlite file Profit!

I have the same issue. I've tried all the scaling modes and multiple vnc clients, but I cant get anything to work.

Yes, you can do this. It's generally not recommended as your cache will run at the speed of the slowest drive. If this doesn't matter to you, go for it.

Looks like parity errors in your L2 cache. Just to clarify, you ran the system at the stock 2133 speed and still got these errors? Did you try resetting the BIOS to default values? If you have another system that would allow you to swap the MB and/or CPU to validate, I'd try that. If none of that works you may have to RMA your CPU.

What does your smb.conf file look like?

Honestly, I wouldn't worry about it. You're not going to notice the difference. With a 2080Ti, you're looking at a 2-3% performance hit. With anything else, it's pretty much nil. See https://www.techpowerup.com/review/nvidia-geforce-rtx-2080-ti-pci-express-scaling/ Nope. Ryzen chips have 24 lanes: 16 for PCIe slots, 4 for NVME, & 4 for chipset. Those 16 PCIe lanes are going to be x16, x8x8, x8x4x4, or x4x4x4x4 depending on how you fill the slots. You'd have to move to a HEDT or server platform (Threadripper, Xeon, EPYC) to get multiple x16 slots. This would work, but it's more money for not much gain. These are technically possible, but I've never seen a board that supports these configs.

https://plex.mydomain.com works fine for me.

Unraid doesn't need much RAM. Get at least 8GB, plus whatever your VMs are going to need. Speed also isn't going to matter much, unless it is important for your VM workloads. I prefer ECC, but many get by without it.

It's not that smart. Files are evaluated one-at-a-time. Your subtitle file met all the requirements and was moved to disk 1. The mkv was evaluated next and your split level and mostly-full disk prevented the mkv from moving. I spent way too much time futzing with this in the past. Eventually I lost patience and set everything to "most-free" and "split any directory as required."

Check the settings for each of your shares. It is probably an issue with "split level" or included/excluded disks.

They are corrected (ECC) memory errors on these 2 DIMMs: Manufacturer: Samsung Serial Number: 4220B624 Part Number: M392B5170EM1-CH9 Manufacturer: Samsung Serial Number: 4221D09E Part Number: M392B5170EM1-CH9 It's not going to hurt anything, but I'd swap them out. 4GB DDR3 DIMMs are dirt cheap on eBay.

I had this problem with a Seagate IronWolf drive (ST8000VN0022). The write cache was disabled and none of the sdparm or hdparm commands would enable it. I was finally able to fix it with SeaChest utilities (https://www.seagate.com/support/software/seachest/). The download includes a boot drive creation tool. I booted a second system into this Linux environment and the following command fixed the issue for me: SeaChest_Configure -d /dev/sg0 --sctWriteCache enable

Thanks. I renamed the file to default.old and left it in the folder. Moving it out fixed it. Compare the new config to your old one. Are you missing the following lines? Are they commented out? Add or uncomment them. add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;"; add_header X-Frame-Options "SAMEORIGIN";