Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am attempting to work around this problem:

on the hypothesis that the problem is a race condition between the boot sequence and '/' and my raid0 disks being available [I don't know that it is, but would like to see if that the case.]

I read this:, and have: * played with plymouth-x11 [very nice] * installed plymouth-theme-script

I would like to do something like this in my boot process, so Plymouth waits for the user's input before continuing:


Show the splash screen

sudo plymouth show-splash 

Stop the graphical progress indicator

sudo plymouth pause-progress 

Display a message

sudo plymouth message --text="pausing boot - press 'c' or space bar to continue" 

Wait for the user to type either 'c', 'C' or space (no return required)

sudo plymouth watch-keystroke --keys="cC " --command="tee /tmp/c_key_pressed" 

Change the on-screen message

sudo plymouth message --text="resuming boot" 

Resume the graphical progress indicator

sudo plymouth unpause-progress

But I don't really know how to proceed safely.

I'm an IDOIT, so would appreciate an IDIOT-proof guide

Thanks in advance

share|improve this question
I'm having a hard time understanding what your actual question is? – Jorge Castro Jun 6 '12 at 21:11

I can't help with your plymouth script, but I can suggest another solution, which you may or may not find satisfactory. I have this same problem with degraded raid, I simply opted to always boot a degraded raid.

sudo nano /etc/initramfs-tools/conf.d/mdadm

and set BOOT_DEGRADED=yes

share|improve this answer
I don't have enough rep to answer Jorge in thread so here goes. The real issue here is that usplash does not allow for errors requiring human interaction, so in this case mdadm is throwing up an error saying that the raid has been degraded do you wish to mount the degraded array [Y/N]. But you can not see or answer the question because usplash is preventing you from doing so (this may be a nvidia only problem). So boot hangs indefinitely. Upon reboot you can choose to go into recovery mode because the last boot failed. At which point you can hit Y and boot. – MickStep Jun 6 '12 at 21:41
Thanks for the answer. I have checked your method against what I have already tried: sudo dpkg-reconfigure mdadm, which sets BOOT_DEGRADED=true in the file you mentioned. Doesn't work for me :( – v4169sgr Jun 6 '12 at 21:44
Is there perhaps something I need to run after having set BOOT_DEGRADED=true? – v4169sgr Jun 6 '12 at 21:49
I'm getting a sneaking suspicion that the answer lies in this thread [as a matter of fact I am getting tingles up my spine, it is so familiar] – v4169sgr Jun 6 '12 at 21:58
made the edit and about to try a few reboots!!! – v4169sgr Jun 6 '12 at 22:02

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.