Jump to content

DaleWilliams

Members
 View Profile  See their activity

  • Posts

    987

  • Joined

  • Last visited

 Content Type 

Posts posted by DaleWilliams

    Accessing unRAID via the OSX Finder it is very slow

    in General Support (V5 and Older)

    Posted

    That's probably just spin up of the drives, etc.

    There's a script around called 'cache drives'. (search the forums).

    It makes unRAID 'pre-read' the directories of your server and pre-load the directory tables into excess RAM on your unRAID server.  That allows directories to load almost instantly...individual files can still take some time to load. (again, drive spinup is the usual culprit for this.)

     

    Margarita 1.7 - Native macOS Monitoring App and Share Automounts

    in User Customizations

    Posted

    What do you prefer...  White or 'Dusk'? I'm over white apps, but not sure if the dusk colour scheme works as a useable app. I think the colours look pretty slick, but I'm also not colour blind  ::)

     

    https://dl.dropboxusercontent.com/u/86051512/white.png

    https://dl.dropboxusercontent.com/u/86051512/dusk.png

    I like the 'dusk'. But then again, I'm just bored with white, as well.

    That said, beware the subtle green shade on the subtle rose shade.

    Some displays may not show that contrast well.

    Margarita 1.7 - Native macOS Monitoring App and Share Automounts

    in User Customizations

    Posted

    Installed it. Excellent!

    Let me be the first with a 'stoopid user' support question!

     

    My unRAID is up and stable and has no errors.

    Margarita reports all is well. Excellent so far!

    The icon in the toolbar is a white on black icon.

    What happens if something happens to the unRAID?

    (temperature, write error, etc.) Does the little icon Turn Red? Flash? Ring Bells? Etc.?

    Of do I need to keep clicking on it to check status?

     

     

    ( I know, I could just RTFM, but what would be the fun of that?)

     

    [SOLVED] Seagate with huge Seek Error Rate, RMA?

    in General Support (V5 and Older)

    Posted

    I believe most SAS cables are shielded--at least up to the point where they fan out to individual leads. YMMV

    Allow them to touch and cross and mingle... just let it happen...its random.

    If you wire tie them together, they look nice and neat and efficient.

    But you've created long lengths of antenna running in parallel and feeding each other stuff.

    (Some electronics engineer might call that bundle of cables a 'transformer' that's actually increasing the voltage on some of the wires.  :o (Or is it an inductor? (I failed EE  >:( and never looked back  ::) ))

    Just cut the cable ties off and let them flop around...they'll be happier for it!

    [SOLVED] Seagate with huge Seek Error Rate, RMA?

    in General Support (V5 and Older)

    Posted

    About the SATA cables...

    They should be tight firm and preferably locked, but Do *NOT* tie them together, lay them out randomly.

    Otherwise you'll something like old fashioned AM radio static on your SATA lines.

     

    SATA cables are usually 'unshielded'...each acts like a little antenna. As real data travels down one, it 'radiates' its signal along the wire in a broadcast..the other cables, running parallel and being very close, will pickup the data signal and think its real.  Errors result.

    Backups

    in General Support (V5 and Older)

    Posted

    I certainly wouldn't start a parity check if the disk errors column wasn't all zeroes. 

    I have my browser HOME Screen set to the Tower/Main GUI page. I automatically scan the drives 'Errors' Column several times a day as a result.

     

    It *would* be very nice if there were some tool available that would identify the file on each physical drive that corresponds to the bad parity byte...but that's way way way over my head on how to do. (or is it at a low low low level of the OS?) Either way, I can't do help.  :(

    cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up

    in User Customizations

    Posted

    I am still noticing a long delay the first time accessing he shares though so I wasn't sure it was actually cached yet.

    Yes. I find that when I first START my array, unRAID is substantially 'unresponsive' for several minutes.

    Based upon that little flickering 'hard drive activity LED' on the front of the box, it appears that cache_dirs has a pretty high priority as it first populates memory with directories.  I just go get more coffee and wait it out.

    cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up

    in User Customizations

    Posted

    See here:

    http://lime-technology.com/forum/index.php?topic=4500.0

    for a lengthy discussion of Cache Directories.

     

    'wait' is discussed very early on...If I understand correctly, 'Cache_directories' is a script that runs, and is started when you boot up unRAID. BUT, at the time the script is started, the array is not yet 'online'.  {So my mental image of what's happening is that the cache_directories script runs, sees there are no disks, and will exit/stop running.  } The -w flag says, 'wait' until the array is actually started, the drives are mounted, and the disks become available, and THEN continue running.

×
×
  • Create New...