mikedpitt420

I have the same issue as HTPC newbie mentioned several pages back which still hasn't gone away. Every time I load the MAIN page, the Unassigned devices plugin spins up all the drives it is handling. Would love to see a fix to this as I tried to keep a warm spare and was unable to as it spun up every time I loaded stats.

Aha. Thanks very much for pointing me towards an answer instead of assuming everyone runs the same software / plugins / dockers setup! Thanks d00d

How do you mean? I don't understand. What more streamlined way of dealing with dockers are you referring to? I'm using unRAID's UI "docker" tab and am running 6.1.5. Is there something I have missed? If you're referring to something not included in the unRAID OS by default, why do you assume anyone has heard of what you're talking about?

So there is no way to add a line to the repositories and install it in this way with the "Add Container" button any longer? It needs manually installed somehow and not through the UI?

What do I add to the Docker Repositories to get the HTPC Manager plugin now?

I agree with your sentiment. However, why not take it a step further and say every single piece of software made by everyone has to have a little ? next to every option, explaining every function of every button in plain, non-technical speak? There would be nothing but "?" buttons and hovering explanations as far as the eye could see. Not trying to offend only playing devil's advocate. I think it's pretty well assumed that if you've decided to build and administer your own NAS, that you'll also spend some time learning the in's and out's of the system itself. Could some stuff be explained a bit better? Sure. Does every single button need ? with a non-tech explanation as well? I think not... They've gone as far as making a pretty darned conclusive manual for 6. That being said, it doesn't encompass plugins and add-ons but it sure does get into quite a bit of detail. Like Trurl stated, these plugins are user written. So it's at the user's end to decide whether or not they wish to venture outside of the published unRAID OS and add plugins. Plugins that are distributed knowingly without manuals and actual support from unRAID itself. To me this would be like adding a user generated script to SABNZBD and then being less than thrilled when it doesn't do exactly what it's supposed to, then trying to get the SAB authors to clean it up and write documentation for it.

Yes, the red X after the preclear next to the drive, that when you hover over it says "Clear Drive Stats".

Clear the stats from the drive, and you can preclear again.

No that's what I was after. Thanks very much! I guess I just misread or botched the replacement process. I keep a precleared warm spare for myself and this was for someone else, so I honestly haven't been through this actual process in a while. I was just curious as to expected behavior in each scenario. That makes it perfectly clear. So in the future, do not remove the bad drive from the array, add the new one and preclear, and reassign. The only question I would still have is, when a drive is failing and you try to watch video stored on it, it tends to buffer and skip. Which would be expected. Removing the failing drive first at least corrects that error while waiting for another drive. I guess the only way to achieve that would be doing it how I did, and just forcing a preclear via the command line? Thanks very much again for the quick response.

That's what I would expect as well, but it's not what happened. The drive failed, the array was stopped and the drive was removed, and the array restarted. All the data was visible. The new drive was added and the machine was rebooted. Listing the drives available for preclear showed no available drives, via the CLI or the unRAID UI. If the array was stopped, I was able to assign the new drive to the array. However, the only way I was able to clear this drive was preclear_disk.sh /dev/sdc So the script did not show the drive as available for a preclear, but it started anyway via the command line. The reason I was reporting it here, was because with the addition of this plugin, this was the last reason I had to regularly use the CLI and I thought that's a huge leap forward for less than experienced users who were possibly unfamiliar with the command line. So either this is expected behavior and unRAID does somehow claim the drive when there is a failed drive in the array, or there is a bug in the preclear script or plugin, that says a drive is not unavailable for preclear when indeed it is.

So is that correct? If there is a failed drive in the array, unRAID "claims it" and you are not able to preclear the drive normally? This doesn't seem like what would be expected behavior unless I'm really missing something. Since unRAID places a fairly high value on pre-clearing drives before they're added to the array (which is one of the nicest features imho) you'd think that it would want you to pre-clear any drive added. Is this a bug in the preclear script or is that actually expected behavior?

So you're saying it's not possible to preclear a drive with another drive missing from the array?

This is in response to fantax's post above. I have been helping him with his new unRAID system. He had a drive die. The array was stopped, the drive was removed from the array, and the array was started again. This seemed to work just fine, and the data on the missing drive was still accessible. He then replaced the drive. The new drive took the assignment of /dev/sdc . This was not shown under the unassigned devices plugin, so the option to preclear it wasn't there either. Stopping the array gives him the option of being able to assign it to the array and begin a parity rebuild of the data, but nothing from the preclear script, or plugin was reported. From the CLI, doing a "preclear_disk.sh -l" produced no results, it did not show the new drive. However, doing a "preclear_disk.sh /dev/sdc" began the preclear process just fine. He's running unRAID 6.1.3 . He has 5 drives attached to his motherboard, and 3 drives attached to an IBM M1015 flashed to IT mode. The drive in question is one of the ones connected to the controller card. I wasn't exactly sure where to post this, but it seems as though both this plugin, and the preclear script, were unable to see this new drive for whatever reason. Any help would be greatly appreciated.

I'm still unable to get the temp sensors plugin working after getting PERL installed. Any other options until lmsensors.org is back up?

Is it possible to change the default webserver to chorus or chorus2? There's a streaming option, like yatse, as well as a whole "tool box" of JSON commands you can send to your kodi box. Apologies if I don't quite wrap my head around why doing a clean library or update from the headless box itself would cause everything to vanish. Wouldn't the "initial" scan to create a DB be done on the docker kodi ? So I guess I don't understand why updating it there would cause an issue.

I would pull your flash drive and check to make sure it's not on it's way out if that were me. Sounds as though something didn't install correctly in the first place. But I'm no expert.

Maybe a reboot, or a hard browser refresh? (Ctrl-F5) ? You don't have this listed in your plugins? "Dynamix Cache Directories"?

Refused for me as well.

Installed PERL, hit detect, blank screen for a second, still detects nothing

I have installed system temp, and click detect, and nothing happens. What am I missing?

Thanks very much.

Am I blind? Where is the actual plugin itself? Or do I have to actually download sensor-detect (lmsensors.org appears down). Is there an actual plugin or do I manually have to set this up with a .conf file?

he's already changed it, of course.

He did not. Wow, that was probably the last thing that would have dawned on me. Thanks very much.

After the tmux session that I could see finished, the GUI was still exhibiting the same issues. He had to perform a reboot, and adding the drives to the array took much longer than expected for precleared drives, so at least one or two of the drives if not all of them never seemed to finish. Is the output of this command still relevant after a reboot? The GUI is now fine, responsive, etc.