Thank you for updating this. Can you please run the apport-collect
command as detailed in my last comment. This will give us most, if not
all the debugging information the developers will need, although what
you have provided so far has been great. Thank you.
** Summary changed:
- [gutsy] mdadm,
Confirming that the problem still exists in Karmic.
If /etc/mdadm/mdadm.conf does not contain an ARRAY line, the system will
not boot from an md array.
If I run mdadm --auto-detect from the recovery console md0 is created
without needing the ARRAY line.
--
[gutsy] mdadm, initramfs missing
After doing a bit of digging it looks like the arrays are built using
the --incremental option to mdadm, specifically with following UDEV
rule:
SUBSYSTEM==block, ACTION==add|change, ENV{ID_FS_TYPE}==linux_raid*, \
RUN+=/sbin/mdadm --incremental $env{DEVNAME}
Here is my not-working
Returning to Incomplete.
Can someone please provide the requested information and let us know if this is
a problem in the latest Ubuntu release (Karmic), and if so, please run
apport-collect 136252 without quotes and let it pull in the required
debugging information.
Thank you.
** Changed in:
Current state of ubuntu systems with md raid:
https://wiki.ubuntu.com/ReliableRaid
--
[gutsy] mdadm, initramfs missing ARRAY lines
https://bugs.launchpad.net/bugs/136252
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
After updating to 9.04, I experienced a similar problem.
I have three md devices: md0 (/dev/sd{a,b}1, swap), md1 (/dev/sd{a,b}2, root),
and md4 (/dev/sd{a,b}3, home). On boot, mdadm would incorrectly detect that
/dev/sda was an md device and create it. Upon inspection (using mdadm -E),
Marking this bug as Triaged as there should be enough debugging information
here for a developer to begin working on it. Please provide them with any
information they need if requested. High importance set - problems with disk
controller(s).
If anyone has Jaunty and this problem, would you run
Thank you for providing a solution - I printed the page and started to
update from 8.10 to 9.04 on AMD64 with /, /home and swap on md0, md1
md2 on RAID1, plus a RAID0 on md3 using two spare partitions on my 2
SATA disks.
But... The upgrade just went as smooth as silk! The system booted just
After the update to 9.04 I had the same problems but could build the md
devices in the emergency shell and resumed booting with:
# mdadm --assemble --scan;exit
Today I found the fix. I removed the duplicated definitions of the
arrays in mdadm.conf with the output of:
# mdadm --detail --scan
Hey, I set the HOMEHOST line in my mdadm.conf and it worked like a
charm. Thanks so much for posting this. BTW this seems to be a
duplicate of https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/226484
When can we get a fix to this released? This is pretty unacceptable
behavior, and there are
I had a similar problem when attempting to move my root filesystem onto
a RAID-1 configuration.
mdadm wouldn't assmble the array while the initramfs was mounted, but
would when the normal root filesystem was mounted.
My mdadm.conf looks to be similar to those described, with a DEVICE
partitions
I had the same problem when converting from one disk to a RAID-1 setup.
I added a break=mount and tried to start the arrays with mdadm -A -s,
but that didn't work.
The default configuration has a line DEVICE partitions in
/etc/mdadm/mdadm.conf. This apparently doesn't work.
(All my partitions
Subscribing to bug
--
[gutsy] mdadm, initramfs missing ARRAY lines
https://bugs.launchpad.net/bugs/136252
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
13 matches
Mail list logo
