[Bug 120375] Re: cannot boot raid1 with only one disk
Comment 91 (https://bugs.launchpad.net/ubuntu/+bug/120375/comments/91) worked for me. I didn't need the extra lvm stuff but it can't hurt. I was booting from /dev/sdb1, which was the 'failed' drive from /dev/md0. In /etc/fstab, I had /dev/md0 als /, and it shows up as such in 'df'. But /dev/md0 was not really mounted as root; is was /dev/sdb1 altough it *says* it's /dev/md0. This is a bug I think. So I made the changes to the initramfs script, and did update-initramfs -u. BUT THAT HAPPENS ON /dev/sdb1 ! So I had to do this: mount -t ext3 /dev/md0 /mnt cd /mnt chroot . # Change the script in /usr/share/initramfs-tools/scripts/local ! the previous change was on /dev/sdb1 !!! update-initramfs -u exit # from the chroot reboot This took me ten hours or more (linux-haters !) Doesn't anyone think it's *really bad* that all 8.04 installs fail horribly when the root raid-array degrades !? Those machines won't boot at all when that happens ! And it's not going to be fixed in 8.04 ? How can this be !? -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
On Thursday 14 August 2008, RpR wrote: > This is a reason why a lot of system administrators that I know went > back to debian which doesn't have this behavior. For a LTS version it > should be fixed. It's extremely weird that the Debian distro doesn't have this bug (or behaviour) and Ubuntu has. But dapper didn't have it; so switching from dapper to hardy burns you -without- knowing it. Because your md's have been working great for years, and they where up when you upgraded. Now then, when one of your root disks fails, you feel safe - you get an email and go to the datacenter and try to reboot. Bummer. And I dare you to be able to bring it up again - it won't be easy unless you brought some instructions! The community brouhgt forward a possible solution within this thread - it's not that hard to fix, is it ? -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu 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
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
On Monday 18 August 2008, Ross Becker wrote: > One more comment on this; I can understand the "conservative" > behaviour, but when an array was degraded, the boot process halted with > NO MESSAGE indicating what was wrong. Please whatever you do, even in > the case of maintaining "conservative" behavior, emit a message telling > the user why you're not continuing the boot process. I totally agree. The system seems to hang at a certain point, and when you wait long enough (180s as far as I understand from this discussion) and then drops you into initramfs. I tried 999 different ways of modifying grub, fstab, mdadm.conf becasue I didn't know WHY the system couldn't boot. The fact was that I very well KNEW the array was degraded, too. A warning message would have helped tremendously. Also, since there is no message and no indication of what was wrong, I had a very hard time finding this thread. I almost exploded when I found the thread, saw it's age, and all the possible workarounds, and the fact that it is not a problem in Debian. This behaviour really and very strongly diminishes my trust in Ubuntu as a system for my servers. Just a question: have you any idea how many systems are affected? The popularity contest says: mdadm 25199 5566 19467 15610 -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 120375] Re: cannot boot raid1 with only one disk
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 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
** 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 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
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
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
[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
