With UUID-based raid assembly that does not rely on mdadm.conf
maintanance this is not an issue. Bug #158918
** Summary changed:
- mdadm software raid breaks on intrepid-jaunty upgrade
+ [->UUIDudev] mdadm software raid breaks on intrepid-jaunty upgrade
--
[->UUIDudev] mdadm software raid bre
Continuing with my 8/31 2009 post, I erased the disks and reinstalled
9.04. Still had problem. Reading the mdadm wiki, kernel detection and
assembly of arrays is considered deprecated, and only works with version
0.9 superblocks anyway. I use version 1.2 superblocks so that they are
near the sta
The title definitely happened to me.
System boots off of a simple, separate disk.
Two 500GB disks (sdb, sdc) were mirrored with md, then a VG created, a LV, and
ext3 on top. Simple, worked great. /etc/mdadm/mdadm.conf did NOT list the
configuration, but rather depended on a scan to figure it a
The title definitely happened to me.
System boots off of a simple, separate disk.
Two 500GB disks (sdb, sdc) were mirrored with md, then a VG created, a LV, and
ext3 on top. Simple, worked great. /etc/mdadm/mdadm.conf did NOT list the
configuration, but rather depended on a scan to figure it a
I still have this problem - appeared after jaunty upgrade.
The machine with 3 disks in raid5 fails to assemble the array upon
startup. I have not found a solution to this problem (mdadm --examine
--scan --config=mdadm.conf >> /etc/mdadm/mdadm.conf) and others do not
appear to work in my case.
The
FYI
i had a similar problem upgrading from 8.10 to 9.04
boot failure occurs after loading mdadm
so i logged into the maintenance console and used the command supplied
by the OP.
mdadm --examine --scan --config=mdadm.conf >> /etc/mdadm/mdadm.conf
this command added the necessary lines to mdadm.
Had similar problem here (RAID 1, upgrade to 9.04, and fail to boot).
Tried to boot from one of my older kernels, and realised that the
upgrade process had removed most of my historic kernels on the boot
drive.
The realised I was still booting from kernel 2.6.27-14, but that I now
also had 2.6.28
Davias,
Thanks for your report! It's good to know it's not a blatant and consistent
problem. For help fixing your md3, however, please post a request on the
Ubuntu forums -- probably the Server Platforms group is best,
http://ubuntuforums.org/forumdisplay.php?f=339
If you figure-out what spec
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
fine
*** This bug is a duplicate of bug 314879 ***
https://bugs.launchpad.net/bugs/314879
Why is this marked as a dupe of bug #314879 when that bug was fixed back
in January and people are still experiencing this with 9.04 'Gold' ?
--
mdadm software raid breaks on intrepid-jaunty upgrade
https:/
*** This bug is a duplicate of bug 314879 ***
https://bugs.launchpad.net/bugs/314879
Same problem for me. I have described my symptoms and solution at
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/136252/comments/5
as it was configuration related.
--
mdadm software raid breaks on int
*** This bug is a duplicate of bug 314879 ***
https://bugs.launchpad.net/bugs/314879
I do not think this is a duplicate, even though this bug is marked as
such currently. As soon as I added a proper entry in
/etc/mdadm/mdadm.conf for my /dev/md2 device and rebooted, everything
came back up as
*** This bug is a duplicate of bug 314879 ***
https://bugs.launchpad.net/bugs/314879
** This bug has been marked a duplicate of bug 314879
root on LVM broken since latest udev 136-2
--
mdadm software raid breaks on intrepid-jaunty upgrade
https://bugs.launchpad.net/bugs/330298
You receiv
I'm not sure yet if my problem is caused by the same bug, but my /home
which is on an "md" (raid 1) device doesn't get mounted automaticly
anymore since I upgraded to jaunty.
The strange thing is: at least sometimes I could see the md device
assembled when I looked at it, but /home wasn't mounted.
I don't think this is a duplicate bug of #332270. #332270 is about a
problem in udev rules while this one is clearly an mdadm packaging
problem (packages should *not* silently override files in /etc.
Especially if the consequence is that they remove your RAID arrays.)
I was hit by this bug too and
*** This bug is a duplicate of bug 332270 ***
https://bugs.launchpad.net/bugs/332270
** This bug has been marked a duplicate of bug 332270
udev repeatedly generates "change" events for the same block device(s)
--
mdadm software raid breaks on intrepid-jaunty upgrade
https://bugs.launchpa
There is nothing I could do about it. The old kernel gave me a busybox
shell but I did not manage to do anything. The new kernel did not even
offer this option :( . I will try from a chrooted cd to see what I can
do. I have a RAID + LVM setup for my pc.
--
mdadm software raid breaks on intrepid-
I have the same problem here. After upgrading to 9.04 yesterday the
system does not boot (it hangs after discovering the disks). It does not
boot even with the old kernel. I have not tried the above solution yet,
but it seemed to me that there was a problem with mdadm.
--
mdadm software raid brea
18 matches
Mail list logo
