| 2009-10-27 22:30:44 |
Jamie Strandboge |
bug |
|
|
added bug |
| 2009-10-27 22:33:40 |
Jamie Strandboge |
nominated for series |
|
Ubuntu Karmic |
|
| 2009-10-27 22:33:40 |
Jamie Strandboge |
bug task added |
|
mdadm (Ubuntu Karmic) |
|
| 2009-10-28 02:21:17 |
Jamie Strandboge |
description |
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 major usability issue as well, because there is no grub boot menu since this was the only operating system installed. I looked in /etc/default/grub and only saw:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
I believe this needs bootdegraded=true to work. I'll try to debug later, but it clearly doesn't work. |
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 major usability issue as well, because there is no grub boot menu since this was the only operating system installed. I looked in /etc/default/grub and only saw:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
I'm new to grub2, so not sure what needs to be adjusted.
|
|
| 2009-10-28 02:22:33 |
Jamie Strandboge |
attachment added |
|
degraded_failure.png http://launchpadlibrarian.net/34507872/degraded_failure.png |
|
| 2009-10-28 02:23:03 |
Jamie Strandboge |
tags |
|
regression-potential |
|
| 2009-10-28 04:13:12 |
Jamie Strandboge |
description |
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 major usability issue as well, because there is no grub boot menu since this was the only operating system installed. I looked in /etc/default/grub and only saw:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
I'm new to grub2, so not sure what needs to be adjusted.
|
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.
|
|
| 2009-10-28 12:05:56 |
Jamie Strandboge |
attachment added |
|
462258_partition_setup.png http://launchpadlibrarian.net/34537638/462258_partition_setup.png |
|
| 2009-10-28 12:06:29 |
Jamie Strandboge |
attachment added |
|
462258_boot_degraded_question.png http://launchpadlibrarian.net/34537661/462258_boot_degraded_question.png |
|
| 2009-10-28 13:17:58 |
Jamie Strandboge |
attachment added |
|
462258_images_and_xml.tar.gz http://launchpadlibrarian.net/34539896/462258_images_and_xml.tar.gz |
|
| 2009-10-28 13:18:56 |
Jamie Strandboge |
attachment added |
|
462258_install_logs.tar.gz http://launchpadlibrarian.net/34539920/462258_install_logs.tar.gz |
|
| 2009-10-28 16:30:27 |
Kees Cook |
mdadm (Ubuntu Karmic): status |
New |
Confirmed |
|
| 2009-10-28 18:03:41 |
Dustin Kirkland |
summary |
raid1 won't boot in degraded mode |
installer's boot-degraded debconf answer not written to installed disk |
|
| 2009-10-28 18:03:51 |
Dustin Kirkland |
mdadm (Ubuntu Karmic): assignee |
|
Colin Watson (cjwatson) |
|
| 2009-10-28 18:03:56 |
Dustin Kirkland |
mdadm (Ubuntu Karmic): importance |
Undecided |
High |
|
| 2009-10-28 21:17:49 |
Mathias Gug |
bug task added |
|
ubuntu-release-notes |
|
| 2009-10-28 21:18:10 |
Mathias Gug |
ubuntu-release-notes: assignee |
|
Mathias Gug (mathiaz) |
|
| 2009-10-28 21:18:17 |
Mathias Gug |
ubuntu-release-notes: status |
New |
In Progress |
|
| 2009-10-28 21:27:37 |
Mathias Gug |
description |
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.
|
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).
================= |
|
| 2009-10-28 21:28:50 |
Mathias Gug |
ubuntu-release-notes: status |
In Progress |
Fix Committed |
|
| 2009-10-28 21:41:50 |
Brian Murray |
description |
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).
================= |
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
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).
=================
|
|
| 2009-10-29 00:08:40 |
Mathias Gug |
description |
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
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).
=================
|
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).
=================
|
|
| 2009-10-29 00:25:32 |
Mathias Gug |
description |
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).
=================
|
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 run dpkg-reconfigure mdadm and select again the option to boot from a degraded array once the system has rebooted after the installation (462258).
=================
|
|
| 2009-10-29 11:04:51 |
Colin Watson |
mdadm (Ubuntu Karmic): status |
Confirmed |
Won't Fix |
|
| 2009-10-29 11:04:51 |
Colin Watson |
mdadm (Ubuntu Karmic): assignee |
Colin Watson (cjwatson) |
|
|
| 2009-10-29 11:05:10 |
Colin Watson |
mdadm (Ubuntu): status |
Confirmed |
In Progress |
|
| 2009-10-29 11:08:35 |
Steve Langasek |
ubuntu-release-notes: status |
Fix Committed |
Fix Released |
|
| 2009-11-09 22:54:50 |
karen pulsifer |
mdadm (Ubuntu): status |
In Progress |
Incomplete |
|
| 2009-11-09 22:54:50 |
karen pulsifer |
mdadm (Ubuntu): assignee |
Colin Watson (cjwatson) |
karen pulsifer (froggy1234) |
|
| 2009-11-09 23:03:25 |
Dustin Kirkland |
mdadm (Ubuntu): status |
Incomplete |
In Progress |
|
| 2009-11-09 23:03:31 |
Dustin Kirkland |
mdadm (Ubuntu): assignee |
karen pulsifer (froggy1234) |
Colin Watson (cjwatson) |
|
| 2009-11-09 23:50:09 |
karen pulsifer |
mdadm (Ubuntu): status |
In Progress |
New |
|
| 2009-11-09 23:50:16 |
karen pulsifer |
mdadm (Ubuntu Karmic): status |
Won't Fix |
Confirmed |
|
| 2009-11-09 23:58:09 |
Steve Langasek |
mdadm (Ubuntu): status |
New |
In Progress |
|
| 2009-11-09 23:58:27 |
Steve Langasek |
mdadm (Ubuntu Karmic): status |
Confirmed |
Won't Fix |
|
| 2009-11-16 00:00:14 |
Launchpad Janitor |
mdadm (Ubuntu): status |
In Progress |
Fix Released |
|
| 2009-11-17 18:04:42 |
Ubuntu QA Website |
tags |
regression-potential |
iso-testing regression-potential |
|
| 2010-05-31 17:47:00 |
vingslagsvisvidare@gmail.com |
mdadm (Ubuntu): status |
Fix Released |
Incomplete |
|
| 2010-05-31 17:47:22 |
vingslagsvisvidare@gmail.com |
mdadm (Ubuntu): status |
Incomplete |
New |
|
| 2010-05-31 17:47:55 |
vingslagsvisvidare@gmail.com |
ubuntu-release-notes: status |
Fix Released |
Invalid |
|
| 2010-05-31 17:55:32 |
vingslagsvisvidare@gmail.com |
mdadm (Ubuntu): status |
New |
Incomplete |
|
| 2010-05-31 17:55:58 |
vingslagsvisvidare@gmail.com |
mdadm (Ubuntu): status |
Incomplete |
New |
|
| 2010-05-31 18:08:03 |
Steve Langasek |
ubuntu-release-notes: status |
Invalid |
Fix Released |
|
| 2010-05-31 18:08:08 |
Steve Langasek |
mdadm (Ubuntu): status |
New |
Fix Released |
|
| 2010-10-19 09:22:23 |
Launchpad Janitor |
branch linked |
|
lp:~csurbhi/+junk/mdadm.fixes |
|
| 2012-04-11 07:49:27 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/lucid/mdadm |
|
| 2012-05-21 23:18:17 |
Launchpad Janitor |
branch linked |
|
lp:~dmitrij.ledkov/ubuntu/natty/mdadm/natty-updates |
|
