Recovery Is Possible Linux rescue system (RIP)

• Home Page: http://www.tux.org/pub/people/kent-robotti/looplinux/rip/
  • Note - it now appears that the RIP project is no longer being maintained - we will replace this with a cramfs based ram live boot image of Ubuntu shortly
  • We have local copies of 13.7 on asimov
• Local resources:
  • asimov:/images/rawiso/linux_utils/RIP - ISO images of RIP
  • ASIMOV Vlan 420 PXE boot option
• NOTE: if you don't have network access to asimov the GUI will come up very slowly!

Booting

• PXE booting
• CD booting

using GUI tools

When using gui tools (eg: Ghost or Avast), choose one of the "Boot to X!" options, eg: "Boot Linux system to X! (skip keymap prompt)"

Local modifications

* We created a tool to repackage RIP with extra tools found useful. These include:

Avast antivirus

• Avast Avast anti Virus

Ghost

• Ghost See: ImageDeploymentGhost

ubuntu-scripts

• See: UbuntuScripts

reg

• • reg - a script to assist restoring registry settings from Windows restore points
    1. ) Mount the windows partitions - hint use fdisk -l to view the partitions
       • Note: the registry files are located in \WINDOWS\system32\config
    2. ) cd "System Volume Information"
    3. ) cd _restore*
    4. ) look at the dates of the RPnn files where nn is a number
    5. ) example: we want to think things were ok on the dat listed by say RP2
       • cd RP2
       • make sure there is a snapshot directory otherwise pick another RP directory
       • cd snapshot
    6. ) run the reg command: ./reg
       • This will create a backup of the current WINDOWS\system32\config registry files
       • It will copy/rename the restore point registry files to the WINDOWS\system32\config directory

RAID

MDADM

• External References:
  • http://www.linuxquestions.org/questions/linux-software-2/recovering-data-from-remaining-raid-1-disk-723225/

1. ) References: http://ubuntuforums.org/showthread.php?t=408461
2. ) Assemble a raid array: mdadm --assemble /dev/md0 /dev/sda1 /dev/sdb1
   • • • Note: the disks actually have the metadata required to know how they work together - hence not required on the mdadm command line.
3. ) stop array: *mdadm --stop"

LVM LVM2

http://linux-sxs.org/storage/fedora2ubuntu.html

• Load the necessary module(s):
  • modprobe dm-mod
• Scan for LVM volumes, identify the group you want (ex: VolGroup00):
• vgscan
• Activate the volume:
  • vgchange -ay VolGroup00
• Find the logical volume with root in it (ex: vg_root ):
  • lvs
• Create a mount point for that volume:
  • mkdir /mnt/root
• Mount it:
  • mount /dev/VolGroup00/vg_root /mnt/root

Updating a new *RIP ISO or PXE image

• • Location: /images/rawiso/linux_utils/RIP
  • File: add_ghost
  • On ASIMOV run as root the following commands:
    • cd /images/rawiso/linux_utils/RIP
    • ./add_ghost version [grub|grub2|syslinux|pxe| - or -
    • ./add_ghost pxeall
    • * version is just a number such as 13.4 the corresponds to the directory /images/rawiso/linux_utils/RIP/RIP13.4
    • grub, grub2 or syslinux options rebuild an ISO image of RIP with the additions and the corresponding boot loader. The new ISO images have a -new added to their names in the original directory: Example: /images/rawiso/linux_utils/RIP/RIP13.4/RIPLinuX-13.4-new.iso
      • pxe option rebuilds the PXE boot image on ASIMOV. It creates a PXE menu file /tftpboot/pxes/pxelinux.cfg/rip_menu this file is currently be included in the primary PXE boot menu for ASIMOV /tftpboot/pxes/pxelinux.cfg/default
    • pxeall rebuilds ALL pxe images, creates a master rip_menu to include all of them automatically by ASIMOV

Making a USB KEY with ALL of the ASIMOV PXE boot environment

• USB version of PXE boot code
• PXEUsbKey documents how to put all of this on a USB key that you can boot

Example Recover of a Linux System

1. ) Boot RIP CD - login in root no password
2. ) View partitions on all disks - hint use fdisk.
   • Example: fdisk -l /dev/sda
3. ) Say we see that partition 5 in Linux - then mount /dev/sda5 /mnt/sda5
4. ) Now you can access the files under /mnt/sda5 or Optional chroot /mnt/sda5 - then access the files relative to /

Recovery alternate method using mntpart

1. ) Boot RIP CD - login in root no password
2. ) View partitions on all disks - hint use fdisk.
   • Example: fdisk -l /dev/sda
3. ) Say we see that partition 5 in Linux - then mount /dev/sda5 /mnt/sda5
4. ) ./mntpart /dev/sda5 - this will copy over the /dev/sda entries for the disk,chroot to it and mount sys,proc and devpts

Recovery repair GRUB2

• See: https://www.cs.uwaterloo.ca/twiki/view/CF/GRUB2

1. ) Boot RIP CD - login in root no password
2. ) dhcpcd - start network
3. ) View partitions on all disks - hint use fdisk.
   • Example: fdisk -l /dev/sda
4. ) Say we see that partition 5 in Linux - then mount /dev/sda5 /mnt/sda5
5. ) ./mntpart /dev/sda5 - this will copy over the /dev/sda entries for the disk,chroot to it and mount sys,proc and devpts
6. ) *./grub-fix

Reset Windows passwords

• See: ResetWindowsAdministrator

Modify Grub while booting to change the options such as the partition and drive beings used

• Boot System
• Hit Escape when you see Grub appear on the screen
• Cursor down to the kernal you want and press "e" - no quotes
  • You can cursor right or left - use delete or insert - finish with hitting ENTER

• Original line says:

/boot/vmlinuz-2.6.27-14-generic root=UUID=333e4b18-6a7b-41c5-9af7-06483a9848a3 ro quiet splash

• Edit to:

/boot/vmlinuz-2.6.27-14-generic root=/dev/sda5 single

• Note: this will boot the kernel but will mount the root fs as /dev/sda5 in single user mode