wayner

My log is showing a Parity Check Tuning issue: Parity Check Tuning: ERROR: marker file found for both scheduled and automatic There are dozens of these messages in my log for Jun 22 and 23 - the last such message was at June 23 08:48.. But the parity check did properly complete and I can see this message in my logs "23-06-2024 08:54 AM Parity Check Tuning [PORTRUSH] Scheduled Correcting Parity-Check finished (0 errors)" Is this something to worry about, or should it go away now? I did have an unclean shutdown on June 15.

I have been using PCs to record TV for over 20 years with Win MCE, BeyondTV, SageTV, Plex, Jellyfin, etc. I have used PCI, PCIe, USB and LAN capture devices. For OSes I have used everything from Win95, to WHSv1, WHSv2, unRAID, Win7, Win10 and Win11. Having a capture device like a HDHR that is on your LAN has, IMO, a bunch of advantages. The device can be shared across multiple PCs seamlessly - you can turn on a new unRAID server and start using the HDHR immediately without having to move and configure hardware. And you can use the capture device with multiple PCs at once, although you might have conflicts if you are not careful. With LAN based capture devices you generally don't have issues when you upgrade your OS or your drivers. It just tends to work without getting disrupted by something local to the PC. And you don't have to worry about passing through hardware. Some of the Hauppauge PCI devices had an issue where they wouldn't work if you had more than 3.5GB of RAM. Hauppauge HD-PVRs can be finicky about USB ports. And for OTA capture devices you can put the HDHR wherever it is convenient. This might even be in your attic close to your antenna so you don't have a long coax run that can degrade your signal, assuming that you have ethernet wiring in your attic. Just one person's opinion...

I have an older unRAID server that was also getting the docker partition full problem. I found a way to fix it on these forums - edit your docker and go into extra parameters. Put this in --log-opt max-size=50m --log-opt max-file=1 as extra parameters and that is supposed to limit your logs to 50 MB each. edit - Make sure that you have advanced mode turned on to see the extra parameters button.

Not a direct answer to your question but I find that the HD HomeRun tuners are a better solution as they are network devices rather than PCIe devices. So you aren't as tied to drivers and having to worry about hardware issues on your server. I would recommend them, plus they have ATSC 3.0 devices for being able to capture the next gen of OTA broadcasts, including 4K.

My pihole docker is getting quite large - the container is 9.2 GB and the Writable column is 8.89GB. How do I troubleshoot this and see what the cause is? The pihole-FTL.db file is about 3.4GB but that appears to be in appdata. What could be causing this? edit - I updated the pihole docker and that fixed the problem. The size fell by over 95% to 328MB. Leaving this comment here in case it helps someone in the future.

We all agree, but the post you are quoting is from six months ago - do we even know if Limetech is addressing it? There have been several new releases of unRAID since then.

@tivodoctor - You might want to look into getting an HD HomeRun tuner. I have a couple of these and they work fine in both Plex and Jellyfin. For the most part I use this with SageTV which is kind of dead now but it was, by far, the best software for recording TV and supported tons of tuners and tuning devices, like IR blasters, etc. You can get used devices pretty cheap on ebay. Sometimes the wall warts die so you may need to replace a power supply. edit - One more good thing about HD Homerun devices is that they are network devices with ethernet connections. So you don't plug them in to your PC and you don't have to worry about drivers and passthroughs in a docker/VM. And you can share them with multiple PCs or other devices.

Thanks

This docker seems to have updates available on a very regular basis, like every week or so. But I believe that this is a relatively small and simple docker, there is no UI, it just updates your dynamic IP and writes to the log. So why are there so many updates to this docker?

I think your first question is more of a generic Handbrake question and doesn't relate to the docker. There are probably other places that are WAY better to answer that question.

Thanks. One of my main uses of unRAID is as a media server which will be accessing lots of metadata and Fanart files. Is there more documentation around pros and cons of various disk formats? Like what format should you use for your cache disk? BTRFS, ZFS, XFS? What are the pros and cons of each?

No one has any thoughts on this? Is there any reason why you can't set the ZFS cache size in the unRAID GUI? Is it because it can only be resized on a reboot? Or it is a new feature an just hasn't yet been implemented?

It seems like unRAID uses 1/8 of your RAM as the size of the cache for ZFS disks. You can change this, but not currently through the GUI - you add a config file. Has anyone done research into determining the optimal cache size? I recently increased my server RAM from 32GB to 64TB and my ZFS cache size went up to 8GB. But I rarely use all of my RAM. Should I increase the ZFS cache size? In what instances does it make sense to have a larger or smaller cache size? I did search but didn't seem any documentation on this. There is a thread that is 1.5 years ago, but it is unclear to me whether this all applies as this predates unRAID official support for ZFS.

You and at least a few dozen others. I am one of them.

At least a few dozen people have had issues with BTRFS corruption on their cache driver under 6.12. I solved my problem by reformatting the cache drive to ZFS.

This appears to happen to many people especially if a browser window is kept open. See:

I have this problem cropping up on a regular basis. It seems like it may occur when there are stale browsers open, but is that the expected behvaiour? In other words, is this a bug or a feature? And if it is a bug, which it appears to be, is it being addressed?

There is talk in this thread about the "official" Jellyfin docker. Where is that? When I look in apps in unRAID I see the binhex, linuxserver, and hotio dockers. But I don't see an official one.

Is this docker supposed to stop itself? I am using it, and it seems to be working ok as I am using custom icons on a couple of VMs. But I noticed that the docker was stopped, so I restarted it. But then after a few minutes it was stopped again. Here is the log: Cloning into 'unraid_vm_icons'... Clear all icons not set......continuing. created directory: '/config/icons' I have created the icon store directory & now will start downloading selected icons . . icons downloaded icons synced Clear all icons not set......continuing. . . Icons downloaded previously. icons synced Clear all icons not set......continuing. . . Icons downloaded previously. icons synced Clear all icons not set......continuing. . . Icons downloaded previously. icons synced ** Press ANY KEY to close this window **

Thanks, I added the memory and all looks well. I didn't bother with a memtest for now.

My server currently has 2x16GB. I am adding two more of the same memory sticks. I don't have to do anything in unRAID, do I? It's just a case of shutting down the system, installing the sticks, and starting back up, is it not? The reason that I am doing this is that I am running more VMs and that is starting to use up all of my RAM.

Thanks, I have considered that but I find it slightly annoying that the ethernet ports on the UXG-Lite are 1Gig. That would be fine for me for now, but I would prefer faster to futureproof.

Sorry, I was using the wrong terminology. The current setting is Cache->Array. I did that to clear off my cache disk to reformat it, and did the same with other shares like appdata, system, etc. But I guess I forgot to change the setting back to Array->Cache for the domains share.

I have two 500GB NVME SSDs in a mirrored ZFS pool for my cache and several 4GB or larger spinning hard drives in my array. I would think that the NVME would be faster.

I have two VMs - Ubuntu and Win11. A few weeks ago I had mover move the files off my cache to the pool to reformat my cache drive to ZFS and add a second disk to the pool in a mirrored configuration. I just noticed that my domains share is mainly in the pool - when I look at the config for the domains share I forgot to change the mover action back to Pool->Cache, it is at Cache->Pool. But my VMs seem to be working ok and don't seem to be much slower, although I haven't used them a lot. I tried googling and don't see a clear answer - what is the reason to have domains on cache? Is it because a VM will run a lot faster on my cache which is a NVME disk, compared to the pool which are regular hard drives?