Bug #1102499 “Cannot see 'bootdegraded' question” : Bugs : plymouth package : Ubuntu

Revision history for this message

Iain Lane (laney) wrote on 2013-01-21:

#1

BootDmesg.txt Edit (60.8 KiB, text/plain; charset="utf-8")
BootLog.txt Edit (3.6 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.3 KiB, text/plain; charset="utf-8")
EtcDefaultGrub.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (10.8 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (524 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (7.4 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (105 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (3.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (6.3 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (189.1 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (425.2 KiB, text/plain; charset="utf-8")

Brian Murray (brian-murray) on 2013-01-22

Changed in plymouth (Ubuntu):
importance:	Undecided → High

Revision history for this message

Steve Langasek (vorlon) wrote on 2013-01-23:

#2

Hi Iain,

> I'm not sure which of plymouth, initramfs-tools or mdadm
> is responsible here.

The answer is mdadm. Plymouth is a boot-time multiplexer; it will not *always* be present in the initramfs, but *when* it is present, it owns the console and other packages need to interface with it if they need to talk to the user. In some cases, such as initramfs-tools' own rescue shell handling, this interfacing consists of calling 'plymouth quit' and restoring the console; in other cases, such as cryptsetup or mdadm, the correct behavior is to use plymouth itself for prompting.

Dmitrijs, could you please take a look at fixing the mdadm initramfs script to use plymouth when present?

Changed in plymouth (Ubuntu):
status:	New → Invalid
Changed in mdadm (Ubuntu):
importance:	Undecided → High
assignee:	nobody → Dmitrijs Ledkovs (xnox)
Changed in initramfs-tools (Ubuntu):
status:	New → Invalid
Changed in mdadm (Ubuntu):
status:	New → Triaged

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-02-15:

#3

Download full text (6.8 KiB)

This bug was fixed in the package mdadm - 3.2.5-5ubuntu1

---------------
mdadm (3.2.5-5ubuntu1) raring; urgency=low

  * Implement plymouth hooks for degraded RAID questions. (LP: #1102499)
  * Merged Intel Matrix Storage initramfs support.
  * Merge from Debian, remaining delta is still the same:
    - Call checks in local-premount to avoid race condition with udev
      and opening a degraded array.
    - debian/initramfs/local-premount: add call wait_for_udev to wait a
      little longer for RAID devices to appear (LP: #942106)
    - d/initramfs/mdadm-functions: Record in /run when boot-degraded
      question has been asked so that it is only asked once
    - pass --test to mdadm to enable result codes for degraded arrays.
    - debian/control: we need udev and util-linux in the right version. We
      also remove the build dependency from quilt and docbook-to-man as both
      are not used in Ubuntus mdadm.
    - debian/initramfs/hook: kept the Ubuntus version for handling the absence
      of active raid arrays in <initramfs>/etc/mdadm/mdadm.conf
    - debian/initramfs/script.local-top.DEBIAN, debian/mdadm-startall,
      debian/mdadm.raid.DEBIAN: removed. udev does its job now instead.
    - debian/mdadm-startall.sgml, debian/mdadm-startall.8: documentation of
      unused startall script
    - debian/mdadm.config, debian/mdadm.postinst - let udev do the handling
      instead. Resolved merge conflict by keeping Ubuntu's version.
    - debian/mdadm.postinst, debian/mdadm.config, initramfs/init-premount:
      boot-degraded enablement; maintain udev starting of RAID devices;
      init-premount hook script for the initramfs, to provide information at
      boot
    - debian/mkconf.in is the older mkconf. Kept the Ubuntu version.
    - debian/rules: Kept Ubuntus version for installing apport hooks, not
      installing un-used startall script.
    - debian/install-rc, check.d/_numbers, check.d/root_on_raid: Ubuntu partman
      installer changes
    - debian/presubj: Dropped this unused bug reporting file. Instead use
      source_mdadm.py act as an apport hook for bug handling.
    - d/p/debian-changes-3.1.4-1+8efb9d1ubuntu4: mdadm udev rule
      incrementally adds mdadm member when detected. Starting such an
      array in degraded mode is possible by mdadm -IRs. Using mdadm
      -ARs without stopping the array first does nothing when no
      mdarray-unassociated device is available. Using mdadm -IRs to
      start a previously partially assembled array through incremental
      mode. Keeping the mdadm -ARs for assembling arrays which were for
      some reason not assembled through incremental mode (i.e through
      mdadm's udev rule).
    - udev-md-raid.rules to not auto-start arrays based on detection
      of ddf or isw (imsm) signatures; this conflicts with dmraid usage in
      precise and requires more analysis before it can be enabled in SRU.

  * Merged in Debian:
    - Copy udev rule from /etc/udev/rules.d/ as well as the
      /lib/udev/rules.d/, to allow local administrator to override mdadm
      rules file.

mdadm (3.2.5-5) unstable; urgency=low

* add (empty) restart and force-reload actions to mdadm-waitidle
...

This bug was fixed in the package mdadm - 3.2.5-5ubuntu1

---------------
mdadm (3.2.5-5ubuntu1) raring; urgency=low

* Implement plymouth hooks for degraded RAID questions. (LP: #1102499)
  * Merged Intel Matrix Storage initramfs support.
  * Merge from Debian, remaining delta is still the same:
    - Call checks in local-premount to avoid race condition with udev
      and opening a degraded array.
    - debian/initramfs/local-premount: add call wait_for_udev to wait a
      little longer for RAID devices to appear (LP: #942106)
    - d/initramfs/mdadm-functions: Record in /run when boot-degraded
      question has been asked so that it is only asked once
    - pass --test to mdadm to enable result codes for degraded arrays.
    - debian/control: we need udev and util-linux in the right version. We
      also remove the build dependency from quilt and docbook-to-man as both
      are not used in Ubuntus mdadm.
    - debian/initramfs/hook: kept the Ubuntus version for handling the absence
      of active raid arrays in <initramfs>/etc/mdadm/mdadm.conf
    - debian/initramfs/script.local-top.DEBIAN, debian/mdadm-startall,
      debian/mdadm.raid.DEBIAN: removed. udev does its job now instead.
    - debian/mdadm-startall.sgml, debian/mdadm-startall.8: documentation of
      unused startall script
    - debian/mdadm.config, debian/mdadm.postinst - let udev do the handling
      instead. Resolved merge conflict by keeping Ubuntu's version.
    - debian/mdadm.postinst, debian/mdadm.config, initramfs/init-premount:
      boot-degraded enablement; maintain udev starting of RAID devices;
      init-premount hook script for the initramfs, to provide information at
      boot
    - debian/mkconf.in is the older mkconf. Kept the Ubuntu version.
    - debian/rules: Kept Ubuntus version for installing apport hooks, not
      installing un-used startall script.
    - debian/install-rc, check.d/_numbers, check.d/root_on_raid: Ubuntu partman
      installer changes
    - debian/presubj: Dropped this unused bug reporting file. Instead use
      source_mdadm.py act as an apport hook for bug handling.
    - d/p/debian-changes-3.1.4-1+8efb9d1ubuntu4: mdadm udev rule
      incrementally adds mdadm member when detected. Starting such an
      array in degraded mode is possible by mdadm -IRs. Using mdadm
      -ARs without stopping the array first does nothing when no
      mdarray-unassociated device is available. Using mdadm -IRs to
      start a previously partially assembled array through incremental
      mode. Keeping the mdadm -ARs for assembling arrays which were for
      some reason not assembled through incremental mode (i.e through
      mdadm's udev rule).
    - udev-md-raid.rules to not auto-start arrays based on detection
      of ddf or isw (imsm) signatures; this conflicts with dmraid usage in
      precise and requires more analysis before it can be enabled in SRU.

* Merged in Debian:
    - Copy udev rule from /etc/udev/rules.d/ as well as the
      /lib/udev/rules.d/, to allow local administrator to override mdadm
      rules file.

mdadm (3.2.5-5) unstable; urgency=low

* add (empty) restart and force-reload actions to mdadm-waitidle
    script -- this script is used only when the system needs to be
    shut down or rebooted, there's nothing to start or restart.

mdadm (3.2.5-4+mdmon) experimental; urgency=low

* fix `/etc/init.d/mdadm-raid status' inverse logic (Closes: #686100)
  * /etc/init.d/mdadm: change RUNDIR to /run instead of /var/run.
    Mdadm itself uses /run internally, we properly depend on initscripts
    version which creates /run, and the initscript itself is started
    after local_fs is processed, so this is merely a no-op, but let's
    do it for consistency.
  * Fix 'enough' function for RAID10, to prevent starting of a RAID10
    array which does not have required minimum of component devices.
    (Closes: #691668).
  * fix segfaults in Detail() - mdadm --detail may segfault if a drive
    has been removed from the array (Closes: #691670)
  * super0: do not override uuid with homehost.  The bug prevented
    re-creating an array with v0.90 superblock with the specified uuid
    when homehost is also specified.  (Closes: #686703)
  * several fixes for mdmon argument processing (Closes: #691671):
    - allow --takeover when original was started with --offroot
    - fix arg parsing.
    - fix arg processing for -a
  * Changes based on a patch by Miquel van Smoorenburg (Closes: #684708):
    - install mdmon in udeb and initramfs, so imsm arrays can work.
      mdadm runs mdmon automatically when needed (currently for imsm
      arrays), and mdmon is required to make such arrays read-write
      (they're read-only by default) so merely presence of mdmon is
      enough to be able to use imsm arrays.
    - /etc/init.d/mdadm start: if a mdmon pidfile is found in /run/mdadm,
      restart mdmon (--takeover --all)
    - /etc/init.d/mdadm stop: link pidfiles of mdmon processes into
      /run/sendsigs.omit.d, and make sure that happens before sendsigs runs.
    - stop mdadm before sendsigs, so that the above code works
    - add script mdadm-waitidle that runs just before reboot/halt.
      For each array that is still running, it sets sync_action to idle,
      and uses mdadm --wait-clean to wait for all arrays to go idle
      (it has a short timeout).

mdadm (3.2.5-3) unstable; urgency=low

* revert "Drop unused debconf templates" change -- the templates
    are actually being (indirectly) used in debian/mdadm.config
  * fix initramfs-script config name (slipped in the initramfs fixes)

mdadm (3.2.5-2) unstable; urgency=low

[ Sergey B Kirpichev ]
  * Fix mdadm.lintian-overrides
  * Fix spelling in binaries, fix lintian warnings
    manpage-has-errors-from-man and hyphen-used-as-minus-sign
  * Drop unused debconf templates
  * Implement status option for mdadm-raid init.d script
  * Fix lintian info's conflicts-with-version: Conflicts -> Breaks

[ Michael Tokarev ]
  * fix spelling mistakes in previous changelog entry
  * some cleanups for checkarray:
   - change --help printing and shorten/simplify the text
   - make --quiet cumulative and stop documenting --real-quiet
   - do not produce help in case of incorrect usage, and exit with 1
  * fixes for initramfs integration (Closes: #644389, #678262, #685161):
   - check INITRDSTART=none early
   - do not explicitly load raid level modules (modprobe/kmod does this)
   - do not collect needed raid levels (we include all modules anyway)
   - load md_mod explicitly since we need to change global parameter

[ Dmitrijs Ledkovs ]
  * Use dh_installinit with --no-restart-on-upgrade, which will start
    arrays, but will not stop them during upgrade. (Closes: 678971)
  * Copy local administrator's modified udev rules as well as the system
    one. (Closes: #678973)
 -- Dmitrijs Ledkovs <dmitrij.ledkov@ubuntu.com>   Fri, 15 Feb 2013 00:23:05 +0100

Changed in mdadm (Ubuntu):
status:	Triaged → Fix Released

Ubuntu
plymouth package

Cannot see 'bootdegraded' question

Bug Description

Related branches

Other bug subscribers

Bug attachments

Remote bug watches

	Status	Importance	Assigned to
initramfs-tools (Ubuntu)	Invalid	Undecided	Unassigned
mdadm (Ubuntu)	Fix Released	High	Dimitri John Ledkov
plymouth (Ubuntu)	Invalid	High	Unassigned

Ubuntuplymouth package

Cannot see 'bootdegraded' question

Bug Description

Related branches

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
plymouth package