Cannot see 'bootdegraded' question
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
initramfs-tools (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
mdadm (Ubuntu) |
Fix Released
|
High
|
Dimitri John Ledkov | ||
plymouth (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
I'm not sure which of plymouth, initramfs-tools or mdadm is responsible here.
I just had a disk in my mirrored md array fail. I wanted to boot the system anyway. The prompt from mdadm in initramfs was obscured behind plymouth so I didn't find it except when I mashed escape out of frustration. (It then wouldn't accept my input, but that's bug #1095156).
This is the same symptoms as bug #628400 but that fix is still in place so some other area has probably regressed.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: plymouth 0.8.8-0ubuntu5
ProcVersionSign
Uname: Linux 3.8.0-1-generic x86_64
NonfreeKernelMo
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Date: Mon Jan 21 16:36:25 2013
DefaultPlymouth: /lib/plymouth/
InstallationDate: Installed on 2012-10-07 (105 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
MachineType: System manufacturer System Product Name
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/17/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1201
dmi.board.
dmi.board.name: P8Z77-V LX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
Related branches
Changed in plymouth (Ubuntu): | |
importance: | Undecided → High |
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?