Maggi0r

Members
  • Posts

    66
  • Joined

  • Last visited

About Maggi0r

  • Birthday 04/22/1981

Converted

  • Gender
    Male

Recent Profile Visitors

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

Maggi0r's Achievements

Rookie

Rookie (2/14)

2

Reputation

  1. Hallo ihr lieben, ich habe mal eine generelle Frage welche Sensoren fragt das Dynamix Auto Fan Plugin ab. Bei Low temperature threshold (°C) und dem Gegenstück High.... Denn die Festplatten Temperatur ist mir nämlich egal da ich nur SSD verwende und die im bei 35 Grad ca liegen mir geht es hier eher um die Temperatur im Gehäuse und CPU somit sollen die Gehäuselüfter hoch gefahren werden wenn eine bestimmte Temperatur überschritten wird. LG Maggi0r
  2. Ich habe nichts gefunden in den Syslogs ich häng diese mal an. Danke für die Hilfe, tower-syslog-20210728-1243.zip
  3. Nein kein HP Server Eigenbau es ging ja bis vor einigen Tagen ohne Probleme.
  4. Hello you unraidlers, I am faced with a problem again I have not been able to create a Linux VM for a few days. I've tried Debian, Ubuntu, Mint, DeepIn, as soon as I start the VM it goes into a boot loop. I get to see the typical selection menu in Linux, no matter what I select there, it always restarts the VM. I noticed the following, when I reboot the VM I get an error message. "Firmwar Bug: the Bios has corrupted hw-PMU resources (MSR c0010200 is 530076). It seems to work for Windows VMs. Hope you have a tip why that could be. Greets Maggi0r
  5. Hallo ihr unraidler, ich stehe mal wieder vor einem Problem ich kann seit einigen Tagen keine Linux VM mehr erstellen. Ich habe es mit Debian, Ubuntu, Mint, DeepIn versucht, sobald ich die VM starte fällt er in eine Bootschleife. Ich bekomme das typisch Auswahlmenü bei Linux zu sehen egal was ich dort auswähle er startet die VM immer wieder neu. Mir ist folgendes aufgefallen, beim reboot der VM bekomme ich eine Fehlermeldung zu sehen. "Firmwar Bug: the Bios has corrupted hw-PMU resources (MSR c0010200 is 530076). Bei Windows VMs scheint es zu funktionieren. Hoffe ihr habt da einen Tipp woran das liegen kann. LG
  6. Hello, Ichjj is faced with a problem again and can't find a solution. I have installed the Unraid API on my main Unraid server. At the beginning I still had the functions that I could control the array etc. there, also the start of the VMs and Docker, but now nothing works anymore. Information is also no longer displayed. I hope you can help me along with that. Greetings Maggi
  7. Oh thank you that was a quick answer. Is there somewhere an overview with commands for the console. Best regards
  8. Hello, I have another request. I would like to restart my VMs from the console if possible. best regards Maggi0r
  9. Yes, thanks, I thought so. I suspect that I will probably not get it with the Sundtek piece. I will probably get one from the main eye soon so that it works. Anyone else has an idea with it. Regards Maggi
  10. Yes, I think so. But somehow doesn't help. I think it is somehow related to the stick even though the driver is loaded. As you can see in DVBUnraid but somehow it is not handed over correctly. Regards Maggi
  11. Yes, I think so too. I don't know why he still complains that he can't open it. Although all rights now fit. As I said what surprised me is that the TVH plugin works. I suspect it's somehow related to the transfer of rights or something. Because the plugin seems to access the / dev / dvb folder directly. As I said, the DVBUnraid plugin finds everything except the adapter itself. Regards Maggi
  12. I have now done it as you said. Before that I stopped the container. on unraid chown -R nobody: users /dev/dvb chmod -R 777 /dev/dvb These are the rights on the container. root @ 2e48b5c5004d: / dev / dvb # ls -al /dev/dvb totally 0 drwxr-xr-x 3 root root 60 Jun 3 12:49. drwxr-xr-x 6 root root 360 Jun 3 12:49 .. drwxr-xr-x 2 root root 100 Jun 3 12:49 adapter0 ls -al /dev/dvb/adapter0 totally 0 drwxr-xr-x 2 root root 100 Jun 3 12:49. drwxr-xr-x 3 root root 60 Jun 3 12:49 .. crwxrwxrwx 1 abc abc 212, 1 Jun 3 12:49 demux0 crwxrwxrwx 1 abc abc 212, 2 Jun 3 12:49 dvr0 crwxrwxrwx 1 abc abc 212, 0 Jun 3 12:49 frontend0 However, I still get the error in the LOG. Regards Maggi
  13. So I think I'm kind of too stupid for that. Here again what I did now. on the unraid servver chown -R nobody: users /dev/dvb chmod -R 777 /dev/dvb This is how it looks now. On the unraid. root @ Tower: / dev / dvb # ls -al /dev/dvb totally 0 drwxrwxrwx 3 nobody users 60 Jun 3 11:10 ./ drwxr-xr-x 17 root root 3320 Jun 3 12:07 ../ drwxrwxrwx 2 nobody users 100 Jun 3 11:10 adapter0 / root @ tower: / dev / dvb # on the TVHDocker chown -R abc: abc /dev/dvb chmod -R 777 /dev/dvb After restarting the container, the rights are set to root again. But unfortunately it doesn't help the adapter is found. Regards Maggi
  14. Ok so that means I have to chown -R abc: abc / dev / dvb or chown -R nobody: users / dev / dvb. If I run chown -R abc: abc / dev / dvb on unraid, I get chown: invalid user: 'abc: abc'. Regards Maggi
  15. If I don't install the driver. If the DVB stick is not found in the TVH plugin. I also have to have installed the DVB plugin otherwise the DVB driver is not recognized by the TVH plugin. root@2e48b5c5004d:/# ls -al /dev/dvb total 0 drwxr-xr-x 3 root root 60 Jun 3 11:36 . drwxr-xr-x 6 root root 360 Jun 3 11:36 .. drwxr-xr-x 2 root root 100 Jun 3 11:36 adapter0 root@2e48b5c5004d:/# These are the authorizations when I reinstall the TVH Docker. Regards Maggi