sibi78

@ich777, awesome, thanks for the quick reply!

Hi All, I recently learnt about PhotoPrism and I'm planning to try the Unraid docker for PhotoPrism. It seems that PhotoPrism supports a "read only" mode where it wouldn't modify anything in the original folders. Is there an easy way to enable this "read only" mode via the Unraid Docker? I tried skimming through the settings, but I couldn't find it. I think I can switch to the "advanced view" in the docker, and may be add the read-only flag to the "Extra Parameters" field (attached image). Would that work or did I miss the "read-only" option somewhere? Thanks in advance!

Hi All, I had been using Zoneminder docker with Unraid for quite a while. It was an older version. I upgraded to the recent version, and things stopped working. Is there a way to revert back to an older version of Zoneminder docker? I'd like to revert back for the short term (and debug why things stopped working in the long term). Could someone provide any pointers for reverting back to the old version? Also, whenever we upgrade Zoneminder, there was a suggestion to delete Zoneminder appdata and then, reconfigure. Did I understand this right? Thanks.

Thanks for confirming, @Vr2Io

Hi All, My current Unraid Server is still working, but I'm looking to upgrade it. I was thinking of doing the transition gradually. I anticipate testing the Unraid licensed flash drive and the data/parity drives in the new server multiple times (perhaps over a week or two) before I make the switch. Is there any downside to moving the Unraid setup (flash drive, data/parity and other drives) back and forth between the new and old servers during this transition? I wanted to check if there are any gotchas (like Unraid detecting a new machine config and behaving differently, etc) I need to be aware of. Thanks in advance. PS: I will back up the boot drive and drive assignments page before I begin.

Never mind, after some googling, I landed here: https://forums.zoneminder.com/viewtopic.php?t=27722 . I had to set the AUTH_RELAY variable to NONE and after that I'm able to see the Montage view now.

Hi All, I just updated my existing zoneminder docker image to pull the latest (it working fine before the upgrade). Everything seems normal after the upgrade except that my Montage view seems broken. I do see the error about checking if CGI is enabled in Apache and checking the PATH_ZMS variable being set correctly in the logs. Any ideas on what might have gone wrong with my upgrade? Thanks.

@trurl, thanks for the catch. I had tried this manually using crontab -e and it worked fine then, but I think I missed a * when I copied it over to the GUI. So I didn't suspect this. Thanks again, and it seems to work fine now!

Hi All, I'm using the user scripts plugin to run a custom script every 5 minutes. I've set it up via the GUI, and I provided "*/5 * * * " in the custom field and applied the changes. However, I don't think my script is running every 5 minutes (I'm looking for a log file the script writes to and the log file doesn't get updated with the right timestamps). Am I missing any final steps to run the script periodically? /etc/cron.d/root file does seem to have an entry for my script.... Thanks!

