Mercantides

Well, I figured out the issue. It was an issue with completion script needing Python 2.7.9 but this docker only having Python 2.7.6. I thought I had disabled completion when I was testing things but apparently I didn't. I was able to update python to 2.7.11 and that fixed it.

Every time Sonarr adds a download to the NZBGet queue the individual status of that download starts as 'paused'. It seems to be a Sonarr issue as the CouchPotato downloads start as 'queued'. I'm using the linuxserver.io dockers for NZBGet, CouchPotato, and Sonarr. Things I've tried: I've looked through the logs for both NZBGet and Sonarr but nothing seems to be out of the ordinary. I've looked through all the settings for Sonarr and NZBGet. Sonarr has the priority setting for the download client but that doesn't seem to affect this. The global NZBGet download control doesn't make a difference. Internet searches talk about this happening with torrents but nothing seems relevant. Is this some weird bug or am I missing something obvious?

When I got home I paused the Midnight Commander transfer and left it alone until the drives stopped making seeking noises. I've got the case apart so I can feel the vibrations in the disks as well. The drives were still cleaning after 23 minutes but they seemed to be finished when I checked again after another half hour. After I resumed the transfer it went along between 80-100MB/s for the first 18GB and then dropped quickly to 40MB/s. After 65GB it's still going at 35-42MB/s so it seems that it was just backed up because of the short spin down time.

It does not work that way.. "shingling" is a part of a regular write cycle, so its not saved up or something like that.. the drive will never spin down without a completed write.. Yes, but it can store writes temporarily in the persistent cache until it gets a chance to write them to the shingled area. That's what I meant by 'shingling activity'. Obviously it's not going to spin down in the middle of a write but it must be able to pause these housekeeping transfers from the persistent cache to the shingled area when it receives a spin down notification. At 100MB/s it would take 4 minutes to transfer all that data. At 10MB/s it would take 45 minutes. A 15 minute spin down is probably too short to allow the drive to finish it's housekeeping in the worst case.

What spin down time should be used for these drives? Does the drive spin down if it is still shingling? Backstory: I've set up a new server with 2 of these as data drives and 3rd as the parity drive. I've temporarily mounted my old drives in the same server to transfer all of my files over. The first transfers of 2TB worth of movies went fine with speed averaging 40MB/s but the second transfer of tv data is only getting 10MB/s or worse. Notes: I originally started the tv transfer before the movies transfer was finished. I thought it would speed up after the movies transfer finished but it didn't. My tv data includes .tbn, .nfo, and .jpg files so it's possible these small files were causing issues but I've deleted them all and the transfer is still slow. The data is being moved from 4 different drives one at a time. The same drives that the movies were on. Often a transfer completes overnight or while I'm at work so there are hours between the end of one transfer and the start of the next. When I start the next transfer the first 5GB - 25GB or so will be fast but then it slows down again. I've tried both mv on the command line and midnight commander to move the files. My current hypothesis is that the default spin down time of 15 minutes is not enough for the drive to finish its shingling activity if it's seriously backed up. If the persistent cache is empty then the first 25GB of writes should be fast, shouldn't they? Is there anything I can do to diagnose this issue further?

I may toss a couple of video cards in my dual E5-2670 server to run some virtualized gaming machines so I've been looking for a cheap quiet tower. My short list right now is: Phanteks Enthoo Pro - $169 Fractal Design Define XL R2 - $203 Fractal Design Define R4 - $141 That's Canadian pricing and includes shipping and taxes. Everything else I can find is either over $200, too loud, or too hot. I found conflicting reports on the R4 actually working with full size SSI EEB but it looks like these guys fit a full size board in:

Thanks. I just found the preclear reports in /boot/preclear_reports/ Completion times were: Hitachi 5K3000 - 24:20:49 Hitachi 5K3000 - 24:10:00 WD20EARS - 26:38:20 This was all three in parallel on a M4A88T-M LE with an Athlon II X2 250.

I built a new unRAID server a couple of days ago. I basically ran memtest86+ and then started preclearing my drives, all via the console. When I went to bed last night there was only a few hours left on the preclears but at some point since then the power supply failed. I'm guessing that there is no way to get the result log of the preclears since I've got the box running again with a new power supply and unintentionally cleared /var/log/syslog in the process. If I was thinking I would have stuck the unRAID thumbdrive into my linux box to read syslog first. That said, there must be a way to verify that the disks were precleared but I haven't been able to find it. Can anybody point me in the right direction?