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/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
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
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
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
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
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
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
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
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
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
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
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:
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
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
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
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
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
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
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
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,
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
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,
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
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,
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
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,
** 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
** 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
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,
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
** 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 =
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,
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
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
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.
*
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
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
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
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
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.
*
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
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
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
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
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
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
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
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.
--
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'
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
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
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
/\
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
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
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
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'
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
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
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
/\
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
** 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
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
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
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
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
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
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
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
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
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
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
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
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
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
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.
--
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
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
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
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
1 - 100 of 230 matches
Mail list logo
