This is a bug with mdadm --incremental not doing hotplug, because it looks for
permission to do so in mdadm.conf.
On hotplug systems mdadm.conf should not have contain any specific references,
maybe it should explicity mention "any" like this:?
DEVICE
HOMEHOST
ARRAY
This whole bussiness o
for your information :
grub-install /dev/md0 just crashed my installation.. seems it's really NOT
a good idea.
server keeps on doing bios -> loading grub -> bios ->
--
boot from manually constructed raid1 root fails because of missing hostname in
initramfs
https://bugs.launchpad.net/bu
This issue is really a matter of process and configuration.
I'm converting it from a bug, to a question/answer.
Cheers,
:-Dustin
** Changed in: mdadm (Ubuntu)
Status: Confirmed => Invalid
** bug changed to question:
https://answers.edge.launchpad.net/ubuntu/+source/mdadm/+question/638
Okay, I've spent a little more time on this, and I think there is a lot
more involved from a configuration perspective to manually take a non-
RAID system to a root-on-RAID1 system.
Here are the steps I was able to use in a Jaunty KVM to get this to
work.
Install Jaunty into a KVM, and boot it wi
** Summary changed:
- boot from raid1 root fails because of missing hostname in initramfs
+ boot from manually constructed raid1 root fails because of missing hostname
in initramfs
--
boot from manually constructed raid1 root fails because of missing hostname in
initramfs
https://bugs.launchpa
