Failed to start create static device nodes in dev linux ubuntu

Не грузится systemd-modules-load.service

# 2 года, 6 месяцев назад (отредактировано 2 года, 6 месяцев назад) Месяц назад я писал об этом в «дефектных обновлениях». С тех пор ничего не изменилось, то есть это не мелкий огрех, который оперативно исправляют, а что-то более хитрое. Вот фрагмент лога загрузки (сфоторграфированый с экрана и отOCRенный):После выхода в emergency mode сделал рекомендованный запрос:
systemctl status systemd-modules-load.service’Проблема возникла одновременно с основным и lts-ядрами. Основное ядро, с которым пролем нет, и которое я заморозил — 4.20.6. Соответственно, lts-яро — 4.19.19. Так вот, если обновить lts до 4.19.29 — проблема есть. То есть с ядром с меньшей версией (lts 4.19.29), но с более поздней датой проблем есть, а с ядром с большей версией (основное 4.20.6) проблемы нет. С другой стороны, проблема однозначно с ядром связана: накат-откат только ядра приволит к появлению-исчезновению проблемы. Притом эта проблема у меня есть на двух компьютерах (железо разное, система под копирку).
Бредовая ситуация. Что-то типа того, что средства сборки ядра (независимо от версии) в какой-то момент стали строить нечто несовместимое с тем, что установлено у меня (ведь проблема только у меня?). У меня нет никаких левых драйверов или модулей, кроме того, что вбрасывает VirtualBox,

В какую сторону вообще копать, чтобы хотя бы зацепку найти?

# 2 года, 6 месяцев назад (отредактировано 2 года, 6 месяцев назад)

akorop
В какую сторону вообще копать, чтобы хотя бы зацепку найти?

Я предлагал несколько вариантов, похоже ты ничего не пробовал.
Тем более, учитывая сообщение
нужно обязательно трейсить загрузку systemd-modules-load и дополнительно можно попробовать отследить загрузку встроенных в ядро модулей.
С чего то нужно начинать сбор информации.

EDIT 1 — и хорошо бы проверить совпадение версий linux-headers, linux и linux-lts-headers, linux-lts
А может это не соответствие было при генерации initramfs?

EDIT 2 — а не пробовал для начала простой анализ, как описано в Wiki?

akorop
Process: 306 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAI

Источник

Ubuntu система не загружается failed to start create static device nodes in /dev

Во время работы перестал работать интернет . Перезапуск и выключения не работали . После этого я зажал кнопку выключения , после чего система перестала запускаться . dev/sda: recovering journal dev/sda: clean, 172698/5496832 files, 3654313/21972736 blocks FAILED Failed to start Create Static Device Nodes in deu.

See ’systemctl status systemd-topfiles-setup-dev.service’ for details.

Starting udev Kernel Device Manager..

[OK ] Started Apply Kernel Variables.

[OX ] Started udev Kernel Device Manager.

[OK ] Started Set the console keyboard layout.

[OK ] Reached target Local File Systems (Pre).

OK Started Snappy daemon.

Mounting Mount unit for gnome-logs, revision 81…

Mounting Mount unit for gtk-common-themes, revision 1440…

Mounting Mount unit for chromium, revision 1056..

Mounting Mount unit for gnome-system-monitor, revision 127…

Mounting Mount unit for core18, revision 1668…

Mounting Mount unit for core, revision 8268…

Mounting Mount unit for gnome-characters, revision 399…

Mounting Mount unit for gnome-3-28-1804, revision 116…

Mounting Mount unit for gnome-calculator, revision 544…

OK Activated swap /swapfile.

OK Started Journal Service. Starting Flush Journal to Persistent Storage…

Starting Show Plymouth Boot Screen…

OK Reached target Started udev Coldplug all Devices.

Starting Wait until snapd is fully seeded…

OK Started Wait until snapd is fully seeded.

OK Created slice User Slice of gdm.

Starting User Manager for UID 121…

OK I Started Session OK Started User Manager for UID 121.

Читайте также:  Обход пароля windows без его смены или сброса

Stopping User Manager for UID 121..

OK Cox Started Flush Journal to Persistent Storage.

OK Started Show Plymouth Boot Screen.

OK Started Forward Password Requests to Plymouth Directory Watch.

