smakovits

this is likely not the right place, but how do I take your container and make it mine? I want to modify it to also install discogs-client automatically. Or, you could add it of course, but I am all for learning too, so whatever.

@smdion, any thoughts as to why when I change out your configuration file for one I have been using from standalone docker (also with your container), then beets no longer starts and instead it complains about a folder already existing config.txt

yeah, mine says 100%, 100% of the time...

After upgrading to version 6, I noticed in the dashboard that my CPU says to be at 100% all the time. It is a Sempron 140, but still, it shouldnt be at 100%. So I looked at the output from top and it was more normal, 5-30% jumping around. I then installed the stats plugin and it too reflects the output from top, so I guess I am wondering why the dashboard CPU statistic is not working as expected and if there is anything I could do to reflect accurate data.

yes?

OK, so while it is a .img extension, it is actually a mounted disk in unraid, separate from the unraid shares and disks? So when a container is downloaded and installed, the main files for it are here, in the img file. Therefore, the amount of space used will be determined by the containers I run.

ok, so I finally went to unraid 6. been running 5.x and a separate system with docker till now. I managed to get things up and running with docker and unraid, but I want to understand the function of the .img file. Since I had no experience with it before, I didnt need to know, but not that it is there, it has me curious. What purpose does it serve when adding containers to unraid? I went with the default 10GB, but saw others say they are near capacity, so that makes me wonder, what is happening to fill it up, etc. Surely it is something stupid simple...

Yes, I was doing it like I do normal preclear, but that is not what the directions say. When I did as told, it worked as expected.

So, I ran a preclear on the said cache drive, here are the results. preclear_finish_WD-WMAP42311958_2015-04-17.txt

OK, hopefully, thats all it is. I will stick it on another system and see what it does, run a preclear against it and stuff to work the drive a bit to see if it still acts crazy.

as a follow-up, I wanted to post a syslog for after removing the cache drive, it would seem as though it may have been my issue...but I really have no idea, but some things do appear functioning with it gone, so maybe. Plus, my log isn't stupid big now that it is gone syslog-2015-04-16_1.txt

here it is... syslog-2015-04-16.zip

How can I get the entire log? I did post the 4MB syslog in the zip there. The strange thing with the sata cable issue is the system hasnt moved in months, so nothing would be jarred loose. but I would be on bored with power as that could likely result from a PSU going bad I suppose. Would it be a bad idea to reboot at this point, just to see if the issue clears? Is there an easy way to figure out what is actually plugged into ata1?

Well, life was going great till this past week. I am hoping the issue is nothing, but thought before I went crazy rebooting, I would ask. The log was too big for pastebine, so I put just a section of it, hopefully it is enough since the same thing is repeated over and over. http://pastebin.com/N9weizCZ edit: looking at the array operation and it appears the mover is running, which it shouldnt be it should run at its default time edit2: the mymain view on unmenu is not showing the cache disk, but the unraid main page, under cache devices does show the drive and it is green, so not sure if this could be the source of the issue syslog-2015-04-15.zip

Answered my own question, put files where specified and now running at the pace expected

Perfect, thanks guys

I'll take a look at the doc. For what is here though, as I understand, going to v6, copy the files reboot. V6 will come up as rfs, that setting will be xfs, so new disk will be xfs unless changed to rfs. But this will only come into play if I add a new disk or format one.

OK, another thing that is changing, the option for the file system. Being on v5 should I mess with this at all or will it just be ReiserFS? I ask this because I set up a test system to preclear some drives and that is where I noticed this. In that case, it is defaulted to XFS I believe. Therefore, if using that system to preclear drives should this be ReiserFS or is XFS ok? Then, once on 6, where is this best? I know it is likely personal opinion, but still gonna ask. Also, can this be changed without losing data on disks already ReiserFS?

So run it again with the right directories? Without that I assume preclear didn't really do its job?

No, everything in boot/preclear, force of habit

dumb question, if I put preclear into /boot/preclear as opposed to just /boot, does it still work the same? I ask because I see this: = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 5,000,839,372,800 of 5,000,981,078,016 bytes read ) Disk Temperature: 40C, Elapsed Time: 22:26:14 ./preclear_bjp.sh: line 1186: post_read_err: command not found ================================================================== 1.15b = unRAID server Pre-Clear disk /dev/sdb = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 40C, Elapsed Time: 22:26:15 ========================================================================1.15b == TOSHIBAMD04ACA500 Y4M5K0PYFS9A == Disk /dev/sdb has NOT been precleared successfully == ./preclear_bjp.sh: line 1182: /boot/readvz: No such file or directory ./preclear_bjp.sh: line 1182: /boot/readvz: No such file or directory ./preclear_bjp.sh: line 1182: /boot/readvz: No such file or directory ./preclear_bjp.sh: line 1182: /boot/readvz: No such file or directory ./preclear_bjp.sh: line 1182: /boot/readvz: No such file or directory ./preclear_bjp.sh: line 1182: /boot/readvz: No such file or directory ./preclear_bjp.sh: line 1182: /boot/readvz: No such file or directory ./preclear_bjp.sh: line 1182: /boot/readvz: No such file or directory ./preclear_bjp.sh: line 1182: /boot/readvz: No such file or directory ./preclear_bjp.sh: line 1182: /boot/readvz: No such file or directory ============================================================================ No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. I mean the message is fairly clear that it failed, but the question is, did it? It is a 5TB drive and it completed in 24hours, so it did seem fast, but before moving the files to /boot and starting again, I thought it is worth asking. thanks

Just delete the folder right?

Just curious what sort of times people are seeing when clearing 5TB drives. I tried to find it in the results thread but failed and just thought to ask. Thanks.

thanks guys, I will remove unmenu from my go script. I did realize the one other thing I did install was the nice web gui for version 5. Is that something that should be removed then? just remove the plugin folder right?

2 things, use trakt, backup watched media, start new with docker and pull from trakt, job done Second to your point on stuttering, I suspect this is less to do with plug in vs docker and more to do with cpu horsepower and the ability to transcode. If your player can handle it itself (most can, ie chromecast, rpi), then set those to max throughput and make sure you tell it not to transcode. At least that's what I had as the issue and my plex was in a standalone docker container (not unRAID) as well as in a bare metal setup. Once I stopped transcoding at the server life was great.