Autor Thema: Problem mit dem laden von Modulen  (Gelesen 130 mal)

0 Mitglieder und 1 Gast betrachten dieses Thema.

Offline Lehmeier

  • Vollwertiges Mitglied
  • ***
  • Beiträge: 116
  • Desktop: KDE
  • Prozessor: 2.5 GHZ Dual Core
  • Skill: Anfänger
  • Zweig: Stable
Problem mit dem laden von Modulen
« am: 12. Januar 2018, 12:06:31 »
Hallo!

Ich habe schon seit einiger Zeit ein Problem damit das die Module von VM-VirtualBox beim Start nicht geladen werden.
Nun kam ich mal dazu mit dem "Systemd System Manager" mal nachzusehen und bekomme nun das Bild dass anscheinend selbst der systemd-modules-load.service Probleme hat.
Wie bekomme ich alles wieder zum laufen?

MfG R.Lehmeier

Offline gosia

  • Held Mitglied
  • *****
  • Beiträge: 1077
  • Dankeschön: 186 mal
  • Desktop: Openbox + xfce
  • Grafikkarte: Intel HD 4000
  • Grafikkartentreiber: i915 (free)
  • Kernel: 4.9 Artix
  • Prozessor: Intel Core i5-3210M
  • Skill: Durchschnitt
  • Zweig: stable
Re: Problem mit dem laden von Modulen
« Antwort #1 am: 12. Januar 2018, 16:08:00 »
Hallo R. Lehmeier
das ist leider noch zu wenig aussagekräftig. Poste mal die Ausgabe von
systemctl status systemd-modules-load.serviceund die Ausgabe, wenn Du systemd-modules-load von Hand startest, also mit
sudo systemctl start systemd-modules-load.service
Viele Grüße gosia

Offline Lehmeier

  • Vollwertiges Mitglied
  • ***
  • Beiträge: 116
  • Desktop: KDE
  • Prozessor: 2.5 GHZ Dual Core
  • Skill: Anfänger
  • Zweig: Stable
Re: Problem mit dem laden von Modulen
« Antwort #2 am: 12. Januar 2018, 21:54:02 »
in_001 ~]$ sudo systemctl status systemd-modules-load.service
...
lines 1--1...skipping...
● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2018-01-12 21:34:59 CET; 16min ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 471 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
 Main PID: 471 (code=exited, status=1/FAILURE)

Jan 12 21:34:59 Lin_001 systemd-modules-load[471]: Failed to insert 'vboxsf': No such device
Jan 12 21:34:59 Lin_001 systemd-modules-load[471]: Failed to insert 'vboxguest': No such device
Jan 12 21:34:59 Lin_001 systemd-modules-load[471]: Failed to insert 'vboxsf': No such device
Jan 12 21:34:59 Lin_001 systemd-modules-load[471]: Failed to insert 'vboxguest': No such device
Jan 12 21:34:59 Lin_001 systemd-modules-load[471]: Failed to insert 'vboxsf': No such device
Jan 12 21:34:59 Lin_001 systemd-modules-load[471]: Failed to insert 'vboxguest': No such device
Jan 12 21:34:59 Lin_001 systemd-modules-load[471]: Failed to insert 'vboxsf': No such device
Jan 12 21:34:59 Lin_001 systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Jan 12 21:34:59 Lin_001 systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Jan 12 21:34:59 Lin_001 systemd[1]: Failed to start Load Kernel Modules.


[ralf@Lin_001 ~]$ sudo systemctl start systemd-modules-load.service

Job for systemd-modules-load.service failed because the control process exited with error code.
See "systemctl status systemd-modules-load.service" and "journalctl -xe" for details.

Offline gosia

  • Held Mitglied
  • *****
  • Beiträge: 1077
  • Dankeschön: 186 mal
  • Desktop: Openbox + xfce
  • Grafikkarte: Intel HD 4000
  • Grafikkartentreiber: i915 (free)
  • Kernel: 4.9 Artix
  • Prozessor: Intel Core i5-3210M
  • Skill: Durchschnitt
  • Zweig: stable
Re: Problem mit dem laden von Modulen
« Antwort #3 am: 12. Januar 2018, 23:19:03 »
Hallo R. Lehmeier,
ich nehme an, dein Manjaro ist Host, d.h. Manjaro läuft als "Hauptsystem" und in deiner Virtualbox läuft was anderes, Windows oder eine andere Linux-Distri.
Wenn dem so ist, dann sieh mal mit
pacman -Qs virtualboxnach, ob irgendwas mit "guest" im Namen vorkommt, z.B. virtualbox-guest-dkms, virtualbox-guest-utils.
Wenn ja, deinstalliere  virtualbox-guest-dkms und  virtualbox-guest-utils.
https://bbs.archlinux.org/viewtopic.php?id=210268

