| Posted by NikolayM, 12-25-2011, 06:56 AM | | Hello,
I am experiencing problems configuring software raid 0. Actually, the raid configuration is not the problem, but perhaps the grub configuration instead. Will leave this to the expert's decision.
The target is to build a software raid 0 configuration, out of 2 drives, each of them consisting of 1TB. I have used the following method to complete the task:
http://www.cyberciti.biz/faq/centos-...-create-raid1/
I have loaded LiveCD and everything went smoothly. After the mdadm step, it finished successfully and the raid was presented. However, after rebooting the server, it failed to boot.
I tried to investigate as much as possible, but because of the lack of experience in grub configuration I'm stuck. You can see in the bottom screenshot of the grub.conf provided that the kernel line points to sda3, which is used for the raid configuration. Therefore, I believe that might be the problem. Not really sure of the whole process (As I said, its pretty new for me), but during the partitioning and the disks syncing, perhaps the information on that partition which holds the kernel, get corrupted. Again, I can not be sure. This is only assumption.
So to solve this issue, based on my assumptions, I guess that I should move the kernel to either sda1 or sda2 and change the configuration. Unfortunately, I do not know how to move the kernel (if that is the solution).
Please be so kind to review the details provided and suggest how to proceed. Am I wrong in my assumptions? Is the problem somewhere else?
Screenshot
OS - CentOS 5.7
No KVM
Thanks!
|
| Posted by madaboutlinux, 12-25-2011, 09:50 AM | | The tutorial only states how to create software raid 0 with existing partition and a new drive. It won't make any changes to grub.conf unless something else is done apart from what is mentioned in the tutorial.
sda1 should still have everything required to boot the system. Try to change the sda3 to sda1 in grub.conf and boot the system. Don't think there is any option other than reinstall the server if that doesn't work. What message does it show when it is stuck during the boot process?
|
| Posted by NikolayM, 12-25-2011, 10:11 AM | | Already tried to change it from sda3 to sda1. It does not work. That's why I thought that probably I should move a specific file, or something like that.
Re-installation is out of the question, because it is an automated process which does not set any Raid options at all.
I'm unable to tell the what is the error, causing the problem because I do not have KVM. If the system is creating logs about it, please let me know.
|
|
 Add to Favourites
 Print this Article
|