@Alphahelix, sure. With due credit to the original link (https://github.com/NoLooseEnds/Scripts/blob/master/R710-IPMI-TEMP/R710-IPMITemp.sh ), I made some slight tweaks. Note I can confirm this is working on my dell poweredge R710, your mileage might vary depending on the type of server. It's nothing fancy, but I'm starting out simple to see how it works - I mainly wanted to reduce the fan speeds from ~6K RPM with automatic fan control to something less noisy. The IPMI* variables must be filled with the right values for your server. Hope this helps. # TEMPERATURE # Change this to the temperature in celcius you are comfortable with. # If the temperature goes above the set degrees it will send raw IPMI command to enable dynamic fan control MAXTEMP=33 TEMP_STEP1=28 TEMP_STEP2=30 TEMP_STEP3=32 # 28 -> 20% # 30 -> 30% # 32 -> 40% # 33 -> Automatic control # This variable sends a IPMI command to get the temperature, and outputs it as two digits. # Do not edit unless you know what you do. TEMP=$(ipmitool -I lanplus -H $IPMIHOST -U $IPMIUSER -P $IPMIPW sdr type temperature |grep Ambient |grep degrees |grep -Po '\d{2}' | tail -1) echo $TEMP if [ $TEMP -ge $MAXTEMP ]; then echo " $TEMP is > $MAXTEMP. Switching to automatic fan control " ipmitool -I lanplus -H $IPMIHOST -U $IPMIUSER -P $IPMIPW raw 0x30 0x30 0x01 0x01 elif [ $TEMP -le $TEMP_STEP1 ]; then echo " $TEMP is < $TEMP_STEP1. Switching to manual 20% control " ipmitool -I lanplus -H $IPMIHOST -U $IPMIUSER -P $IPMIPW raw 0x30 0x30 0x01 0x00 ipmitool -I lanplus -H $IPMIHOST -U $IPMIUSER -P $IPMIPW raw 0x30 0x30 0x02 0xff 0x14 elif [ $TEMP -le $TEMP_STEP2 ]; then echo " $TEMP is < $TEMP_STEP2. Switching to manual 30% control " ipmitool -I lanplus -H $IPMIHOST -U $IPMIUSER -P $IPMIPW raw 0x30 0x30 0x01 0x00 ipmitool -I lanplus -H $IPMIHOST -U $IPMIUSER -P $IPMIPW raw 0x30 0x30 0x02 0xff 0x1e elif [ $TEMP -le $TEMP_STEP3 ]; then echo " $TEMP is < $TEMP_STEP3. Switching to manual 40% control " ipmitool -I lanplus -H $IPMIHOST -U $IPMIUSER -P $IPMIPW raw 0x30 0x30 0x01 0x00 ipmitool -I lanplus -H $IPMIHOST -U $IPMIUSER -P $IPMIPW raw 0x30 0x30 0x02 0xff 0x28 fi

@Squid, thanks for the reply, and for the "user scripts" plugin - it's very useful. I've created the same script via the user scripts plugin, and everything works well. I'm looking for a way to capture the output of my script to a log file (preferably in the plugin folder or in /tmp/) to check if everything is running properly. I couldn't find a way when I searched the forum. Could you shed some light into how I'd do this? Thanks!

Hi All, I have a Dell R710, and I found this script (https://github.com/NoLooseEnds/Scripts/blob/master/R710-IPMI-TEMP/R710-IPMITemp.sh) online to automatically control fan speed via IPMI. I was trying to set this up on my server with a custom script. I had a couple of questions regarding this: 1) I originally created my own shell script based off the above example in /root of my UNRAID server. The script was working well, but I had to stop the array, and restart the server. When the system rebooted, I noticed that my script stored in the path /root was deleted. This was surprising to me as I had expected the root filesystem to be persistent. Is this not true? If it is, where is a recommended place to store this script? 2) I had manually created a crontab entry for the root user to the run the above script periodically. That crontab entry also didn't persist across reboots. I was wondering what's the recommended way (plugin) for doing the crontab entry? Thanks for your help!

Ok, great news! After around a day of messing with things, and playing with @Fireball3's instructions, I was able to cross-flash the Dell H200A to the LSI IT firmware version 20. All of the instructions worked seamlessly (huge thanks to @Fireball3 and all other folks who contributed - you are all awesome!). The only hiccup I faced was the 2.bat step in the instructions, where we are trying to save the original Serial Boot ROM of the original H200A firmware. After @Fireball3 confirmed that I can ignore Megarec.exe tool hanging, I still managed to save the original firmware and flash contents using the SAS2FLSH.exe tool. Here's a snapshot of my H200A listing using SAS2FLSH *before* I flashed the firmware: As you can see it has the IR firmware. After following the instructions, I first flashed the Dell IT firmware, then I moved to LSI IT firmware version 7 and from there, I flashed LSI IT firmware version 20. I didn't flash the mptsas2.rom (BIOS) at first, but I didn't know how to confirm if the H200A was still working or not. So, I reflashed the firmware along with mptsas2.rom, and I was able to see the H200A listed in that BIOS. After this, I plugged into two 4 TB hard drives, and I was able to see them being listed. I also briefly booted ubuntu, and it was able to see the 4 TB drive. The next step is to try booting with UNRAID. Here's a snapshot from the BIOS utility which shows the H200A flashed with the IT version: For reference, I did have to purchase these SAS cables to work with the H200A on my Dell R710: https://www.amazon.com/gp/product/B07CKXFKHT/ref=oh_aui_search_asin_title?ie=UTF8&amp;psc=1 (not sure if amazon links are allowed in UNRAID). If not, please let me know and I can delete the link. So, overall, it was much smoother than I expected. I was able to flash the H200A from *within the Dell R710* itself, and I did NOT need a UEFI shell, etc...Phew...what a relief! Once again, thanks everyone, specifically to @Fireball3!!!

Just a quick update. I looked at the 2.bat and tried to see which step is failing. Only Megarec.exe (saving the serial boot rom) step is hanging. Googling for R710 and Megarec turns up several folks running into similar issues. However, I'm able to successfully run the SAS2FLSH utility to save the firmware (-ufirmware command) and flash (-uflash command) contents. Is it true that I don't have to really worry about backing up the serial boot rom? Even if I mess up the H200, can I restore the original card by using the saved firmware and flash contents? Any pointers would be helpful.

@Fireball3, I'm trying your instructions to cross-flash the H200 right now on Dell R710. I'm at step 2.BAT where we are saving the existing controller software to the logs folder. My system printed the "MegaRAID HWR Controller.." message and seems stuck there for about ~10 minutes. Is this normal? I tried CTRL-C ing but didn't help. Should I assume the system is hung and reboot and try again? Was wondering what's the "normal" time it takes to complete 2.BAT? Thanks!