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

  • How To Force Flash an AMD Instinct GPU To Another Model Using Debian Ubuntu Mint Linux
  • How To compile ollama from source to use unsupported AMD GPU with rocm in Ubuntu Debian
  • QEMU KVM Virtio GPU Windows Cannot Select 1080P
  • Linux Gnome Desktop Ubuntu Mint Debian Gets Slower After Weeks
  • Firefox How to Save Full Page As Screenshot/PDF
  • Nvidia Datacenter Driver Tesla Slow nvidia-smi response and high utilization with 0 usage
  • ffmpeg how to normalize / increase the volume of your audio
  • kdenlive audio blips pops cracks artifacts solution fix
  • haproxy / nginx certbot SSL issues
  • nginx how to see the real IP when behind a CDN
  • Docker how to find real container child process ID
  • Alibaba Aliyun how to reset password solution 'Setup does not meet the requirements, please resetting'
  • RTL88X Series 80Mhz hostapd mode for Linux Debian Kali
  • How To Deploy Your Own Mastodon Server in Docker
  • ffmpeg burning subtitles in non-English errors [Parsed_subtitles_0 @ 0x561d3a0b3b80] Glyph 0x6709 not found, selecting one more font for (Sans, 700, 0)
  • rsyslog in container config
  • Interesting Whisper AI CPU vs GPU Test
  • How to install pytorch with cuda capability for AI acceleration with Nvidia Tesla etc.. GPUs
  • How to Spider the web archive.org to recover your old website/webpage
  • Debian 10 /etc/apt/sources.list