RockBian

The file /boot/armbian_first_run.txt is sourced by a bash script (/usr/lib/armbian/armbian-firstrun-config), but only if the file /root/.not_logged_in_yet exists.

On modern disks (modern as in the last 25+ years) the heads don't have to be parked. When you remove the power, the heads are automatically parked. The momentum of the rotating disk is used to provide the energy.

On my system it are symlinks to /sys/..: $ ls -l /dev/fan* lrwxrwxrwx 1 root root 41 Feb 19 17:50 /dev/fan-p6 -> /sys/devices/platform/p6-fan/hwmon/hwmon6 lrwxrwxrwx 1 root root 41 Feb 19 17:50 /dev/fan-p7 -> /sys/devices/platform/p7-fan/hwmon/hwmon5 Those are generated by an udev rule: $ cat /etc/udev/rules.d/90-helios64-hwmon.rules # Helios64 persistent hwmon ACTION=="remove", GOTO="helios64_hwmon_end" # KERNELS=="p6-fan", SUBSYSTEMS=="platform", ENV{_HELIOS64_FAN_}="p6", ENV{_IS_HELIOS64_FAN_}="1", ENV{IS_HELIOS64_HWMON}="1" KERNELS=="p7-fan", SUBSYSTEMS=="platform", ENV{_HELIOS64_FAN_}="p7", ENV{_IS_HELIOS64_FAN_}="1", ENV{IS_HELIOS64_HWMON}="1" KERNELS=="2-004c", SUBSYSTEMS=="i2c", DRIVERS=="lm75", ENV{IS_HELIOS64_HWMON}="1" SUBSYSTEM!="hwmon", GOTO="helios64_hwmon_end" ENV{HWMON_PATH}="/sys%p" # ATTR{name}=="cpu", ENV{IS_HELIOS64_HWMON}="1", ENV{HELIOS64_SYMLINK}="/dev/thermal-cpu" # ENV{IS_HELIOS64_HWMON}=="1", ATTR{name}=="lm75", ENV{HELIOS64_SYMLINK}="/dev/thermal-board" ENV{_IS_HELIOS64_FAN_}=="1", ENV{HELIOS64_SYMLINK}="/dev/fan-$env{_HELIOS64_FAN_}" # ENV{IS_HELIOS64_HWMON}=="1", RUN+="/bin/ln -sf $env{HWMON_PATH} $env{HELIOS64_SYMLINK}" LABEL="helios64_hwmon_end"

I don't think cpufreq config will help much. A cpu intensive task will eat all cpu cycles, no matter what frequency the cpu runs at. Somehow your task switching doesn't work as it should. Did you change anything in default priorities? How about memory utilization? Didn't know what Mastodon is, but it seems to be a social network. How do you use a NAS to browse a network?

A partition that start on byte 0? That's fishy. I think you don't have a partition on sda, only a filesystem.

Long shot. In the wiki on the corresponding screenshot you have the choice between /dev/sda1, /dev/sdb1 and /dev/sdc1, which are all partitions. Your sda isn't partitioned. Nor is your md0, but maybe the algorithm simply skips all device nodes which does not end in a number. So put a partition on your disk.