[Bug 120375] Re: cannot boot raid1 with only one disk
This is a very old LP bug, but for completeness it worth mentioning here that recently some patches were merged on initramfs-tools and cryptsetup, that allow a good experience booting with LUKS-encrypted rootfs on top of a degraded RAID1 array; for details, please check: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980 Cheers, Guilherme -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
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 Bugs, which is subscribed to Ubuntu. 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/120375 Title: cannot boot raid1 with only one disk -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
[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 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
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
[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
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
Yeah, isn't 8.04 an LTS edition? My 8.04 Desktop machine suffers from this problem. I think I got it fixed by adding the command to assemble the arrays degraded to the initramfs 'local' script, but finding what needed to be done was a real PITA and I'm sure others will continue to hit this issue. Can't we get a fix in 8.04? -- 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
[Bug 120375] Re: cannot boot raid1 with only one disk
This bug has been fixed, and backported to hardy-updates. :-Dustin ** Changed in: initramfs-tools Status: Confirmed = Fix Released ** Changed in: grub (Ubuntu Hardy) Assignee: Dustin Kirkland (kirkland) = (unassigned) ** Changed in: initramfs-tools (Ubuntu Hardy) Assignee: Dustin Kirkland (kirkland) = (unassigned) ** Changed in: mdadm (Ubuntu Hardy) 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
[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 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
[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
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
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
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 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
** 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Has anyone tested the packages in Dustin's PPA? (Are the beers coming?) It would be really nice know before we place those in -proposed to follow the proper SRU process for 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
** Changed in: initramfs-tools (Ubuntu Hardy) Assignee: (unassigned) = Dustin Kirkland (kirkland) Status: Confirmed = In Progress ** Changed in: mdadm (Ubuntu Hardy) Assignee: (unassigned) = Dustin Kirkland (kirkland) Status: Confirmed = In Progress Target: None = ubuntu-8.04.2 ** Changed in: initramfs-tools (Ubuntu Hardy) Target: None = ubuntu-8.04.2 ** Also affects: grub (Ubuntu) Importance: Undecided Status: New ** Changed in: grub (Ubuntu Hardy) Importance: Undecided = Medium Assignee: (unassigned) = Dustin Kirkland (kirkland) Status: New = In Progress Target: None = ubuntu-8.04.2 ** Changed in: grub (Ubuntu) Status: New = 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
I think it's time for some tough love. No one would be taking the time to comment on this if they didn't want to see Ubuntu Server be a better product. I personally feel this is a significant issue for because it demonstrates Canonical's interest in supporting an LTS release and seriousness about becoming a presence in the server market. I know it can be difficult when people are lambasting a product you've put a lot of time into, believe me, I got more than my fair share of that this week. However, sometimes you have to step back and realize that your product quality has been lower than many people expect and you have to either step up or risk losing more customers. Make no mistake, this bug has lost a lot of sysadmins, some of whom had to fight hard to get Ubuntu onto servers in their workplaces in the first place. I was one of them, and I know a few more personally. I pitched that it made sense to have Ubuntu on the Server because of the benefits of the LTS release, including the longer support time and the large community that contributes to Ubuntu, therefore leading to more bugs being found and resolved. However, I doubt I will be able to propose Ubuntu again until version 10.04. If this bug were to be resolved in 8.04.2 I might at least start pitching it next year, barring any other bugs of this level of severity. To respond to Steve Langasek, while I understand that a lot of these emails are not terribly useful, this bug is exactly what the SRU team is supposed to be addressing. There have been many proposed fixes in this thread and 8 patches uploaded. Do any of them work correctly? Well that is the question, but it's inaccurate to state that this bug does not contain proposed fixes. Furthermore this fits the SRU criteria of being a high impact bug representing a severe regression from earlier versions and one which also may lead to a loss of user data. When the average user is confronted with the initramfs shell during a drive failure I suspect they have the potential to do serious damage to their file systems in an attempt to fix the problem. I don't feel it's possible for me to understate the severity of this bug and how badly sysadmins are going to react when they encounter it or read about it. It is certainly not the kind of bug one can dismiss in an LTS release if LTS is to say anything about quality, and hence suggestions to upgrade to Intrepid, while acceptable to a home user building a server, are not going to be acceptable in the workplace. If this is a market segment that Ubuntu Server is catered to than this issue needs to be addressed. If on the other hand Ubuntu Server is meant merely for enthusiasts with their home file servers than the solution should be to make sure that goal is clearly articulated. To keep us focused on the work at hand and to avail myself of the opportunity that having this number of people working for fix this bug represents I'll say that I've tried a number of solutions on this page but none have been satisfactory. I tried changing the udev rule as suggested above (see Plnt 2007-12-25) but got the same results that have been reported: I can get the system to boot any time the disk is degraded but at the expense that it boots degraded sometimes even when the disks are fine. This is the setting on my remaining Ubuntu servers (which will be migrated to Debian in the near future). This option is suboptimal but better than the default behavior. I would say that the ideal (and expected) behavior is for the system to boot in the case of a degraded array by default, with an option to turn that off if the sysadmin chooses. For those with Ubuntu servers, assuming this never gets fixed, I think an initramfs script (in /etc/initramfs- tools/scripts/) that anyone could copy onto their server might be ideal. Alternatively patching the mdadm udev script to try and start with --no-degraded and on failure use --run might also be an option. I have a server I may be able to user for testing but if anyone has a script to start with that would be great. -- 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
[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 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 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
[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
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
[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 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
[Bug 120375] Re: cannot boot raid1 with only one disk
Hello, I second RpR post word by word: it's sincerely hard to accept that such a serious bug is, not present until 7.04, is still open 14 months and 2 distros after, one of them being LTS. And this is even more true for the - arguably called - server edition: it's like putting on the market a TIR truck that has no double tyres and doing it twice. Dustin, could you please explain how do you run Hardy+RAID: it is still not clear to me after reading the whole thread, sorry. Thanks, brunus -- 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
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 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
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
Full ack to miguel. Why is somebody using a raid1 on his system. Does he want to have trouble, if a disk fails, or does he want a running system and to be informed about a hardware failue? Ubuntu raid is useless! The conservative mode is useless! If i had a 4 disk RAID1 system or a RAID5 with a spare disk and ONE fails. Is it useful to stop the boot process??? I have the same issue on my new system. First, I had one disk and decided to upgrade to software raid. With the second HD, I created a degraded raid1, copied the contents of the first disk to the second, and wanted to add the first disk to the raid. Ubuntu drops me into the shell. :-( And in spite of booting with a live CD and adding the first disk to the raid, the system refused to boot. Because it is a new system without any data on it, I will do a new installation with debian or suse. For my home server, I will see. -- 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
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
[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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120375] Re: cannot boot raid1 with only one disk
In my new installations of Alpha 4 this did not 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
[Bug 120375] Re: cannot boot raid1 with only one disk
In my new installations of Alpha 4 this did not 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
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
[Bug 120375] Re: cannot boot raid1 with only one disk
** Description changed:
+ The impact of the bug on users: Systems with root on a RAID array will
+ not be able to boot if the array is degraded. Usrs affected by this will
+ encounter an unusable system after a reboot (say, a kernel upgrade).
+
+ Justification for backporting the fix to the stable release: Hardy is a
+ LTS edition. It is expected that people will continue to use this
+ version and not upgrade to Intrepid. People who have upgrade from Dapper
+ LTS to Hardy LTS are affected too.
+
+ TEST CASE
+ Build a clean system with root on RAID, with Ubuntu 8.04 LTS. Degrade the
root array. Reboot and shiver.
+
+ A discussion of the regression potential of the patch and how users could get
inadvertently effected.
+ - the only users that could be affected, as fas as know, are the ones that
already made a workaround and altered their system files accordingly.
+
+
Binary package hint: mdadm
if i unplug one hd from raid1 i cannot successfully boot because raid
starts only if all disks are available through
: ${MD_DEGRADED_ARGS:= --no-degraded} in /usr/share/initramfs-
tools/scripts/local-top/mdadm
my workaround is:
/etc/initramfs-tools/hooks/startdegradedraid
#!/bin/sh
#
# Copyright C2A9 2006 Martin F. Krafft [EMAIL PROTECTED]
# based on the scripts in the initramfs-tools package.
# released under the terms of the Artistic Licence.
#
# $Id: hook 281 2006-12-08 08:14:44Z madduck $
#
set -eu
PREREQ=udev
prereqs()
{
echo $PREREQ
}
case ${1:-} in
prereqs)
prereqs
exit 0
;;
esac
MDADM=$(command -v mdadm 2/dev/null) || :
[ -x $MDADM ] || exit 0
DESTCONFIG=$DESTDIR/conf/md.conf
echo MD_DEGRADED_ARGS=' ' $DESTCONFIG
exit 0
--
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
[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
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 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
