On 07/09/2007 06:31 AM, Brandon Carl wrote:
That way I can boot from either the first drive, or the one-drive RAID
on the second drive.
I have run into a problem, however. When I attempt to choose "Boot
from RAID" it gets to the boot commands, but it stalls at "Waiting for
device /dev/md10 to appear: ................................. not
found -- Exiting to /bin/sh".
Why is it now md10? It should be md0, md1, md2. What does
/etc/mdadm.conf show you?
I changed it to md10 because somehow I accidentally deleted /dev/md0,
/dev/md1, and /dev/md2, probably in an attempt to unmount them, lol.
I couldn't find a way to create them again, so I just decided to use
md10 and md11. I can't imagine this would affect anything, however.
/etc/mdadm.conf does not exist on either drive.
OK, I think it would be helpful to create that file. Examples are in
the man page for mdadm. I will attach mine for reference.
Here is the contents of my fstab under the /dev/md10, in case it's
helpful:
/dev/md10 / reiserfs
acl,user_xattr,usrquota,grpquota 1 1
/dev/md11 /home reiserfs
acl,user_xattr,usrquota,grpquota 1 2
/dev/hdb5 swap swap
defaults 0 0
proc /proc proc
defaults 0 0
proc /proc proc
defaults 0 0
sysfs /sys sysfs
noauto 0 0
debugfs /sys/kernel/debug debugfs
noauto 0 0
usbfs /proc/bus/usb usbfs
noauto 0 0
devpts /dev/pts devpts
mode=0620,gid=5 0 0
/dev/fd0 /media/floppy auto
noauto,user,sync 0 0
Is that a typo, or are you missing a comma between reiserfs and acl? Do
you really have proc twice? You did make sure there was a /proc and
/sys folder for mounting their respective filesystems.
I copied directly from the file, but there is a few spaces in between
the reiserfs and the acl,user... The formatting got messed up, sorry.
I am not bothered by the formatting, but those lines options and syntax
are important. There should NOT be spaces between the options, and
there should be a comma separating the list options. Having 2 proc
entries will probably cause an error message.
I have decided against mirroring the swap space, and just using both
the /dev/hda5 and /dev/hdb5 as swap space, so it is doubled.
OK
Is this a wise choice?
I would say yes. I see no need to raid swap, and making them separate
doubles swaps size, assuming the same priority.
So that is where I am stuck. I cannot figure how to get past the
"waiting for device /dev/md10 to appear......".
I have tried "mkinitrd" and "cd /mnt; chroot /mnt; mkinitrd" to try
and fix it, but to no avail.
Anyone have any ideas?
Thanks for your help thus far!
Check /etc/mdadm.conf to make sure you really have such raid devices.
The file does not exist.
Create it as per man mdadm, check attachment for reference.
--
Joe Morris
Registered Linux user 231871 running openSUSE 10.2 x86_64
OK, I can successfully boot from either hard drive and choose the option to
boot from HDA or the RAID drive from grub.
Now what do I do from here? I'm pretty sure the data is all copied over,
but is there a way I can be sure? You said something about using rsync, but
I'm not familiar with that tool.
And then, once that is done, how do I "add" the old drive into the RAID
array.
Thanks!
-Brandon Carl
[EMAIL PROTECTED]
www.spleeyah.com
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
