trurl

Have you patched the script as mentioned in recent posts in this thread?

What version unRAID and plugin?

Post a screenshot

I need some help! What info does the community need to help me?

I have used HDHRFling (Windows), which provides both live and recording. There is also this: urlxl - HDHomeRun DVR . Don't know if it does live or not.

I always pipe in on this sort of thing to elaborate. A formatted disk is obviously NOT clear because it has had an empty filesystem written to it. An empty filesystem contains the metadata of the filesystem and a clear disk just has all zeros in every byte. The point of a clear disk is all zeros has no impact on parity. The metadata of an empty filesystem does impact parity, which is why unRAID updates parity when you format a disk you have added to the array. Format means "write an empty filesystem to this disk". That is what it has always meant in every operating system you have ever used. If the disk is in the parity array, unRAID treats this write to this array disk just like it does any other write, by updating parity. If you try to add a formatted disk to the parity array unRAID will want to clear it so parity will remain valid.

Sounds like a question for plex instead of unRAID, but as far as I know you can only watch recordings for now. Since it is beta functionality maybe more to come.

Many times. See search tips in my sig

Probably depends on the character set in force when the folder/file names were created. Try renaming them.

Try copying bzimage,bzroot from the download.

Already done. See this thread

Put your flash drive in your PC and let it checkdisk.

On array start, that still works. unRaid will keep checking until it finds the appropriate key. But on a registration transfer, none of the keys are going to match, so it has no choice but to pick one out of the hat. ergo: only put a single key on the flash drive and you'll have no problems So just to clarify this for myself (and maybe others). If you are trying to register a replacement flash, only put the key for the flash you are trying to replace on the new flash drive.

OK, I get it now. I thought Danconio and jonathanm were saying that a key file was blacklisted. They were talking about the flash GUID that went with a key, which effectively blacklists the key. So when he went to get a replacement for a new flash drive, it blacklisted the wrong flash based on just picking one of the keys it found on there. I never had to use the online registration and still have the emails for both of my keys so I am good as far as sorting this out on my systems. I do seem to recall some post or something saying we could put multiple keys on and it would check them all until it found the match. And I don't recall ever seeing anything that said we shouldn't do that now that we have online registration (which apparently includes online blacklisting).

I'm not getting it. Why would a key be blacklisted? I understand blacklisting a flash GUID. You get a replacement key for a replacement flash, and the original flash would be blacklisted so you couldn't have 2 that work when you had only paid for 1. But what good is it to blacklist a key? It can't be used on another flash. Yes it could be used on the original flash, but since there is no phone home the blacklist has to be in the downloaded distribution, so you would still be able to use either the original flash or the original key until you installed a new distribution regardless of any blacklist. I'm sure I'm missing something obvious here.

It will check all keys until it finds the correct one so having multiple keys on the drive doesn't matter. I have both of my keys on both of my systems. How did you get these blacklisted drives and blacklisted keys? They were blacklisted for a reason. You will have to contact [email protected] to get them replaced. They usually respond pretty quickly.

Just to elaborate. Changing the disk to xfs will format it. Format means "write an empty filesystem to this disk". That is what it has always meant on every operating system you have ever used. unRAID treats this write of the empty filesystem just like it treats all other writes, but updating parity. So after you change the filesystem (format), parity will agree that the disk has an empty filesystem on it, and if you rebuild from parity you will get an empty filesystem. There is already a very long sticky thread about converting to XFS at the top of this subforum.

Never tried that. I just reverted yesterday so I could develop Sent from my LG-D852 using Tapatalk I will be rebooting in the next day or so to upsize my cache pool. Will try again after the reboot. It's a typo in the plugin file (basically, it was saving the downloaded txz under a different name than it was uninstalling it under ) Uninstall it again, and reinstall, and it'll pull the updated .plg file with the correction... ( Only affected people who try and uninstall it. If you've never tried to uninstall it, no need to do anything. The updated .plg will automatically get installed with today / tomorrow's update) You'd almost think that I knew what I was doing by now I went ahead and rebooted before I saw your post. And then it installed fine. Then I read your post, so just to test the uninstall for you I uninstalled it and reinstalled it again. All OK. Noticed it doesn't seem to put any bait in my Backup share though. Don't know if this is intentional or not. This is the same share I use for CA backup among other things.

Never tried that. I just reverted yesterday so I could develop Sent from my LG-D852 using Tapatalk I will be rebooting in the next day or so to upsize my cache pool. Will try again after the reboot.

Now that inotify is back in 6.3 I don't seem to be able to reinstall this plugin. Just get the "puzzle piece" icon on the Plugins page for ransomware.bait, and nothing for it in the Settings page.

Nevermind about the diagnostics. You're correct. However the problem actually isn't with this plugin per se. Nerd Pack isn't working properly on 6.3.0-rc1 Going to the ransomware settings states that inotifytools isn't installed, and going to Nerd Pack settings just sits there on retrieving plugin information. Now this is a case that I have to handle, where inotify was installed, but no longer is, so kudos for finding that bug... But I think that dmascias also has something to do here... Now that you mention it I did notice something about inotifytools in my syslog and should have made the connection. So I guess that means I will have to regenerate my .hash files again also. Still using your "deprecated" Checksum Suite after all this time.

This plugin is preventing my array from starting on 6.3.0-rc1 Or possibly, it is stopping my array due to some sort of false-positive before I can even load the webUI. After upgrading to unRAID 6.3.0-rc1, I was surprised to see that my array wasn't started. So I tried to start it manually, but it wouldn't. Then I tried booting in SAFE mode, and it booted up fine with the array started. Then I happened to check my email and had some alerts from this plugin. So I removed the plugin, booted in normal mode, and it booted up with the array started. So something going on with this plugin and unRAID 6.3.0-rc1

If you don't understand then you don't really understand volume mappings. If you understand volume mappings then you will be able to figure out what to do with other dockers. If you don't understand volume mappings then you will always be asking someone else how to do it. And there will often be others who don't understand either willing to "help" you.

Sounds like a question for NZBGet support rather than for this docker. Have you tried searching or asking there?

Please ask next time if you aren't sure what you should do. Format means "write an empty filesystem to this disk". That is what it has always meant in every operating system you have ever used. unRAID treats this write just like any other, by updating parity, so parity agrees you have an empty filesystem.