[Bug 120375] Re: cannot boot raid1 with only one disk
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1003309 and https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/251164 had the info I needed to fix my problems with encrypted RAID1 not booting in degraded mode. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to a duplicate bug report (125471). https://bugs.launchpad.net/bugs/120375 Title: cannot boot raid1 with only one disk To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/120375/+subscriptions -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
My server was in 8.04 LTS, having a raid 1 setup with 2 mirrored harddisk. I have tested, if I unplug one of the disk, the raid 1 was working fine. Sadly, after upgraded my system to 10.04.1 LTS, if I unplug one of the disk and boot, the raid 1 become inactive. #mdadm --detail /dev/md0 mdadm: md device /dev/md0 does not appear to be active. # cat /proc/mdstat md0 : inactive sdb1[0](S) I have removed some of the messages to save space here. In the above case, I have unplug the sdc, the raid 1 is not working anymore. It treated the sdb as spare disk. If I plug back the sdc, the raid 1 will be back to normal. It doesn't make any sense. Honestly, I am not a real expert in system admin. I implemented the software raid is simply to protect my data in case of a harddisk failure. Now I need to pray for both disk working in order for this raid 1 keeping a live. really frustrating. MAY I KNOW, what I need to do to fix this problem? Thank you very much! -- You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug (125471). https://bugs.launchpad.net/bugs/120375 Title: cannot boot raid1 with only one disk -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
Thank you Emanuele, I really haven't tried what you're suggesting, will definitely do it if I have time, or if my hard disk crashes for real. I've a question, I subscribe to this bug, but when I look at my ACCOUNT - BUGS - LIST SUBSCRIBED BUGS, it's not there, and I really want to be updated on this!!! Is this a bug? Help! :) -- 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 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
[Bug 120375] Re: cannot boot raid1 with only one disk
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. -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
Is this bug still present? I've installed a fresh 8.04.2 amd64 in a VirtualBox 2.1.2 with three SATA harddrives. When i switch off a drive, kernel is loadding but at the end the raid arrays are stopped and the system is unusable. r...@ubuntu:~# dpkg-reconfigure mdadm Do you want to boot your system if your RAID becomes degraded? - YES r...@ubuntu:~# uname -a Linux ubuntu 2.6.24-23-server #1 SMP Mon Jan 26 01:36:05 UTC 2009 x86_64 GNU/Linux r...@ubuntu:~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION=Ubuntu 8.04.2 r...@ubuntu:~# dpkg -l mdadm grub initramfs-tools Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ NameVersion Beschreibung +++-===-===-== ii grub0.97-29ubuntu21.1 GRand Unified Bootloader ii initramfs-tools 0.85eubuntu39.3 tools for generating an initramfs ii mdadm 2.6.3+200709292116+4450e59- tool to administer Linux MD arrays (software RAID) r...@ubuntu:~# cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md1 : active raid5 sda5[0] sdc5[2] sdb5[1] 5124480 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU] md2 : active raid5 sda2[0] sdc2[2] sdb2[1] 995840 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU] md0 : active raid1 sda1[0] sdc1[2] sdb1[1] 80192 blocks [3/3] [UUU] r...@ubuntu:~# mount | grep ^/ /dev/md1 on / type ext3 (rw,relatime,errors=remount-ro) /sys on /sys type sysfs (rw,noexec,nosuid,nodev) /dev/md0 on /boot type ext2 (rw,relatime) This would be a real show stopper for the 8.04 LTS... -- 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 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
[Bug 120375] Re: cannot boot raid1 with only one disk
Degraded RAID 1 array with encryption, Bug #324997. -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
Dustin, thank you for your quick answer and tips. It took me a while to test it, as I have an encrypted RAID 1 array with LVM, and things are not that straightforward with that setup. So far I have been using one of the tricks described in this thread earlier (ie. edit /etc/udev/rules.d/85-mdadm.rules: change the --no- degraded to -R, after that sudo update-initramfs -u -k all). It allows me to boot with only one drive, but has that annoying side effect where one of the partitions often starts in degraded mode, even if both drives are in fact present and working. I wanted to get rid of that problem, so I did this: - return 85-mdadm.rules as it used to be, ie. --no-degraded - sudo update-initramfs -u -k all - cat /proc/mdstat and check that all drives are online and sync'ed - upgrade all packages - re-install grub to both drives These are my test results: 1. Restart computer with both disks - everything works OK 2. Restart computer with only one disk - Keeps asking Enter password to unlock the disk (md1_crypt): even though I write the correct password 3. Restart computer again with both disks - everything works OK So, first it seemed that the fix does not work at all, as Ubuntu starts only when both disks are present. Then I made some more tests: 4. Restart computer with only one disk - Keeps asking Enter password to unlock the disk (md1_crypt): even though I write the correct password - Now press CTRL+ALT+F1, and see these messages: Starting up ... Loading, please wait... Setting up cryptographic volume md1_crypt (based on /dev/md1) cryptsetup: cryptsetup failed, bad password or options? cryptsetup: cryptsetup failed, bad password or options? - After waiting some minutes, I got dropped into the busybox - Something seems to be going wrong with encryption 5. Restart computer with only one disk, without quiet splash boot parameters in /boot/grub/menu.lst - Got these messages: Command failed: Not a block device cryptsetup: cryptsetup failed, bad password or options? ... other stuff ... Command failed: Not a block device cryptsetup: cryptsetup failed, bad password or options? Command failed: Not a block device cryptsetup: cryptsetup failed, bad password or options? cryptsetup: maximum number of tries exceeded Done. Begin: Waiting for root file system... ... - After waiting some minutes, I get the question whether I want to start the system with degraded setup. However, it does not matter what I answer, as the system cannot start since the encryption has already given up trying. I don't know what it was trying to read as a password, because I did not type anything. 6. Restart computer with only one disk, with quiet splash bootdegraded=true boot parameters in /boot/grub/menu.lst - Keeps asking Enter password to unlock the disk (md1_crypt): even though I write the correct password - Now press CTRL+ALT+F1, and see these messages: Starting up ... Loading, please wait... Setting up cryptographic volume md1_crypt (based on /dev/md1) cryptsetup: cryptsetup failed, bad password or options? Summary: The fix does not seem to work, in case you have encrypted your RAID disks. To be more specific: after a long wait it does ask whether to start in degraded mode, although the question seems to appear only when booted without quiet splash parameters. I guess it also starts in degraded mode automatically if bootdegraded parameter is set. Nevertheless the system will not start, as this seems to happen too late for encryption has already given up. Question: Is this fix tested with encryption at all? Is it suppose to work with it, or not? I think this is important, as if you have a RAID setup you obviously have some important data and in many cases want to encrypt it, too. -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
Ok, I'm answering myself: there is a workaround for getting it to work with LUKS encryption. You can run sudo dpkg-reconfigure mdadm and enable automatic startup with degraded RAID array if you want, or watch the screen and be quick enough to answer Yes when asked to start degraded. Nevertheless, you need to wait again until you're dropped to BusyBox. Then do this: # to enter the passphrase. md1 and the md1_crypt are the same values # you had to put in /target/etc/crypttab at the end of the install cryptsetup luksOpen /dev/md1 md1_crypt # (type your LUKS password, as requested) # continue to boot! hit CTRL+D I found the instructions from here: http://ubuntuforums.org/archive/index.php/t-524513.html Now, if only someone could give a hint on how to make this automatic, so that there would be no need to write anything. It is ok to wait a few minutes, though. Nevertheless, I'm pretty happy now that I can use --no-degraded parameter in 85-mdadm.rules, yet get the system up in case a disk fails. In the rare case of an actual disk failure, writing a one-liner can be tolerated. Thank you everyone who have worked with this issue and helped to get it solved in Hardy. -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
It seems that the issue is now fixed in Intrepid, and also backported to Hardy 8.04.2, which was released a few days ago. However, it is unclear to me if I need to reinstall from 8.04.2 distribution media, or can I fix an existing Hardy installation via software updates? -- 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 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
[Bug 120375] Re: cannot boot raid1 with only one disk
** Changed in: grub (Ubuntu Hardy) Status: In Progress = Fix Released ** Changed in: initramfs-tools (Ubuntu Hardy) Status: In Progress = Fix Released ** Changed in: mdadm (Ubuntu Hardy) Status: In Progress = Fix Released -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
Thanks, Nick. Please respond with any test results in Bug #290885. Bug #120375 is hereby reserved for wailing, moaning, fussing, cursing, complaining, lamenting, murmuring, regretting, repining, bewailing, deploring, weeping, mourning, protesting, charging, accusing, disapproving, grumbling, fretting, whining, peeving, quarreling, resenting, dissenting, discontenting, malcontenting, bellyaching, and non-constructive criticisms :-) :-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
[Bug 120375] Re: cannot boot raid1 with only one disk
Now that the Intrepid development cycle has wound down, I was finally able to circle back to this. For those of you interested in seeing this backported to Hardy, see Bug #290885. I have test packages available in my PPA--standard PPA disclaimers apply. Please refer to Bug #290885 for test instructions. :-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
[Bug 120375] Re: cannot boot raid1 with only one disk
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) -- 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 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
[Bug 120375] Re: cannot boot raid1 with only one disk
No one should be taking any of this personally or feel berated. People should feel free to be honest about their experiences without fear that doing so will drive away people that could be of help in resolving the issues. I've been keeping my mouth shut on this bug for a couple of months and I apologize for being long winded when I finally took the time to post my experiences. Dustin Kirkland, you did not offer to fix this problem in the LTS release. You stated that you would consider it. And that's great, but without any commitment to fix the problem in 8.04 it would be nice to actually be able to offer up a simple solution to the people that come across this page when trying to resolve this bug. I will not unsubscribe from this bug because I know that people will be bit by it again, come to me for help, and I wish to have a good solution for them when they do. I re-read the Code of Conduct and note that being collaborative seems to be at odds with disengaging when one finds the process unpleasant. I certainly respect the right of people to do so but I feel it's a loss to actually making progress on this bug. Granted, I've only been subscribed for 2 months; if I had been subscribed for a year I acknowledge I might feel differently. Since people seem to feel that this hasn't been a friendly exchange I will be happy to buy a drink of choice to: 1) Anyone that comes up with a good solution to this bug for Ubuntu 8.04 and 8.04.1. 2) Anyone who works to get this bug fixed in 8.04.2. 3) Dustin Kirkland and anyone else who makes sure this bug never appears in 8.10. -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
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! -- 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: 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
[Bug 120375] Re: cannot boot raid1 with only one disk
Dustin I love the work that you've put in to this but I need to stand by Ace Suares and for a LTS version it should be fixed. It prevents me to use ubuntu for my servers which uses software raid. The ones with hardware raid could use ubuntu. But sticking with debian for the moment because of this. If hardy wasn't a LTS version I would understand when you would just say upgrade to ... -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
Just post a file with patch which works for hardy, and that's all folks :) -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
Dustin, I am glad you may be spending some time on this bug. You mention rebuilding ISO's. But why can't it just be an upgrade to the existing installations? I mean, on an existing system, all we need to do is upgrade ? Also, I am not being sarcastic at all, when I say that I can not understand that there needs to be so much regression testing for the patch that removes the bug, since to introduce the bug was possible at all. The bug is not present in Debian, and was not present in Dapper. Anyway, I am going to install the workaround on all my affected machines because I cannot wait that long. (But then I will get some trouble when an update finally comes around..). And I am not going to advice using Ubuntu for servers that use software raid anymore. I am really disappointed in the way this is going. I am happy it will be fixed in Ibex tough. Just keep smiling... I am also unsubscribing from this bug. I feel that I am becoming unconstructive. -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
Unsubscribing ubuntu-sru. Please do not subscribe the SRU team to bugs that don't actually include proposed fixes to previous releases. a) this is not the documented procedure for SRU fixes, b) the SRU team has other things to do that actually benefit Ubuntu users, instead of following a bug report that consists of lambasting Ubuntu for a bug that the relevant developers have already agreed should receive attention. With regard to the last, I've accepted the nomination for hardy based on Dustin's statement that he'll work on this for 8.04.2. Ross, as for the other bugs you mentioned: the ext2resize package is not part of Ubuntu main, which means it's not part of the set of software supported by Canonical. It's a third-party tool that ext3 upstream has repeatedly recommended against using. The package from Debian is included in the universe repository in the hope that it's useful to someone, but there is no one at all in Ubuntu tending that package - there's no reason to think it was subjected to any QA for it to fail. If you believe this problem makes the package unusable, then I'm happy to escalate bug #256669 and have the ext2resize package removed from subsequent Ubuntu releases. ** Changed in: initramfs-tools (Ubuntu Hardy) Status: New = Confirmed ** Changed in: mdadm (Ubuntu Hardy) Importance: Undecided = Medium Status: New = Confirmed ** Changed in: initramfs-tools (Ubuntu Hardy) Importance: Undecided = Medium -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
Another thing to mention: Which systems are using raid? Right! ... Server! Such systems are usually maintained remotely and rebooted through a ssh connection. This message an the question is very very useful. :-( If you abort now, you will be provided with a recovery shell. Do you wish to boot the degraded RAID? [y/N]: The last you will see from this server is rebooting now -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
I've experimented this bug on a new system I sold.. After a few days working, one of the disks just died for my bad luck. I lost a Lot of hours trying to fix it, resulting downtime to our costumer.. I couldn't believe when I saw the panic I went to was the result of a bug not fixed on this so called LTS release.. I would call Hardy a Long Time Supported Testing Release.. This bug has been here more than 1 year.. I just dumped hardy out of my way and went back to Debian Etch. No more Hard(y) and strange works for me! It's extremely weird that the Debian distro doesn't have this bug (or behaviour) and Ubuntu has. Not that weird.. I just can't imagine Debian simply put out there a final release with a serious bug like this one.. -- 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 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
[Bug 120375] Re: cannot boot raid1 with only one disk
The attached patch adds a debconf question, prompting the user as to the desired behavior on a newly degraded RAID... To boot, or not to boot, that is the question. The priority is currently set to medium, with the default being BOOT_DEGRADED=false, which is the conservative/traditional behavior. Perhaps that priority could be raised to high, such that the user would actually be prompted with this question in the installer. I leave that for another discussion, and another bug, please. :-Dustin ** Attachment added: mdadm.boot_degraded_debconf.debdiff http://launchpadlibrarian.net/16894081/mdadm.boot_degraded_debconf.debdiff -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
Updated patch. Only difference from the previous is that I added a line to the change log about the debian/po/*.po files changed. :-Dustin ** Attachment added: mdadm.boot_degraded_debconf.debdiff http://launchpadlibrarian.net/16894112/mdadm.boot_degraded_debconf.debdiff -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
Dustin, you could have open a separate bug with your debconf patch to track your work and at the same time keep the comunity updated and able to give you feedback in a more organized manner. the default being BOOT_DEGRADED=false, which is the conservative/traditional behavior. 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. The reason for all this restrictivity with starting arrays comes from those start up scripts that use(ed) mdadm --assemble --scan to start arrays. Those run whatever (partially) connected arrays they can get hold of (in degraded mode). IMHO the right thing for start up scripts to do is to only start arrays that are needed to set up the root device and fstab, and degrade only them after a timeout. (/usr/share/initramfs-tools/hooks/cryptroot contains code to determine devices that the root device depends on.) Hotplugging can start any arrays afterwards, if it is completely attatched. The homehost feature is one suboptimal attempt to restrict array assembly. Same with the restriction with DEVICE or ARRAY definitions in mdadm.conf. Such restrictions add extra configuration burdens and should not be necessary with start up scripts that just correctly honor the root device and fstab information. In fact the homehost, and ARRAY restrictions prevent the hotplugging from beeing any better than manual configuration. Arrays still have to be configured in mdadm.conf (Bug #252345) . -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
This bug is considerably overloaded. Thus, I have split the mdadm/debconf/boot_degrade bug/patch to: * Bug #259127 :-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
[Bug 120375] Re: cannot boot raid1 with only one disk
Wow, Dustin we again wrote or comments almost simultaneously. Thank you for separating the issue. -- 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 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
[Bug 120375] Re: cannot boot raid1 with only one disk
I have separated out the issue of booting with degraded non-root arrays into Bug# 259145. As a user merely helping to gather info I can't say if updates to hardy (ubuntu 8.04) will be made available. 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
[Bug 120375] Re: cannot boot raid1 with only one disk
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. -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
Comment 91 (https://bugs.launchpad.net/ubuntu/+bug/120375/comments/91) worked for me. I didn't need the extra lvm stuff but it can't hurt. I was booting from /dev/sdb1, which was the 'failed' drive from /dev/md0. In /etc/fstab, I had /dev/md0 als /, and it shows up as such in 'df'. But /dev/md0 was not really mounted as root; is was /dev/sdb1 altough it *says* it's /dev/md0. This is a bug I think. So I made the changes to the initramfs script, and did update-initramfs -u. BUT THAT HAPPENS ON /dev/sdb1 ! So I had to do this: mount -t ext3 /dev/md0 /mnt cd /mnt chroot . # Change the script in /usr/share/initramfs-tools/scripts/local ! the previous change was on /dev/sdb1 !!! update-initramfs -u exit # from the chroot reboot This took me ten hours or more (linux-haters !) Doesn't anyone think it's *really bad* that all 8.04 installs fail horribly when the root raid-array degrades !? Those machines won't boot at all when that happens ! And it's not going to be fixed in 8.04 ? How can this be !? -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
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. -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
Michael- Is there any chance you can test the functionality on Intrepid? Also, would you please open a new bug, and reference this one? With 91+ comments, these bugs tend to spiral out of control and cover way too many independent though possibly related problems. :-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
[Bug 120375] Re: cannot boot raid1 with only one disk
One additional comment on this; this bug will also prevent a system from booting if the array is reshaping (as opposed to missing a disk) -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
4 of the 5 bugs taged as duplicates use a separate home array, the fix will not let such systems boot degraded. WARNING: The mdadm - 2.6.7-3ubuntu2fix uses mdadm --assemble --scan on a system based on udev hotplugging. It will start all partly attatched arrays in degraded mode. When any members of the arrays that got degraded comes available (very likely for arrys that got started degraded only as a sideeffect) you risk Bug #244792 corrupting your data. (As long as ubuntu still uses --assemble --scan --no-degraded in the udev rule.) -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
I just noticed that with slowly-appearing drives (with md devices on it) the md device will not exist on the regular run of init-premount/mdadm. But since introducing another waiting loop into the coldplug driven boot does not make much sence it'll be preferable to just do degration with failure hooks after a full rootdelay. That means that with a degraded md array two wainting loops will have to time out. (the one in local-top/cryptroot and the rootwait in local) But this is now an issue of local and local-top/cryptroot. So the remaining list for package mdadm is down to the array degration of md devices on which the fstab depends in /etc/init.d/mdadm. BTW /usr/share/initramfs-tools/hooks/cryptroot contains code to determine cryptdevices that the rootdevice depends on. Similar approach may work to find md devices the rootdevice depends on. It may help to identify the particular arrays to degrade and solve this bug in a way that does not introduce new problems. -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
This bug was fixed in the package initramfs-tools - 0.92bubuntu7 --- initramfs-tools (0.92bubuntu7) intrepid; urgency=low * scripts/functions: - add_mountroot_fail_hook(): set up symlinks to hooks in tmp directory - try_failure_hooks(): new function that executes each fail hook in lexographic order, exiting successfully if a hook succeeds - panic(): remove the fail hook calling logic, now provided by try_failure_hooks() * scripts/local: - get_fstype(): FSTYPE must be initialized to unknown in case the fstype call does not set it - root_missing(): new function to provide the oft-called set of checks on the ROOT device - mountroot(): use root_missing(), and try the failure hooks before giving up * Fixes required for (LP: #120375), lots of help from Kees Cook, thanks! -- Dustin Kirkland [EMAIL PROTECTED] Fri, 25 Jul 2008 17:34:21 -0500 ** Changed in: initramfs-tools (Ubuntu) Status: In Progress = Fix Released ** Changed in: mdadm (Ubuntu) Status: In Progress = Fix Released -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
How can you install the solution. Tried a sudo apt-get -y update sudo apt-get -y upgrade -- 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 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
[Bug 120375] Re: cannot boot raid1 with only one disk
I think it can be understood that using mdadm --assemble --scan instead of
doing selective mdadm --run device calls on all devices ${ROOT} depends on
could be a reasonable and quick fix, if the information is not available
somwhere allready. Full support here.
My interest lies in getting the algorithm right, so that it will work
out for most if not all possible ways of udev,raid,crypt,lvm, etc.
stacked configs. And we won't hit a whole waterfall of subsequent bugs.
Also configuring selective arrays to be run or not run degraded might be
somthing that can be postponed. The list of md devices that are needed
to fully bring up a server or desktop system consists of the md devices
on which the devices listed in fstab depend on.
When a disk fails in a running system, it doesn't stop by default, and
probably should't. This is the reason for the mdadm notification
functionality. So defaulting to bootdegraded=yes seems reasonable, once
the patches are tested to work with enough configurations, and will be
safe if no other md devices than the ones neccessary to set up the fstab
are touched.
https://wiki.ubuntu.com/BootDegradedRaid updated
--
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
[Bug 120375] Re: cannot boot raid1 with only one disk
Thank you for your comments and I'm sorry me slowly commenting overlapped with
your updated patches. (Of course you just worked to fast ;-), and fixed things
beforehand, perfect. :)
It's good to see that happen, and I've seen the merrit of the while loop
in intrepid now. It looks much better than in hardy.
Yes, lets fix things avoiding immeadiate pittfalls.
Lets think crucial things like initramfs through while we are at it. I'll try
to shake the ends over here that together we'll get those bugs thoroughly out
of our puppy.
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.
${ROOT} may be the md device that needs to be run degraded in the corner
case of a non-partitionable, non-crypted, non-lvm, md device.
What you're talking about is going to be more complicated, and can be handled
at a later time, by subsequent patches.
Yes, initramfs setup doesn't seem to be easy to me. I'd like to make
much later work unneccesary.
How about opening a separate bug for independently
allowing/disallowing each array to be started in degraded mode?
It's more than that. For example the --incremental option is neccessary,
because there is this nasty Bug #244792 waiting, (For that reason I have
gathered all that in the BootDegradedRaid comments.)
---
I tested the changes and a crypted root does not yet come up degraded.
The init-premount/mdadm script is responsible to set up arrays. (the
local script depends on it) With udev+mdadm init-premount/mdadm doesn't
have to do more then register its mountfail hook and degrade arrays if
they are not available after a while, if requested.
init-premount/mdadm needs to degrade the array before local-
top/cryptroot.
I see two changes for package mdadm.
- in init-premount/mdadm:mountroot_fail() run the array degraded imediately
(implemented by ppa9). This will start degraded arrays that are made of several
_crypt devices, after the rootdelay.
- Regular degraded arrays should be run degraded directly in
init-premount/mdadm, if a while array not active slumber loop timed out. (not
yet implemented in ppa9)
Here is why:
With the second change local-top/cryptroot can find its source device.
Cryptsetup is not triggered by udev (and can not be, because non-luks
partitions can not trigger events), its run by local-top/cryptroot. It
doesn't make much sence to enter local-top/cryptroot with an inactive
array, only to let it fail and then wait rootdelay to see that mounting
the rootfs also fails and then try to recover with another rootdelay.
The rootdelay is there to wait for removable root devices. But encrypted
root devices won't show up.
(Its another bug 251164, but serves the understanding:
local-top/cryptroot fails even with full array present when the disk has not
triggerd an udev event. This is because cryptroot does not have its own
checking loop, just as mdadm does not have its own checking loop yet. Only
mounting root has its checking loop. Mixing one into another is not such a good
idea because dependencies get lost and no while condition is adequate for all
waiting involved.)
If a missing encrypted array member shows up 1 second into the rootdelay,
cryptroot can't set up the root device before the failure hooks kick in, the
root device won't show up for sure.
(And maybe we don't want the cryptsetup to be part of a loop with unlimited
trys.)
When instad mdadm waits for the raid device to become active,
local-top/cryptroot will start to set the root device up a second later and
rootdelay would exit immediately.
On my testing system (8.04) local-top/cryptroot is not run at all after
the array is degraded, and the root mounting fails. (cryptroot has no
failure hooks) Ok, cryptsetup is a different package producing the issue
at hand, but we are not yet done with package mdadm.
With manual cryptsetup and mounting of the rootfilesystem, the system
still did not come up degraded. The /home raid isn't set up. Of course
this part of cannot boot raid1 with only one disk can be dealt with
in /etc/init.d/mdadm-raid with a while array inactive delay loop.
---
When the confusion sets in, orchestred or not, recall.
Do stay on top. Fix the system, not the numberd bugs.
Orientation is your mastership.
--
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
[Bug 120375] Re: cannot boot raid1 with only one disk
From my perspective, what needs to happen is that the issue of booting from a degraded root on kernel software raid needs a simple, easy to implement fix for those who run fixed configuration machines, I.E. servers and the like. The provided patches seem to accomplish this goal with a boot parameter that an individual that administers/manages servers would be able to apply. Furthermore, it would be reasonable to me that the server distribution have that boot parameter set as a default to minimize the number of surprises. Someone running a server system is unlikely to be using external storage that is not for backup of some sort or some type of more reliable hardware configuration (SAS, SCSI etc...) and can be considered on their own recognizance for doing weird things like making a raid stripe of firewire drives or something bizarre like that. The issue of a desktop system booting with missing raid elements is another issue. The same workaround should be available for those who choose to run their root on software raid disks with the aforementioned caveats. It would of course be quite nice to have some sort of iterative y/n/r prompt sort of setup for filesystems listed in /etc/fstab so that a marginally technical user could interactively make a decision about continuing to bring the system up with degraded disks or a more technical user could set the kernel parameter, again at their own risk. This discussion, while absolutely necessary, is somewhat political and outside the scope of this bug and belongs in another bug if for no other reason than to close the bug and stabilize the distro for those who are running business functions on it. I am using Alexanders patch and will switch over to Dustin's as I have time. Thank you both for your contributions. -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
How can I apply 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
[Bug 120375] Re: cannot boot raid1 with only one disk
And this mdadm patch supercedes the previous one. It uses the new initramfs-tools interface for adding the fail hook. Updated package in my PPA: * https://launchpad.net/~kirkland/+archive :-Dustin ** Attachment added: mdadm.120375.debdiff http://launchpadlibrarian.net/16314962/mdadm.120375.debdiff -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
** Changed in: initramfs-tools Status: Confirmed = In Progress ** Changed in: mdadm (Ubuntu) Status: Triaged = In Progress ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) = Dustin Kirkland (kirkland) Status: New = In Progress ** Changed in: initramfs-tools Assignee: Dustin Kirkland (kirkland) = (unassigned) Status: In Progress = Confirmed ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided = Medium Target: None = ubuntu-8.10 -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
Testing instructions for Intrepid are available in a wiki page for a specification covering this bug: * https://wiki.ubuntu.com/BootDegradedRaid#head-a5a91db34505d4a047fd7f30e44ac2020da369a6 :-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
[Bug 120375] Re: cannot boot raid1 with only one disk
Hi, some feedback about the patches.
Does it matter if call_failure_hooks is allways called?
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.
This means of course we need to know the required array in initramfs.
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.)
A regular init.d script (like the former mdadm-raid or mdadm-degreade)
can handle the non-root startdegraded devices.
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.
The error output could be more informative:
Instead of Check rootdelay= (did the system wait long enough?)
--If rootdelay=${VARIABLE} is not long enough, customize kernel parameter.
I have updated the comments on
https://wiki.ubuntu.com/BootDegradedRaid#head-59fd70893e835c25f3c7a40741e1b24ad6066a64
--
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
[Bug 120375] Re: cannot boot raid1 with only one disk
After # We've given up, A while loop is calling panic. An if statement might look better. -- 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 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
[Bug 120375] Re: cannot boot raid1 with only one disk
initramfs-tools patch. :-Dustin ** Attachment added: initramfs-tools.120375.debdiff http://launchpadlibrarian.net/16293732/initramfs-tools.120375.debdiff ** Changed in: mdadm (Ubuntu) Status: Confirmed = Triaged -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
mdadm patch. :-Dustin ** Attachment added: mdadm.120375.debdiff http://launchpadlibrarian.net/16293729/mdadm.120375.debdiff -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
I have a pair of debdiffs which will be posted in the following two messages. One for mdadm, and a second for initramfs-tools. The mdadm patch supports an optional kernel parameter, which can be any of: * bootdegraded * bootdegraded=true * bootdegraded=yes * bootdegrade=1 If a RAID device containing the root filesystem fails to start, the mdadm failure hooks will eventually run. When they do, the kernel command line will be checked for a valid 'bootdegraded' flag. If it is set affirmatively, it will run: * mdadm --assemble --scan --run which will attempt to start the array in a degraded mode. I have also changed the printed error message to direct the user to use bootdegraded=true. For the failure hooks to execute before the init scripts bail out, I have a patch to initramfs-tools. Here, I split out the mountroot-fail.hooks code to its own independently callable function, call_failure_hooks(). And the panic() function conditionally invokes call_failure_hooks(). Furthermore, the local script invokes the call_failure_hooks() function *before* it gives up on finding the root device. I have packages available for testing in my PPA. * https://launchpad.net/~kirkland/+archive :-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
[Bug 120375] Re: cannot boot raid1 with only one disk
I successfully installed raid 1 on an Ubuntu Desktop 8.04 64-bit machine
according to Martiis intructions:
http://users.piuha.net/martti/comp/ubuntu/en/raid.html
The only thing missing in Martiis instructions was
sudo update-initramfs -u (thx to Alexander)
after inserting Kens lines
# The following code was added to allow degraded RAID arrays to start
if [ ! -e ${ROOT} ] || ! /lib/udev/vol_id ${ROOT} /dev/null 21; then
# Try mdadm and allow degraded arrays to start in case a drive has failed
log_begin_msg Attempting to start RAID arrays and allow degraded arrays
/sbin/mdadm --assemble --scan
log_end_msg
fi
into /usr/share/initramfs-tools/scripts/local script just before the
comment # We've given up, but we'll let the user fix matters if they
can as described in Kens posting.
--
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
[Bug 120375] Re: cannot boot raid1 with only one disk
This also affects raid5 (seems logical) but the patch doesn't seem to work for me when also using lvm. My test setup: sda1 100Mb /boot sda2 raid sdb1 100Mb (manual copy of /boot) sdb2 raid sdc1 100Mb (manual copy of /boot) sdc2 raid /dev/md0 is a raid5 using sda2/sdb2/sdc2, on that is a volume group 'vg' with 2 logical volumes 'lv0' which is / and lv1 which is swap. when removing a disk (lets say disk 3/sdc) I see the patch kick in and start the degraded raid5 with 2 disks but from there it's downhill: Found volume group vg using metadata type lvm2 ALERT! /dev/mapper/vg-lv0 does not exist. Dropping to a shell! but /dev/mapper/vg-lv0 and /dev/mapper/vg-lv1 DO seem to exist. Re- adding the drive and rebooting works fine, is this another 'feature' of the /usr/share/initramfs-tools/scripts/local script ? -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
Correct my if I'm wrong, but it looks like the patch file is not actually in /usr/share/initramfs-tools/scripts? If you downloaded the file to any other location, you need to specify the full path when executing patch. -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
I have created a patch for the initramfs-tools script as suggested by Ken in this comment: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/120375/comments/47 In order to apply it (as root), cd /usr/share/initramfs-tools/scripts, patch initramfs-mdadm-assemble-scan.patch, then update-initramfs -u. With an initrd patched in this manner, I was able to disconnect either of my harddrives and still boot my server without manual intervention. The patch does not address the generous wait for the missing harddrive, so give it some time. ** Attachment added: Patch for initramfs-tools as suggested by Ken on 2008-03-31 http://launchpadlibrarian.net/15929571/initramfs-mdadm-assemble-scan.patch -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
I have been fighting installing a RAID setup with 8.04 + GRUB for about 20 hours. My old setup used a CF card mounted as /boot but I can't get that to work with some newer hardware and with grub and 8.04. This worked fine under 6.x and 7.x... So I give up and set up a md RAID 1 partition as ext2 as /boot at the start of my disk, I get grub installed on both drives no problem and now I hit this. It took a long time to figure out what was going on as I thought it was hanging because the scripts take so long to time out... it needs to say something like waiting for root device to spin up if it hits the part of the script looking for a removable root device so you can quickly identify what is going on. I find it amazing that it has been going for a full year. The issue I have is that I am using RAID and redundant disks for my boot/root partition so that I can be hardware agnostic and not have to worry about getting the system up and going if I think my hardware RAID card is flaking out. If I can't boot the thing with a failed disk without having to google up the commands to get the array going it's just about worthless. If someone participating in this bug has a good description of how to get it to work automatically with 8.04 I would really appreciate it if they could post either the modified initramfs scripts or whatever it takes to get it working. -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
I added notes on how to adjust the ubuntu hotplug setup to cope with raid devices at: https://wiki.ubuntu.com/BootDegradedRaid See under Implementation. -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
So, just to summarize, we are stuck to ubuntu 7.10? I would like to upgrade to 8.04 for many reasons, but to risk to find myself with the same problem as before is unacceptable. Do you guys think situation will improve by the time of 8.10 ? Do you also find the following procedure suitable: 1) unplug 1 drive from RAID 1 2) update ubuntu from 7.10 to 8.04 with only one drive in the array 3) verify that everything works; if yes... 4) add the drive as spare and reassemble 5) No, upgrade is not good; then... 6) plug back the old drive and start the machine with that and reassemble the other as spare... Help? Suggestions? TIA -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
didn't a previous poster say that this works fine in the current Debian? So maybe the place to start is to identify what was changed from the 'base' Debian scripts, and why. -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
** Also affects: initramfs-tools Importance: Undecided Status: New -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
You are probably correct, that some changes may be needed to initramfs- tools. I will be working on this for Intrepid. See: * Blueprint: https://blueprints.edge.launchpad.net/ubuntu/+spec/boot-degraded-raid * Specification: https://wiki.ubuntu.com/BootDegradedRaid :-Dustin ** Changed in: initramfs-tools Assignee: (unassigned) = Dustin Kirkland (kirkland) Status: New = Confirmed ** Changed in: mdadm (Ubuntu) Importance: Undecided = Medium Assignee: (unassigned) = Dustin Kirkland (kirkland) Target: None = ubuntu-8.10 -- 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
