[Bug 1264413] [NEW] Kernel parameter 'break=init' don't work

Jiaxing Wang hello.wjx at gmail.com
Fri Dec 27 02:19:57 UTC 2013


Public bug reported:

    Adding kernel paramter 'break=init' should stop before init and prompt (initramfs) but this don't work in Saucy with the following
error info:

/init: line 327: can't create /dev/null:Read-only file system
Spawning shell within the initramfs
mknod: /dev/tty1: Read-only file system
mknod: /dev/tty2: Read-only file system
mknod: /dev/tty3: Read-only file system
mknod: /dev/tty4: Read-only file system
mknod: /dev/tty5: Read-only file system
mknod: /dev/tty6: Read-only file system
/scripts/panic/console_setup: line 81: can't create /dev/null: Read-only
filesystem
/init: line 5: can't open /dev/console: no such file

Description:	Ubuntu 13.10
Release:	13.10
Package:
udev:
  Installed: 204-0ubuntu19.1
  Candidate: 204-0ubuntu19.1

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1264413

Title:
  Kernel parameter 'break=init' don't work

Status in “systemd” package in Ubuntu:
  New

Bug description:
      Adding kernel paramter 'break=init' should stop before init and prompt (initramfs) but this don't work in Saucy with the following
  error info:

  /init: line 327: can't create /dev/null:Read-only file system
  Spawning shell within the initramfs
  mknod: /dev/tty1: Read-only file system
  mknod: /dev/tty2: Read-only file system
  mknod: /dev/tty3: Read-only file system
  mknod: /dev/tty4: Read-only file system
  mknod: /dev/tty5: Read-only file system
  mknod: /dev/tty6: Read-only file system
  /scripts/panic/console_setup: line 81: can't create /dev/null: Read-only
  filesystem
  /init: line 5: can't open /dev/console: no such file

  Description:	Ubuntu 13.10
  Release:	13.10
  Package:
  udev:
    Installed: 204-0ubuntu19.1
    Candidate: 204-0ubuntu19.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1264413/+subscriptions



More information about the foundations-bugs mailing list