Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Hosed wrote: Hi, I have Ubuntu 9.04. I have Two (2) 36gb Seagate Cheetah with Raid 1 - Mirroring Setup. When I boot to Ubuntu 9.04 with One (1) of the hard disks unplugged, it fails to boot, it drops me to a shell with initramfs. What's the deal with that? Does it mean that Raid1 is NOT WORKING with Ubuntu 9.04? Any help is greatly appreciated. Thanks. Hi, I had a similar issue on Friday: a disk failed on a raid 1 ubuntu 9.10 system. After shutdown I removed the failed disk and added a new one. While booting I got an initramfs shell, as in your case. In my case the instructions on screen said that the system requested me whether to boot with a degraded array (y/N) or not and that and I did not answer quickly enough to the question, so, after timeout, it brought me the initramfs shell. To be honest I never saw that question on screen and the reason was that the splashscreen covered it. So I just rebooted and pressed 'y' some times when the splashscreen appeared and then the degraded boot started as expected. After that I had to manually partition the new disk (I have 2 different raid1 systems, one for /boot, one for / ) and add each partition to the raid system: sfdisk -d /dev/sda | sfdisk /dev/sdb # partition sdb as sda mdadm /dev/md0 -a /dev/sdb1# add sdb1 to the raid1 system md0 (/boot) mdadm /dev/md1 -a /dev/sdb2# add sdb2 to the raid1 system md1 (/) WARNING: this worked for my setting so don't take them as general instructions! If you have a mirroring setup than you could need just to add sdb1. After this the new disk sdb started syncing as expected. HTH, Emanuele -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Hosed wrote: Hi, I have Ubuntu 9.04. I have Two (2) 36gb Seagate Cheetah with Raid 1 - Mirroring Setup. When I boot to Ubuntu 9.04 with One (1) of the hard disks unplugged, it fails to boot, it drops me to a shell with initramfs. What's the deal with that? Does it mean that Raid1 is NOT WORKING with Ubuntu 9.04? Any help is greatly appreciated. Thanks. Hi, I had a similar issue on Friday: a disk failed on a raid 1 ubuntu 9.10 system. After shutdown I removed the failed disk and added a new one. While booting I got an initramfs shell, as in your case. In my case the instructions on screen said that the system requested me whether to boot with a degraded array (y/N) or not and that and I did not answer quickly enough to the question, so, after timeout, it brought me the initramfs shell. To be honest I never saw that question on screen and the reason was that the splashscreen covered it. So I just rebooted and pressed 'y' some times when the splashscreen appeared and then the degraded boot started as expected. After that I had to manually partition the new disk (I have 2 different raid1 systems, one for /boot, one for / ) and add each partition to the raid system: sfdisk -d /dev/sda | sfdisk /dev/sdb # partition sdb as sda mdadm /dev/md0 -a /dev/sdb1# add sdb1 to the raid1 system md0 (/boot) mdadm /dev/md1 -a /dev/sdb2# add sdb2 to the raid1 system md1 (/) WARNING: this worked for my setting so don't take them as general instructions! If you have a mirroring setup than you could need just to add sdb1. After this the new disk sdb started syncing as expected. HTH, Emanuele -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Tapani- I very much appreciate the detail with which you have constructed your report, as well as your followup which provides a hint as to how one might fix this issue. Thank you! But you are describing a different issue, which is deeper, and more involved. Please, please, please open a new bug report against mdadm ;-) :-Dustin -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Tapani- I very much appreciate the detail with which you have constructed your report, as well as your followup which provides a hint as to how one might fix this issue. Thank you! But you are describing a different issue, which is deeper, and more involved. Please, please, please open a new bug report against mdadm ;-) :-Dustin -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
You should not need to reinstall. To solve this, you need to: a) live upgrade all packages (specifically, you need to upgrade grub, mdadm, and initramfs-tools) b) install grub to the raid (for instance, if /dev/md0 provides your /boot directory, you can do grub-install /dev/md0) Cheers, :-Dustin -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
You should not need to reinstall. To solve this, you need to: a) live upgrade all packages (specifically, you need to upgrade grub, mdadm, and initramfs-tools) b) install grub to the raid (for instance, if /dev/md0 provides your /boot directory, you can do grub-install /dev/md0) Cheers, :-Dustin -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Dustin, Steve, thank you for your support. I'll be waiting for the updates on my hardy, and pray to not get in a situation where this bug will show up ugly on my servers. I remain subscribed, as I believe guys will make their job done soon. Good luck! On Fri, 2008-10-10 at 06:01 +, Dustin Kirkland wrote: I'm un-subscribing from this bug as well. Anyone who believes that berating the developer who has (finally) fixed this bug in the current release of Ubuntu, and offered to fix it in the LTS release, is constructive desperately needs to re-read the Ubuntu Code of Conduct. * http://www.ubuntu.com/community/conduct If you feel that this issue is urgently blocking your organization from adopting Ubuntu LTS at an enterprise level, I remind you that contracting commercial support from Canonical or one of the numerous Ubuntu partners around the globe is always an option. * http://www.ubuntu.com/support/paid * http://webapps.ubuntu.com/partners/ Dustin ** Changed in: initramfs-tools (Ubuntu) Assignee: Dustin Kirkland (kirkland) = (unassigned) ** Changed in: mdadm (Ubuntu) Assignee: Dustin Kirkland (kirkland) = (unassigned) -- () Campania Panglicii în ASCII /\ http://stas.nerd.ro/ascii/ -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Subscribing to what agent 8131 said. Now there are two drinks to get for the guy who helps us! On Fri, 2008-10-10 at 07:13 +, agent 8131 wrote: agent 8131 -- () Campania Panglicii în ASCII /\ http://stas.nerd.ro/ascii/ -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Dustin, Steve, thank you for your support. I'll be waiting for the updates on my hardy, and pray to not get in a situation where this bug will show up ugly on my servers. I remain subscribed, as I believe guys will make their job done soon. Good luck! On Fri, 2008-10-10 at 06:01 +, Dustin Kirkland wrote: I'm un-subscribing from this bug as well. Anyone who believes that berating the developer who has (finally) fixed this bug in the current release of Ubuntu, and offered to fix it in the LTS release, is constructive desperately needs to re-read the Ubuntu Code of Conduct. * http://www.ubuntu.com/community/conduct If you feel that this issue is urgently blocking your organization from adopting Ubuntu LTS at an enterprise level, I remind you that contracting commercial support from Canonical or one of the numerous Ubuntu partners around the globe is always an option. * http://www.ubuntu.com/support/paid * http://webapps.ubuntu.com/partners/ Dustin ** Changed in: initramfs-tools (Ubuntu) Assignee: Dustin Kirkland (kirkland) = (unassigned) ** Changed in: mdadm (Ubuntu) Assignee: Dustin Kirkland (kirkland) = (unassigned) -- () Campania Panglicii în ASCII /\ http://stas.nerd.ro/ascii/ -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Subscribing to what agent 8131 said. Now there are two drinks to get for the guy who helps us! On Fri, 2008-10-10 at 07:13 +, agent 8131 wrote: agent 8131 -- () Campania Panglicii în ASCII /\ http://stas.nerd.ro/ascii/ -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
On Thursday 09 October 2008, Stanislav Sushkov wrote: Can somebody explain, is this bug fixed in hardy packages? A lot of comments, and not a single clear report!!! If it is not fixed... Is there a patch for local script in initramfs- tools and mdadm or is there any rebuilt package with the fixes? Currently in Hardy i got: ~$ apt-cache policy mdadm mdadm: Installed: 2.6.3+200709292116+4450e59-3ubuntu3 Candidate: 2.6.3+200709292116+4450e59-3ubuntu3 Version table: *** 2.6.3+200709292116+4450e59-3ubuntu3 0 500 http://ro.archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status [EMAIL PROTECTED]:~$ apt-cache policy initramfs-tools initramfs-tools: Installed: 0.85eubuntu39.2 Candidate: 0.85eubuntu39.2 Version table: *** 0.85eubuntu39.2 0 500 http://ro.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status 0.85eubuntu36 0 500 http://ro.archive.ubuntu.com hardy/main Packages ~$ apt-cache policy mdadm mdadm: Installed: 2.6.3+200709292116+4450e59-3ubuntu3 Candidate: 2.6.3+200709292116+4450e59-3ubuntu3 Version table: *** 2.6.3+200709292116+4450e59-3ubuntu3 0 500 http://ro.archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status Thank you in advance! It's not fixed in hardy LTS, which is very strange... ace -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Can you point to a wiki page or a comment in this thread where I'll find a solution for hardy? Or I should install Intrepid packages? Thank you. On Thu, 2008-10-09 at 15:14 +, Dustin Kirkland wrote: This is fixed in Intrepid, not in Hardy. :-Dustin -- () Campania Panglicii în ASCII /\ http://stas.nerd.ro/ascii/ -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
On Thursday 09 October 2008, Stanislav Sushkov wrote: Just post a file with patch which works for hardy, and that's all folks :) No it's not. There is a procedure for that, so it will be updated automatically. That procedure I followed but at some point in the procedure, powers of 'normal' people are insufficient. We have to find an overlord who will sponsor the process and move it forward. Even the developer who made the patch for Ibex, can not move this forward on his own. Where are the Power Puff Girls when you need them ? -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
You mean this procedure? It didn't work for me. I mean I patched my local manually, but it broke my init image in /boot after update-initramfs... Maybe I the patch really works, but no one from this thread reported it as a solution... On Thu, 2008-10-09 at 20:37 +, Ace Suares wrote: On Thursday 09 October 2008, Stanislav Sushkov wrote: Just post a file with patch which works for hardy, and that's all folks :) No it's not. There is a procedure for that, so it will be updated automatically. That procedure I followed but at some point in the procedure, powers of 'normal' people are insufficient. We have to find an overlord who will sponsor the process and move it forward. Even the developer who made the patch for Ibex, can not move this forward on his own. Where are the Power Puff Girls when you need them ? -- () Campania Panglicii în ASCII /\ http://stas.nerd.ro/ascii/ -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Fixing Hardy would mean, at the very least: 1) porting the patches for: * mdadm * initramfs-tools * grub * grub-installer 2) Rebuilding the installation ISO's. 3) Obsessively regression testing the new install media. After Intrepid releases on October 30, 2008, I will spend a few cycles considering the port to Hardy 8.04.2. No guarantees, but rest assured that I am a Canonical/Ubuntu Server developer, who runs Hardy+RAID on my own systems, and have plenty of motivation to see this fixed. If anyone wants to volunteer to do (1), that would help move things along. And I certainly hope at the very least some of you are willing to help with (3). :-Dustin p.s. Please understand that your sarcasm is completely unappreciated. -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Dustin, what about those packages for ibex. If I update my hardy with those, so I risk serious troubles? Or it is not possible cause of difference between kernels? Someone did this before? On Thu, 2008-10-09 at 21:21 +, Dustin Kirkland wrote: Dustin -- () Campania Panglicii în ASCII /\ http://stas.nerd.ro/ascii/ -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Dustin, I've been doing sysadmin work for 15 years. I chose to try out Ubuntu for a home RAID server project, and loaded up Hardy as it was an LTS edition. In my first day working with Ubuntu, I ran into this bug, a bug where the version of mdadm (pretty well out of date) on Hardy was unable to resume a RAID reshape operation, and the ext2resize tools incorrectly detect the RAID stride. All of these bugs are BASIC functionality of the storage management tools which should have never made it through any sort of QA. I reported all of them as bugs, and this is the ONLY one which has even recieved a developer response after 2 months. For a Long Term Support edition, that's shameful. Not only that, but a bug which in a COMMON situation can prevent boot and your response as to whether a fix will be backported is I'll spend a few cycles considering backporting it Your lack of understanding for someone's sarcasm is completely unjustified, and the level of developer/bugfix support I'm seeing for Ubuntu is pathetic. With this level of support, using Ubuntu for any sort of a corporate server application would be a really poor decision. -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
On Thursday 09 October 2008, Stanislav Sushkov wrote: Just post a file with patch which works for hardy, and that's all folks :) No it's not. There is a procedure for that, so it will be updated automatically. That procedure I followed but at some point in the procedure, powers of 'normal' people are insufficient. We have to find an overlord who will sponsor the process and move it forward. Even the developer who made the patch for Ibex, can not move this forward on his own. Where are the Power Puff Girls when you need them ? -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
You mean this procedure? It didn't work for me. I mean I patched my local manually, but it broke my init image in /boot after update-initramfs... Maybe I the patch really works, but no one from this thread reported it as a solution... On Thu, 2008-10-09 at 20:37 +, Ace Suares wrote: On Thursday 09 October 2008, Stanislav Sushkov wrote: Just post a file with patch which works for hardy, and that's all folks :) No it's not. There is a procedure for that, so it will be updated automatically. That procedure I followed but at some point in the procedure, powers of 'normal' people are insufficient. We have to find an overlord who will sponsor the process and move it forward. Even the developer who made the patch for Ibex, can not move this forward on his own. Where are the Power Puff Girls when you need them ? -- () Campania Panglicii în ASCII /\ http://stas.nerd.ro/ascii/ -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Fixing Hardy would mean, at the very least: 1) porting the patches for: * mdadm * initramfs-tools * grub * grub-installer 2) Rebuilding the installation ISO's. 3) Obsessively regression testing the new install media. After Intrepid releases on October 30, 2008, I will spend a few cycles considering the port to Hardy 8.04.2. No guarantees, but rest assured that I am a Canonical/Ubuntu Server developer, who runs Hardy+RAID on my own systems, and have plenty of motivation to see this fixed. If anyone wants to volunteer to do (1), that would help move things along. And I certainly hope at the very least some of you are willing to help with (3). :-Dustin p.s. Please understand that your sarcasm is completely unappreciated. -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Dustin, what about those packages for ibex. If I update my hardy with those, so I risk serious troubles? Or it is not possible cause of difference between kernels? Someone did this before? On Thu, 2008-10-09 at 21:21 +, Dustin Kirkland wrote: Dustin -- () Campania Panglicii în ASCII /\ http://stas.nerd.ro/ascii/ -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Stanislav- First, the Intrepid packages won't work, due to toolchain (glibc, klibc) differences. I just tested out of curiosity in a virtual machine. Second, under no circumstances would I recommend this as an acceptable thing to do. If you are beholden to running Hardy, I presume that's because Hardy is supported as an LTS. Once you start changing the Hardy LTS packages and replacing them with Intrepid packages, you're no longer in a supported configuration. Especially when we're talking about things that are so fundamental to booting your system. If you would be willing to upgrade these four key packages to Intrepid, I'd say you would be much better served upgrading to Intrepid across the board. :-Dustin -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Dustin, I've been doing sysadmin work for 15 years. I chose to try out Ubuntu for a home RAID server project, and loaded up Hardy as it was an LTS edition. In my first day working with Ubuntu, I ran into this bug, a bug where the version of mdadm (pretty well out of date) on Hardy was unable to resume a RAID reshape operation, and the ext2resize tools incorrectly detect the RAID stride. All of these bugs are BASIC functionality of the storage management tools which should have never made it through any sort of QA. I reported all of them as bugs, and this is the ONLY one which has even recieved a developer response after 2 months. For a Long Term Support edition, that's shameful. Not only that, but a bug which in a COMMON situation can prevent boot and your response as to whether a fix will be backported is I'll spend a few cycles considering backporting it Your lack of understanding for someone's sarcasm is completely unjustified, and the level of developer/bugfix support I'm seeing for Ubuntu is pathetic. With this level of support, using Ubuntu for any sort of a corporate server application would be a really poor decision. -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
This is fixed in Intrepid, not in Hardy. :-Dustin -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
On Thursday 09 October 2008, Stanislav Sushkov wrote: Can somebody explain, is this bug fixed in hardy packages? A lot of comments, and not a single clear report!!! If it is not fixed... Is there a patch for local script in initramfs- tools and mdadm or is there any rebuilt package with the fixes? Currently in Hardy i got: ~$ apt-cache policy mdadm mdadm: Installed: 2.6.3+200709292116+4450e59-3ubuntu3 Candidate: 2.6.3+200709292116+4450e59-3ubuntu3 Version table: *** 2.6.3+200709292116+4450e59-3ubuntu3 0 500 http://ro.archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status [EMAIL PROTECTED]:~$ apt-cache policy initramfs-tools initramfs-tools: Installed: 0.85eubuntu39.2 Candidate: 0.85eubuntu39.2 Version table: *** 0.85eubuntu39.2 0 500 http://ro.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status 0.85eubuntu36 0 500 http://ro.archive.ubuntu.com hardy/main Packages ~$ apt-cache policy mdadm mdadm: Installed: 2.6.3+200709292116+4450e59-3ubuntu3 Candidate: 2.6.3+200709292116+4450e59-3ubuntu3 Version table: *** 2.6.3+200709292116+4450e59-3ubuntu3 0 500 http://ro.archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status Thank you in advance! It's not fixed in hardy LTS, which is very strange... ace -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Can you point to a wiki page or a comment in this thread where I'll find a solution for hardy? Or I should install Intrepid packages? Thank you. On Thu, 2008-10-09 at 15:14 +, Dustin Kirkland wrote: This is fixed in Intrepid, not in Hardy. :-Dustin -- () Campania Panglicii în ASCII /\ http://stas.nerd.ro/ascii/ -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
The new behavior present in Intrepid, following my series of patches, results in the following message being printed to the console after 30 seconds of waiting for a complete array... | There appears to be one or more degraded RAID devices, and your root device | may depend on the RAID devices being online. One or more of the following RAID | devices are degraded: | md0 : inactive sda1[0](S) |1020032 blocks [See attached screenshot] You can configure your RAID to boot even if degraded by running `dpkg-reconfigure mdadm`, or, you can simply edit the file: /etc/initramfs-tools/conf.d/mdadm by hand, and set BOOT_DEGRADED=true. They have the same effect. Additionally, you can set or override this on the kernel boot line by entering the grub menu and using any of the following: * bootdegraded * bootdegraded=1, bootdegraded=true, bootdegraded=on, bootdegraded=yes If BOOT_DEGRADED=true, it will continue to boot automatically in the event of a degraded RAID event. If those are set to false, the following prompt will appear, and wait 15 seconds for you to hit 'y' or 'n', at which point it will default to 'n': | ** WARNING: The root filesystem was found on a degraded RAID array! ** | | The system may have suffered a hardware fault, such as a disk drive failure. | You may attempt to start the system anyway, or stop now and attempt manual | recovery operations. | | If you choose to boot the degraded RAID, the system may start normally, but | performance may be degraded, and a further hardware fault could result in | permanent data loss. | | If you abort now, you will be provided with a recovery shell. | Do you wish to boot the degraded RAID? [y/N]: [See attached screenshot] This interactive selection is a one time deal. It does not affect the configuration as written to file. These changes involve too much code (grub, mdadm, initramfs-tools), too many new 'features', and are not security-critical enough to be _automatically_ published to Hardy LTS. That said, we do have documented process for providing Stable Release Updates, and Backports to previous releases. Please follow the procedures specified in: * https://wiki.ubuntu.com/StableReleaseUpdates * https://help.ubuntu.com/community/UbuntuBackports This bug, [Bug 120375] Re: cannot boot raid1 with only one disk, is solved, and I'm un-subscribing from it. If you have separate or additional issues, please open new bugs. Thanks, :-Dustin ** Attachment added: Screenshot.png http://launchpadlibrarian.net/16926424/Screenshot.png -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
The new behavior present in Intrepid, following my series of patches, results in the following message being printed to the console after 30 seconds of waiting for a complete array... | There appears to be one or more degraded RAID devices, and your root device | may depend on the RAID devices being online. One or more of the following RAID | devices are degraded: | md0 : inactive sda1[0](S) |1020032 blocks [See attached screenshot] You can configure your RAID to boot even if degraded by running `dpkg-reconfigure mdadm`, or, you can simply edit the file: /etc/initramfs-tools/conf.d/mdadm by hand, and set BOOT_DEGRADED=true. They have the same effect. Additionally, you can set or override this on the kernel boot line by entering the grub menu and using any of the following: * bootdegraded * bootdegraded=1, bootdegraded=true, bootdegraded=on, bootdegraded=yes If BOOT_DEGRADED=true, it will continue to boot automatically in the event of a degraded RAID event. If those are set to false, the following prompt will appear, and wait 15 seconds for you to hit 'y' or 'n', at which point it will default to 'n': | ** WARNING: The root filesystem was found on a degraded RAID array! ** | | The system may have suffered a hardware fault, such as a disk drive failure. | You may attempt to start the system anyway, or stop now and attempt manual | recovery operations. | | If you choose to boot the degraded RAID, the system may start normally, but | performance may be degraded, and a further hardware fault could result in | permanent data loss. | | If you abort now, you will be provided with a recovery shell. | Do you wish to boot the degraded RAID? [y/N]: [See attached screenshot] This interactive selection is a one time deal. It does not affect the configuration as written to file. These changes involve too much code (grub, mdadm, initramfs-tools), too many new 'features', and are not security-critical enough to be _automatically_ published to Hardy LTS. That said, we do have documented process for providing Stable Release Updates, and Backports to previous releases. Please follow the procedures specified in: * https://wiki.ubuntu.com/StableReleaseUpdates * https://help.ubuntu.com/community/UbuntuBackports This bug, [Bug 120375] Re: cannot boot raid1 with only one disk, is solved, and I'm un-subscribing from it. If you have separate or additional issues, please open new bugs. Thanks, :-Dustin ** Attachment added: Screenshot.png http://launchpadlibrarian.net/16926424/Screenshot.png -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
On Tuesday 19 August 2008, Dustin Kirkland wrote: The new behavior present in Intrepid, following my series of patches, results in the following message being printed to the console after 30 seconds of waiting for a complete array... | There appears to be one or more degraded RAID devices, and your | root device may depend on the RAID devices being online. One or more | of the following RAID | devices are degraded: | md0 : inactive sda1[0](S) |1020032 blocks [See attached screenshot] You can configure your RAID to boot even if degraded by running `dpkg-reconfigure mdadm`, or, you can simply edit the file: /etc/initramfs-tools/conf.d/mdadm by hand, and set BOOT_DEGRADED=true. They have the same effect. Additionally, you can set or override this on the kernel boot line by entering the grub menu and using any of the following: * bootdegraded * bootdegraded=1, bootdegraded=true, bootdegraded=on, bootdegraded=yes If BOOT_DEGRADED=true, it will continue to boot automatically in the event of a degraded RAID event. If those are set to false, the following prompt will appear, and wait 15 seconds for you to hit 'y' or 'n', at which point it will default to 'n': | ** WARNING: The root filesystem was found on a degraded RAID array! | ** | | The system may have suffered a hardware fault, such as a disk drive | failure. You may attempt to start the system anyway, or stop now and | attempt manual recovery operations. | | If you choose to boot the degraded RAID, the system may start | normally, but performance may be degraded, and a further hardware | fault could result in permanent data loss. | | If you abort now, you will be provided with a recovery shell. | Do you wish to boot the degraded RAID? [y/N]: [See attached screenshot] This interactive selection is a one time deal. It does not affect the configuration as written to file. These changes involve too much code (grub, mdadm, initramfs-tools), too many new 'features', and are not security-critical enough to be _automatically_ published to Hardy LTS. That said, we do have documented process for providing Stable Release Updates, and Backports to previous releases. Please follow the procedures specified in: * https://wiki.ubuntu.com/StableReleaseUpdates * https://help.ubuntu.com/community/UbuntuBackports This bug, [Bug 120375] Re: cannot boot raid1 with only one disk, is solved, and I'm un-subscribing from it. If you have separate or additional issues, please open new bugs. Thanks, :-Dustin ** Attachment added: Screenshot.png http://launchpadlibrarian.net/16926424/Screenshot.png Good work. -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Only some may consider this conservative behaviour a broken behavior, when a system on a redundant array of independent disks will degrade just fine when running, but won't even come up when booting. Even the more when you have upgraded from dapper LTS to hardy LTS and you *think* you are all peachy. Big surprise the first time when the root array degrades. Very unacceptable by all means. Thanks for adressing this tough. But is it going to be worked into an upgrade for the system or do we have to manually patch ? And if it's an upgrade, will I be suffciently warned now I have patched a workaround into the iniramfs scripts ? Dang ! -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
On Monday 18 August 2008, Ross Becker wrote: One more comment on this; I can understand the conservative behaviour, but when an array was degraded, the boot process halted with NO MESSAGE indicating what was wrong. Please whatever you do, even in the case of maintaining conservative behavior, emit a message telling the user why you're not continuing the boot process. I totally agree. The system seems to hang at a certain point, and when you wait long enough (180s as far as I understand from this discussion) and then drops you into initramfs. I tried 999 different ways of modifying grub, fstab, mdadm.conf becasue I didn't know WHY the system couldn't boot. The fact was that I very well KNEW the array was degraded, too. A warning message would have helped tremendously. Also, since there is no message and no indication of what was wrong, I had a very hard time finding this thread. I almost exploded when I found the thread, saw it's age, and all the possible workarounds, and the fact that it is not a problem in Debian. This behaviour really and very strongly diminishes my trust in Ubuntu as a system for my servers. Just a question: have you any idea how many systems are affected? The popularity contest says: mdadm 25199 5566 19467 15610 -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Only some may consider this conservative behaviour a broken behavior, when a system on a redundant array of independent disks will degrade just fine when running, but won't even come up when booting. Even the more when you have upgraded from dapper LTS to hardy LTS and you *think* you are all peachy. Big surprise the first time when the root array degrades. Very unacceptable by all means. Thanks for adressing this tough. But is it going to be worked into an upgrade for the system or do we have to manually patch ? And if it's an upgrade, will I be suffciently warned now I have patched a workaround into the iniramfs scripts ? Dang ! -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
On Monday 18 August 2008, Ross Becker wrote: One more comment on this; I can understand the conservative behaviour, but when an array was degraded, the boot process halted with NO MESSAGE indicating what was wrong. Please whatever you do, even in the case of maintaining conservative behavior, emit a message telling the user why you're not continuing the boot process. I totally agree. The system seems to hang at a certain point, and when you wait long enough (180s as far as I understand from this discussion) and then drops you into initramfs. I tried 999 different ways of modifying grub, fstab, mdadm.conf becasue I didn't know WHY the system couldn't boot. The fact was that I very well KNEW the array was degraded, too. A warning message would have helped tremendously. Also, since there is no message and no indication of what was wrong, I had a very hard time finding this thread. I almost exploded when I found the thread, saw it's age, and all the possible workarounds, and the fact that it is not a problem in Debian. This behaviour really and very strongly diminishes my trust in Ubuntu as a system for my servers. Just a question: have you any idea how many systems are affected? The popularity contest says: mdadm 25199 5566 19467 15610 -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
On Thursday 14 August 2008, RpR wrote: This is a reason why a lot of system administrators that I know went back to debian which doesn't have this behavior. For a LTS version it should be fixed. It's extremely weird that the Debian distro doesn't have this bug (or behaviour) and Ubuntu has. But dapper didn't have it; so switching from dapper to hardy burns you -without- knowing it. Because your md's have been working great for years, and they where up when you upgraded. Now then, when one of your root disks fails, you feel safe - you get an email and go to the datacenter and try to reboot. Bummer. And I dare you to be able to bring it up again - it won't be easy unless you brought some instructions! The community brouhgt forward a possible solution within this thread - it's not that hard to fix, is it ? -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
On Mon, Jul 28, 2008 at 3:41 PM, RpR [EMAIL PROTECTED] wrote: How can you install the solution. Tried a sudo apt-get -y update sudo apt-get -y upgrade This has been fixed in the development tree of Ubuntu Intrepid for further testing. It's not available for Hardy (or anything prior to Intrepid, rather) at this time. If you would like to test this in Ubuntu Intrepid, follow the instructions on this wiki page: * https://wiki.ubuntu.com/BootDegradedRaid#head-140b6fbe658cc11fc2710fa57b826dbf374abb69 -- :-Dustin -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
unsubscribe [EMAIL PROTECTED] -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
On Mon, Jul 28, 2008 at 3:41 PM, RpR [EMAIL PROTECTED] wrote: How can you install the solution. Tried a sudo apt-get -y update sudo apt-get -y upgrade This has been fixed in the development tree of Ubuntu Intrepid for further testing. It's not available for Hardy (or anything prior to Intrepid, rather) at this time. If you would like to test this in Ubuntu Intrepid, follow the instructions on this wiki page: * https://wiki.ubuntu.com/BootDegradedRaid#head-140b6fbe658cc11fc2710fa57b826dbf374abb69 -- :-Dustin -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
On Sat, Jul 26, 2008 at 01:15:08AM -, ceg wrote: # We've given up, A while loop is calling panic. An if statement might look better. No, the while loop is correct -- it lets the user attempt to fix the system repeatedly and on failures, it will drop to a shell again. -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
On Fri, Jul 25, 2008 at 8:08 PM, ceg [EMAIL PROTECTED] wrote: Instead of fixed sleep 5 in init-premount/mdadm, you could introduce a check timeout loop after call_failure_hooks in the local script. (So we can resume booting ASAP.) Maybe just copy the slumber while loop from above the call_failure_hooks. I removed the sleep 5 in a later patch. Please make sure your comments are with respect to the latest patch attached to this bug. :-Dustin -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
On Fri, Jul 25, 2008 at 8:08 PM, ceg [EMAIL PROTECTED] wrote:
mdadm --run --scan will start all arrays degraded not only the one needed
for the rootfs (and
its lvm and crypt respectively).
It will start for example a partial array from a removable disk that was
attatched and hasn't been
forgotten when the computer was turned off. Remember starting an array
degraded means it will
also start degraded next time. To prevent accidential degration and
sideeffect just start the
required arrays with mdadm --run /dev/mdX or even better by UUID.
...
Another point are required non-root filesystems, like a /home array that
needs to startdegraded.
...
We need a way to configure non-root raid devices to startdegraded
anyway, so this configuration could as well be used (hooked into
initramfs like the cryptroot script does) for the root device. (The
bootdegraded kernel parameter might not be neccesary then.)
I agree that my patch might start more degraded raids than someone may
necessarily want, but the current bug and the current issue at handle
is about providing a mechanism to configurably allow booting if a RAID
is missing a disk. This bug already has 73+ comments, and has been
around for over a year. Let's fix at least the immediate problem at
hand.
What you're talking about is going to be more complicated, and can be
handled at a later time, by subsequent patches. How about opening a
separate bug for independently allowing/disallowing each array to be
started in degraded mode?
This means of course we need to know the required array in initramfs.
Well, that part is doable for the root filesystem at least. It's
${ROOT} within the initramfs scripts.
:-Dustin
:-Dustin
--
cannot boot raid1 with only one disk
https://bugs.launchpad.net/bugs/120375
You received this bug notification because you are a member of Ubuntu
Server Team, which is a subscriber of a duplicate bug.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
On Sat, Jul 26, 2008 at 01:15:08AM -, ceg wrote: # We've given up, A while loop is calling panic. An if statement might look better. No, the while loop is correct -- it lets the user attempt to fix the system repeatedly and on failures, it will drop to a shell again. -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
On Fri, Jul 25, 2008 at 8:08 PM, ceg [EMAIL PROTECTED] wrote: Instead of fixed sleep 5 in init-premount/mdadm, you could introduce a check timeout loop after call_failure_hooks in the local script. (So we can resume booting ASAP.) Maybe just copy the slumber while loop from above the call_failure_hooks. I removed the sleep 5 in a later patch. Please make sure your comments are with respect to the latest patch attached to this bug. :-Dustin -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
On Fri, Jul 25, 2008 at 8:08 PM, ceg [EMAIL PROTECTED] wrote:
mdadm --run --scan will start all arrays degraded not only the one needed
for the rootfs (and
its lvm and crypt respectively).
It will start for example a partial array from a removable disk that was
attatched and hasn't been
forgotten when the computer was turned off. Remember starting an array
degraded means it will
also start degraded next time. To prevent accidential degration and
sideeffect just start the
required arrays with mdadm --run /dev/mdX or even better by UUID.
...
Another point are required non-root filesystems, like a /home array that
needs to startdegraded.
...
We need a way to configure non-root raid devices to startdegraded
anyway, so this configuration could as well be used (hooked into
initramfs like the cryptroot script does) for the root device. (The
bootdegraded kernel parameter might not be neccesary then.)
I agree that my patch might start more degraded raids than someone may
necessarily want, but the current bug and the current issue at handle
is about providing a mechanism to configurably allow booting if a RAID
is missing a disk. This bug already has 73+ comments, and has been
around for over a year. Let's fix at least the immediate problem at
hand.
What you're talking about is going to be more complicated, and can be
handled at a later time, by subsequent patches. How about opening a
separate bug for independently allowing/disallowing each array to be
started in degraded mode?
This means of course we need to know the required array in initramfs.
Well, that part is doable for the root filesystem at least. It's
${ROOT} within the initramfs scripts.
:-Dustin
:-Dustin
--
cannot boot raid1 with only one disk
https://bugs.launchpad.net/bugs/120375
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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Peter Haight [EMAIL PROTECTED] writes: I've only tried it on fiesty. I don't have a gutsy machine handy. You have the 'mdadm' package installed, right? If so, then they must have moved stuff around. You could try this: The model for starting mdadm disks has changed substantially in gutsy; it is now driven from a udev rule, building the devices as disks are discovered. Regards, Daniel -- Daniel Pittman [EMAIL PROTECTED] Phone: 03 9621 2377 Level 4, 10 Queen St, Melbourne Web: http://www.cyber.com.au Cybersource: Australia's Leading Linux and Open Source Solutions Company -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
Hey Peter, when I try to apply your patch I get questioned where the /scripts/local file is located. I coulnd't find it. Could you please specify it better? thanks , this patch is not from me - ist is from the other Peter in this bugreport cu Peter -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
