.secret_squirrel

I completely missed the checkbox for the option to include duplicate file hashes in Find command. Thank you bonienl.

I just recently found this tool, so thank you bonienl for sharing it with the community. So far it is working pretty awesome. I do have a question: I have been playing with the `Find` feature and it isn't behaving as I am expecting. Just a quick manual glance at my exported hash files, I am finding duplicates that the tool isn't detecting. Here are some quick examples: 659ea86a44709dee1386da8fb4291cc9c123310b67cc62da3a2debf2f3e9593ad8f2bfb20ab1eedc7b357c20dd6bdcdd4709450b4e7cbfb46cde19773a78612e */mnt/disk1/Documents/Finances/Beneficiary Forms/SF1152.pdf 873588b4cc6056b6aba1b435124f59b25f68e7403d5c361efe1c24d22d623f12fa0c097f97a86f534878caa4c9e5b5d51e0ac21b5d6d628abbcf8f8c6d371c55 */mnt/disk1/Documents/Finances/Beneficiary Forms/SF2823.pdf 62bebcf21626d8062d0881c8f7a3587d0070af77704935d7ad09558f758475a7fd32ee6e923b7cc52c822fe8066b1fecc23f76f140463edd5119318be74ece60 */mnt/disk1/Documents/Finances/Beneficiary Forms/SF3102.pdf 762a1e0ed8d97e46a9a4db1fb0560bd3f5487ffff5e4b925a3cbf14ebd36e510382487625a825dd3805e2ca510105c11770d154e6e3e97655ea509055cfde19f */mnt/disk1/Documents/Finances/Beneficiary Forms/TSP3.pdf 659ea86a44709dee1386da8fb4291cc9c123310b67cc62da3a2debf2f3e9593ad8f2bfb20ab1eedc7b357c20dd6bdcdd4709450b4e7cbfb46cde19773a78612e */mnt/disk1/Documents/Finances/Beneficiary/SF1152.pdf 873588b4cc6056b6aba1b435124f59b25f68e7403d5c361efe1c24d22d623f12fa0c097f97a86f534878caa4c9e5b5d51e0ac21b5d6d628abbcf8f8c6d371c55 */mnt/disk1/Documents/Finances/Beneficiary/SF2823.pdf 62bebcf21626d8062d0881c8f7a3587d0070af77704935d7ad09558f758475a7fd32ee6e923b7cc52c822fe8066b1fecc23f76f140463edd5119318be74ece60 */mnt/disk1/Documents/Finances/Beneficiary/SF3102.pdf 762a1e0ed8d97e46a9a4db1fb0560bd3f5487ffff5e4b925a3cbf14ebd36e510382487625a825dd3805e2ca510105c11770d154e6e3e97655ea509055cfde19f */mnt/disk1/Documents/Finances/Beneficiary/TSP3.pdf `find` reports no duplicates: --------------------------------------- Reading and sorting hash files Including... disk1.export.hash Including... disk2.export.hash Finding duplicate file names No duplicate file names found Maybe there is an explanation I am overlooking?

Yes. Trial is restricted to 3 devices as of beta 15. You can hot plug devices manually after array start, but after a reboot you will need to detach them before you can start the array again. Thanks jonp. First I umounted the hot plug drive via command line, and refreshed my browser (clearing cache) with no luck. I was mounting it in the go file, so I removed those entries and rebooted. Still no luck. The array still is sitting with the invalid configuration message and won't let me start it up. I'm going to poke around and look for something that might be incorrectly persisting across reboots that stands out, but maybe you can point me in a direction? You have to physically detach the device. Not unmount it, but physically unplug the device from the system. Once the array is started, you can hotplug the device back and use it. Okay - got it. Thanks for the quick clarification.

Yes. Trial is restricted to 3 devices as of beta 15. You can hot plug devices manually after array start, but after a reboot you will need to detach them before you can start the array again. Thanks jonp. First I umounted the hot plug drive via command line, and refreshed my browser (clearing cache) with no luck. I was mounting it in the go file, so I removed those entries and rebooted. Still no luck. The array still is sitting with the invalid configuration message and won't let me start it up. I'm going to poke around and look for something that might be incorrectly persisting across reboots that stands out, but maybe you can point me in a direction?

Update appears to have gone well, but after a reboot the array was stopped and I have a message of "Too many assigned devices or too many attachd devices. Please consider upgrading your registration key." This machine is not licensed (trial only), and my configuration is 1 parity drive, 2 data drives, and another drive mounted outside of unraid. Would this be expected moving from 14b to 15b? I realize I am long overdue to purchase a license for this rig...

Thank you trurl. For clarification sake, a scenario where user and user0 will have differences is if you have files on your cache drive (or pool) that haven't been moved to a parity protected drive yet? If that is true, since I don't have a cache drive they will always be equivalent?

Hello Lime Tech Community! Since updating to 6b10a, I noticed I now have two user shares: /mnt/user & /mnt/user0. A command line diff between the two shares reveals they are equivalent. The logs further reveal two shfs commands that I was hoping to understand, but oddly enough searching got me nowhere. Some questions I had are, [*]What exactly is the -disks parameter, and why might two varying ranges be used to create multiple shares? [*]What is the "-o remember" on the second shfs command? My intuition tells me I have something configured incorrectly, and this is the side effect. Apologies if this was covered elsewhere, but does anyone else have insight they can offer to help me figure out what is going on? Relevant log entries that establish the two user shares: Sep 29 19:16:06 unraid-server emhttp: shcmd (26): mkdir /mnt/user0 Sep 29 19:16:07 unraid-server emhttp: shcmd (27): /usr/local/sbin/shfs /mnt/user0 -disks 16777214 -o noatime,big_writes,allow_other |& logger Sep 29 19:16:07 unraid-server emhttp: shcmd (28): mkdir /mnt/user Sep 29 19:16:07 unraid-server emhttp: shcmd (29): /usr/local/sbin/shfs /mnt/user -disks 16777215 2048000000 -o noatime,big_writes,allow_other -o remember=0 |& logger

Okay - fixed this thanks to dougnliz's recent post. I had previously tried granting ownership of the container's /config location to unraid-plex:users, but I didn't realize that wouldn't be enough. chmod -R 777 worked. Thank you.

Nice work needo! Unfortunately I am having trouble with the plex container, and so I am hoping the collective group can set me straight. I am unable to connect to plex once I get a container started using: docker run -d --net="host" --name="plex" -v /mnt/appdisk/plex:/config -v /mnt/user:/data -v /etc/localtime:/etc/localtime:ro -p 32400:32400 needo/plex Looking at the logs from within the plex container, I am getting seg faults. And when I restart from the ground up and watch the terminal output interactively as the container comes up, I see the following progression (with the last bit Ad nauseam): *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... No SSH host key available. Generating one... Creating SSH2 RSA key; this may take some time ... Creating SSH2 DSA key; this may take some time ... Creating SSH2 ECDSA key; this may take some time ... Creating SSH2 ED25519 key; this may take some time ... invoke-rc.d: policy-rc.d denied execution of restart. *** Running /etc/my_init.d/firstrun.sh... Version not specified. *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 107 6 3000 /config/Library/Application Support unlimited Segmentation fault 6 3000 /config/Library/Application Support unlimited Segmentation fault I am able to use the eshultz/plex tag in the meantime, but I would like to make a switch to this more minimalist approach that needo has created. My skill set is very limited when it comes to diagnosing within these containers, but I can follow orders well Thanks for any help in advance.