I have two identical SLES9 servers that each have a software raid configured on them. Unfortunately, I didn't understand that after configuring them and reinstalling GRUB onto the secondary drives, that I inadvertently nuked the original grub.conf's in each server. Cluster2 is down at the grub prompt, and cluster1 is up in linux in runlevel3.

Here is my configuration on cluster1 that is currently booted up and in Linux:
Code:
│Device                          │     Size   │ F │Type           │ Mount   │
│/dev/sda                        │    149.0 GB│   │HDT722516DLA380│         │
│/dev/sda1                       │    101.9 MB│   │Linux native   │/boot    │
│/dev/sda2                       │      4.0 GB│   │Linux swap     │swap     │
│/dev/sda3                       │    144.9 GB│   │Linux RAID     │         │
│/dev/sdb                        │    149.0 GB│   │HDT722516DLA380│         │
│/dev/sdb1                       │    101.9 MB│   │Linux native   │ *       │
│/dev/sdb2                       │      4.0 GB│   │Linux swap     │swap     │
│/dev/sdb3                       │    144.9 GB│   │Linux RAID     │         │
│/dev/sdc                        │     10.0 GB│   │DF600F         │         │
│/dev/sdd                        │     20.0 MB│   │DF600F         │         │
│/dev/sdd1                       │      8.0 MB│   │Novell Netware │         │
│/dev/md0                        │    144.9 GB│   │Linux LVM      │         │
│/dev/system                     │    144.9 GB│   │LVM2 system    │         │
│/dev/system/root                │    144.9 GB│   │LV             │/        │
│/dev/evms/printcluster1/printVOL│     unknown│   │EVMS           │/mnt/ipri│
I checked /dev/system/root and it is a link to /dev/mapper/system-root . I've established that /boot on sda1 lives on grub (hd0,0), and can tab through the kernels available in my /boot dir by doing...
Code:
grub> root (hd0,0)
When I try...
Code:
grub> kernel /boot/vmlinuz root=/dev/mapper/system-root
and boot, I get a
Code:
VFS: Cannot open root device "mapper/system-root" or unknown-block (0,0)
Please append a correct "root=" boot option
Kernel Panic: VFS: unable to mount root fs on unknown-block (0,0)
The thing that irks me is that I've been in this same place before on cluster1, but I didn't document which paths I used to successfully manually get through grub. My /boot partition is ext2 and my / partition is on a LVM partition formatted with reiserfs. I figure it mustn't be too difficult to get cluster2 to boot since cluster1 is set up the same way, so at least I have a working copy to look at, but sheesh! Any ideas which path I should chose for root=? Any other ways to get this puppy booted back into Linux so I can get grub configured permanently (at least until a kernel upgrade!)?