** 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
** 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
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
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
** 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
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
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
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.
--
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
** 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
** 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
** 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
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
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
** 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
Documented at
https://wiki.ubuntu.com/KarmicKoala/ReleaseNotes#Automatic%20boot%20from%20a%20degraded%20RAID%20array%20not%20configured%20upon%20installation:
The installer option to support boot from a degraded array does not
properly configure the installed system. To correct this after
** 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
** 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
** 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
** 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
** 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
** 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
--
22 matches
Mail list logo
