Jump to content

greenythebeast

Members
  • Posts

    101
  • Joined

  • Last visited

Posts posted by greenythebeast

  1. I suspect it's what I noted earlier -- the allocation method check is done before the include/exclude.    Seems like a bug !!

     

    If that's the case, then it won't write to disk4 until either disk2 hits the 1.5TB point (50%); or disk3 doesn't have room.

     

    ... but before concluding that, you should at least upgrade to RC13 and see if that resolves it.

     

    I'd rather not upgrade to rc13 because of all the problems it's been having. I just remembered that disk2 is a 2TB disk. I'm going to try to get disk2 to 1TB to see if I can confirm your hypothesis.

  2. What file does the settings page write to? I could find it manually and see what is being set in the file.

     

    In the Config\Shares folder on the flash drive, there's a .CFG file for each of your shares.

     

    It will have a shareInclude=<...>  line and a shareExclude=<...> line that will list all of the included and excluded disks.  You should NOT set both of these manually ... you set one; then UnRAID simply lists all of the other disks on the opposing list.  I don't know what happens if you set them manually, and the intersection of the two sets isn't exactly the complete set of disks.

     

    But, for example, your Files.CFG should have these three lines in it (among others):

     

    shareInclude=disk3,disk4

    shareExclude=disk1,disk2

    shareAllocator=highwater

     

    I removed the excludes from the settings page like you suggested. The config file now reads:

     

    shareInclude="disk3,disk4"
    shareExclude=""
    shareUseCache="no"
    shareAllocator="highwater"
    shareSplitLevel="999"

     

    So it seems the settings are being written correctly. Not sure what the deal is :/

  3. You don't need to (and shouldn't) specify BOTH incudes and excludes.    If you list includes, then all other disks are automatically excluded.    In addition, I'd do as JoeL noted ... list the disks with no spacing, as UnRAID requires.  I have no idea if Simple Features "translates" this correctly -- but why take a chance?

     

    The disk allocation is indeed a bit strange.  Are ALL of your shares set to High Water?

     

    List the allocation on each disk of this specific share -- just do a "Properties" of the high-level folder "Files" on each disk (be sure to check ALL disks for this file ... not just the "includes").

     

    Finally, which disk is which?  I assume disk4 is the 1TB unit ... so it won't be written to until the high-water mark drops below 1TB ... meaning the 3TB unit needs to be more than 50% full.  If disk2 is your 3TB unit, then that hasn't happened yet.  But whether this what's happening or not depends on the actual interactions between the includes, excludes, and split levels -- and I'm not sure what impact your excludes are having, since you also have includes set ... and all of them aren't using the "no-space" format that UnRAID expects.

     

    Disk 3 is a 2TB while Disk 4 is a 1TB, so the high water mark should have been crossed by now. All of my non-cache-only shares are set to High Water.

  4. The one configuration screen you have shown has a "space" in each of the disk names.  That is wrong.

     

    Use "disk1"

    Not "Disk 1"

     

    Use all lower case for the disk names (although I'm not sure if that matters)

     

    There is no need to populate BOTH the includes and excludes.  One is enough.

     

    As I said, you've not listed "disk4"  Your include line is likely being ignored.  (Disk 4 != disk4 )

     

    As I mentioned, SimpleFeatures doesn't allow you to type in the disk names. It uses a checkbox system:

    fEhkWvZ.png

  5. The one configuration screen you have shown has a "space" in each of the disk names.  That is wrong.

     

    Use "disk1"

    Not "Disk 1"

     

    Use all lower case for the disk names (although I'm not sure if that matters)

     

    There is no need to populate BOTH the includes and excludes.  One is enough.

     

    As I said, you've not listed "disk4"  Your include line is likely being ignored.  (Disk 4 != disk4 )

     

    I use SimpleFeatures. It is my understanding that the capitalization and spacing is just a formatting decision on the developer's part and that's not how the actual config is written. What file does that config screen write to? I could check to see what the file looks like and go from there.

  6. This is the current setup of one of my shares:

    faRhyYN.png

     

    Essentially, I want the share to be allocated with the high-water method over Disks 3 (2TB) and 4 (1TB). However, this is how my drives are filling up:

    2Q2j4ui.png

     

    So my question is, why isn't any data being written to Disk 4? I have split level disabled so that shouldn't be the problem. Do I have something setup wrong? Please help!

  7. Are you saying the same sized (thread size) screws used to secure the hard drives are also the correct size to mount the rack to the case? That's odd since every 5.25 " and 2.5" drive I've dealt with uses to smaller M3 screws whereas every 3.5" HDD I own uses the larger 6/32 screws....

     

    All I can say is that the same screw worked great for both mounting the drives and mounting the unit itself.

     

    http://www.ipcdirect.net/servlet/Detail?no=211

  8. Sorry, I don't mean the screws that hold the 3.5" drives into the trays, I mean the screws holding the SS-500 into the 3 5.25" bay slots.  Are you saying Norco uses 6/32 screws to hold the SS-500 itself in the case as well?

     

    Previous SS-500 owner here. Yes, the screws are used for both mounting the drives as well as mounting the unit itself.

  9. Apparently iotop needs a Linux kernel that has TASK_DELAY_ACCT and TASK_IO_ACCOUNTING options set to yes. Doesn't look like unRAID has that since I get this when running it:

     

    root@Greenyserver:/mnt/user/Downloads# python iotop.py
    Could not run iotop as some of the requirements are not met:
    - Python >= 2.5 for AF_NETLINK support: Found
    - Linux >= 2.6.20 with I/O accounting support: Not found

×
×
  • Create New...