This doesnt look fixed for me too.
I run a software raid and the "solution" posted by Josh is the only one which
is working in my case.
I have a software raid5 and my root partition is not part of the array.
I get the "Raid is degraded" warning in about 90% of my reboots.
--
You received this
Hi,
This fix does not work for me. I have a system with a single md raid 5 array
with 5 disks, and root on a seperate non-raid disk. With the default
bootdegraded=false my system frequently drops to the initramfs prompt with the
usual timed out message. With BOOT_DEGRADED=true set in the mdad
The patch of
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/942106/comments/5
does not work in following case:
- Ubuntu 12.04
- partitionable RAID-1 on two complete disks sda and sdb, giving array md0.
Root partition is md0p1, swap partition is md0p2.
- One disk physically removed
BTW. My RAID 5 is perfectly healthy and can be assembled after booting
process is finished. crypttab decrypts the devices automatically using
key files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/94
12.04.1 with all updated.This bug still affects me too!
My setup is the following: 4 LUKS encrypted partitions with mdadm RAID5
on top. The reason I encrypted first and then added them into the array
was based on performance: 4 threads doing encryption/decryption instead
of just 1. The max speed o
@Brian, Dmitrijs:
Thanks.
I have filed Bug # 1036366 to report the symptoms not resolved by this
recent fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942106
Title:
software raid doesn't assem
This bug was fixed in the package mdadm - 3.2.5-1ubuntu0.2
---
mdadm (3.2.5-1ubuntu0.2) precise-proposed; urgency=low
* Patch udev-md-raid.rules to not auto-start arrays based on detection
of ddf or isw (imsm) signatures; this conflicts with dmraid usage in
precise and requi
@Doug:
The correct command is 'sudo ubuntu-bug mdadm' or 'sudo apport-bug
mdadm'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942106
Title:
software raid doesn't assemble before mount on boot
To
@Dmitrijs:
sudo apport mdadm does nothing. I know that apport is installed and the
service is running. Am I doing this wrong?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942106
Title:
software
@Dmitrijs:
I must agree with your assessment. I cannot really tell which (of many)
existing bug reports are most relevant to my system, so I've been
chiming in on a bunch of them, just in case they provide clues helpful
to others :-)
This latest mdadm update does not have any negative impact on
@Doug Jones (djsdl)
This bug report is not meant to fix *all* issues with raid, with respect
to booting. Previously booting would drop into initramfs too quickly,
now we wait for udev events to be processed and then we drop to
initramfs. So this particular bug fix is fixing just this issue. You do
This does NOT fix this issue for me.
My system still boots up with some RAID arrays not running. Every
single time.
This system has six SATA drives on two controllers. It contains seven
RAID arrays, a mix of RAID 1, RAID 10, and RAID 6; all are listed in
fstab. Some use 0.90.0 metadata and so
It fixes the issue for me.
Ever since I have installed this version, this problem has disappeared.
Previously, one over 3 boot did fail to assemble the software RAID
volumes.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Jean-Philippe, Håvar, are either of you able to confirm that the mdadm
in precise-proposed fixes this issue for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942106
Title:
software raid doesn't
Hello Håvar, or anyone else affected,
Accepted mdadm into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/mdadm/3.2.5-1ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942106
Title:
software raid doesn't assemble before mount on boot
To manage notif
The 3.2.5-1ubuntu0.1 package fixes the problem for me through three
reboots. I reported duplicate bug #776908 and was experiencing the
problem consistently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
I have had similar failure on all versions of precise on my Asus M4A785
with AMD X4 9850 with one drive on SiI 3132 Serial ATA Raid II
Controller Boot from IDE drive and 6 SATA drives in raid5. Every boot
failed with initramfs stop into busybox. Installing precise.proposed
version of mdadm versi
Mark Ovens, you could do a test of:
1) connecting, assembling and mounting MD-ADM raid
2) $ sudo update-initramfs -u
3) reboot a couple of times and check if the boot succeeds each time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I only use the mdadm array for data, i.e. I don't boot from them. I was
originally subscribed to one of the duplicate bugs. The problem I had
was that booting would stop with a message about the disks not being
ready and the option to 'S'kip or 'M'anual.
To work round this I added the `noauto` opt
Mark Ovens - could you please provide some detailed information
regarding the testing that you did so that we can release the update to
everyone? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
This has fixed the bug for me - thanks to the devs for doing the work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942106
Title:
software raid doesn't assemble before mount on boot
To manage noti
Hello Håvar, or anyone else affected,
Accepted mdadm into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/mdadm/3.2.5-1ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
** Changed in: mdadm (Ubuntu Precise)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942106
Title:
software raid doesn't assemble before mount on boot
To mana
...
* Upgrade to the -proposed package
...
This bug was fixed in the package mdadm-3.2.5-1ubuntu1
...
How to upgrade to a fixed version? install mdadm-3.2.5-1ubuntu1 from
PPA?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Dmitrijs: What's the state of this SRU? will it make it to the point
release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942106
Title:
software raid doesn't assemble before mount on boot
To mana
** Description changed:
- Booting a system with a software raid device can randomly or systematically
- fail.
+ [IMPACT]
- The system boot will fail at the initramfs stage and the system complain
- that it can't find the software raid device.
+ * Due to small time-outs udev may not detect all
** Changed in: mdadm (Ubuntu Precise)
Milestone: None => ubuntu-12.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942106
Title:
software raid doesn't assemble before mount on boot
To manage
Although this is fix released, it's just an improvement by waiting for
udev to settle.
Further improvements to RAID reliability will be done as part of:
https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-software-raid
--
You received this bug notification because you are a member of Ubu
This bug was fixed in the package mdadm - 3.2.5-1ubuntu1
---
mdadm (3.2.5-1ubuntu1) quantal; urgency=low
* Merge from Debian testing. (LP: #920324) Remaining changes:
- Call checks in local-premount to avoid race condition with udev
and opening a degraded array.
- d/i
** Also affects: mdadm (Ubuntu Quantal)
Importance: High
Assignee: Dmitrijs Ledkovs (dmitrij.ledkov)
Status: Confirmed
** Also affects: update-manager (Ubuntu Quantal)
Importance: Medium
Assignee: Michael Vogt (mvo)
Status: Fix Released
** Also affects: mdadm (Ubuntu
** Branch linked: lp:~dmitrij.ledkov/ubuntu/quantal/mdadm/merge
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942106
Title:
software raid doesn't assemble before mount on boot
To manage notificatio
The Debian mdadm scripts uses an explicit assembly in initramfs and
seems to offer a lot more of fallback logic than we currently have.
Also, udev settle makes you wait for devices that might not be
necessary for boot.
The full Debian mdadm initramfs logic seems to be a good alternative
to the cu
Setting multiple md arrays seems to be a good way to reproduce this bug
(see #682019). Or maybe just a big md array.
After that, it's just a timing issue. After rebooting several times, you will
probably run into this issue.
--
You received this bug notification because you are a member of Ubunt
I'm still trying to reproduce/test this bug.
By the looks of it, adding wait_for_udev call is sensible.
On the other hand, udev incremental assembly has been disabled in a debian
patch, which we inherited.
I am going to suggest dropping that patch & allow incremental udev assembly in
mdadm packag
** Changed in: mdadm (Ubuntu)
Assignee: (unassigned) => Dmitrijs Ledkovs (dmitrij.ledkov)
** Changed in: mdadm (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
I believe that any disk listed on the fstab failing to mount will lead
to the dreaded initramfs console.
** Description changed:
- Booting from a software raid device can randomly or systematically fail.
+ Booting a system with a software raid device can randomly or systematically
+ fail.
T
It is not just booting from a software raid, I have never tried that.
For me, it was enough that I had a software raid in my computer. I was
booting from an SSD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Description changed:
+ Booting from a software raid device can randomly or systematically fail.
+
+ The system boot will fail at the initramfs stage and the system complain
+ that it can't find the root device.
+
+ The user ends up on the initramfs console. Rebooting might solve the issue
+ (
** Summary changed:
- mdadm-functions missing udevadm settle (?)
+ software raid doesn't assemble before mount on boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942106
Title:
software raid does
40 matches
Mail list logo
