mikedpitt420

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.

This docker fails to start for me. I have more then 10GB available in my image, and all other dockers are running just fine. Attached is a copy of my settings. There is also no setting.conf or any other files where I mapped the config folder to. I also get dae9c26d16de67a73dc8a5856b290fab78ee27a2a2c42990ad0037f37253b453 Error response from daemon: Cannot start container dae9c26d16de67a73dc8a5856b290fab78ee27a2a2c42990ad0037f37253b453: error gathering device information while adding custom device "/dev/sr0": lstat /dev/sr0: no such file or directory EDIT: by removing the "extra parameters" settings referencing sr0= , I managed to get the docker to start. Should I have removed this line? Should it be something else entirely? Is this solely for passing an otical drive to this program? Also, I cannot paste the key into the MakeMKV GUI when you hit "register". And there is no settings.conf file in the /config folder. Will it still work? EDIT: Just creating a file called settings.conf in your config (666 perms and chowned to nobody:users) and adding that string seems to do the trick.

I am helping a friend build a new system. There was initially no disk.cfg as there was no array ever, which made the preclear plugin throw an error about there not being one. After creating the array, starting, then stopping again, I was able to get to start a preclear. He is on unRAID 6.1.3, no controller (all drives plugged directly into mobo) and started preclearing 5 x 4TB WD Purples. Status reported fine on all drives through the preclear plugin, until step 10, where status stopped showing in the UI, and the plugin information just hung at "Retrieving Information" with the UI throwing all kinds of odd errors and becomes largely unresponsive and almost unusable (icons missing, other odd behavior): Warning: readlink(): No such file or directory in /usr/local/emhttp/plugins/dynamix/include/local_prepend.php on line 18 Warning: readlink(): No such file or directory in /usr/local/emhttp/plugins/dynamix/include/local_prepend.php on line 18 43% core 0 / 1 Warning: readlink(): No such file or directory in /usr/local/emhttp/plugins/dynamix/include/local_prepend.php on line 18 3714 MHz eth0 Warning: readlink(): No such file or directory in /usr/local/emhttp/plugins/dynamix/include/local_prepend.php on line 18 1000Mb/s - full duplex *I also checked the tmux session just to make sure that 43% at the end of one of the lines wasn't garbled information from a tmux screen, and it's not. Dropping into the only active tmux session showed only one screen, of one drive at ~ 25% done with post read (still moving). I will report back as to whether the GUI un-hangs after it completes, or a reboot was required.

Well, no amount of flashing seemed to recognize this card with any firmware I could find. I tried flashing through a windows command prompt, through a freedos boot USB stick to no avail. I think you can add this card to the list of NOT compatible with unRAID.

I just installed this and cannot get it to load. I click webUI and get a ERR_CONNECTION_REFUSED ? I installed this with a valid code, using all the defaults. EDIT: Now I just get a gigantic page of errors, that is too long to list, starting with Caught exception in MusicBrainz::Server::Controller::Root->begin "08006 DBI connect('dbname=musicbrainz_db','musicbrainz',...) failed: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? at lib/MusicBrainz/Server/Connector.pm line 42. I have my mappings as: /config/ to /mnt/cache/appdata/musicbrainz/config /data to /mnt/cache/appdata/musicbrainz /music to /mnt/user/media/music I have read I may need to delete a folder from within the docker possibly or something? I haven't exec'ed into a docker before, if this is in fact what I need to do, can someone tell me the commands to do so, and which directories etc, I need to delete?

I've pointed him towards the IT firmware from this page here: https://lime-technology.com/forum/index.php?topic=12767.0 . Specifically, to this firmware here: LSI SAS2008 Controllers(P11).rar - 2.21 MB (Windows) http://www.mediafire.com/?n5p145c4z03t27r will report back if flashing this card is successful. Looking up the card, it has a SAS2108 (ROC) chipset and is an 8 port card, but there is no confirmation anywhere that this card was ever able to be flashed successfully. *Crossed fingers*

I've posted over in that thread as well. The more odd thing is, that the OTHER drive that unassigned devices is managing (for mythtv recording and KVM mythbuntu ISO) stays spun down after it's inactive time. It seems simply loading the unRAID GUI makes it only spin up the drive with no FS on it yet.

