[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[Steve Langasek]

don't change bug status without explanation.

** Changed in: ubuntu-release-notes
   Status: Invalid => Fix Released

** Changed in: mdadm (Ubuntu)
   Status: New => Fix Released

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[vingslagsvisvid...@gmail.com]

** Changed in: mdadm (Ubuntu)
   Status: New => Incomplete

** Changed in: mdadm (Ubuntu)
   Status: Incomplete => New

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[vingslagsvisvid...@gmail.com]

** Changed in: mdadm (Ubuntu)
   Status: Fix Released => Incomplete

** Changed in: mdadm (Ubuntu)
   Status: Incomplete => New

** Changed in: ubuntu-release-notes
   Status: Fix Released => Invalid

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[Ubuntu QA Website]

** Tags added: iso-testing

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[Jonah]

well i get installed fine, then reboot and it gets stuck at initramfs
and i have this error:

ALERT! /dev/mapper/nvidia_dcfadeef2 does not exist. Dropping to a shell!

is this a current bug or should i report this? please help. thanks

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[Launchpad Bug Tracker]

This bug was fixed in the package mdadm - 2.6.7.1-1ubuntu14

---
mdadm (2.6.7.1-1ubuntu14) lucid; urgency=low

  * Fix boot_degraded handling during installation (LP: #462258):
- Source /lib/preseed/preseed.sh in check.d/root_on_raid.
- Change mdadm/boot_degraded default in templates file to match the
  apparently-intended behaviour (i.e. false), and stop overriding
  debconf preseeding if BOOT_DEGRADED is not already set in the
  initramfs configuration file.
 -- Colin WatsonSun, 15 Nov 2009 17:53:53 -0600

** Changed in: mdadm (Ubuntu)
   Status: In Progress => Fix Released

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[Steve Langasek]

Jonah,

The problem you describe is unrelated to this bug report.

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[Jonah]

what's this won't fix status, does that mean i'm screwed?

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[Steve Langasek]

Please stop messing with the bug state.

** Changed in: mdadm (Ubuntu)
   Status: New => In Progress

** Changed in: mdadm (Ubuntu Karmic)
   Status: Confirmed => Won't Fix

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[karen pulsifer]

** Changed in: mdadm (Ubuntu)
   Status: In Progress => New

** Changed in: mdadm (Ubuntu Karmic)
   Status: Won't Fix => Confirmed

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[Dustin Kirkland]

** Changed in: mdadm (Ubuntu)
   Status: Incomplete => In Progress

** Changed in: mdadm (Ubuntu)
 Assignee: karen  pulsifer (froggy1234) => Colin Watson (cjwatson)

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[karen pulsifer]

** Changed in: mdadm (Ubuntu)
   Status: In Progress => Incomplete

** Changed in: mdadm (Ubuntu)
 Assignee: Colin Watson (cjwatson) => karen  pulsifer (froggy1234)

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[Jonah]

Hi guys I don't know if i have the same bug but I'm gutted I can't use
my system.

Basically I had 9.04 working fine and when karmic was released I
invested in a second hard drive thinking i could combine my current 1tb
drive and my new 1tb into a raid and do clean install of the new
release. i backed up to externals, fitted the new drive and tried the
install.

The first time i got an error that the bootloader couldn't install to
/target/. so i tried installing again from livecd but first did an
aptitude upgrade, which seemed to install a new ubiquity and some other
stuff. then i did the install again.

it seemed to work but on reboot i get stuck at initramfs - with an error
saying the nvidia mapper path doesn't exist. i have tried several times
reinstalling but i can't get past this.

and if it's the same bug i can't run the dpkg-reconfigure mdadm as
suggested as this command is not recognised from initramfs... please
help.

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[Dustin Kirkland]

Colin-

What do you think about publishing an mdadm package to karmic-updates
that raises this question to debconf critical, such that an
administrator has the opportunity (or, rather is forced?) to actually
make this decision and ensure that it gets written to disk?

We could touch a flag to ensure that the question is only posed once.

I recognize this is pretty egregious.  But it is a rather unfortunate
regression, considering the work that went into this feature.

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[Steve Langasek]

Documented at
:

The installer option to support "boot from a degraded array" does not
properly configure the installed system.  To correct this after
installation, run {{{dpkg-reconfigure mdadm}}} after installation and
select the option again. (Bug:462258)


** Changed in: ubuntu-release-notes
   Status: Fix Committed => Fix Released

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[Colin Watson]

** Changed in: mdadm (Ubuntu Karmic)
   Status: Confirmed => Won't Fix

** Changed in: mdadm (Ubuntu Karmic)
 Assignee: Colin Watson (cjwatson) => (unassigned)

** Changed in: mdadm (Ubuntu)
   Status: Confirmed => In Progress

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[Mathias Gug]

** Description changed:

  Binary package hint: mdadm
  
  In testing raid1 according to
  http://testcases.qa.ubuntu.com/Install/ServerRAID1, the system installed
  fine and both disks show up in /proc/mdstat. I installed using my
  procedure found in
  https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/457687/comments/6.
  I anwered 'yes' to booting in degraded mode. I noticed during install
  the grub-install did reference both /dev/vda and /dev/vdb
  
  However, if I remove the first disk (vda), the system drops to the
  initramfs telling me the disk could not be found. If I remove the second
  disk (after adding the first disk back), I'm told about the
  'bootdegraded=true' option.
  
  This ends up being a usability issue as well, because now 'Shift' is
  needed to get to the hidden boot menu since this was the only operating
  system installed.
  
  I tried adding bootdegraded=true to the kernel command line when vda was
  removed, and got the same message in initramfs.
  
  =
  Karmic release note:
  
  Automatic boot from a degraded RAID array is not configured correctly
  after installation
  
  Even if "boot from a degraded array" is set to yes during the install
  the system will not be properly configured to automatically boot from a
- degraded array. A workaround is to edit /etc/initramfs-
- tools/conf.d/mdadm after installation to set BOOT_DEGRADED to yes
- (BOOT_DEGRADED=yes) and then update the ramdisk with "sudo update-
- initramfs -u" (462258).
+ degraded array. A workaround is to run dpkg-reconfigure mdadm and select
+ again the option to boot from a degraded array once the system has
+ rebooted after the installation  (462258).
  
  =

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[Mathias Gug]

** Description changed:

  Binary package hint: mdadm
  
  In testing raid1 according to
  http://testcases.qa.ubuntu.com/Install/ServerRAID1, the system installed
  fine and both disks show up in /proc/mdstat. I installed using my
  procedure found in
  https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/457687/comments/6.
  I anwered 'yes' to booting in degraded mode. I noticed during install
  the grub-install did reference both /dev/vda and /dev/vdb
  
  However, if I remove the first disk (vda), the system drops to the
  initramfs telling me the disk could not be found. If I remove the second
  disk (after adding the first disk back), I'm told about the
  'bootdegraded=true' option.
  
  This ends up being a usability issue as well, because now 'Shift' is
  needed to get to the hidden boot menu since this was the only operating
  system installed.
  
  I tried adding bootdegraded=true to the kernel command line when vda was
  removed, and got the same message in initramfs.
  
  =
  Karmic release note:
  
  Automatic boot from a degraded RAID array is not configured correctly
- after installation or a mdadm package reconfiguration
+ after installation
  
  Even if "boot from a degraded array" is set to yes during the install
  the system will not be properly configured to automatically boot from a
  degraded array. A workaround is to edit /etc/initramfs-
  tools/conf.d/mdadm after installation to set BOOT_DEGRADED to yes
  (BOOT_DEGRADED=yes) and then update the ramdisk with "sudo update-
  initramfs -u" (462258).
  
  =

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[Brian Murray]

** Description changed:

  Binary package hint: mdadm
  
  In testing raid1 according to
  http://testcases.qa.ubuntu.com/Install/ServerRAID1, the system installed
  fine and both disks show up in /proc/mdstat. I installed using my
  procedure found in
  https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/457687/comments/6.
  I anwered 'yes' to booting in degraded mode. I noticed during install
  the grub-install did reference both /dev/vda and /dev/vdb
  
  However, if I remove the first disk (vda), the system drops to the
  initramfs telling me the disk could not be found. If I remove the second
  disk (after adding the first disk back), I'm told about the
  'bootdegraded=true' option.
  
  This ends up being a usability issue as well, because now 'Shift' is
  needed to get to the hidden boot menu since this was the only operating
  system installed.
  
  I tried adding bootdegraded=true to the kernel command line when vda was
  removed, and got the same message in initramfs.
  
  =
  Karmic release note:
  
- Automatic boot from a degraded RAID array not configured correctly after
- installation or a mdadm package reconfiguration
+ Automatic boot from a degraded RAID array is not configured correctly
+ after installation or a mdadm package reconfiguration
  
  Even if "boot from a degraded array" is set to yes during the install
  the system will not be properly configured to automatically boot from a
  degraded array. A workaround is to edit /etc/initramfs-
  tools/conf.d/mdadm after installation to set BOOT_DEGRADED to yes
  (BOOT_DEGRADED=yes) and then update the ramdisk with "sudo update-
  initramfs -u" (462258).
  
  =

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[Mathias Gug]

** Description changed:

  Binary package hint: mdadm
  
  In testing raid1 according to
  http://testcases.qa.ubuntu.com/Install/ServerRAID1, the system installed
  fine and both disks show up in /proc/mdstat. I installed using my
  procedure found in
  https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/457687/comments/6.
  I anwered 'yes' to booting in degraded mode. I noticed during install
  the grub-install did reference both /dev/vda and /dev/vdb
  
  However, if I remove the first disk (vda), the system drops to the
  initramfs telling me the disk could not be found. If I remove the second
  disk (after adding the first disk back), I'm told about the
  'bootdegraded=true' option.
  
  This ends up being a usability issue as well, because now 'Shift' is
  needed to get to the hidden boot menu since this was the only operating
  system installed.
  
  I tried adding bootdegraded=true to the kernel command line when vda was
  removed, and got the same message in initramfs.
+ 
+ =
+ Karmic release note:
+ 
+ Automatic boot from a degraded RAID array not configured correctly after
+ installation or a mdadm package reconfiguration
+ 
+ Even if "boot from a degraded array" is set to yes during the install
+ the system will not be properly configured to automatically boot from a
+ degraded array. A workaround is to edit /etc/initramfs-
+ tools/conf.d/mdadm after installation to set BOOT_DEGRADED to yes
+ (BOOT_DEGRADED=yes) and then update the ramdisk with "sudo update-
+ initramfs -u" (462258).
+ 
+ =

** Changed in: ubuntu-release-notes
   Status: In Progress => Fix Committed

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[Mathias Gug]

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

** Changed in: ubuntu-release-notes
 Assignee: (unassigned) => Mathias Gug (mathiaz)

** Changed in: ubuntu-release-notes
   Status: New => In Progress

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 462258] Re: installer's boot-degraded debconf answer not written to installed disk

[Dustin Kirkland]

** Summary changed:

- raid1 won't boot in degraded mode
+ installer's boot-degraded debconf answer not written to installed disk

** Changed in: mdadm (Ubuntu Karmic)
 Assignee: (unassigned) => Colin Watson (cjwatson)

** Changed in: mdadm (Ubuntu Karmic)
   Importance: Undecided => High

-- 
installer's boot-degraded debconf answer not written to installed disk
https://bugs.launchpad.net/bugs/462258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs