Noim

As far as I can tell, it really crashes for me. The server in general doesn't even respond to pings after the crash. franz-diagnostics-20230623-2012.zip

Easy is very expensive and cost more time. What are some other options? This is the fdisk output: Disk /dev/sdb: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors Disk model: WDC WD80EZAZ-11T Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 8253E41B-E414-4985-BD29-FBE663B171ED Device Start End Sectors Size Type /dev/sdb1 64 15626928094 15626928031 7.3T Linux filesystem

Yes, he doesn't like the partition layout. Any way to fix this?

What will happen if I start the array with the new config? Will it wipe my drives? I mean, they are formatted correctly with xfs by unraid. I can't remember if unraid prompts you first, or just format automatically.

Hi guys, Because of the rising energy costs, I decided to move my drives from my r710 to a more energy efficient hardware. In my r710 I used a PERC card which just passed the disk to the system. Because of this, the disk are now called different. This is why unraid says they are the wrong disks. But they are not. Both disk just contain the file system, and were not used with any raid feature of the PERC card. I verified this with Unassigned Devices. How can I force unraid to accept the renamed drives? Greetings Nils Edit: I don't have any parity disk. Just this 2 drives. Both a xfs (formatted by unraid). What happens if I just add both drives as drive 3 and 4? Will unraid format them again? Or just use these with their files?

Oh, I am sorry. There was no response to @HarryMuscle question and a quick google search wasn't helpful either. So, I just expected there is no repo. I will do a proper pull request.

Because nobody cared, and the dev doesn't even publish the plugin on GitHub, so I could make a pull request I investigated by myself. The abort how it is implemented is flawed. This is my fix. Not elegant, but it works better than the current version. Starting at line 115 in exec.php: case 'abortScript': $script = isset($_POST['name']) ? urldecode(($_POST['name'])) : ""; $pid = file_get_contents("/tmp/user.scripts/running/$script"); exec("pkill -TERM -P $pid"); exec("kill -9 $pid"); $processListOutput = null; exec("ps aux | grep -i '/tmp/user.scripts/tmpScripts/$script' | grep -v grep", $processListOutput); foreach ($processListOutput as $emergencyKill) { $emergencyKill = str_replace("root","",$emergencyKill); $emergencyKill = trim($emergencyKill); $rawKill = explode(" ",$emergencyKill); logger("Kill pid: ".$rawKill[0]); exec("kill -9 ".$rawKill[0]); } @unlink("/tmp/user.scripts/running/$script"); file_put_contents("/tmp/user.scripts/finished/$script","aborted"); file_put_contents("/tmp/user.scripts/tmpScripts/$script/log.txt","Execution was aborted by user\n\n",FILE_APPEND); break; The original version didn't kill all running script instances. And the grep command not even found the correct processes if I tried it manual.

@Squid My issue still persists. Here is a test script: After aborting it, the script process is still running: What am I doing wrong?! This is how it gets spawned if I press background process: The process 10197 survives if I press abort. Plugin is up-to-date and running on unraid 6.9.2.

But it doesn't spawn any new process. The content of fan-script.sh is the content of the user script.

Hey guys, I have a problem. Currently I use User Scripts for controlling my fans. For this I have two scripts. One for the night and one for the day. Always when I go to bed, I abort the day script and start the night one. After some time I noticed, my script stopped working and throws the same error again and again. The error itself has nothing to do with user script. It only made me realize something. When I press abort, the script itself doesn't get killed. Here you can see the output of ps -ax | grep script after I aborted the script: The highlighted process is the process I aborted. It is still running which obviously is an issue. The first time I had 20 processes running without noticing. All doing the same thing which overloaded my ipmi controller. I attached the script to this comment. fan-script.sh Why does user script not kill the script. This is what I expect when I press abort. Or is it even a problem of my script?