Am 06.08.2015 um 22:43 schrieb Chris Murphy <lists@xxxxxxxxxxxxxxxxx>:
> On Thu, Aug 6, 2015 at 2:39 PM, Leon Fauster <leonfauster@xxxxxxxxxxxxxx> wrote:
>> Am 06.08.2015 um 22:21 schrieb Chris Murphy <lists@xxxxxxxxxxxxxxxxx>:
>>> On Thu, Aug 6, 2015 at 2:08 PM, Bowie Bailey <Bowie_Bailey@xxxxxxx> wrote:
>>>
>>>
>>> Sounds like a pain. I would just adapt the CentOS 6 program.log
>>> commands for your case. That's a 2 minute test. And it ought to work.
>>>
>>> Clearly the computer finds the drive, reads the MBR and executes stage
>>> 1. The missing part is it's not loading or not executing stage 2 for
>>> some reason. I'm just not convinced the bootloader is installed
>>> correctly is the source of the problem with the 2nd drive. It's not
>>> like the BIOS or HBA card firmware is going to faceplace right in
>>> between stage 1 and stage 2 bootloaders executing. If there were a
>>> problem there, the drive simply doesn't show up and no part of the
>>> bootloader gets loaded.
>>
>>
>> on which OS (eg. c5, c6) was the partition created?
>
> For the OP, I think it was CentOS 5, but he only said it's running CentOS 5 now.
>
> For my test, it was CentOS 6, but that uses the same version of GRUB
> legacy so the bootloader installation method for raid1 disks should be
> the same.
C6's grub has large inode support (and for sure a couple
of others patches) which is missing in C5's grub.
Not sure if this is here the case but i got triggered while reading this thread
because we had here problems with filesystems that where "premastered" on
C6 systems to install C5 on it (KVM). The above mentioned missing large inode
support was the problem.
--
LF
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
