So I played it by ear and I’m going to post how I did it so you won’t have to. You’ll need to be using mdadm. I’m going to assume the partitions you want raided are /dev/sda1 and /dev/sdb1 and that you are currently booted to /dev/sda1. A rescue disk will also be helpful.

We are going to get a mirror going with just /dev/sdb1 (empty I hope) in it. Then we’ll copy everything over to it so everything is the same after reboot when it does a resync. Makes your data a bit safer.

Here we go…

Have you tried to setup raid before on these drives? This checks them for superblocks.

If it spat up lines like “ARRAY blah blah UUID=34cd3:etc”, zero them. Don’t worry not dangerous to data.

OK now we want to copy the partition tables over:

Now we create the raid array in a degraded mode with the master drive missing and format it to your filesystem.

Have a look at your new RAID:

Now we need to make sure that the kernel modules for scsi and raid are built in to the kernel. I am not actually sure if this step is needed but it worked on mine.

Now you’ll be presented with the kernel modules config screen. Find Device Drivers then in SCSI Device Support. In this section we need to make sure a few things have the asterisk in the brackets (should mean built in on the legend). These things for me were RAID Transport Class, SCSI device support, SCSI disk support and SCSI generic support. Press spacebar on each of them to change the M or blank in the brackets to an asterisk. Then exit out of it saving your config as you leave.

Now the important part – creating the kernel image. This worked for me… at about the sixth time and exhaustive google searches:

Now you want to modify /boot/grub/grub.conf and /boot/grub/device.map.

Need to make sure we have both devices in there
/boot/grub/device.map:

Need to make a backup bootloader entry and a raided one too
/boot/grub/grub.conf:

That boot list boots off /dev/sdb before and loads into the system with the raid array active. This allows you to add /dev/sda1 into the array. If it booted off /dev/sda1 (e.g. hd0) then /dev/sda1 would be locked and you would not be able to do the mdadm command.

It also allows you to boot without the raid array if your raid setup failed to boot (i.e. kernel panic). The setting for root in fstab doesn’t matter if its set to /dev/md0, /dev/sda1 still becomes the root drive.

Now install grub on /dev/sdb:

Now change the root device in your fstab to be /dev/md0
/etc/fstab:

Now we need to copy everything over to the raid array, however it will probably crash out copying with the running system like mine did, but not to worry we are pretty much ready to go here.

Shut down and boot into a linux rescue disk (the first cd of RHEL5.4 has it), and get to the command line, don’t bother mounting filesystems or anything.
Try this:

If that doesn’t work then try this:

and push y if it asks you to create over another array.

Create mountpoints and mount your drives:

Now copy everything over:

Wait a while till that is done then reboot. Hopefully you don’t get a kernel panic, and it boots up on the degraded /dev/md0 array. If it does then add your /dev/sda1 in like follows:

Now you can watch the resync progress like this:

mdadm is pretty smart.

Here’s some other links that may help you out if you’re stuck:
http://wiki.clug.org.za/wiki/RAID-1_in_a_hurry_with_grub_and_mdadm
http://www.mail-archive.com/linux-raid@vger.kernel.org/msg09672.html
http://www.debian-administration.org/articles/238
http://unthought.net/Software-RAID.HOWTO/Software-RAID.HOWTO-7.html

Check it out:

for i in `ps auwx|grep hamstar|cut -f2 -d’ ‘`; do kill $i; done

That would kill all the processes that I have started under my username. Notice the red part is where it takes all the entries (puts each one into $i as it uses it, and the blue part is where it does something with the entries ($i again)). Adding kill to the start and ; to the end using sed would not work for this.

Ok that might a bit tricky for some of you, especially if you haven’t come across the miracle of piping yet, let me show you a simpler one.

for i in *; do echo $i; done

Basically another form of ls but thing of the things you can do with this. Rename from lowercase to uppercase:

for i in *; do mv $i `echo $i|tr [A-Z] [a-z]`; done

So its basically limitless to what you can do with this cool thing.

I also found another cool thing while writing this. Doing the following will covert all characters in a given file to lowercase or uppercase if you changed it:

dd file.txt conv=lcase

Okay, here it is broken down. Lets say, you have two linux boxes, both running GUI’s, and you want to open gedit on one machine (machine1), but display it on the other machine (machine2):

Getting the info:

On machine1, open a console and do:

ifconfig eth0

This should tell you your IP address (e.g. 10.0.0.1). Now go to the other machine and do following:

xhost 10.0.0.1
ifconfig eth0
echo $DISPLAY

OK, that has added machine1 to machine2s receiving trusted list. Now grab your IP on that box (e.g. 10.0.0.2) and the DISPLAY number (e.g. :0) and go back to machine1. Do the following:

DISPLAY=10.0.0.2:0
export DISPLAY
gedit

Now with a bit a bit of luck, gedit should have opened on the other machine.

Handy for:

• Remote administration! Put the box under the stairs without a screen or anything, ssh into it and open any windows on your own desktop.
• Open stuff on other people desktops! “I swear, that porn window came out of nowhere, I clicked nothing!”

Drawbacks:

• The environment that the sent window runs in is still that of machine1. So you can’t access machine2’s files even though you are using the window on machine2 (unless you set up a samba share or something)

My main problem is that I can’t get internet on my laptop at home. I’m on dialup and my external modem only connects by serial, which my laptop doesn’t have. Problem.

Solution. I can ssh into my main box which has the modem, connect it to the net and run firefox and it will open it on my laptop screen, using the network. This is a built in feature of X, the display manager for linux.

This HOWTO assumes the following:

1. You already have ssh setup on the main box
2. The main box is called serj with an IP of 10.0.0.1
3. The other box is called malakian with an IP of 10.0.0.4

Here’s how ya do it:

1. Open up a console window
2. Add the other box to your X “allow” list by typing the following:
   xhost serj

   
   

3. Find out your display number and remember it (lets say it is 1). Type:
   echo $DISPLAY

   
   

4. SSH into your main box from the other box
   ssh serj -l <em>username</em>

   
   

5. Once you’ve logged in, you need to edit the DISPLAY variable to be the IP and display number (1) of the box you’re on and export it:
   DISPLAY=10.0.0.4:1; export DISPLAY

   
   

6. Once you’ve done that check that it is set properly by echo’ing the DISPLAY variable again. It should show 10.0.0.4:1
   echo $DISPLAY
7. Now simply run a program like firefox from the command line and the window will open on your box:
   firefox

When you run a program it will open with all the settings from your main box. Unfortunately it won’t work with 3D games but there are a few things it could be useful for e.g.:

1. Administering one of your screenless servers through an actual GUI (provided you installed with KDE/gnome/some other window manager)
2. Opening dirty sites on your friends/workmates PC. Open a console, set your display to your workmates IP/display and run
   firefox http://nastyjapanesegirls.com

   . Of course it will be running of your profile so he won’t get done for porn if you do this at work… you will.

There is one draw back though, all sound will run on the main box.