no space at the system partition of OMV / Kein Speicherplatz auf der Systempartition verfügbar

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • no space at the system partition of OMV / Kein Speicherplatz auf der Systempartition verfügbar

      Hello,
      I am new here at this forum and I am from german. I use the OMV since 2 years. I build a PC with 1 SSD (120 GB) for the OMV System and 4 HDD (each 2TB) for the Data.
      Now I have the problem, that I can not connect over firefox to my OMV. Also the data drives at my network are not available. I can just connect via Putty to the OMV Server.

      There I have looked and see that the /dev/sde1 is full. But 100GB full 8o ? I thought OMV did not need many space. A lot of people use it on a raspberry pi with not so much space...

      Hope someone can help me. I am not a goog Linux user. So I need detail helps how I can get my data back or better how I can OMV System back to run without loosing data.

      In the attachment you will find some pictures of the used datas:




      Now again in German: :D

      Ich benutze seit ca. 2 Jahren OMV. Ich habe mir einen PC mit einer SSD(120GB) für das OMV System und 4 HDD (je 2TB) für die Daten zusammengebaut.
      Jetzt habe ich das Problem, dass ich über Firefox nicht mehr auf die OMV Oberfläche komme. Auch über die Netzlaufwerke komm ich nicht mehr drauf. Nur über Putty kann ich mich noch verbinden.

      Über Putty habe ich mal geschaut, und gesehen dass die /dev/sde1 voll ist. Also 100GB belegt. Kann das aber sein 8o ? Ich dachte, dass OMV nicht viel Speicherplatz benötigt. Einige Leute benutzen OMV sogar auf nem raspberry pi...

      Ich hoffe jemand kann mir helfen. Ich bin kein guter Linux Benutzer. Also brauche ich detailierte Hilfe, wie ich meine Daten zurück bekomme (das was auf den 2TB platten drauf ist). Oder noch besser, wie ich OMV reparieren kann, dass es wieder läuft.

      Im Anhang findest du einige Bilder von dem verbrauchten Speicherplatz.
      Gruß
      odwquad
    • You have to look at the files to see what is filling them.
      But I am not sure how to view such larges files.
      Maybe nano or less.
      The files with .gz at the end are compressed files. So use syslog and kern.log for the analysis.
      Odroid HC2 - armbian - Seagate ST4000DM004 - OMV4.x
      Asrock Q1900DC-ITX - 16GB - 2x Seagate ST3000VN000 - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!:
    • macom wrote:

      You have to look at the files to see what is filling them.
      But I am not sure how to view such larges files.
      Maybe nano or less.
      The files with .gz at the end are compressed files. So use syslog and kern.log for the analysis.
      okay thank you maron.
      I have also no idea. maybe I can delete this files? If this are just log data, maybe the system do not need them?
      Gruß
      odwquad
    • odwquad wrote:

      If this are just log data, maybe the system do not need them?
      If kern.log and syslog are spammed at this rate there's something seriously wrong. These log files are there to be read/parsed and not ignored. So you better activate SSH login, then login via SSH (to be able to do copy&paste and stop posting screenshots but TEXT that is readable) and post the output from

      Source Code

      1. tail -n 1000 /var/log/syslog | curl -F 'f:1=<-' ix.io
    • tkaiser wrote:

      odwquad wrote:

      If this are just log data, maybe the system do not need them?
      If kern.log and syslog are spammed at this rate there's something seriously wrong. These log files are there to be read/parsed and not ignored. So you better activate SSH login, then login via SSH (to be able to do copy&paste and stop posting screenshots but TEXT that is readable) and post the output from

      Source Code

      1. tail -n 1000 /var/log/syslog | curl -F 'f:1=<-' ix.io
      Thanks for helping tKaiser.
      Sorry I did not know, that I could copy paste the text from putty to this forum, so I made a screenshot xD

      Your code did not work. "curl" are unknow. So I try without curl.
      Now I see about 54 pages of different notes of the syslog data.

      but the most are the same. I post just a view, and hope you can tell me, what is wrong on my system:

      Source Code

      1. Jan 25 18:15:02 homeserverga kernel: [ 247.169465] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      2. Jan 25 18:15:02 homeserverga kernel: [ 247.170740] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffffa0b0654d7550), AE_NOT_FOUND (20160831/psparse-543)
      3. Jan 25 18:15:02 homeserverga kernel: [ 247.172103] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      4. Jan 25 18:15:02 homeserverga kernel: [ 247.176451] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      5. Jan 25 18:15:02 homeserverga kernel: [ 247.177718] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffffa0b0654d7550), AE_NOT_FOUND (20160831/psparse-543)
      6. Jan 25 18:15:02 homeserverga kernel: [ 247.179398] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      7. Jan 25 18:15:02 homeserverga kernel: [ 247.182085] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      8. Jan 25 18:15:02 homeserverga kernel: [ 247.183342] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffffa0b0654d7550), AE_NOT_FOUND (20160831/psparse-543)
      9. Jan 25 18:15:02 homeserverga kernel: [ 247.184669] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      10. Jan 25 18:15:02 homeserverga kernel: [ 247.187593] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      11. Jan 25 18:15:02 homeserverga kernel: [ 247.188830] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffffa0b0654d7550), AE_NOT_FOUND (20160831/psparse-543)
      12. ...
      13. ...
      14. Jan 27 16:15:01 homeserverga kernel: [ 241.795797] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff96bde54d70a0), AE_NOT_FOUND (20160831/psparse-543)
      15. Jan 27 16:15:01 homeserverga kernel: [ 241.797036] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      16. Jan 27 16:15:01 homeserverga kernel: [ 241.799343] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      17. Jan 27 16:15:01 homeserverga kernel: [ 241.800574] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff96bde54d70a0), AE_NOT_FOUND (20160831/psparse-543)
      18. Jan 27 16:15:01 homeserverga kernel: [ 241.801800] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      19. Jan 27 16:15:01 homeserverga kernel: [ 241.804121] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      20. Jan 27 16:15:01 homeserverga kernel: [ 241.805341] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff96bde54d70a0), AE_NOT_FOUND (20160831/psparse-543)
      21. Jan 27 16:15:01 homeserverga kernel: [ 241.806575] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      22. Jan 27 16:15:01 homeserverga kernel: [ 241.808888] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      23. Jan 27 16:15:01 homeserverga kernel: [ 241.810108] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff96bde54d70a0), AE_NOT_FOUND (20160831/psparse-543)
      24. Jan 27 16:15:01 homeserverga kernel: [ 241.811352] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      Display All

      Source Code: kern.log

      1. Jan 25 18:15:01 homeserverga kernel: [ 247.115608] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      2. Jan 25 18:15:01 homeserverga kernel: [ 247.117975] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      3. Jan 25 18:15:01 homeserverga kernel: [ 247.119228] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffffa0b0654d7550), AE_NOT_FOUND (20160831/psparse-543)
      4. Jan 25 18:15:01 homeserverga kernel: [ 247.120511] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      5. Jan 25 18:15:01 homeserverga kernel: [ 247.122941] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      6. Jan 25 18:15:01 homeserverga kernel: [ 247.124176] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffffa0b0654d7550), AE_NOT_FOUND (20160831/psparse-543)
      7. Jan 25 18:15:01 homeserverga kernel: [ 247.125477] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      8. Jan 25 18:15:01 homeserverga kernel: [ 247.128018] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      9. Jan 25 18:15:01 homeserverga kernel: [ 247.129259] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffffa0b0654d7550), AE_NOT_FOUND (20160831/psparse-543)
      10. Jan 25 18:15:01 homeserverga kernel: [ 247.130496] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      11. Jan 25 18:15:01 homeserverga kernel: [ 247.133044] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      12. Jan 25 18:15:01 homeserverga kernel: [ 247.134331] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffffa0b0654d7550), AE_NOT_FOUND (20160831/psparse-543)
      13. Jan 25 18:15:01 homeserverga kernel: [ 247.136220] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      14. ...
      15. ...
      16. Jan 27 16:15:01 homeserverga kernel: [ 241.787478] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      17. Jan 27 16:15:01 homeserverga kernel: [ 241.789813] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      18. Jan 27 16:15:01 homeserverga kernel: [ 241.791027] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff96bde54d70a0), AE_NOT_FOUND (20160831/psparse-543)
      19. Jan 27 16:15:01 homeserverga kernel: [ 241.792267] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      20. Jan 27 16:15:01 homeserverga kernel: [ 241.794572] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      21. Jan 27 16:15:01 homeserverga kernel: [ 241.795797] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff96bde54d70a0), AE_NOT_FOUND (20160831/psparse-543)
      22. Jan 27 16:15:01 homeserverga kernel: [ 241.797036] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      23. Jan 27 16:15:01 homeserverga kernel: [ 241.799343] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      24. Jan 27 16:15:01 homeserverga kernel: [ 241.800574] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff96bde54d70a0), AE_NOT_FOUND (20160831/psparse-543)
      25. Jan 27 16:15:01 homeserverga kernel: [ 241.801800] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      26. Jan 27 16:15:01 homeserverga kernel: [ 241.804121] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      27. Jan 27 16:15:01 homeserverga kernel: [ 241.805341] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff96bde54d70a0), AE_NOT_FOUND (20160831/psparse-543)
      28. Jan 27 16:15:01 homeserverga kernel: [ 241.806575] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      29. Jan 27 16:15:01 homeserverga kernel: [ 241.808888] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      30. Jan 27 16:15:01 homeserverga kernel: [ 241.810108] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff96bde54d70a0), AE_NOT_FOUND (20160831/psparse-543)
      31. Jan 27 16:15:01 homeserverga kernel: [ 241.811352] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      Display All
      Gruß
      odwquad
    • Found this which seems to be related to your issue:

      superuser.com/questions/111799…-gpe-method-floods-syslog

      For others that might know more details: what is your hardware and post the output of uname -a as the issue might be fixed with a newer kernel version, so let's see which kernel you are running.

      BTW you can install curl with apt install curl
      Odroid HC2 - armbian - Seagate ST4000DM004 - OMV4.x
      Asrock Q1900DC-ITX - 16GB - 2x Seagate ST3000VN000 - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!:
    • I would delete the .gz files to get space on the drive. Seems you have enough messages left even if you delete the old ones ;)
      Then I would update the system with omv-update and then restart the server and check if the logs are still flushed.
      Odroid HC2 - armbian - Seagate ST4000DM004 - OMV4.x
      Asrock Q1900DC-ITX - 16GB - 2x Seagate ST3000VN000 - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!:
    • odwquad wrote:

      delete the files with sudo echo "" /var/log/syslog right? This I found via google^^.
      I would use rm <filename> and only delete the .gz files. For example rm syslog.2.gz
      Odroid HC2 - armbian - Seagate ST4000DM004 - OMV4.x
      Asrock Q1900DC-ITX - 16GB - 2x Seagate ST3000VN000 - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!:
    • macom wrote:

      With tail -f /var/log/syslog you can see the content of syslog in realtime. So you can easily see if the syslog is still flodded.

      To finsh tail press Ctrl-c
      I try this, and yes it still flooded:

      Source Code

      1. Jan 27 17:21:27 homeserverga kernel: [ 1330.875111] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      2. Jan 27 17:21:27 homeserverga kernel: [ 1330.877408] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      3. Jan 27 17:21:27 homeserverga kernel: [ 1330.878618] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff93a9654d7d70), AE_NOT_FOUND (20160831/psparse-543)
      4. Jan 27 17:21:27 homeserverga kernel: [ 1330.879841] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      5. Jan 27 17:21:27 homeserverga kernel: [ 1330.882133] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      6. Jan 27 17:21:27 homeserverga kernel: [ 1330.883351] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff93a9654d7d70), AE_NOT_FOUND (20160831/psparse-543)
      7. Jan 27 17:21:27 homeserverga kernel: [ 1330.884598] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      8. Jan 27 17:21:27 homeserverga kernel: [ 1330.886967] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      9. Jan 27 17:21:27 homeserverga kernel: [ 1330.888189] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff93a9654d7d70), AE_NOT_FOUND (20160831/psparse-543)
      10. Jan 27 17:21:27 homeserverga kernel: [ 1330.889438] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      11. Jan 27 17:21:27 homeserverga kernel: [ 1330.891816] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      12. Jan 27 17:21:27 homeserverga kernel: [ 1330.893034] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff93a9654d7d70), AE_NOT_FOUND (20160831/psparse-543)
      13. Jan 27 17:21:27 homeserverga kernel: [ 1330.894277] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      14. Jan 27 17:21:27 homeserverga kernel: [ 1330.896641] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      15. Jan 27 17:21:27 homeserverga kernel: [ 1330.897854] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff93a9654d7d70), AE_NOT_FOUND (20160831/psparse-543)
      16. Jan 27 17:21:27 homeserverga kernel: [ 1330.899072] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      17. Jan 27 17:21:27 homeserverga kernel: [ 1330.901379] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      18. Jan 27 17:21:27 homeserverga kernel: [ 1330.902591] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff93a9654d7d70), AE_NOT_FOUND (20160831/psparse-543)
      19. Jan 27 17:21:27 homeserverga kernel: [ 1330.903820] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160831/evgpe-646)
      20. Jan 27 17:21:27 homeserverga kernel: [ 1330.906122] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
      21. Jan 27 17:21:27 homeserverga kernel: [ 1330.907335] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff93a9654d7d70), AE_NOT_FOUND (20160831/psparse-543)
      Display All
      Gruß
      odwquad
    • If the update does not solve the flodding, try the workaround. To edit the /etc/rc.local use the command:

      nano /etc/rc.local

      Nano is a small text editor. You can finish nano with Ctrl-x. Then nano will ask you if you want to save the file.
      Odroid HC2 - armbian - Seagate ST4000DM004 - OMV4.x
      Asrock Q1900DC-ITX - 16GB - 2x Seagate ST3000VN000 - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!: