pantheis

I am also experiencing this exact same issue. It started sometime on the 6.11.x branch, I think at .3. I just upgraded to 6.11.5, rebooted, did the check for updates, waited, then clicked update all. It does the same thing as above, goes through and successfully updates all of the dockers with updates, then instead of saying "done", wraps around and begins again. It'll keep doing this until I refresh the page. tower-diagnostics-20221124-2232.zip

I have a Cyberpower model CP1500PFCLCDa 1000w UPS, and it was literally plug and play. I disconnected the old APC ups, plugged in the new one, and that was that. The APCUPS daemon immediately detected it and it's been working without any other configuration. I have apcupsd installed on my Windows 10 VM and it correctly sees the status across the "network" and can shut itself down without any issues. It just works.

I just posted my own upgrade advice thread with this exact question, regarding 11th gen iGPU transcoding 4k HDR to 1080p with tone mapping, all in hardware. I am very curious if this is working as I expect it should be. My aging 3770k isn't cutting it for out of the home streaming.

I'm looking for advice and suggestions on an Unraid server upgrade I'm planning on doing within the next few months. I have parted out the following as an upgrade. The RAM is on the approved list for the motherboard. PCPartPicker Part List: https://pcpartpicker.com/list/cBvx9r CPU: Intel Core i7-11700K 3.6 GHz 8-Core Processor CPU Cooler: Cooler Master Hyper 212 EVO V2 62 CFM CPU Cooler Motherboard: Asus TUF Gaming Z590-PLUS WIFI ATX LGA1200 Motherboard Memory: G.Skill Trident Z Neo 64 GB (2 x 32 GB) DDR4-3200 CL16 Memory Storage: Samsung 980 Pro 2 TB M.2-2280 NVME Solid State Drive Case: Fractal Design Define R5 ATX Mid Tower Case Power Supply: SeaSonic FOCUS Plus Platinum 850 W 80+ Platinum Certified Fully Modular ATX Power Supply My current Unraid box is running on an Intel 3770k with 32GB of ram. I have the plus license for Unraid, 7 drives total attached (1 parity, 5 array, one 240GB SSD as Cache and for the VM running on a PCI-E 2 port SATA card using an ASMedia ASM1062 controller), I run multiple docker containers, including Emby, and a Windows 10 VM I use for hosting my own game servers. I am figuring out an upgraded server to replace the current one with an eye towards Emby's hardware transcoding requirements and an improved VM server hosting experience. I have two questions I'm hoping to leverage the vast experience in the community to help inform my decisions. 1) Will the below system be able to do HEVC 4K HDR to 1080p non-HDR transcoding in hardware? From everything I can find online, it should be able to do the transcoding and tone mapping in hardware. Does anyone have experience with this CPU in Emby on Unraid that can confirm? I know the Intel CPU I picked does support x264 and x265 in hardware, and should support GPU hardware tone mapping, but whether this actually works is unknown. 2) It's been a long time since I've had to buy a hard drive for my Unraid box. Some of my drives are going on 8+ years of online time in the current Unraid box and still kicking, but I know it's only a matter of time before I finally have a failure. When I first built my Unraid box, 2TB drives were all the rage, and so I've got a set of 2TB drives in my array. That's tiny by today's standards. I'd like to start adding larger drives to the array and I know that means swapping out the parity drive for something larger. What are the current recommendations for drives (make/model/size) for home Unraid boxes? The case I spec'd below will take up to eight 3.5 inch drives in the main drive cage. My plan would be to buy two larger drives, add one as the new parity drive, and convert the current party drive to a data drive. The 2TB NVMe drive in the list below would replace the current 240GB SSD as the cache and VM drive. Any advice is appreciated! Thanks!

I felt compelled to post here and give you a HUGE thank you for putting this utility together. It is exactly what I didn't know I needed! I have a lot of 2TB drives of various ages, some over 7 years, and while they pass their monthly parity check and show no issues in SMART, your utility will help me monitor the actual performance of the drives and help catch any issues. I imagine it's only a matter of time before I'll need to replace a couple of the drives. Thank you!

Adding this as a new reply so it doesn't get lost. I fixed the above issue. The specific issue was located in the conf/my.service.xml file, down at the very bottom is a configuration section titled <socialNetworkConfig> under which each of the inbound backup computers were configured AND for some reason the manifestPath was configured separately for each one and had the old path under my old unRaid install (/mnt/user/Backups/). I shutdown the Crashplan docker, edited the paths on each (I'm sure there's an option to use the system default but I'm not going to tweak it right now as it's now working), restarted Crashplan and everything just worked.

It's accessible as well. I should also point out that in the first screenshot I took, you can see the unRaid crashplan client backing up to "Clint's nimbus", a remote linux server with Crashplan installed that accepts my backups from my server. It's backing up data from /data/Documents and /data/Arrange a Memory just fine, so obviously Crashplan CAN access those folders.

Hello! I just upgraded from unRaid 4.x to the latest 6.1.3 release, got Docker setup with the Crashplan docker, got my identity file and such copied over. It is successfully backing up to other destinations but computers are not able to backup to unRaid. The error they are getting (and I'm seeing on the server) is "Backup disabled -- backup location is not accessible". I have the backup destination configured to an accessible location, I can access the share with that destination just fine. I've run the permissions script to fix the permissions for updating from unRaid 4.x to 6.1.3. I can access the Backup directory from the shell without issue. I have no idea why Crashplan thinks it can't access the location but I need to get this working. Any ideas? I checked using docker that the directory is accessible.

I wanted to post a quick thank you for developing this script. This has greatly improved access times to the large number of picture files I have stored on my array!

If it helps any, I have two 2TB EARS drives and I cannot hear them at all. My unRaid server is very quiet as well.