Viele Grüße gosia

Offline Lehmeier

  • Vollwertiges Mitglied
  • ***
  • Beiträge: 116
  • Desktop: KDE
  • Prozessor: 2.5 GHZ Dual Core
  • Skill: Anfänger
  • Zweig: Stable
Re: Problem mit dem laden von Modulen
« Antwort #4 am: 13. Januar 2018, 12:54:09 »
Hallo R. Lehmeier,
ich nehme an, dein Manjaro ist Host, d.h. Manjaro läuft als "Hauptsystem" und in deiner Virtualbox läuft was anderes, Windows oder eine andere Linux-Distri.

Richtig, Windows läuft in der Virtualbox

Wenn dem so ist, dann sieh mal mit
pacman -Qs virtualboxnach, ob irgendwas mit "guest" im Namen vorkommt, z.B. virtualbox-guest-dkms, virtualbox-guest-utils.
Wenn ja, deinstalliere  virtualbox-guest-dkms und  virtualbox-guest-utils.
https://bbs.archlinux.org/viewtopic.php?id=210268

Habe ich.
Wozu waren virtualbox-guest-dkms und  virtualbox-guest-utils denn da?
Ich dachte die wären dazu nötig das Gastsystem laufen zu lassen.

So sehen die Ausgabe jetzt aus:
systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2018-01-13 12:43:01 CET; 4min 10s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 1562 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
 Main PID: 1562 (code=exited, status=1/FAILURE)

Jan 13 12:43:01 Lin_001 systemd[1]: Starting Load Kernel Modules...
Jan 13 12:43:01 Lin_001 systemd-modules-load[1562]: Failed to insert 'vboxguest': No such device
Jan 13 12:43:01 Lin_001 systemd-modules-load[1562]: Failed to insert 'vboxsf': No such device
Jan 13 12:43:01 Lin_001 systemd-modules-load[1562]: Failed to insert 'vboxguest': No such device
Jan 13 12:43:01 Lin_001 systemd-modules-load[1562]: Failed to insert 'vboxsf': No such device
Jan 13 12:43:01 Lin_001 systemd-modules-load[1562]: Failed to insert 'vboxguest': No such device
Jan 13 12:43:01 Lin_001 systemd-modules-load[1562]: Failed to insert 'vboxsf': No such device
Jan 13 12:43:01 Lin_001 systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Jan 13 12:43:01 Lin_001 systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Jan 13 12:43:01 Lin_001 systemd[1]: Failed to start Load Kernel Modules.
[ralf@Lin_001 ~]$ sudo systemctl start systemd-modules-load.service
Job for systemd-modules-load.service failed because the control process exited with error code.
See "systemctl status systemd-modules-load.service" and "journalctl -xe" for details.
[ralf@Lin_001 ~]$

Einen Screenshot habe ich auch noch gemacht - falls benötigt

Offline gosia

  • Held Mitglied
  • *****
  • Beiträge: 1077
  • Dankeschön: 186 mal
  • Desktop: Openbox + xfce
  • Grafikkarte: Intel HD 4000
  • Grafikkartentreiber: i915 (free)
  • Kernel: 4.9 Artix
  • Prozessor: Intel Core i5-3210M
  • Skill: Durchschnitt
  • Zweig: stable
Re: Problem mit dem laden von Modulen
« Antwort #5 am: 13. Januar 2018, 17:37:35 »
Hallo  R. Lehmeier,
war ja wohl ein Schlag ins Wasser, sieht ja genauso aus wie vorher  >:D
Poste mal die Ausgabe von
sudo modprobe vboxdrvAber ich bin so ziemlich am Ende meiner bescheidenen Weisheit, zumal ich schon lange kein systemd mehr benutze.
Für meine Virtualbox habe ich nur diese Pakete installiert:
  • virtualbox
  • linuxXY-virtualbox-host-modules (XY = meine Kernelversion, bei mir 49)
  • virtualbox-guest-iso (wohl nicht unbedingt notwendig, aber hilfreich, z.B. für gemeinsame Ordner, Zwischenablage u.ä.)

Viele Grüße gosia

Offline Lehmeier

  • Vollwertiges Mitglied
  • ***
  • Beiträge: 116
  • Desktop: KDE
  • Prozessor: 2.5 GHZ Dual Core
  • Skill: Anfänger
  • Zweig: Stable
Re: Problem mit dem laden von Modulen
« Antwort #6 am: 13. Januar 2018, 18:06:27 »
Hier die gewünschte Ausgabe :

