Hi all,

I went ahead and set up OpenFiler 1.1.1 on an old Pentium III with two 250GB
PATA hard drives (one master, one slave), and, with the OpenFiler installer,
created 4 RAID-1 devices using the two drives as follows:

md0: /boot [100 MB]
md1: /     [4096 MB]
md2: swap  [2048 MB]
md3: LVM   [rest of space]

I installed "Everything", created a volume group at the command line,
configured everything else with the web interface, and was up and running
with a public read/write Samba share.

To test the RAID-1 configuration, I then shut down, disconnected the slave
drive, booted up, and the master HDD continued to operate fine.

I then disconnected the master HDD, changed the jumper on the slave to
master and re-connected that drive (leaving the original master
disconnected), and tried booting the machine.  Unfortunately, I didn't get
to the grub loader.  The drive does seem to churn (in a good-sounding way),
but all I get is a blinking cursor; the bootloader, even after minutes,
never comes up.

My understanding, based on reading over the Software-RAID HOWTO
(http://www.tldp.org/HOWTO/Software-RAID-HOWTO.html) is that, per section
7.3, I *should* at least get as far as the bootloader, at which point I can
tell it to boot from what was once the second drive in the array.  But,
again, just a blinking prompt.  (Using fdisk, I did confirm that the first
partitions on /dev/hda and /dev/hdb are flagged as "bootable".)

Am I going about "recovering" from a failure (albeit simulated) in the wrong
way for software-based RAID-1?

Many thanks.

Yours,
David

_______________________________________________
Openfiler-users mailing list
[email protected]
https://lists.openfiler.com/mailman/listinfo/openfiler-users

Reply via email to