lasers

Thank you! changing to the same path: /mnt/user helped with the rewriting, it now moves the files in a matter of milliseconds. I then tweaked my cache dir settings and now sonarr move files without spinning up the array. Thank you so much for your help! Really appreciated. :-)

Thanks for replying! /media = use cache disk: yes /mnt/cache is a drive share so no cache setting I guess? I feel quite lost here...

I have noticed that whenever sonarr moves files from my download folder to my media library it spins up the array even though I have a cachedisk. I can also see that the file is written rather than moved to the new destination which is on the cache drive /mnt/cache/. (While the move is in progress I can see a .partial~ file in the destination folder). Is there any way to avoid this? Paths: /config --> /mnt/cache/appdata/sonarr/ /dev/rtc --> /dev/rtc /tv --> /mnt/user/media/tv /downloads --> /mnt/cache/appdata/sabnzbddownloads/complete/ Thank you!!

scroll up and start reading at Reply #21 Thank you for your reply. I've tried to restart it and reinstall it. It did not work. When I tried needos the last time (1-2 weeks ago) it was still on ver 12. Do I need to change EDGE setting? In that case, to what? I also saw: But I do not know how to compile it from source I'm afraid... You don't have to compile it, the docker does that. I have EDGE set to 1286. See here. Note that you have to wait a little while it compiles before you can access its WebUI. You can monitor the progress in the docker log. Thank you so much! It worked. Took maybe 10-15 minutes to compile but seems to be working now.

scroll up and start reading at Reply #21 Thank you for your reply. I've tried to restart it and reinstall it. It did not work. When I tried needos the last time (1-2 weeks ago) it was still on ver 12. Do I need to change EDGE setting? In that case, to what? I also saw: But I do not know how to compile it from source I'm afraid...

Is there any way to update nzbget to v15?

128,000TB. I believe that's the current 48-bit LBA BIOS limit. Is this also true for the N36L? I'm thinking of upgrading my 1.5TB drives to 4-6TB WD Red depending on what deal I can get.

Nice to hear from another N36L owner, im getting one more drive tomorrow and some ram to really get going with my server build. Did you preclear you're drives. How long did it take you for?

I'm currently building my first unraid server, using a HP N36L, I've just finished preclearing on two of my drives. Got a couple of SMART-errors and it was also very slow, should I be worried? The F4 2TB is brand new, but is showing some errors: Multi_Zone_Error_Rate = 100 252 0 ok 11 - it was also really slow. Is it because of the overall hardware of the n36l? (AMD Athlon II Neo 1.3GHz - 1GB ram) or something else? The F2 has reported some smart-errors before (UDMA_CRC_Error_Count 0x003e 100 095 000 Old_age Always - 64) but since I changed cable in my previous computer I haven't seen it rise. I'm really thankful for your help! preclear_log.txt preclear_log_2.txt

I bought the 160GB version, it was really cheap here in Sweden. I'm running preclear on two samsung harddrives, one F2 1.5TB and one F4 2TB. The F2 took 25 hours to complete. Pre-read time 5:40:31 (73MB/s) Zeroing time 5:22:48 (77MB/s) Post-Read time 14:06:12 (29MB/s) My F4 has been running for 35 hours now, and is Post-reading at 21MB/s according to unmenu - if I telnet in to the server it tells me that its running at 60-85MB/s. Why is it so slow, it should only take about 24-26 hours, right? Running the latest (modded) bios from here: http://www.avforums.com/forums/networking-nas/1521657-hp-n36l-microserver-updated-ahci-bios-support.html - Preclear script is latest version.