glennbrown

Native Docker Compose with it properly recognizing when a stack/container has been updated manually or via watchtower.

I did call out system too He did not mention using VM's but yes if you do run VM's that one as well. I see little benefit to have iso's sitting on a pool device fulltime. I just have mine personally set Yes for iso's

Stop the array. Add a pool, add the NVMe drive to that pool. Start the array In the appdata share settings change the following: "Use cache pool (for new files/directories):" - Set this to Prefer "Select Cache Pool:" - Set this to name of the pool you created. Do the above for the "system" share too You will want to stop Docker then execute mover, that should move all data to the pool.

@ich777 I submitted a pull request against the smartctl exporter textfile collector. There was a spelling mistake in the one nested if conditional when checking node_exporters settings.cfg causing it to always return null. I also did some minor bash syntax cleanup in that nested IF. Also wondering did you have any plans to update node-exporter to 1.5.0 and would be open to a pull request to enable the cpu info collector by default?

Replaced my cable, problem went away

Has anyone encountered problems with this NIC? Everytime I reboot my server it will come back up at 100MB full, if I unplug/replug it negotiates to 1GB Full. I found lots of posts of seeing similar issues with windows and other Linux systems but no concrete “this is how you fix it” answers.

Disregard, 6.11.0 fixed the issue with the module loading now the problem is none of my fans show up in sensors.

I am getting a error when attempting to load nct6775 driver for sensors and the System Temp plugin. The error is related to this bug https://github.com/lm-sensors/lm-sensors/issues/197 so i need to append the kernel boot parameter acpi_enforce_resources=lax Should it as simple as this: kernel /bzimage append initrd=/bzroot acpi_enforce_resources=lax

Nice build, I saw you mentioned about anexternal GPU for transcoding. If you have not set it up yet you should setup the iGPU in Plex. Intel Quicksync is hard to beat in terms of perforance to power over a dedicated GPU for Plex usage.

System was originally built in 2020 to just run Ubuntu Linux and my storage was held by a Synology, after a series of hard drive failures I got a different case and switched my setup to Snapraid+Mergerfs on Ubuntu. After recommending numerous people to use Unraid including my father I decided to walk the talk so to speak and switched to Unraid myself maybe about 10 months ago now. Today I did a motherboard and ram upgrade plus added some new fans, CPU Cooler and an additional 1TB NVMe. Specs CPU: Intel i5-10400 Motherboard: MSI Z590-A Pro (was originally a Gigabyte B460M-DS3H) Memory: 96GB Team Group VulcanZ DDR4-3200 2x32GB Kit and a 2x16GB Kit SSD: 500GB WD SN750 Black m.2, 1TB WD SN750 Black m2 & 2x Samsung 840 SSD's (going to be retiring the Samsungs) HDD: 2x WD 10TB, 2x WD 12TB (all where shucked Easystores) HBA: LSI 9207-8i PSU: Cooler Master 450W CASE: Silverstone CS380 Miscellaneous: Arctic P12 Fans and Arctic Freezer i35 CPU cooler Some potential future upgrades: Power Supply, the current budget one has held up extremely well but would kind of like a Seasonic CPU, I am hoping that with Raptor Lake the 11700K will have some good sales at Microcenter.

Following the procedure to just rest the root password, that seems to have fixed the issue. Not really sure why that was necessary when SSH was working.

6.10.3 Nope using root as username. Tried two different laptops/browsers as well as my iPad.

Just started tonight, webgui says invalid password until it puts me into the attempts timeout. SSH works just fine. I tried restarting nginx and php-fpm but still not working, any suggestions?

Just wanted to report back, system is back up and everything is happy. Parity is rebuilding. Was nice and painless. Only real issue is completely not related to Unraid, the Plex DB's corrupted on me yet again. I am not sure why but they seem temperamental to being rsync'd this happened when I converted back to my Ubuntu setup too, Thank god for backups.

I was going to put them on a cache pool but just wasn't sure if I should create empty folders on the array as well. Tomorrow going to boot backup into Unraid and will see how it goes.