[OK Reached target Local Encrypted Volumes.

OK I Mounted Mount unit for gtk-common-themes, revision 1440.

Mount Mount unit for gnome-system-monitor, revision127 OK 1 Mounted Mount unit for gnome-logs, revision 81.

COX Mount Mount unit for gnome-calculator, revision 544.

OK Mounted Mount unit for core18, revision 1668 OK 3 Mounted Mount unit for core, revision 8268.

OK Mounted Mount unit for chroniun, revision 1056 OK 1 Mount Mount unit for gnome-characters, revision 399.

OK Mounted Mount unit for gnome-3-28-1804, revision 116.

OK Created slice system-system dxzd backlight.slice.

Starting Load/Save Screen Backlight Brightness of backlight acpi video.

OK 1 Started GNOME Display Manager…. and deal with any system charges.details.deo.shut down

Как можно решить эту проблему ?

После этого я зажал кнопку выключения , после чего система перестала запускаться

и «побилась» ФС на /dev/sda.

Опыт у тебя минимальный, так ведь? Самый простой путь

  • сделать загрузочную флешку с дистром, который используешь
  • сделать бекап своих пользовательских файлов (фоточки, музычка, лабораторки, «все вот это») на внешний носитель/в облако
  • посмотреть SMART диска (очень может быть, что у него серьёзные проблемы)

Во время работы перестал работать интернет . Перезапуск и выключения не работали .

одна из возможных причин, сбой диска во время работы. Сделай бекап содержимого /var/log/ – может потребоваться для «разбора полётов» // не потребуется, выкинешь

  • дальше проверить диск, можно попробовать восстановить ФС…
  • но я выбираю переустановку

Да, ещё ты бы разметку сообщений освоил Markdown или LORCODE

Источник

Thread: boot issues / unstable system/ — any help greatly appreciated 15.04

Thread Tools
Display

boot issues / unstable system/ — any help greatly appreciated 15.04

Having multiple issues. I know enough to get ubuntu installed but do not have enough experience to keep it running smoothly.

1 Can’t install updates — receive error that I do not have enough free disk space »
The upgrade needs a total of 86.4 M free space on disk ‘/boot’. Please free at least an additional 23.8 M of disk space on ‘/boot’. Empty your trash and remove temporary packages of former installations using ‘sudo apt-get clean’.»

I have tried teh sudo apt-get clean makes not difference and of course emptied all trash but still get same error when I attempt to update.

2 boot issues , took me multiple attempts and finally it fired up.

custom built laptop
Memory 15.6 GiB
Processor Intel® Core™ i7-4700MQ CPU @ 2.40GHz Ч 8
Graphics Intel® Haswell Mobile
OS type 64-bit
Disk 1.1 TB plus a solid state drive where the OS is loaded

Here the details over my head:
elcome to Ubuntu 15.04!

[ OK ] Created slice Root Slice.
[ OK ] Listening on Journal Audit Socket.
[ OK ] Listening on fsck to fsckd communication Socket.
[ OK ] Listening on Journal Socket (/dev/log).
[ OK ] Listening on Delayed Shutdown Socket.
[ OK ] Created slice User and Session Slice.
[ OK ] Created slice System Slice.
[ OK ] Created slice system-getty.slice.
[ OK ] Reached target Slices.
[ OK ] Listening on udev Kernel Socket.
[ OK ] Reached target Remote File Systems (Pre).
Starting Increase datagram queue length.
[ OK ] Listening on Journal Socket.
Starting Load Kernel Modules.
Starting Nameserver information manager.
Starting Create list of required static device nodes for the current kernel.
Starting Uncomplicated firewall.
Mounting Debug File System.
[ OK ] Started Read required files in advance.
Starting Read required files in advance.
Mounting Huge Pages File System.
Mounting POSIX Message Queue File System.
[ OK ] Started Braille Device Support.
Starting Braille Device Support.
Starting Setup Virtual Console.
[ OK ] Listening on udev Control Socket.
Starting udev Coldplug all Devices.
[ OK ] Created slice system-systemd\x2dcryptsetup.slice.
[ OK ] Set up automount Arbitrary Executable File Formats File System Automount Point.
[ OK ] Created slice system-systemd\x2dfsck.slice.
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
[ OK ] Mounted POSIX Message Queue File System.
[ OK ] Mounted Debug File System.
[ OK ] Mounted Huge Pages File System.
[ OK ] Started Increase datagram queue length.
[ OK ] Started Create list of required static device nodes for the current kernel.
[ OK ] Started Setup Virtual Console.
[ OK ] Started Nameserver information manager.
Starting Create Static Device Nodes in /dev.
[ OK ] Listening on Syslog Socket.
Starting Journal Service.
[ OK ] Started udev Coldplug all Devices.
Starting udev Wait for Complete Device Initialization.
[ OK ] Started Load Kernel Modules.
Mounting FUSE Control File System.
Starting Apply Kernel Variables.
[ OK ] Mounted FUSE Control File System.
[ OK ] Started Apply Kernel Variables.
[ OK ] Started Create Static Device Nodes in /dev.
Starting udev Kernel Device Manager.
[ OK ] Started Journal Service.
[ OK ] Started udev Kernel Device Manager.
Starting Show Plymouth Boot Screen.
[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Created slice system-systemd\x2dbacklight.slice.
[ OK ] Started Uncomplicated firewall.
[ OK ] Created slice system-ifup.slice.
[ OK ] Reached target Sound Card.
[ OK ] Created slice system-systemd\x2drfkill.slice.
[ OK ] Found device WDC_WD10JUCT-63CYNY0 1.
[ OK ] Found device PLEXTOR_PX-128M6M 6.
[ OK ] Found device PLEXTOR_PX-128M6M 1.
[ OK ] Started udev Wait for Complete Device Initialization.
Starting Copy rules generated while the root was ro.
Starting File System Check on Root Device.
[ OK ] Started Copy rules generated while the root was ro.
[ OK ] Started File System Check Daemon to report status.
Starting File System Check Daemon to report status.
[FAILED] Failed to start File System Check on Root Device.
See «systemctl status systemd-fsck-root.service» for details.
Starting Remount Root and Kernel File Systems.
[ OK ] Reached target Timers.
[ OK ] Closed ACPID Listen Socket.
[ OK ] Closed UUID daemon activation socket.
[ OK ] Stopped Getty on tty1.
[ OK ] Stopped getty on tty2-tty6 if dbus and logind are not available.
[ OK ] Stopped Network Manager Wait Online.
[ OK ] Stopped target Graphical Interface.
[ OK ] Stopped Accounts Service.
[ OK ] Stopped Light Display Manager.
[ OK ] Stopped Detect the available GPUs and deal with any system changes.
[ OK ] Stopped target Multi-User System.
[ OK ] Stopped LSB: automatic crash report generation.
[ OK ] Stopped Thermal Daemon Service.
[ OK ] Stopped Wait for Plymouth Boot Screen to Quit.
[ OK ] Stopped D-Bus System Message Bus.
[ OK ] Stopped /etc/rc.local Compatibility.
[ OK ] Reached target Login Prompts.
[ OK ] Stopped Permit User Sessions.
[ OK ] Stopped System Logging Service.
[ OK ] Closed Syslog Socket.
[ OK ] Stopped Network Manager.
[ OK ] Stopped Modem Manager.
[ OK ] Stopped LSB: Record successful boot for GRUB.
[ OK ] Stopped LSB: Tool to automatically collect and submit kernel crash signatures.
[ OK ] Stopped Cgroup management proxy.
[ OK ] Stopped Cgroup management daemon.
[ OK ] Stopped Enable support for additional executable binary formats.
[ OK ] Stopped Login Service.
[ OK ] Closed D-Bus System Message Bus Socket.
[ OK ] Stopped Make remote CUPS printers available locally.
[ OK ] Stopped CUPS Scheduler.
[ OK ] Closed CUPS Scheduler.
[ OK ] Stopped Avahi mDNS/DNS-SD Stack.
[ OK ] Closed Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK ] Stopped LSB: Set the CPU Frequency Scaling governor to «ondemand».
[ OK ] Stopped crash report submission daemon.
[ OK ] Stopped Regular background program processing daemon.
[ OK ] Stopped Restore /etc/resolv.conf if the system crashed before the ppp link was shut down..
[ OK ] Stopped LSB: Speech Dispatcher.
[ OK ] Stopped Run anacron jobs.
[ OK ] Stopped LSB: Cleans up any mess left by 0dns-up.
[ OK ] Stopped LSB: daemon to balance interrupts for SMP systems.
[ OK ] Stopped target Basic System.
[ OK ] Reached target Paths.
[ OK ] Reached target Sockets.
[ OK ] Stopped target System Initialization.
Starting Restore Sound Card State.
[ OK ] Started Emergency Shell.
Starting Emergency Shell.
[ OK ] Reached target Emergency Mode.
[ OK ] Started Restore Sound Card State.
[ OK ] Started Remount Root and Kernel File Systems.
Starting Flush Journal to Persistent Storage.
Starting Load/Save Screen Backlight Brightness of backlight:intel_backlight.
[ OK ] Reached target Local File Systems (Pre).
Starting File System Check on /dev/disk/by-uuid/21bdf37d-f5d2-484a-a851-2e2bc5e88ae4.
Starting File System Check on /dev/disk/by-uuid/89130cc0-2867-4a9e-a95c-ede7e2e9d2a9.
Starting Load/Save RF Kill Switch Status of rfkill0.
Starting Load/Save Random Seed.
[ OK ] Started Load/Save Screen Backlight Brightness of backlight:intel_backlight.
[ OK ] Started File System Check on /dev/disk/by-uuid/21bdf37d-f5d2-484a-a851-2e2bc5e88ae4.
[ OK ] Started File System Check on /dev/disk/by-uuid/89130cc0-2867-4a9e-a95c-ede7e2e9d2a9.
[ OK ] Started Load/Save RF Kill Switch Status of rfkill0.
[ OK ] Started Load/Save Random Seed.
[ OK ] Started Flush Journal to Persistent Storage.
Starting Cryptography Setup for cryptswap1.
Mounting /boot.
Mounting /home.
[ OK ] Mounted /boot.
[ OK ] Started Cryptography Setup for cryptswap1.
[ OK ] Reached target Encrypted Volumes.
[ OK ] Mounted /home.
[ OK ] Found device /dev/mapper/cryptswap1.
Activating swap /dev/mapper/cryptswap1.
[ OK ] Reached target Local File Systems.
Starting Wait for all «auto» /etc/network/interfaces to be up for network-online.target.
[ OK ] Reached target Remote File Systems.
Starting Set console keymap.
Starting Create Volatile Files and Directories.
Starting Tell Plymouth To Write Out Runtime Data.
Starting LSB: AppArmor initialization.
[ OK ] Started Wait for all «auto» /etc/network/interfaces to be up for network-online.target.
[ OK ] Activated swap /dev/mapper/cryptswap1.
[ OK ] Started Create Volatile Files and Directories.
Starting Update UTMP about System Boot/Shutdown.
Starting Network Time Synchronization.
[ OK ] Reached target Swap.
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[ OK ] Started Set console keymap.
[ OK ] Started LSB: AppArmor initialization.
Starting LSB: Raise network interfaces.
[ OK ] Started ifup for eth0.
Starting ifup for eth0.
[ OK ] Started ifup for wlan0.
Starting ifup for wlan0.
[ OK ] Started Update UTMP about System Boot/Shutdown.
Starting Update UTMP about System Runlevel Changes.
[ OK ] Started Network Time Synchronization.
[ OK ] Reached target System Time Synchronized.
[ OK ] Started Update UTMP about System Runlevel Changes.
[ OK ] Started LSB: Raise network interfaces..
[ OK ] Reached target Network.
[ OK ] Reached target Network is Online.
think@7887-W65-67SZ:

Читайте также:  Epub редактор mac os

$ systemctl status systemd-fsck-root.service
● systemd-fsck-root.service — File System Check on Root Device
Loaded: loaded (/lib/systemd/system/systemd-fsck-root.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since dom 2016-01-03 12:01:00 CST; 4h 30min ago
Condition: start condition failed at dom 2016-01-03 12:01:15 CST; 4h 29min ago
ConditionPathIsReadWrite=!/ was not met
Docs: man:systemd-fsck-root.service(8)
Process: 622 ExecStart=/lib/systemd/systemd-fsck (code=exited, status=1/FAILURE)
Main PID: 622 (code=exited, status=1/FAILURE)

ene 03 12:00:24 7887-W65-67SZ systemd-fsck[622]: /dev/sdb5: Inode 12785 has imagic flag set.
ene 03 12:00:24 7887-W65-67SZ systemd-fsck[622]: /dev/sdb5: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
ene 03 12:00:24 7887-W65-67SZ systemd-fsck[622]: (i.e., without -a or -p options)
ene 03 12:01:00 7887-W65-67SZ systemd-fsck[622]: fsck failed with error code 4.
ene 03 12:01:00 7887-W65-67SZ systemd-fsck[622]: Running request emergency.target/start/replace
ene 03 12:01:00 7887-W65-67SZ systemd[1]: systemd-fsck-root.service: main process exited, code=exited, status=1/FAILURE
ene 03 12:01:00 7887-W65-67SZ systemd[1]: Failed to start File System Check on Root Device.
ene 03 12:01:00 7887-W65-67SZ systemd[1]: Unit systemd-fsck-root.service entered failed state.
ene 03 12:01:00 7887-W65-67SZ systemd[1]: systemd-fsck-root.service failed.
ene 03 12:01:15 7887-W65-67SZ systemd[1]: Started File System Check on Root Device.

Last edited by ubuntark; January 3rd, 2016 at 11:32 PM .

Источник

Оцените статью