On many of my systems, the assignment of drives to letters depends on a
number of unpredictable factors, so it's much safer to use the UUID to
define arrays than /dev/sd[a-z]1.
Running sudo mdadm --detail --scan usually gets you pretty good ARRAY
lines to put into your mdadm.conf file.
--
You
@tombert, your bug is different than this bug. Please do open another
bug for the same and run apport-collect for it. Thanks!
--
mdadm update is scaring me: YOUR SYSTEM IS NOW UNBOOTABLE!
https://bugs.launchpad.net/bugs/652327
You received this bug notification because you are a member of Ubuntu
@whoop, will you please do the following:
1) copy your mdadm.conf somewhere safe
2) run /usr/share/mdadm/mkconf and see if the definition of md0 is in place. If
so please use generate with mkconf to generate a new mdadm.conf.
While updating initramfs, the mdadm's initramfs hook expects that the
/usr/share/mdadm/mkconf gives me:
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE /dev/sdb1 /dev/sdc1
#
Does affect me as well - here are the steps to reproduce:
Fresh install of Ubuntu Desktop 10.10, performing all online updates - reboot
works fine. Then install mdadm the system does not boot any more:
mount: mounting /dev/disk/by-uuid/ on /root
failed: Device or resource busy
...
...
No
This bug is a real killer - please put this to your highest prio or please give
some workarounds!
thx
--
mdadm update is scaring me: YOUR SYSTEM IS NOW UNBOOTABLE!
https://bugs.launchpad.net/bugs/652327
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Here the steps to rescue the system:
Boot with the live CD.
Mount the hard-disc:
mount /dev/sda1 /mnt
Mount system folders into sda1:
mount –t proc none /mnt/proc
mount –o bind /dev /mnt/dev
mount –o bind /sys /mnt/sys
Change the apparent disk root directory:
chroot /mnt
Now delete all
Tombert: I think you are suffering from another problem than I am trying
to describe in this bug report I assume this as your problem is an
unbootable system, me problem is that it boots just fine...
--
mdadm update is scaring me: YOUR SYSTEM IS NOW UNBOOTABLE!
Found another possibility to make the system start:
from the modules file:
/lib/modules/kernel/modules.*
remove all occurances which load raid libraries - they include the path
.../md/...
then run:
depmod
then run:
update-initramfs -u
the system boots again.
I'am trying to manually assemble
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/652327/+attachment/1658870/+files/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/652327/+attachment/1658871/+files/CurrentDmesg.txt
** Attachment added: Dependencies.txt
10 matches
Mail list logo
