Jump to content

petsheep

Members
  • Posts

    44
  • Joined

  • Last visited

Posts posted by petsheep

  1. 19 hours ago, Hoopster said:

    I went all the way from 5.14.23 to 7.1.66 in one upgrade with no other incremental version needing to be installed in between.  Given that worked, it should be the same for 6.5.54.  You can likely go all the way to a 7.x.x version now if you wish.

    Thank you. I just worry about their latest versions and don't need the latest features. I believe 6.5.55 is stable and has the Java patch so I should be set if I ever upgrade a device. 

  2. On 12/15/2021 at 9:02 AM, jademonkee said:

    Good luck! For me it worked with only small problems. Although I think I might have had to reset the APs so that they would adopt.

    The tag I use is:

    linuxserver/unifi-controller:version-6.5.54

     

    So for both to confirm, going from 5.14.23 to 6.5.54 is a good route? No need to take any earlier 6.* version to start with and then upgrade to 6.5.54? I'm really just looking for a stable version of 6 so I can eventually get upgrade to 7. Thanks!

  3. I've precleared many many disks and this is the first time I'm noticing something about the Post-Read. All my array disks are spun up and they are being read from. What's going on? Have I never noticed that before? No writes are being done, just reads. Should I be concerned?

     

    putty window tells me this:

    (  1,748,694,528,000  of  2,000,398,934,016  bytes read ) 109 MB/s

    Disk Temperature: 32C, Elapsed Time:  20:57:25

     

    unMENU tells me this:

    Post-Read (1 of 3). 87% @ 41 MB/s (20:57:25)

     

    Thanks

  4. Your "drill" in might be reading other files besides the directory entries.  (scanning contents of files, displaying thumbnail images, etc) Those other files are not cached.

     

    The initial list of directories is just the top level directories.  Use the "-F" option to put the cache_dirs in the foreground to watch as it does its scanning.  It will help to understand what it is doing.  Add the "-v" option to see even more detail when running  in the foreground.

     

    If you find your media player is reading the .jpg or .xml files, you can add a line something like this in the loop just above line 472.

    find /mnt/user/Movies -type f \( -name *.jpg -o -name *.xml \) -exec cat "{}" >/dev/null \;

     

    It will read the contents of all the .jpg and .xml files and send the output to /dev/null.  the side effect is that their contents is now in the disk buffer cache.  Modify as needed with the name of your own "Movies" share.

     

    Joe L.

     

    Thanks Joe! Your explanation makes sense.

  5. Hi there...

     

    Love the script and this is exactly what I'm looking for... but I'm not too sure if it's working as I expected. I've added the arg "-d 5" to scan 5 levels deep, but I can never get past the 1st level before the disks spin up. My shell skills are a little week (haven't written an sh since I was an intern), but from what I can tell, directories are cached from "build_dir_list()" function. This function has a predefined "-maxdepth 1" and does not use "$maxdepth". I've changed the 1 to 5 and I swear that fixes my problem. Any have similar experiences? Am I crazy? Suggestions?

     

    Thanks!

     

    -----20 min later update-----

    Ok, I see. Line 472 is where the caching starts and uses the arg -d. My question still stands... not sure why I get spin up after 2nd drill in.

  6. - user defined spin down time in minutes/hours per drive or the option for all drives (not just 1,2,3,4,5 hrs in a dropdown)

    - auto refresh of main.htm: would help with parity check or rebuild to get an updated status instead of clicking refresh. this could be a user defined option too.

    - ability to modify disk names instead of disk1,disk2,ect.....

    - choose which installed network card you would like to use. could be a dropdown and a forced restart after modification of NIC

     

    keep up the good work!

    Thanks.

×
×
  • Create New...