Juve Napisano Październik 4, 2013 Zgłoszenie Share Napisano Październik 4, 2013 Witam! System w zasadzie 'nowy'. Postawiony serwer dhcpd, ssh i apache + squid. Z działaniem nie mam żadnego problemu. Nic w plikach konfiguracyjnych systemu nie było grzebane oprócz ustawień kart sieciowych. Po reboocie przestała odpowiadać klawiatura i myszka. Ręczny start daje 'failed' [root@ log]# cat boot.log udevd[87]: worker [187] unexpectedly returned with status 0x0100 udevd[87]: worker [187] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:02/device:03' udevd[87]: worker [188] unexpectedly returned with status 0x0100 udevd[87]: worker [188] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:02/device:08' udevd[87]: worker [189] unexpectedly returned with status 0x0100 udevd[87]: worker [189] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:0a/device:0b' udevd[87]: worker [190] unexpectedly returned with status 0x0100 udevd[87]: worker [190] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:12/IBM3737:00' udevd[87]: worker [192] unexpectedly returned with status 0x0100 udevd[87]: worker [192] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:12/PNP0100:00' udevd[87]: worker [196] unexpectedly returned with status 0x0100 udevd[87]: worker [196] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:12/PNP0800:00' udevd[87]: worker [198] unexpectedly returned with status 0x0100 udevd[87]: worker [198] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:12/PNP0B00:00' udevd[87]: worker [199] unexpectedly returned with status 0x0100 udevd[87]: worker [199] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:12/PNP0C02:00' udevd[87]: worker [200] unexpectedly returned with status 0x0100 udevd[87]: worker [200] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:12/PNP0C04:00' udevd[87]: worker [204] unexpectedly returned with status 0x0100 udevd[87]: worker [204] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:12/PNP0A05:00/PNP0401:00' udevd[87]: worker [206] unexpectedly returned with status 0x0100 udevd[87]: worker [206] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:12/PNP0A05:00/PNP0501:00' udevd[87]: worker [197] unexpectedly returned with status 0x0100 udevd[87]: worker [197] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:12/PNP0A05:00/PNP0303:00' udevd[87]: worker [211] unexpectedly returned with status 0x0100 udevd[87]: worker [211] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:12/PNP0A05:00/PNP0501:01' udevd[87]: worker [212] unexpectedly returned with status 0x0100 udevd[87]: worker [212] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:12/PNP0A05:00/PNP0700:00' udevd[87]: worker [216] unexpectedly returned with status 0x0100 udevd[87]: worker [216] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:12/PNP0A05:00/PNP0F13:00' udevd[87]: worker [191] unexpectedly returned with status 0x0100 udevd[87]: worker [191] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:12/PNP0000:00' udevd[87]: worker [194] unexpectedly returned with status 0x0100 udevd[87]: worker [194] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:12/PNP0200:00' udevd[87]: worker [201] unexpectedly returned with status 0x0100 udevd[87]: worker [201] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:13/device:14' udevd[87]: worker [202] unexpectedly returned with status 0x0100 udevd[87]: worker [202] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:13/device:17' udevd[87]: worker [207] unexpectedly returned with status 0x0100 udevd[87]: worker [207] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:1a/MGMT201:00' udevd[87]: worker [208] unexpectedly returned with status 0x0100 udevd[87]: worker [208] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:1a/MGMT201:01' Welcome to CentOS Starting udev: [ OK ] Setting hostname [ OK ] Setting up Logical Volume Management: No volume groups found [ OK ] Checking filesystems _CentOS-6.4-i386: clean, 83258/966656 files, 622961/3840000 blocks /dev/sda1: clean, 46/51200 files, 55479/204800 blocks /dev/sda2: clean, 33094/2949120 files, 531676/11776000 blocks [ OK ] Remounting root filesystem in read-write mode: [ OK ] Mounting local filesystems: [ OK ] Enabling local filesystem quotas: [ OK ] Enabling /etc/fstab swaps: [ OK ] Entering non-interactive startup Calling the system activity data collector (sadc): iptables: Applying firewall rules: [ OK ] Starting portreserve: [ OK ] Starting system logger: [ OK ] Enabling p4-clockmod driver (passive cooling only): [ OK ] Starting irqbalance: [ OK ] Starting rpcbind: [ OK ] Starting lldpad: [ OK ] Starting FCoE initiator service: [ OK ] Starting system message bus: [ OK ] Setting network parameters... [ OK ] Starting NetworkManager daemon: [ OK ] Starting NFS statd: [ OK ] Initializing OpenCT smart card terminals: [ OK ] Starting RPC idmapd: [ OK ] Starting cups: [ OK ] Starting acpi daemon: [ OK ] Starting HAL daemon: [FAILED] Retrigger failed udev events [ OK ] Starting PC/SC smart card daemon (pcscd): [ OK ] Loading autofs4: [ OK ] Starting automount: [ OK ] Starting sshd: [ OK ] Starting mysqld: [ OK ] Starting dhcpd: [FAILED] Starting postfix: [ OK ] Starting httpd: [ OK ] Starting radiusd: [ OK ] Starting crond: [ OK ] Starting squid: . [ OK ] Starting VNC server: no displays configured [FAILED] Starting atd: [ OK ] Gdzie znajdują jakieś bardziej szczegółowe logi hala? Odnośnik do komentarza Udostępnij na innych stronach More sharing options...
SeeM Napisano Październik 4, 2013 Zgłoszenie Share Napisano Październik 4, 2013 Jeśli zmieniłeś coś z sieciówką, to mogły się pomieszać nazwy plików urządzeń, mają teraz inne numery i stąd zamieszanie. Ja bym nie wnikając w nature problemu zrobił: udevadm control --reload-rules udevadm trigger i się "powinno naprawić"™. A jeśli wolisz najpierw sprawdzić co psuje start systemu: udevadm --export-db >> /jakiś/plik.txt i znajdź urządzenia, o których mówią błędy. Odnośnik do komentarza Udostępnij na innych stronach More sharing options...
Rekomendowane odpowiedzi
Jeśli chcesz dodać odpowiedź, zaloguj się lub zarejestruj nowe konto
Jedynie zarejestrowani użytkownicy mogą komentować zawartość tej strony.
Zarejestruj nowe konto
Załóż nowe konto. To bardzo proste!
Zarejestruj sięZaloguj się
Posiadasz już konto? Zaloguj się poniżej.
Zaloguj się