I have been trying to keep a precleared warm spare drive in my NAS. I use the unassigned devices plugin to maintain another drive outside of the array drive for MythTV. I precleared the device, hit the "Clear Statistics" mark in the unassigned devices plugin. Next I clicked on the drive itself, and set the spindown time to 15 minutes. After which the device spins down, and is reported by hdparm as "standby". Whenever I load the unRAID UI, the Unassigned Devices plugin takes a bit to load, after which the drive is spun up again. Is there any way to prevent the plugin from spinning up this drive every time the unRAID UI loads?

Here is what now happens. I clicked the drive in the unRAID UI and set the spindown to 15 minutes. It spun down after that amount of time. I checked with hdparm -C and it reported as standby. After loading the unraid UI, the unassigned devices plugin takes about 15 seconds to report back information, after which the drive is spun up. How can I prevent the unassigned devices plugin from spinning up my drives?

So I've now set it also to s18 which is 1min 30sec. And I check it with the -C flag, and it continues to show as active/idle

Well, S6 is 30 seconds. Is that still too low?

I've run that command Weebotech, the hdparm -S6 ata-WDC etc. I get a response saying "Setting Standy to 6 (30 seconds) but in the unRAID GUI it never appears to actually spin down? What am I doing wrong?

So it sounds like my "feature request" had already been planned Thanks for the info !

Awesome! So when does unRAID actually do the SMART tests on a disk drive? At boot? With this spun down those results will be inaccessible correct?

Also, I've put in a feature request for this for the unassigned devices plugin here: https://lime-technology.com/forum/index.php?topic=38635.555 anyone wants to 2nd that or chime in to see if it can be added as a feature would be greatly appreciated Thanks again!

Weebotech, that would be exactly what I was looking for although I only want hdparm command to affect that warm spare drive. I definitely see why a hot spare, and auto rebuild wold not be preferable in a lot of situations, and that's not what I want. What I do want, as mentioned above, is the ability to have the drive ready, precleared, and KNOW it's in good working order. Then when I get a bad drive, I can affect a drive rebuild immediately from anywhere. I have an OpenVPN server on my router that allows me to get a local subnet IP and access my unRAID webGUI from anywhere, so if I'm on the road I can start a rebuild right away and not have to worry another drive will fail until I can get back to the server. Thanks Weebotech

I know this has been a failed feature request and discussed before in v5. I don't seem to be able to find anything in the forums that actually solved this question. I can't imagine I'm the only person wanting to keep a warm, pre-cleared and ready spare drive in their unRAID system so there has to be a "right" way to do this. For anyone who doesn't have easy and ready access to their NAS or does a lot of remote watching while on the road, this would be an absolutely necessary feature and I'm kind of surprised no one else has really tackled this issue as of yet. I also just want to make sure that some of the info may be different in v6 and above as most of the info I can find on this topic is from v5. I would like to keep a pre-cleared warm spare, plugged in and in my NAS but not added to my array. I would like this drive to be spun down after boot. It would be great if unRAID still would do SMART tests on it etc. and let me know that the drive is still in good status but simply being plugged in and remaining spun down would be sufficient. What would I need to add to the go script to make sure that this drive spins down after everything has booted? Also, some of the solutions I've seen use commands that reference /sdX which seems incorrect as those can be rearranged at reboot. Any help in this topic would be greatly appreciated :-D

I don't either I only use it for remote watching. But when I saw HTPC manager, as a possible alternative to nzb360 I jumped on it. I just wanted to know if anyone else had my same issue.

There USED to be an auth token setting in CP's Plex notifications, which is now gone. I can get Sonarr and Couchpotato to update plex with only the username and PW, but HTPC manager will not. Odd.

There are quite a few people that are having problems with their SSL certs. Plex claiming that you should not have to accept a cert, which I definitely have several times after restarting Plex. It also isn't viewable as a secure connection on Plex.TV although any of my friends can see my shared library securely. For the moment I'm going to chalk this up to Plex's new, and not executed correctly, certs and security.

That's definitely on as well.