sts the raid arrays as the command "blkid". Does it make any sense
to manually edit fstab to match the mdam UUIDs?
Since it seems you guys know more about the system than I do, please give me
some advice as soon as you find an answer. Thanks,
Rui Ruas
--
2.6.24-21 kernel update bre
It's me again! :-)
only to say that I'm currently using kernel 2.6.24-19-server x86_64.
Rui Ruas
--
2.6.24-21 kernel update breaks mdadm raid 1 boot
https://bugs.launchpad.net/bugs/290231
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
After reading about this on a few foruns, I think the problem is created
by mdadm. Have you tried manually editing the contents of fstab using
the output of "mdadm --detail --scan"?
--
2.6.24-21 kernel update breaks mdadm raid 1 boot
https://bugs.launchpad.net/bugs/290231
You received this bug no
Hi,
I left you a message in the ubuntuforuns, regarding the use of the UUID in the
grub "menu.lst", and re-reading the posts here I wandered if you already tried
to do the reverse: using the "old names" in everything instead of UUIDs (using
your "/dev/mapper/group0-linux" in fstab and grub).
Rui
tly. We were wondering is this still an
> issue for you? Can you try with latest Ubuntu Intrepid release? Thanks
> in advance.
>
>
--
*Rui Ruas*
[EMAIL PROTECTED]
Tlm: 962915270
Evite imprimir emails, protej
** Attachment added: "logo_mail.jpg"
http://launchpadlibrarian.net/17900982/logo_mail.jpg
--
mdadm fails to stop RAID on shutdown
https://bugs.launchpad.net/bugs/111398
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I also confirm this problem. My ubuntu feisty 64 fails to stop three of
four raid arrays on shutdown. While booting I receive an error message:
mdadm can't find the raid arrays in conf file, but after that it boots
fine with all arrays working and synchronised. (???)
--
mdadm fails to stop RAID o
