DZMM

Members
  • Content count

    723
  • Joined

  • Last visited

  • Days Won

    1

DZMM last won the day on October 3

DZMM had the most liked content!

Community Reputation

15 Good

About DZMM

Converted

  • Gender
    Male
  • Location
    London

Recent Profile Visitors

582 profile views
  1. [Support] Linuxserver.io - Kodi-Headless

    Is it really that simple to get add-ons to work? You just copy the userdata and addon_data folders? I'll give this a go tonight
  2. Drive getting Full

    Cut and paste job from the unraid inline help! High water for the reasons given. I also use share split levels and per share drive inclusion settings to try and further minimise drive spin-ups
  3. Personally, with so many old drives in your system I think you should go dual parity to start with. A 8TB seems to go for £160/$200 - how long would it take you to recover from two of your drives failing? More than a day's worth of hassle at least - I'm sure a day of your time is worth more than that. In the future as you replace the 2TBs and have fewer, newer drives in your system then single would be a safer option and you could move the second parity to the array. It's all about personal choice and risk levels. e.g. I've been using single parity for just over a year with a 5 disk array. Just this week I installed a 8TB parity (why my interest was piqued by this thread) and increased my array to 6 disks. Only one of my drives is older than 15 months (5 years old like yours) and it's the only one I'm expecting to die, so I've been getting by with single parity. However, I think next year when I add my next couple of drives I think I'll go dual as the chances of a dual failure (more drives and existing drives getting older) will increase and I don't want to waste my 'valuable' time trying to recover data.
  4. single parity allows you to recover from one drive failure, dual allows you to recover from two e.g. two fail at the same time, or one fails and 2nd fails while first is being rebuilt. I think the consensus on the forum is that if you have more than 10 drives, dual parity is a must. Or, you could take your chances and if you've never or rarely have two drives fail at the same time (I've only had two 'fail' at the same time and that was when I built my unraid server and actually did some rigourous drive testing, was moving drives around and had one drive I already knew was dodgy) then single parity should be sufficient.
  5. Drive getting Full

    Depends on the allocation method you've set for each of your shares: This setting determines how unRAID OS will choose which disk to use when creating a new file or directory: High-water Choose the lowest numbered disk with free space still above the current high water mark. The high water mark is initialized with the size of the largest data disk divided by 2. If no disk has free space above the current high water mark, divide the high water mark by 2 and choose again. The goal of High-water is to write as much data as possible to each disk (in order to minimize how often disks need to be spun up), while at the same time, try to keep the same amount of free space on each disk (in order to distribute data evenly across the array). Fill-up Choose the lowest numbered disk that still has free space above the current Minimum free space setting. Most-free Choose the disk that currently has the most free space.
  6. calibre safe setup

    no problem. I agree books (and music) don't have the same slick dockers like tv shows and movies, but this setup is working better for me than music where headphones does my head in. Yes, I have to use 3 apps but I barely have to use LL other than to add a new author, and I open RDP-Calibre maybe once a month or so to process books as they go into the library to ensure I don't end up with an unmanageable metadata mess further down the line.
  7. [Support] Linuxserver.io - Kodi-Headless

    If you manage to get this working I'd love to know how, so I can get trakt and artwork beef working. I'm currently running kodi on one of my VMs as I'm running Leia builds so sonarr etc can ping it and so trakt and artwork beef work. If I can get my add-ons working I can return to the headless version once v18 is supported
  8. Cache drive and downloading

    I don't use my cache for downloading as (i) it's a waste of SSD lifespan as it's only going to get written to the array when the mover has to kick in (probably before you've watched the download) (ii) I don't need SSD write speed for 'background' activity What I do is assign my downloads share to one array disk to minimise disk spin-ups, then have an import share on the same disk for completed downloads and my various media apps then move the completed downloads to their respective shares on the array. I've chosen the disk that is pretty much on all day as it has the most accessed files i.e. it's already spun up If I was going for silence during the days I'd use the cache drive or an unassigned SSD like @marshy919 but the file would still need moving to the array at some point i.e. you can't avoid the spin-up, although this could be overnight if you have a big enough SSD or not too many files downloaded.
  9. calibre safe setup

    Here's my setup: LL to download books and books are left in an import folder for Calibre to import and LL shares the Calibre library RDP-Calibre imports the books and I use to tidy-up metadata etc calibre-web is a very nice front-end to download and browse books and allows multiple users to track their reading progress e.g. I've created accounts for my kids, family and friends. calibre-web is accessible via the web via LE, so no need to open a port. Very easy one-time setup and it's working well for me. I don't find sending via the amazon address a problem - although I can appreciate there might be privacy concerns. #calibre-web location /books { proxy_bind $server_addr; proxy_pass http://172.30.12.2:8086; proxy_set_header Host $http_host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Scheme $scheme; proxy_set_header X-Script-Name /books; }
  10. Thanks. I'm on a mission to reduce server noise and spin ups this week
  11. I'm not sure if I'm using this plugin correctly. After installing the plugin does it work out of the box, or do I need to make the changes listed in the wiki? https://wiki.lime-technology.com/index.php?title=Improving_unRAID_Performance#Keep_directory_entries_cached Edit your go script to include the following line, near the bottom: /boot/cache_dirs -w This will go into effect on your next boot, and will cache all files and folders, with a scanning interval of between 1 and 10 seconds The cache_dirs command is commonly customized, for example like this: /boot/cache_dirs -d 5 -m 3 -M 5 -w confused
  12. [Support] Linuxserver.io - Kodi-Headless

    I used to have this problem. What fixed it was letting only kodi handle the metadata - no .NFO file from radarr, CP etc in the movie folder and making sure folder names are just movie name (year). This also solved the problem I was having with movie years always being wrong e.g a 2010 movie coming up as 1923
  13. ok, I've joined the 8TB club!! First drive was DOA - powered up with unbelievably loud (scared me to death!) and then wasn't even visible in BIOS. 2nd drive worked perfectly - precleared in 33hours (1 pass): ############################################################################################################################ # # # unRAID Server Preclear of disk Z840QTHH # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [4:16:13 @ 520 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [14:36:35 @ 152 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read verification: [14:30:05 @ 153 MB/s] SUCCESS # # # # # # # # # # # # # # # ############################################################################################################################ # Cycle elapsed time: 33:23:08 | Total elapsed time: 33:23:09 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status default # # # # # # ATTRIBUTE INITIAL CYCLE 1 STATUS # # 5-Reallocated_Sector_Ct 0 0 - # # 9-Power_On_Hours 0 33 Up 33 # # 183-Runtime_Bad_Block 0 0 - # # 184-End-to-End_Error 0 0 - # # 187-Reported_Uncorrect 0 0 - # # 190-Airflow_Temperature_Cel 29 39 Up 10 # # 197-Current_Pending_Sector 0 0 - # # 198-Offline_Uncorrectable 0 0 - # # 199-UDMA_CRC_Error_Count 0 0 - # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ --> ATTENTION: Please take a look into the SMART report above for drive health issues. --> RESULT: Preclear Finished Successfully!. root@Highlander:/usr/local/emhttp#
  14. I've just gone through this after adding my first drive in nearly 12 months. I grouped some of my shares onto certain drives to keep noise/spin ups down e.g. I do my downloads to disk 3 and I've moved my kids tv shows and movies to disk 3. This way when I'm working at the PC and the kids are watching TV, disk 3 is already spinning so there's no extra noise. All the kids tv is on this drive as they tend to flick around a lot, so again reducing spin-ups I've put my work files on disk 4 and the rest of the kids movies for the same reason grown-up movies and tv are on disks 1,2,5,6 i.e. they will spin-up in the evenings when i'm not at the PC as I'm watching something or someone else is. For TV, I've grouped my seasons using split-levels onto single disks so once a show is chosen the next episode loads immediately I write new grown-up movies and tv to the cache so to reduce 'unnecessary' spin-ups during the day My goal is to only have disk 3 and maybe 4 spinning (and parity of course), while I'm working to keep my system nice and quiet. So far it's working
  15. First drive was DOA - 'spun up' in bios but made an awful racket, but bios wouldn't detect. Una sent a replacement the next day - very easy to process. Pre-clearing now and looking all good so far.
Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.