Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Software
User Name
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.


  Search this Thread
Old 04-28-2012, 02:50 PM   #16
LQ Newbie
Registered: Nov 2010
Location: Czech republic, Europe
Distribution: RedHat, CentOS, Ubuntu
Posts: 5

Rep: Reputation: 0

Success! sv1cec was right. When editing the grub.conf (menu.lst) we must also change the line that refers to the splashimage. Since then booting each drive separately. Thanks so much to sv1cec for the tip! :-)
Old 04-28-2012, 03:16 PM   #17
LQ Newbie
Registered: Apr 2012
Posts: 6

Rep: Reputation: Disabled
Tell me what you mean by "the same problem". I've managed to solve my issue.

If you get the errors I mentioned in post #10, I first followed the procedure mentioned in post #9. That took away the errors, when removing one of the disks, but still didn't allow the system to boot from either one of them. If the two disks were present, everything worked OK, but with one disk only, the system didn't boot. The message showing which kernel would load was shown, but the system was rebooting the PC from scratch, from the BIOS screen.

By carefully studying the grub.conf, I noticed that the system was trying to boot the kernel from hd1, which I believe doesn't exist when only one disk is present. So I edited grub.conf and changed every reference to hd1 to hd0. That allowed the system to boot, even when only one disk was present. I tried with either disk and both booted fine. When I connected both disks again, the system also booted fine, but it seemed that the arrays were not correct. I then used mdadm to re-add the missing partitions to the raid devices and everything worked just fine and I had a full working system, with a working RAID 1 array, able to boot from either disk.

It took me a while fighting the various issues of the RAID but I think it is something well-worth it, since it adds a significant feature to my system and gives me some peace of mind.
Old 03-26-2013, 07:30 PM   #18
LQ Newbie
Registered: Nov 2009
Posts: 2

Rep: Reputation: 0
I was having a similar problem, where the system would not boot if the bootloader was installed on md0. I found that my problem was that md0 was mapped to sda3/sdb3, but when I made md0 map to sda1/sdb1 my problem was solved. In this case, md0 was /boot.

The reasoning is that the motherboard looks for the bootloader at the beginning of the drive, so either the master boot record or sda1/sdb1. If md0 is mapped to sda3/sdb3 then the bootloader is not found properly by the motherboard.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Grub: If exists sdb, then boot sdb, else sda defaultyeti Linux - Desktop 6 06-28-2011 02:38 AM
[SOLVED] FC 10: RAID failure test: grub cannot find boot device jot Fedora 3 03-26-2009 09:11 AM
Ubuntu Raid 1, can't boot after Single Disk Failure elliotfuller Linux - General 7 06-05-2007 10:05 PM
Will not boot RAID drive after PS failure. webguyinternet Linux - Server 0 10-04-2006 02:59 PM
can't boot raid array after drive failure Rascale Linux - Hardware 4 02-12-2006 06:41 PM > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 06:28 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration