Carlos Hartmann

  • Content Count

    4
  • Joined

  • Last visited

About Carlos Hartmann

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Reporting back after roughly 12 hours of letting it transcode video under the new setting. It has not crashed, which it most likely would have otherwise. It also solved my mini problem that the server got too loud when working. The noise now is acceptable. Am I assuming correctly that I could do the same but with a lower CPU speed if I wanted less noise and would be willing to accept lower performance? But yes, my problem seems solved, this is amazing. Thanks all! I will report back how the server did after a few days of working.
  2. Trying this and will report back, thank you.
  3. Setup: Helios64 with Armbian 20.08.8 Buster with Linux 4.4.213-rk3399. Will change to Linux 5.8 soon though. 5 x 8 TB drives. Not using battery. I’ve had this issue ever since beginning to use my Helios. It first happened when I tried building a RAID with OpenMediaVault: It would crash and reboot while building. Sometimes after only 10 minutes, sometimes after 8+ hours of working. The same is true for video transcoding nowadays: it will sometimes crash after a little while, sometimes after a few consecutive hours of working, but it will never be able to work much longer than 12 hou
  4. I'm getting a blank terminal window when running the command to connect to the console: $ screen /dev/tty.usbserial-XXXXXXXX 1500000 -L Of course I did input the correct usbserial number that shows up in the /dev/ directory. The very first time the terminal window displayed a lot of noise with seemingly random characters. I killed the window and re-opened, and now whenever I re-open it, the terminal window is just empty. I've restarted the helios twice already while connected in the terminal, but still nothing. Not sure where the error could be. EDIT: Forgot to s