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

  • Wordpress overwrites and wipes out custom htaccess rules and changes soluton
  • Apache htaccess and mod_rewrite how to redirect and force all URLs and visitors to the SSL / HTTPS version
  • python 3 pip cannot install mysql module
  • QEMU-KVM won't boot Windows 2016 or 2019 server on an Intel Core i3
  • Virtualbox vbox not starting "No suitable module for running kernel found"
  • Bind / named not responding to queries solution
  • Linux Mint How To Set Desktop Background Image From Bash Prompt CLI
  • ImageMagick Convert PDF Not Authorized
  • ImageMagick Converted PDF to JPEG some files have a black background solution
  • Linux Mint Mate Customize the Lock screen messages and hide username and real name
  • Ubuntu/Gnome/Mint/Centos How To Take a partial screenshot
  • ssh how to verify your host key / avoid MIM attacks
  • Cisco IP Phone CP-8845 8800/8900 Series How To Reset To Factory Settings Instructions
  • ls how to list ONLY directories
  • How to encrypt your SSH private key file id_rsa
  • Linux Mint 18 Disable User Name List from showing on Login Screen
  • Firefox Cannot Hit Enter Key In Address Bar and Location History Not Working
  • Cisco Unified Communications Manager / CUCM IP 8.6,10,12 Install Error Solution
  • Ubuntu Debian Mint Linux SSHD OpenSSH Server Not Starting After Reboot Solution
  • nmap how to scan for all ports and not just the 1000 most common ports