Reboot nach Systemupdate
Hallo, ich musste mein System OS 13.1 neu aufsetzen, weil es immer wieder neu gestartet ist. Nach der Auswahl im Grub2- Menue lief der Rechner an und bootet danach wieder neu. Ich habe die boot.log einmal beigefügt und hoffe, Ihr könnt mir sagen, was passiert ist. Gruss Bernd Trying manual resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 Invoking userspace resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 resume: libgcrypt version: 1.5.3 Trying manual resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 Invoking in-kernel resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 Waiting for device /dev/root to appear: ok fsck from util-linux 2.23.2 [/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/sda3 /dev/sda3: recovering journal /dev/sda3: clean, 398003/1313280 files, 2735743/5242880 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/root mount -o rw,acl,user_xattr -t ext4 /dev/root /root Welcome to [0;32mopenSUSE 13.1 (Bottle) (x86_64)[0m! [[32m OK [0m] Listening on /dev/initctl Compatibility Named Pipe. [[32m OK [0m] Listening on Delayed Shutdown Socket. [[32m OK [0m] Listening on LVM2 metadata daemon socket. [[32m OK [0m] Set up automount Arbitrary Executable File Formats File System Automount Point. [[32m OK [0m] Listening on Journal Socket. Starting Create list of required static device nodes for the current kernel... Starting Tell Plymouth To Write Out Runtime Data... Mounting Huge Pages File System... Starting Create dynamic rule for /dev/root link... Starting Journal Service... [[32m OK [0m] Started Journal Service. Starting Trigger Flushing of Journal to Persistent Storage... [[32m OK [0m] Listening on udev Kernel Socket. [[32m OK [0m] Listening on udev Control Socket. Starting udev Coldplug all Devices... Mounting Debug File System... Mounting POSIX Message Queue File System... Expecting device dev-disk-by\x2did-ata\x2dST2000DM001\x2d1CH164_Z1F2VS6S\x2dpart2.device... [[32m OK [0m] Created slice Root Slice. [[32m OK [0m] Created slice System Slice. Expecting device dev-disk-by\x2did-ata\x2dST2000DM001\x2d1CH164_Z1F2VS6S\x2dpart4.device... [[32m OK [0m] Reached target Unmount All Filesystems. Starting Store Sound Card State... [[32m OK [0m] Started Tell Plymouth To Write Out Runtime Data. [[32m OK [0m] Mounted Huge Pages File System. [[32m OK [0m] Mounted Debug File System. [[32m OK [0m] Mounted POSIX Message Queue File System. [[1;31mFAILED[0m] Failed to start Store Sound Card State. See 'systemctl status alsa-store.service' for details. [[32m OK [0m] Started udev Coldplug all Devices. [[32m OK [0m] Started Create list of required static device nodes for the current kernel. Starting Create static device nodes in /dev... Starting Show Plymouth Boot Screen... [[32m OK [0m] Started Trigger Flushing of Journal to Persistent Storage. [[32m OK [0m] Started Create dynamic rule for /dev/root link. [[32m OK [0m] Started Create static device nodes in /dev. Starting udev Kernel Device Manager... [[32m OK [0m] Started udev Kernel Device Manager. [[32m OK [0m] Started Show Plymouth Boot Screen. Starting Show Plymouth Reboot Screen... [[32m OK [0m] Started Show Plymouth Reboot Screen. [[32m OK [0m] Found device ST2000DM001-1CH164. [[32m OK [0m] Found device ST2000DM001-1CH164. Starting File System Check on /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part4... systemd-fsck[510]: /dev/sda4: clean, 1353/120643584 files, 20715165/482569216 blocks [[32m OK [0m] Started File System Check on /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part4. [[32m OK [0m] Reached target Shutdown. Starting /etc/init.d/halt.local Compatibility... [[32m OK [0m] Started /etc/init.d/halt.local Compatibility. [[32m OK [0m] Reached target Final Step. Starting Reboot... -- Um die Liste abzubestellen, schicken Sie eine Mail an: opensuse-de+unsubscribe@opensuse.org Um den Listen Administrator zu erreichen, schicken Sie eine Mail an: opensuse-de+owner@opensuse.org
Am 10.03.2014 14:56, schrieb Bernhard Junk:
Hallo,
ich musste mein System OS 13.1 neu aufsetzen, weil es immer wieder neu gestartet ist. Nach der Auswahl im Grub2- Menue lief der Rechner an und bootet danach wieder neu.
Ich habe die boot.log einmal beigefügt und hoffe, Ihr könnt mir sagen, was passiert ist.
Gruss Bernd
Trying manual resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 Invoking userspace resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 resume: libgcrypt version: 1.5.3 Trying manual resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 Invoking in-kernel resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 Waiting for device /dev/root to appear: ok fsck from util-linux 2.23.2 [/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/sda3 /dev/sda3: recovering journal /dev/sda3: clean, 398003/1313280 files, 2735743/5242880 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/root mount -o rw,acl,user_xattr -t ext4 /dev/root /root
Welcome to [0;32mopenSUSE 13.1 (Bottle) (x86_64)[0m!
[[32m OK [0m] Listening on /dev/initctl Compatibility Named Pipe. [[32m OK [0m] Listening on Delayed Shutdown Socket. [[32m OK [0m] Listening on LVM2 metadata daemon socket. [[32m OK [0m] Set up automount Arbitrary Executable File Formats File System Automount Point. [[32m OK [0m] Listening on Journal Socket. Starting Create list of required static device nodes for the current kernel... Starting Tell Plymouth To Write Out Runtime Data... Mounting Huge Pages File System... Starting Create dynamic rule for /dev/root link... Starting Journal Service... [[32m OK [0m] Started Journal Service. Starting Trigger Flushing of Journal to Persistent Storage... [[32m OK [0m] Listening on udev Kernel Socket. [[32m OK [0m] Listening on udev Control Socket. Starting udev Coldplug all Devices... Mounting Debug File System... Mounting POSIX Message Queue File System... Expecting device dev-disk-by\x2did-ata\x2dST2000DM001\x2d1CH164_Z1F2VS6S\x2dpart2.device... [[32m OK [0m] Created slice Root Slice. [[32m OK [0m] Created slice System Slice. Expecting device dev-disk-by\x2did-ata\x2dST2000DM001\x2d1CH164_Z1F2VS6S\x2dpart4.device... [[32m OK [0m] Reached target Unmount All Filesystems. Starting Store Sound Card State... [[32m OK [0m] Started Tell Plymouth To Write Out Runtime Data. [[32m OK [0m] Mounted Huge Pages File System. [[32m OK [0m] Mounted Debug File System. [[32m OK [0m] Mounted POSIX Message Queue File System. [[1;31mFAILED[0m] Failed to start Store Sound Card State. See 'systemctl status alsa-store.service' for details. [[32m OK [0m] Started udev Coldplug all Devices. [[32m OK [0m] Started Create list of required static device nodes for the current kernel. Starting Create static device nodes in /dev... Starting Show Plymouth Boot Screen... [[32m OK [0m] Started Trigger Flushing of Journal to Persistent Storage. [[32m OK [0m] Started Create dynamic rule for /dev/root link. [[32m OK [0m] Started Create static device nodes in /dev. Starting udev Kernel Device Manager... [[32m OK [0m] Started udev Kernel Device Manager. [[32m OK [0m] Started Show Plymouth Boot Screen. Starting Show Plymouth Reboot Screen... [[32m OK [0m] Started Show Plymouth Reboot Screen. [[32m OK [0m] Found device ST2000DM001-1CH164. [[32m OK [0m] Found device ST2000DM001-1CH164. Starting File System Check on /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part4... systemd-fsck[510]: /dev/sda4: clean, 1353/120643584 files, 20715165/482569216 blocks [[32m OK [0m] Started File System Check on /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part4. [[32m OK [0m] Reached target Shutdown. Starting /etc/init.d/halt.local Compatibility... [[32m OK [0m] Started /etc/init.d/halt.local Compatibility. [[32m OK [0m] Reached target Final Step. Starting Reboot...
Hi, ohne, dass ich mir (und Dir) das erklären könnte ... es sieht so aus, als ob "reboot" das "Ziel" (=target) des Boots sei ... würde man z.B. erhalten, wenn man als zu bootenden "runlevel" in der Systemkonfiguration "6" eingibt, aber das wirst Du ja wohl nicht gemacht haben? Man kann den runlevel auch auf der Boot-Commandline mitgeben, IMHO am Ende der Zeile einfach die Nr. des Runlevels. Also, wenn da eine "herrenlose" "6" herumgestanden hätte, würde das wohl auch passieren... cu jth -- www.teddylinx.de -- Um die Liste abzubestellen, schicken Sie eine Mail an: opensuse-de+unsubscribe@opensuse.org Um den Listen Administrator zu erreichen, schicken Sie eine Mail an: opensuse-de+owner@opensuse.org
Am 10.03.2014 15:07, schrieb Joerg Thuemmler:
Am 10.03.2014 14:56, schrieb Bernhard Junk:
Hallo,
ich musste mein System OS 13.1 neu aufsetzen, weil es immer wieder neu gestartet ist. Nach der Auswahl im Grub2- Menue lief der Rechner an und bootet danach wieder neu.
Ich habe die boot.log einmal beigefügt und hoffe, Ihr könnt mir sagen, was passiert ist.
Gruss Bernd
Trying manual resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 Invoking userspace resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 resume: libgcrypt version: 1.5.3 Trying manual resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 Invoking in-kernel resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 Waiting for device /dev/root to appear: ok fsck from util-linux 2.23.2 [/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/sda3 /dev/sda3: recovering journal /dev/sda3: clean, 398003/1313280 files, 2735743/5242880 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/root mount -o rw,acl,user_xattr -t ext4 /dev/root /root
Welcome to [0;32mopenSUSE 13.1 (Bottle) (x86_64)[0m!
[[32m OK [0m] Listening on /dev/initctl Compatibility Named Pipe. [[32m OK [0m] Listening on Delayed Shutdown Socket. [[32m OK [0m] Listening on LVM2 metadata daemon socket. [[32m OK [0m] Set up automount Arbitrary Executable File Formats File System Automount Point. [[32m OK [0m] Listening on Journal Socket. Starting Create list of required static device nodes for the current kernel... Starting Tell Plymouth To Write Out Runtime Data... Mounting Huge Pages File System... Starting Create dynamic rule for /dev/root link... Starting Journal Service... [[32m OK [0m] Started Journal Service. Starting Trigger Flushing of Journal to Persistent Storage... [[32m OK [0m] Listening on udev Kernel Socket. [[32m OK [0m] Listening on udev Control Socket. Starting udev Coldplug all Devices... Mounting Debug File System... Mounting POSIX Message Queue File System... Expecting device dev-disk-by\x2did-ata\x2dST2000DM001\x2d1CH164_Z1F2VS6S\x2dpart2.device...
[[32m OK [0m] Created slice Root Slice. [[32m OK [0m] Created slice System Slice. Expecting device dev-disk-by\x2did-ata\x2dST2000DM001\x2d1CH164_Z1F2VS6S\x2dpart4.device...
[[32m OK [0m] Reached target Unmount All Filesystems. Starting Store Sound Card State... [[32m OK [0m] Started Tell Plymouth To Write Out Runtime Data. [[32m OK [0m] Mounted Huge Pages File System. [[32m OK [0m] Mounted Debug File System. [[32m OK [0m] Mounted POSIX Message Queue File System. [[1;31mFAILED[0m] Failed to start Store Sound Card State. See 'systemctl status alsa-store.service' for details. [[32m OK [0m] Started udev Coldplug all Devices. [[32m OK [0m] Started Create list of required static device nodes for the current kernel. Starting Create static device nodes in /dev... Starting Show Plymouth Boot Screen... [[32m OK [0m] Started Trigger Flushing of Journal to Persistent Storage. [[32m OK [0m] Started Create dynamic rule for /dev/root link. [[32m OK [0m] Started Create static device nodes in /dev. Starting udev Kernel Device Manager... [[32m OK [0m] Started udev Kernel Device Manager. [[32m OK [0m] Started Show Plymouth Boot Screen. Starting Show Plymouth Reboot Screen... [[32m OK [0m] Started Show Plymouth Reboot Screen. [[32m OK [0m] Found device ST2000DM001-1CH164. [[32m OK [0m] Found device ST2000DM001-1CH164. Starting File System Check on /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part4... systemd-fsck[510]: /dev/sda4: clean, 1353/120643584 files, 20715165/482569216 blocks [[32m OK [0m] Started File System Check on /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part4. [[32m OK [0m] Reached target Shutdown. Starting /etc/init.d/halt.local Compatibility... [[32m OK [0m] Started /etc/init.d/halt.local Compatibility. [[32m OK [0m] Reached target Final Step. Starting Reboot...
Hi,
ohne, dass ich mir (und Dir) das erklären könnte ... es sieht so aus, als ob "reboot" das "Ziel" (=target) des Boots sei ... würde man z.B. erhalten, wenn man als zu bootenden "runlevel" in der Systemkonfiguration "6" eingibt, aber das wirst Du ja wohl nicht gemacht haben?
Man kann den runlevel auch auf der Boot-Commandline mitgeben, IMHO am Ende der Zeile einfach die Nr. des Runlevels. Also, wenn da eine "herrenlose" "6" herumgestanden hätte, würde das wohl auch passieren...
cu jth
Hallo Joerg, Du hast Recht! Ich kann es mir auch nicht erklären, da ich auf der Kommandozeile nichts beigefügt habe. Vor Allem war es noch so, dass auch das Rescue das Gleiche ergab. Auch bei anderen Kernels die ich im System habe passierte es. Am Tag zuvor war alles in Ordnung. Ich habe dann am Abend nur den Kernel aktualisiert. Am nächsten Morgen ging nichts mehr. Gruss Bernd -- Um die Liste abzubestellen, schicken Sie eine Mail an: opensuse-de+unsubscribe@opensuse.org Um den Listen Administrator zu erreichen, schicken Sie eine Mail an: opensuse-de+owner@opensuse.org
Hallo, On 03/10/2014 02:56 PM, Bernhard Junk wrote:
Hallo,
ich musste mein System OS 13.1 neu aufsetzen, weil es immer wieder neu gestartet ist. Nach der Auswahl im Grub2- Menue lief der Rechner an und bootet danach wieder neu.
Ich habe die boot.log einmal beigefügt und hoffe, Ihr könnt mir sagen, was passiert ist.
Gruss Bernd
Trying manual resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 Invoking userspace resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 resume: libgcrypt version: 1.5.3 Trying manual resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 Invoking in-kernel resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 Waiting for device /dev/root to appear: ok fsck from util-linux 2.23.2 [/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/sda3 /dev/sda3: recovering journal /dev/sda3: clean, 398003/1313280 files, 2735743/5242880 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/root mount -o rw,acl,user_xattr -t ext4 /dev/root /root
Welcome to [0;32mopenSUSE 13.1 (Bottle) (x86_64)[0m!
[[32m OK [0m] Listening on /dev/initctl Compatibility Named Pipe. [[32m OK [0m] Listening on Delayed Shutdown Socket. [[32m OK [0m] Listening on LVM2 metadata daemon socket. [[32m OK [0m] Set up automount Arbitrary Executable File Formats File System Automount Point. [[32m OK [0m] Listening on Journal Socket. Starting Create list of required static device nodes for the current kernel... Starting Tell Plymouth To Write Out Runtime Data... Mounting Huge Pages File System... Starting Create dynamic rule for /dev/root link... Starting Journal Service... [[32m OK [0m] Started Journal Service. Starting Trigger Flushing of Journal to Persistent Storage... [[32m OK [0m] Listening on udev Kernel Socket. [[32m OK [0m] Listening on udev Control Socket. Starting udev Coldplug all Devices... Mounting Debug File System... Mounting POSIX Message Queue File System... Expecting device dev-disk-by\x2did-ata\x2dST2000DM001\x2d1CH164_Z1F2VS6S\x2dpart2.device... [[32m OK [0m] Created slice Root Slice. [[32m OK [0m] Created slice System Slice. Expecting device dev-disk-by\x2did-ata\x2dST2000DM001\x2d1CH164_Z1F2VS6S\x2dpart4.device... [[32m OK [0m] Reached target Unmount All Filesystems. Starting Store Sound Card State... [[32m OK [0m] Started Tell Plymouth To Write Out Runtime Data. [[32m OK [0m] Mounted Huge Pages File System. [[32m OK [0m] Mounted Debug File System. [[32m OK [0m] Mounted POSIX Message Queue File System. [[1;31mFAILED[0m] Failed to start Store Sound Card State. See 'systemctl status alsa-store.service' for details. [[32m OK [0m] Started udev Coldplug all Devices. [[32m OK [0m] Started Create list of required static device nodes for the current kernel. Starting Create static device nodes in /dev... Starting Show Plymouth Boot Screen... [[32m OK [0m] Started Trigger Flushing of Journal to Persistent Storage. [[32m OK [0m] Started Create dynamic rule for /dev/root link. [[32m OK [0m] Started Create static device nodes in /dev. Starting udev Kernel Device Manager... [[32m OK [0m] Started udev Kernel Device Manager. [[32m OK [0m] Started Show Plymouth Boot Screen. Starting Show Plymouth Reboot Screen... [[32m OK [0m] Started Show Plymouth Reboot Screen. [[32m OK [0m] Found device ST2000DM001-1CH164. [[32m OK [0m] Found device ST2000DM001-1CH164. Starting File System Check on /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part4... systemd-fsck[510]: /dev/sda4: clean, 1353/120643584 files, 20715165/482569216 blocks [[32m OK [0m] Started File System Check on /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part4. [[32m OK [0m] Reached target Shutdown. Starting /etc/init.d/halt.local Compatibility... [[32m OK [0m] Started /etc/init.d/halt.local Compatibility. [[32m OK [0m] Reached target Final Step. Starting Reboot...
auf welchen runlevel verweist /etc/systemd/system/default.target ? bei mir auf runlevel 5 : /etc/systemd/system/default.target -> /lib/systemd/system/runlevel5.target Gruss, Kai -- Um die Liste abzubestellen, schicken Sie eine Mail an: opensuse-de+unsubscribe@opensuse.org Um den Listen Administrator zu erreichen, schicken Sie eine Mail an: opensuse-de+owner@opensuse.org
Am 10.03.2014 15:10, schrieb Kai Grunau:
Hallo,
On 03/10/2014 02:56 PM, Bernhard Junk wrote:
Hallo,
ich musste mein System OS 13.1 neu aufsetzen, weil es immer wieder neu gestartet ist. Nach der Auswahl im Grub2- Menue lief der Rechner an und bootet danach wieder neu.
Ich habe die boot.log einmal beigefügt und hoffe, Ihr könnt mir sagen, was passiert ist.
Gruss Bernd
Trying manual resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 Invoking userspace resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 resume: libgcrypt version: 1.5.3 Trying manual resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 Invoking in-kernel resume from /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part2 Waiting for device /dev/root to appear: ok fsck from util-linux 2.23.2 [/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/sda3 /dev/sda3: recovering journal /dev/sda3: clean, 398003/1313280 files, 2735743/5242880 blocks fsck succeeded. Mounting root device read-write. Mounting root /dev/root mount -o rw,acl,user_xattr -t ext4 /dev/root /root
Welcome to [0;32mopenSUSE 13.1 (Bottle) (x86_64)[0m!
[[32m OK [0m] Listening on /dev/initctl Compatibility Named Pipe. [[32m OK [0m] Listening on Delayed Shutdown Socket. [[32m OK [0m] Listening on LVM2 metadata daemon socket. [[32m OK [0m] Set up automount Arbitrary Executable File Formats File System Automount Point. [[32m OK [0m] Listening on Journal Socket. Starting Create list of required static device nodes for the current kernel... Starting Tell Plymouth To Write Out Runtime Data... Mounting Huge Pages File System... Starting Create dynamic rule for /dev/root link... Starting Journal Service... [[32m OK [0m] Started Journal Service. Starting Trigger Flushing of Journal to Persistent Storage... [[32m OK [0m] Listening on udev Kernel Socket. [[32m OK [0m] Listening on udev Control Socket. Starting udev Coldplug all Devices... Mounting Debug File System... Mounting POSIX Message Queue File System... Expecting device dev-disk-by\x2did-ata\x2dST2000DM001\x2d1CH164_Z1F2VS6S\x2dpart2.device... [[32m OK [0m] Created slice Root Slice. [[32m OK [0m] Created slice System Slice. Expecting device dev-disk-by\x2did-ata\x2dST2000DM001\x2d1CH164_Z1F2VS6S\x2dpart4.device... [[32m OK [0m] Reached target Unmount All Filesystems. Starting Store Sound Card State... [[32m OK [0m] Started Tell Plymouth To Write Out Runtime Data. [[32m OK [0m] Mounted Huge Pages File System. [[32m OK [0m] Mounted Debug File System. [[32m OK [0m] Mounted POSIX Message Queue File System. [[1;31mFAILED[0m] Failed to start Store Sound Card State. See 'systemctl status alsa-store.service' for details. [[32m OK [0m] Started udev Coldplug all Devices. [[32m OK [0m] Started Create list of required static device nodes for the current kernel. Starting Create static device nodes in /dev... Starting Show Plymouth Boot Screen... [[32m OK [0m] Started Trigger Flushing of Journal to Persistent Storage. [[32m OK [0m] Started Create dynamic rule for /dev/root link. [[32m OK [0m] Started Create static device nodes in /dev. Starting udev Kernel Device Manager... [[32m OK [0m] Started udev Kernel Device Manager. [[32m OK [0m] Started Show Plymouth Boot Screen. Starting Show Plymouth Reboot Screen... [[32m OK [0m] Started Show Plymouth Reboot Screen. [[32m OK [0m] Found device ST2000DM001-1CH164. [[32m OK [0m] Found device ST2000DM001-1CH164. Starting File System Check on /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part4... systemd-fsck[510]: /dev/sda4: clean, 1353/120643584 files, 20715165/482569216 blocks [[32m OK [0m] Started File System Check on /dev/disk/by-id/ata-ST2000DM001-1CH164_Z1F2VS6S-part4. [[32m OK [0m] Reached target Shutdown. Starting /etc/init.d/halt.local Compatibility... [[32m OK [0m] Started /etc/init.d/halt.local Compatibility. [[32m OK [0m] Reached target Final Step. Starting Reboot...
auf welchen runlevel verweist /etc/systemd/system/default.target ?
bei mir auf runlevel 5 :
/etc/systemd/system/default.target -> /lib/systemd/system/runlevel5.target
Gruss, Kai
Hallo Kai, Du hast Recht! es war der Runlevel! Nur wie ist das da reingekommen? Ich habe da nicht am Runlevel gespielt! Auszug aus runlevel.target # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. [Unit] Description=Reboot Documentation=man:systemd.special(7) DefaultDependencies=no Requires=systemd-reboot.service After=systemd-reboot.service AllowIsolate=yes [Install] Alias=ctrl-alt-del.target Es ist vom Vortag. Alle Dateien unter ... /system haben da gleiche Datum und die gleiche Uhrzeit. Kann es sein, dass da ein Einbruch stattgefunden hat? Ich musste die Firewall deaktivieren um meine Netzwerkdrucker zu installieren. Gruss Bernd -- Um die Liste abzubestellen, schicken Sie eine Mail an: opensuse-de+unsubscribe@opensuse.org Um den Listen Administrator zu erreichen, schicken Sie eine Mail an: opensuse-de+owner@opensuse.org
Am 10.03.2014 15:25, schrieb Bernhard Junk:
Am 10.03.2014 15:10, schrieb Kai Grunau:
Hallo,
On 03/10/2014 02:56 PM, Bernhard Junk wrote:
Hallo,
ich musste mein System OS 13.1 neu aufsetzen, weil es immer wieder neu gestartet ist. Nach der Auswahl im Grub2- Menue lief der Rechner an und bootet danach wieder neu.
auf welchen runlevel verweist /etc/systemd/system/default.target ?
bei mir auf runlevel 5 :
/etc/systemd/system/default.target -> /lib/systemd/system/runlevel5.target
Gruss, Kai
Hallo Kai,
Du hast Recht! es war der Runlevel!
Nur wie ist das da reingekommen? Ich habe da nicht am Runlevel gespielt! Auszug aus runlevel.target
# This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version.
[Unit] Description=Reboot Documentation=man:systemd.special(7) DefaultDependencies=no Requires=systemd-reboot.service After=systemd-reboot.service AllowIsolate=yes
[Install] Alias=ctrl-alt-del.target
Es ist vom Vortag. Alle Dateien unter ... /system haben da gleiche Datum und die gleiche Uhrzeit. Kann es sein, dass da ein Einbruch stattgefunden hat? Ich musste die Firewall deaktivieren um meine Netzwerkdrucker zu installieren. Gruss Bernd
Ausschließen kann man sowas natürlich nicht... aber so richtig wahrscheinlich sieht es auch nicht aus, warum sollte jemand, der bei Dir einbricht, gerade den runlevel manipulieren ... und unnötig auffallen... Außerdem führt eine abgeschaltete FW ja nun nicht gerade zwingend zur Root-Manipulation, hast Du denn besondere Services im Netz, die das dann ermöglichen könnten? Ich tippe eher auf einen Konfigurationsfehler, ggf. auch in dem von Dir genannten update. cu jth -- www.teddylinx.de -- Um die Liste abzubestellen, schicken Sie eine Mail an: opensuse-de+unsubscribe@opensuse.org Um den Listen Administrator zu erreichen, schicken Sie eine Mail an: opensuse-de+owner@opensuse.org
On 03/10/2014 03:33 PM, Joerg Thuemmler wrote:
Am 10.03.2014 15:25, schrieb Bernhard Junk:
Am 10.03.2014 15:10, schrieb Kai Grunau:
Hallo,
On 03/10/2014 02:56 PM, Bernhard Junk wrote:
Hallo,
ich musste mein System OS 13.1 neu aufsetzen, weil es immer wieder neu gestartet ist. Nach der Auswahl im Grub2- Menue lief der Rechner an und bootet danach wieder neu.
auf welchen runlevel verweist /etc/systemd/system/default.target ?
bei mir auf runlevel 5 :
/etc/systemd/system/default.target -> /lib/systemd/system/runlevel5.target
Gruss, Kai
Hallo Kai,
Du hast Recht! es war der Runlevel!
Nur wie ist das da reingekommen? Ich habe da nicht am Runlevel gespielt! Auszug aus runlevel.target
# This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version.
[Unit] Description=Reboot Documentation=man:systemd.special(7) DefaultDependencies=no Requires=systemd-reboot.service After=systemd-reboot.service AllowIsolate=yes
[Install] Alias=ctrl-alt-del.target
Es ist vom Vortag. Alle Dateien unter ... /system haben da gleiche Datum und die gleiche Uhrzeit. Kann es sein, dass da ein Einbruch stattgefunden hat? Ich musste die Firewall deaktivieren um meine Netzwerkdrucker zu installieren. Gruss Bernd
Ausschließen kann man sowas natürlich nicht... aber so richtig wahrscheinlich sieht es auch nicht aus, warum sollte jemand, der bei Dir einbricht, gerade den runlevel manipulieren ... und unnötig auffallen... Außerdem führt eine abgeschaltete FW ja nun nicht gerade zwingend zur Root-Manipulation, hast Du denn besondere Services im Netz, die das dann ermöglichen könnten?
Ich tippe eher auf einen Konfigurationsfehler, ggf. auch in dem von Dir genannten update. ich hatte in der vergangenen Woche bei einem "zypper dup" von 12.2 auf 12.3 das Problem, das der Runlevel von 3 auf 5 veraendert war. Das hing vermutlich damit zusammen, dass das Verzeichnis /lib/systemd/system/ nach /usr/lib/systemd/system/ verschoben wurde.
Ein Einbruch mit einem Veraendern des Runlevel ist eher unwahrscheinlich ... Hth, Kai -- Um die Liste abzubestellen, schicken Sie eine Mail an: opensuse-de+unsubscribe@opensuse.org Um den Listen Administrator zu erreichen, schicken Sie eine Mail an: opensuse-de+owner@opensuse.org
participants (3)
-
Bernhard Junk -
Joerg Thuemmler -
Kai Grunau