SlrG

What version of unraid do you use? If you are on v6b I would recommend to not use the plugin for now.

@maspiter: I think the device nodes might change on reboot so the excluded drive outside the array could become one of the array drives suddenly. It propably would be better to let the user define outside drives by their drive id.

Before we start troubleshooting this, I think you should upgrade your server to beta 10a ASAP! Beta 7 and 8 have a DATA CORRUPTION ISSUE and could damage your data! Once you have done that and checked your data, please post a full syslog when booting your system with the plugin enabled. This should give me a first idea what is going wrong. Also the newest betas introduce a new plugin framework and the plugin is not yet adapted to support this. I'll have a look at this in the future, but it'll take some time, as I'm rather busy in real life at the moment.

The ^M at the end of the interpreter line suggests you have propably used a windows editor to create the script file. Don't do that. Use vi or nano in a console window. Or make sure your editor saves the file as unix type.

+1

Could be. Here are the exact filenames in that directory: 01 Kami nomi zo Shiru Sekai/ 02 Kami Nomi zo Shiru Sekai_II_-_[1280x720_Blu-ray_FLAC]/ 03 Kami nomi zo Shiru Sekai - 4-nin to Idol [OVA] (BD 1280x720)/ 04 Kami nomi zo Shiru Sekai - Tenri-hen [OVA] (BD 1280x720)/ 05 Kami nomi zo Shiru Sekai - Megami-hen [season 3] (BD 1280x720\)/ 06 Kami nomi zo Shiru Sekai - Magical Star Kanon 100% [DVD 576p 10bit AAC].mkv Other Special chars and even Japanese Characters are possible. So if the script could be improved to handle such special cases, that would be great.

