petsheep

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.

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!

I am having the exact same issue. Have just started after upgrading to 6.6.3. What does "Fix Common Problems, Troubleshooting Mode" refer to?

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

Thanks Joe! Your explanation makes sense.

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.