Changes

type "sme rescue" at the command prompt and hit enter

type "sme rescue" at the command prompt and hit enter

Note: don't start the network and skip mounting the filesystem. If you are on a newer board the disk may show up on /dev/sdx so the reference to hdx2 should be changed to sdx2; where you need to change "x" to the appropriate letter to match the the disk.

{{Note box|don't start the network and skip mounting the filesystem.}}

Note: when you do the "lvm vgscan" the LVM name should be "main" thus the value "orig_vg_name" should be "main". If it is different then use the appropriate LVM name.  

{{Note box|If you are on a newer board the disk may show up on /dev/sd'''x''' so the reference to hdx2 should be changed to sd'''x'''2; where you need to change "'''x'''" to the appropriate letter to match the the disk.

  mdadm -AR /dev/md5 /dev/hdx2

 

  mdadm -AR /dev/md5 /dev/'''hdx'''2

  lvm vgscan

  lvm vgscan

  lvm vgs -v

  lvm vgs -v

  exit

  exit

Now remove the CD and reboot. In most cases you won't need the mdadm, vgscan, vgchange commands below but they won't hurt. If you get an error with mdadm in regards to md5 being busy it is likely because your drive was automatically mounted. If the mount command works and you can see your data on it then it worked.

Now remove the CD and reboot.

 

{{Note box|In most cases you won't need the mdadm, vgscan, vgchange commands below but they won't hurt. If you get an error with mdadm in regards to md5 being busy it is likely because your drive was automatically mounted. If the mount command works and you can see your data on it then it worked.

NOTE: don't forget that "new_vg_name" references below should be whatever you used above.

don't forget that "new_vg_name" references below should be whatever you used above.}}

  mdadm -AR /dev/md5 /dev/hdx2

  mdadm -AR /dev/md5 /dev/'''hdx'''2

  vgscan

  vgscan

  vgchange -a y new_vg_name

  vgchange -a y new_vg_name