Great script! Sadly when adding my Anime collection I get the following error: bitrot.sh -a -p /mnt/user/Anime bitrot, by John Bartlett, version 1.0 Scanning for new files... (53.9%) stat: cannot stat `/mnt/user/Anime/Kami Nomi zo Shiru Sekai/05 Kami nomi zo Shiru Sekai - Megami-hen [season 3] (BD 1280x720)/[JacobSwaggedUp] Kami nomi zo Shiru Sekai - Megami-hen - 01 (BD 1280x720).mp4': No such file or directory ./bitrot.sh: line 195: 874833978000 + : syntax error: operand expected (error token is "+ ") Do you have an idea what goes wrong?

I'm back from vacation. Do you want to continue trouble shooting?

1.) Just prepare the new stick with a stock new unraid system. Start with the new stick but don't start the array! Only get the GUID of the new stick. Send it to Tom and ask him to transfer your license to the new stick, because the old one failed. He'll send you a new license. 2.) Delete all files from the new stick (don't format!) and copy over all files of the old one. Put the new license on the new stick (overwriting the old) and you are ready to go. If it does not work, you'll propably have to run make_bootable again.

No problem. I'll be on vacation starting tomorrow however. If we don't solve the problem today, it will have to wait till I return or some other user has an idea how to help you. Sorry. Another question: Do you have other drives in your system besides the array drives and the cache?

If you are still able to connect a shell window when the gui hangs, then yes, a syslog after you clicked apply would be great. Beforehand, please try to enable debug mode on the s3 sleep settings page (output to syslog). You'll find the syslog at /var/log/syslog. Also I'll need the content of /boot/config/plugins/dynamix/dynamix.s3.sleep.cfg. Another idea would be to disable all other not dynamix plugins. It might be some unknown clash between plugins. If it should work after disabling the other plugins you could try to reenable one by one, to find the culprit. If it still doesn't work after disabling all others, we will be sure, that something is wrong with the plugin on your system.

Hi Kricker, I'm sad to hear you have problems. I'll need some more info. - What is your unraid version? - How did you install the plugin? - Did you reboot afterwards? (Normally not necessary, but I won't hurt to try. ) - Did you have an older version of the plugin before? - Does the error occur when you still have the default settings? Or did you change anything? If so, please post a screenshot of your settings before you hit apply. - A full syslog would be great also. regards SlrG

Someone posted some time ago, that there is an error in the network checking of the s3sleep script of dynamix. He also said he was going to fix it and send the code. But he never did, so the bug is propably still in there. Could you test with the standalone s3sleep script from this thread and report if it works for you? If it does, it might be possible to port the changes there over to the dynamix script, to fix the issues.

I did not test it on other betas, so I can't say for sure, but in theory it should work without problems. Just give it a try and report your findings. If you have trouble, we can try to solve them together.

Plex will never let the cache spindown, no matter what settings you use. (At least that is the current state of things). You'll have to install plex to a ssd drive outside the array to get your cache to spindown. Sorry. Of course the ssd will be always active, but as it makes no noise and little heat and takes only a small amount of power, thats not so much an issue.

I added a modified version, which should work on v6b6. Please give it a try and report problems. For sql support maria db should be supported. The plugin is still in old unraid plugin design structure.

On 5.0 and above the command to invoke the s3sleep has changed. Please use echo -n mem > /sys/power/state instead.

I'm still on V5. Over the next week I will give V6 a go again. If the s3sleep problem I had on the last try is gone and it works for me, I'll look into the plugin. But I'm not really sure how the best future would be. There are several options. 1) Try to get the plugin to work with V6 as it is now. It might be meaningless work, as changes in the next beta might break it again. 2) Wait for the V6 plugin system to be finished and convert the plugin to use that. 3) Drop the plugin route and create a docker container (There might be already something available? Did you look into that?) 4) Let people use a vm where it is much easier to install proftpd including graphical management tools like gadmin-proftpd. For all ways there are pros and cons. What do you think?

Check the flash drives file system in an windows pc. If you get unfixable errors or if it still fails to delete afterwards, your flash drive is propably broken.

Unraid boots and installs everything into the RAM of your computer. So /etc/vsftpd.conf is in RAM too. On reboot all changes will be lost. You have to create a vsftpd.conf with your changes on your flash drive and add a line to your go file, that replaces the /etc/vsftpd.conf with your version on the flash. This will then happen on every reboot and restore your settings.

Sounds nice. Please keep us updated.

My plugins are: unmenu dynamix with plugins (esp. s3sleep) powerdown screen snap lms pyload transmission proftpd glftpd mysql nzbget plex trolley boiler APCupsd VirtualBox

Great it works now. I'll fix both problems and send a pull request to be included in the official version.

That is propably the reason -ED fails. The empty line when no cache is detected is jumbling something up in the script I guess. I never tested it with no cache drive present. Please give me a little time to take a closer look. I'll report back once I have news. Thank you very much for patiently helping me finding the core of the problems. edit: could you maybe edit s3_sleep and replace the 76 devicelist+=("$cache"); with if [ "$cache" != "-" ]; then devicelist+=("$cache"); fi Then please run s3_sleep -ED again and post the output. Ideally it should be your drive outside the array. If it is, then please check if the error message in the settings still appears. The change will not survive a reboot, but if it works, I'll fix it on github and send a pull to include it in the official version.

Further testing on my system shows the idle value propably sticks too. The problem is that it does not get shown on the config page. Could you please issue the following commands and post the output? echo /dev/$(ls -l /dev/disk/by-label | awk -F/ '/UNRAID/ {print $3}' | cut -c1-3) echo $(awk '/\/mnt\/cache/ {print $1}' /proc/mounts | cut -c1- echo $(ls -l /dev/disk/by-id/[au]* | grep -v part1 | sed 's/.*id\///g' | sed 's/-> ..\/..\//\/dev\//g' | awk '{ print $2 "|" $1}' | sort -k1) while read ini; do case $ini in rdevName.*) device=${ini#*=}; if [ ! "/dev/$device" == "/dev/" ]; then echo "/dev/$device "; fi; esac; done < /proc/mdcmd