pantheis

Members
  • Posts

    55
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

pantheis's Achievements

Rookie

Rookie (2/14)

3

Reputation

  1. 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
  2. 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.
  3. 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.
  4. 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!
  5. 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!
  6. 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.
  7. 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.
  8. 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.
  9. Thanks, I did find that information before, but won't need to use it this time. I'm not upgrading to a larger disk at this time due to the complexities that will be involved in dealing with a disk that's potentially failing and having to upgrade unRaid versions all at once. My plan right now is to spare out the drive with the replacement, then hit the old drive with a couple passes of preclear to see what happens.
  10. Ah yes, sorry about that, forgot to include it. Added to the opening post.
  11. Trurl, I've added the syslog and a screenshot of the front page of the webUI as requested. I'm still pretty sure it's the disk itself, but I wanted to get a second opinion.
  12. I'm using Spinrite to run a read pass across the suspect drive. --edit-- I've ordered a 2TB drive to replace the suspect drive for now. While I'd love to take this opportunity to upgrade to a larger parity drive for future expansion the drives are a little more expensive than I'd like to spend right now. This will also minimize the complexity of repairing my array right now by not having to also deal with upgrading to the next version of unRaid. Thanks for the information on the swap disabled option. When I'm ready to actually update my parity drive, I'll now know how to go about doing it.
  13. Thanks for the information. I'll look up the procedure called swap disabled. Once the current offline utility finishes (probably overnight), I'll get the SMART and syslog reports posted as well as a screenshot of the main page.
  14. I noticed my unraid box responding slowly to some file access and checked the system log. There were disk errors showing on the original data disk I had purchased. Checking the SMART report shows about 1400 sectors pending relocation, but no actual relocation events yet. Trying a number of offline utilities to get the disk to recognize if it needs to spare them out or not does not necessarily seem to have worked, so it seems it's time to replace the disk, or at least get it offline into another machine to work on as I need to get my unraid array back up. Please note, even with the read errors in the log, there have been zero write errors noticed by unRaid and the array did not offline itself, nor did the disk red ball. I run automated monthly parity checks and those have all shown zero errors. I currently have 4 drives attached, all 2TB drives. When purchasing the replacement drive, what I'd like to do is upgrade the parity drive to a larger size (4TB likely), then use the 2TB that was the parity drive to replace the failing disk. I'd hate to spend the money on just buying a replacement 2TB drive when it's just a tiny bit more to open up larger size disks in the future. I also realize that this will require upgrading to the 5.x unRaid to support the larger disks. What is the best way to make the above changes, assuming that the parity drive is correct, but one of the data drives is suspect? Thanks! I can provide logs if needed, but I'm pretty sure the disk is failing. --edit-- I had removed the failing disk from the array, started and stopped the array, then readded the disk to force it to rebuild the data on the disk from parity. The rebuild finished without any errors showing up, but after a bit I started to see errors again. I've attached my syslog and the front page of the web UI as requested just to get a second opinion on it. I've already ordered a replacement drive as the drives internal long self-test indicated possible failed sectors, but if there's something else going on as well I'd like to know about it. Thanks! syslog-2015-05-16.zip 20150516_smartreport.txt
  15. Since I'm still back on 4.7, I don't really have any official plugins. I've got a customized 'go' file manually mounting a separate drive as /mnt/cache2 (this was setup prior to purchasing unRaid), and setting up links using ln to /usr/local/crashplan and others, so that crashplan and other things are installed on an actual hard disk. It works great, and was all that was available back when I set all of this up. I see that there are actual plugins now for things like Crashplan, but I have no idea how to migrate from what I've got setup to a plugin system. I'm going to have to tackle the move to 5 at some point so I can support larger drives. My next drive purchase will be a 4 or 6TB, replacing the current 2TB parity drive to set the stage for future larger drive purchases.