p0xus

So I think I may have found a glitch in this plugin. I wrote a script that mounts a drive using unassigned devices, spins it up, and after some checks backs up a series of folders to the drive. Afterward it unmounts the drive and spins it back down. The glitch comes in when running this script through User.Scripts. After the execution of the script ends, the drive spins back up and remains in that state. The drive only spins back up when running the script through User.Scripts. When run through terminal or ran after the Appdata Backup plugin's process, the drive remains spun down. Here is the script: #!/bin/bash source_dir="/mnt/user/Backups" destination_dir="/mnt/disks/External_Backup" script_dir="/mnt/user/scripts/Backup_to_External_Drive/" config_file="${script_dir}backup_config.json" logger_tag="Backup to External Drive Script" echo "##### Backup Script Starting #####" | tee >(logger -t "$logger_tag") if [ -s "$config_file" ]; then folders=($(jq -r '.folders[]' "$config_file")) backup_drive=$(jq -r '.backup_drive' "$config_file") else echo "ERROR: Config file: "$config_file" not found. Exiting." | tee >(logger -t "$logger_tag") echo "##### Backup Script Exiting #####" | tee >(logger -t "$logger_tag") exit 1 fi echo "Mounting and spinning up drive." | tee >(logger -t "$logger_tag") /usr/local/sbin/rc.unassigned mount "$backup_drive" hdparm -C "$backup_drive" # Check if the source directory exists if [ ! -d "$source_dir" ]; then echo "ERROR: Source directory $source_dir not found." | tee >(logger -t "$logger_tag") echo "##### Backup Script Exiting #####" | tee >(logger -t "$logger_tag") exit 1 fi # Check if the destination directory exists if [ ! -d "$destination_dir" ]; then echo "ERROR: Destination directory $destination_dir not found." | tee >(logger -t "$logger_tag") echo "##### Backup Script Exiting #####" | tee >(logger -t "$logger_tag") exit 1 fi # Loop through each folder and perform backup for folder in "${folders[@]}"; do # Check if the folder exists in the source directory if [ -d "$source_dir/$folder" ]; then echo "Backing up $folder..." | tee >(logger -t "$logger_tag") rsync -av --delete "$source_dir/$folder" "$destination_dir" 2>&1 | tee >(logger -t "$logger_tag") echo "Backup of $folder completed." | tee >(logger -t "$logger_tag") else echo "Folder $folder not found in $source_dir. Skipping..." | tee >(logger -t "$logger_tag") fi done echo "All backups completed." | tee >(logger -t "$logger_tag") echo "Unmounting and spinning down drive." | tee >(logger -t "$logger_tag") /usr/local/sbin/rc.unassigned umount "$backup_drive" /usr/local/sbin/rc.unassigned spindown "$backup_drive" echo "##### Backup Script Exiting #####" | tee >(logger -t "$logger_tag")

Do you guys think you could add bpytop (the new python port of bashtop)? The author recommends everyone migrate from bashtop to bpytop.

Im having the same problem as some others on this forum. I have a Supermicro X10DAL-i with dual Xeon E5-2678s and when I say detect drivers, it says "coretemp nct7904", but there are no sensors in the list. I think I remember seeing them right before I saved which sensor was which, but the lists have been blank ever since. I am new to UnRAID, but will do my best to send any diagnostic info you want. Ive tried reinstalling the plugin, but no difference. If not this plugin, is there any other way to see CPU temps in unraid? It concerns me greatly that I have no idea how hot they are. I havn't wanted to stress them without knowing.