[ralf@Lin_001 ~]$ sudo modprobe vboxdrv
[sudo] Passwort für ralf:
[ralf@Lin_001 ~]$

Wenn ich es richtig gesehen habe gibt es beim starten nur noch die Meldung das  :Jan 13 17:40:20 Lin_001 systemd[1]: Failed to start Load Kernel Modules.

Warum also werden diese Kernel module nicht geladen ?

Ich habe mal versucht im Bootlog etwas zu finden aber es kam nur dieses :

[ralf@Lin_001 ~]$ sudo journalctl -b
[sudo] Passwort für ralf:
-- Logs begin at Sun 2016-11-20 20:10:15 CET, end at Sat 2018-01-13 17:57:41 CET. --
Jan 13 17:40:10 Lin_001 kernel: Linux version 4.14.11-3-MANJARO (builduser@manjaro) (gcc version 7.2.1 20171128 (GCC)) #1 SMP PREEMPT Thu Jan 4 13:28:20 UTC 2018
Jan 13 17:40:10 Lin_001 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.14-x86_64 root=UUID=5b86c428-6cea-47ef-a6e0-aad27954ccda rw quiet splash resume=UUID=fc711a68-15f7-436e-8955-f
Jan 13 17:40:10 Lin_001 kernel: x86/fpu: x87 FPU will use FXSAVE
Jan 13 17:40:10 Lin_001 kernel: e820: BIOS-provided physical RAM map:
Jan 13 17:40:10 Lin_001 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
Jan 13 17:40:10 Lin_001 kernel: BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
Jan 13 17:40:10 Lin_001 kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000bfe5abff] usable
Jan 13 17:40:10 Lin_001 kernel: BIOS-e820: [mem 0x00000000bfe5ac00-0x00000000bfe5ebff] ACPI NVS
Jan 13 17:40:10 Lin_001 kernel: BIOS-e820: [mem 0x00000000bfe5ec00-0x00000000bfe60bff] ACPI data
Jan 13 17:40:10 Lin_001 kernel: BIOS-e820: [mem 0x00000000bfe60c00-0x00000000bfffffff] reserved
Jan 13 17:40:10 Lin_001 kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Jan 13 17:40:10 Lin_001 kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fed003ff] reserved
Jan 13 17:40:10 Lin_001 kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed9ffff] reserved
Jan 13 17:40:10 Lin_001 kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000feefffff] reserved
Jan 13 17:40:10 Lin_001 kernel: BIOS-e820: [mem 0x00000000ffb00000-0x00000000ffffffff] reserved                                                                                       
Jan 13 17:40:10 Lin_001 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000013bffffff] usable                                                                                         
Jan 13 17:40:10 Lin_001 kernel: NX (Execute Disable) protection: active                                                                                                               
Jan 13 17:40:10 Lin_001 kernel: random: fast init done                                                                                                                                 
Jan 13 17:40:10 Lin_001 kernel: SMBIOS 2.5 present.                                                                                                                                   
Jan 13 17:40:10 Lin_001 kernel: DMI: Dell Inc. OptiPlex 360                 /0T656F, BIOS A07 06/18/2012                                                                               
Jan 13 17:40:10 Lin_001 kernel: tsc: Fast TSC calibration using PIT                                                                                                                   
Jan 13 17:40:10 Lin_001 kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved                                                                                           
Jan 13 17:40:10 Lin_001 kernel: e820: remove [mem 0x000a0000-0x000fffff] usable                                                                                                       
Jan 13 17:40:10 Lin_001 kernel: e820: last_pfn = 0x13c000 max_arch_pfn = 0x400000000                                                                                                   
Jan 13 17:40:10 Lin_001 kernel: MTRR default type: uncachable                                                                                                                         
Jan 13 17:40:10 Lin_001 kernel: MTRR fixed ranges enabled:                                                                                                                             
Jan 13 17:40:10 Lin_001 kernel:   00000-9FFFF write-back                                                                                                                               
Jan 13 17:40:10 Lin_001 kernel:   A0000-BFFFF uncachable                                                                                                                               
Jan 13 17:40:10 Lin_001 kernel:   C0000-D3FFF write-protect                                                                                                                           
Jan 13 17:40:10 Lin_001 kernel:   D4000-EFFFF uncachable                                                                                                                               
Jan 13 17:40:10 Lin_001 kernel:   F0000-FFFFF write-protect                                                                                                                           
Jan 13 17:40:10 Lin_001 kernel: MTRR variable ranges enabled:                                                                                                                         
Jan 13 17:40:10 Lin_001 kernel:   0 base 000000000 mask 000000000 write-back                                                                                                           
Jan 13 17:40:10 Lin_001 kernel:   1 base 0BFF00000 mask FFFF00000 uncachable                                                                                                           
Jan 13 17:40:10 Lin_001 kernel:   2 base 0C0000000 mask FC0000000 uncachable                                                                                                           
Jan 13 17:40:10 Lin_001 kernel:   3 disabled                                                                                                                                           
Jan 13 17:40:10 Lin_001 kernel:   4 disabled                                                                                                                                           
Jan 13 17:40:10 Lin_001 kernel:   5 disabled                                                                                                                                           
Jan 13 17:40:10 Lin_001 kernel:   6 disabled                                                                                                                                           
Jan 13 17:40:10 Lin_001 kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT                                                                                           
Jan 13 17:40:10 Lin_001 kernel: e820: update [mem 0xbff00000-0xffffffff] usable ==> reserved                                                                                           
Jan 13 17:40:10 Lin_001 kernel: e820: last_pfn = 0xbfe5a max_arch_pfn = 0x400000000                                                                                                   
Jan 13 17:40:10 Lin_001 kernel: found SMP MP-table at [mem 0x000fe710-0x000fe71f] mapped at [ffffffffff200710]
Jan 13 17:40:10 Lin_001 kernel: Scanning 1 areas for low memory corruption
Jan 13 17:40:10 Lin_001 kernel: Base memory trampoline at [ffff8d8fc0099000] 99000 size 24576
Jan 13 17:40:10 Lin_001 kernel: BRK [0xad635000, 0xad635fff] PGTABLE
Jan 13 17:40:10 Lin_001 kernel: BRK [0xad636000, 0xad636fff] PGTABLE
Jan 13 17:40:10 Lin_001 kernel: BRK [0xad637000, 0xad637fff] PGTABLE
Jan 13 17:40:10 Lin_001 kernel: BRK [0xad638000, 0xad638fff] PGTABLE
Jan 13 17:40:10 Lin_001 kernel: BRK [0xad639000, 0xad639fff] PGTABLE
Jan 13 17:40:10 Lin_001 kernel: RAMDISK: [mem 0x36e77000-0x37732fff]
Jan 13 17:40:10 Lin_001 kernel: ACPI: Early table checksum verification disabled
Jan 13 17:40:10 Lin_001 kernel: ACPI: RSDP 0x00000000000FEBF0 000024 (v02 DELL  )
Jan 13 17:40:10 Lin_001 kernel: ACPI: XSDT 0x00000000000FD0E7 00005C (v01 DELL   B9K      00000015 ASL  00000061)
Jan 13 17:40:10 Lin_001 kernel: ACPI: FACP 0x00000000000FD1FF 0000F4 (v03 DELL   B9K      00000015 ASL  00000061)
Jan 13 17:40:10 Lin_001 kernel: ACPI: DSDT 0x00000000FFF62E78 003346 (v01 DELL   dt_ex    00001000 INTL 20050624)
Jan 13 17:40:10 Lin_001 kernel: ACPI: FACS 0x00000000BFE5AC00 000040
Jan 13 17:40:10 Lin_001 kernel: ACPI: FACS 0x00000000BFE5AC00 000040
Jan 13 17:40:10 Lin_001 kernel: ACPI: SSDT 0x00000000FFF662DF 0000AC (v01 DELL   st_ex    00001000 INTL 20050624)
Jan 13 17:40:10 Lin_001 kernel: ACPI: APIC 0x00000000000FD2F3 000092 (v01 DELL   B9K      00000015 ASL  00000061)
Jan 13 17:40:10 Lin_001 kernel: ACPI: BOOT 0x00000000000FD385 000028 (v01 DELL   B9K      00000015 ASL  00000061)
Jan 13 17:40:10 Lin_001 kernel: ACPI: MCFG 0x00000000000FD3AD 00003E (v01 DELL   B9K      00000015 ASL  00000061)
Jan 13 17:40:10 Lin_001 kernel: ACPI: HPET 0x00000000000FD3EB 000038 (v01 DELL   B9K      00000015 ASL  00000061)
Jan 13 17:40:10 Lin_001 kernel: ACPI: SLIC 0x00000000000FD423 000176 (v01 DELL   B9K      00000015 ASL  00000061)
Jan 13 17:40:10 Lin_001 kernel: ACPI: Local APIC address 0xfee00000
Jan 13 17:40:10 Lin_001 kernel: No NUMA configuration found

Da dieser Versuch nichts weiter gebracht aht ahbe ich die beiden Pakete wieder eingespielt.