Ubuntu 10.04/GRUB2 mdadm won't boot

Moving to RAID was a pain.
What you have to do is the following from an existing install:

Install mdadm


Create your mdadm RAID 1 array on your spare hard drive.
Start it with the missing disk.

rsync the entire contents of your current / to the md partition.

Here's a good way of doing it:

rsync -Pha --exclude=/proc/* --exclude=/sys/* --exclude=/mnt/* /. /mnt/md2

"/mnt/md2" is the mount point of the md array I want to boot from.

*Note the "/." at the end, the . makes sure that all hidden files will be copied (weirdly enough rsync and other commands will IGNORE and NOT copy hidden files without specifying the .)  Do not specify a ".*", bad and unexpected things copy/happen when you do that.

chroot into your mdadm partition:

mount -o bind /proc /mnt/$path/proc
mount -o bind /dev/ mnt/$path/dev
mount -o bind /sys /mnt/$path/sys
chroot /mnt/$path

You'll need to setup /etc/mdadm/mdadm.conf

sudo mdadm --detail --brief /dev/md0 >> /etc/mdadm/mdadm.conf

You'll need to install grub on the actual hard drive

Use the correct device name for your RAID drives (for me it is sdb and sda).

*Note it's not the actual device such as /dev/sda1, it's just the drive device name alone (GRUB 2 does the rest by default).


grub-install /dev/sdb

grub-install /dev/sda

We run "update-grub" so that the UUID for your mdadm RAID array is specified when booting (otherwise booting will fail and you'll be frustrated/stressed out-that's how this guide was created).

update-grub

Update your initramfs with "update-initramfs -u".
exit chroot
unmount your /mnt/$path/*

reboot and it should work.

*Often it seems initramfs does not get mdadm added to it UNLESS mdadm is freshly installed in the chroot environment.  To be sure remove mdadm and then reinstall it and that should make 100% mdadm is added.  Just running update-initramfs has not always worked for me.

*One problem I had is that at one point my OS install called my md0 /dev/md_d0 for some reason.  Even so my /etc/mdadm/mdadm.conf referred to it as md0.  Yet grub set the root as being "root=md_d0" and this caused booting/mounting to fail until I set it back to "root=UUID=".

 


Tags:

ubuntu, grub, mdadm, bootmoving, raid, existing, install, array, disk, rsync, contents, md, partition, pha, exclude, proc, sys, mnt, quot, mount, copied, weirdly, commands, specifying, specify, chroot, bind, dev, ll, etc, conf, sudo, sdb, sda, default, update, uuid, specified, booting, frustrated, stressed, initramfs, unmount, reboot, freshly, installed, reinstall, os, md_d, referred, mounting,

Latest Articles

  • FreePBX 17 How To Add a Trunk
  • Docker Container Onboot Policy - How to make sure a container is always running
  • FreePBX 17 How To Add Phones / Extensions and Register
  • Warning: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes. solution
  • Cisco How To Use a Third Party SIP Phone (eg. Avaya, 3CX)
  • Cisco Unified Communication Manager (CUCM) - How To Add Phones
  • pptp / pptpd not working in DD-WRT iptables / router
  • systemd-journald high memory usage solution
  • How to Install FreePBX 17 in Linux Debian Ubuntu Mint Guide
  • How To Install Cisco's CUCM (Cisco Unified Communication Manager) 12 Guide
  • Linux Ubuntu Redhat How To Extract Images from PDF
  • Linux and Windows Dual Boot Issue NIC Won't work After Booting Windows
  • Cisco CME How To Enable ACD hunt groups
  • How to install gns3 on Linux Ubuntu Mint
  • How to convert audio for Asterisk .wav format
  • Using Cisco CME Router with Asterisk as a dial-peer
  • Cisco CME How To Configure SIP Trunk VOIP
  • Virtualbox host Only Network Error Failed to save host network interface parameter - Cannot change gateway IP of host only network
  • Cisco CME and C7200 Router Testing and Learning Environment on Ubuntu 20+ Setup Tutorial Guide
  • Abusive IP ranges blacklist