Ben wrote:
On Wed, 16 Apr 2008, John Summerfield wrote:
Ben wrote:
On Wed, 16 Apr 2008, John Summerfield wrote:
Ben wrote:
On Tue, 15 Apr 2008, solarflow99 wrote:
It would also be possible to install grub on the other drive
manually if that is good enough, I have the grub commands if you
need.
That's helpful, thanks... but I'd still like to know why it's
choosing the MBR of sdb over the one on sda!
I did a manual install to a dc7700. Here is the relevant section
from anaconda-ks.cfg
bootloader --location=mbr --driveorder=hda,hdc
--append="pci=nomsi,nommconf vga=794 rhgb quiet"
[...]
Yeah, my bootloader line was of the form
bootloader --location=mbr --driveorder=sda
Maybe I should have added ",sdb" to the end?
It's an idea worth trying, I think.
Tried it, didn't work (-:
Now, the drive names _might_ be signficant. So might the fact that
the bootloader line lists two drives.
That's perhaps my thinking. But here's a twist:
I set up two RAID1 arrays. Array one contained disks 0 and 1, array
two contained disks 2 and 3. That was also the order in which I
created them. Pre OS-installation the LSI BIOS listed "Array 1 of 2"
as the one containing disks 0 and 1 and "Array 2 of 2" as having the
other pair. "Scan Order" was listed as "0" for the RAID1 array with
disks 0 and 1, and "2" for the second array. I'm assuming these were
(SCSI?) ID numbers (see below).
Now I'm thoroughly lost; I don't know whether you're using SCSI or
serial ATA, and I know nothing about them SUNs, and next to nothing
about SCSI.
It's SAS.
I just saw some similarities between what you are doing, and what I
did, and it seemed to me that what I did is close to what you want to do.
I appreciate the help. Thank you. I was almost certain your solution
would fix things. I tried it in concert with the below and things
worked. However taking the driveorder thing (adding in ",sdb") back out
didn't break the installation so I'm forced to conclude that it's the
below that makes or breaks the installation.
Should I go and stick my head in a pig?
What sort of pig do you have in mind:-)
Something from Wiltshire where the bacon is extra good. Anyway, no, I
It's not the sort of place I'd want to put a head, mine your yours. Too
smelly. These are nicer:
http://images.google.com/images?ie=UTF-8&oe=utf-8&q=salt+pig&um=1&sa=N&tab=wi
have a verifiable (but vaguely incomprehensible) solution. The trick
with a four disk configuration of a Sun x4200 M2 where you wish to
create two RAID1 volumes and RHEL 5 is having problems and putting the
MBR on the other logical volume/swapping the SCSI IDs (enough search
engine fodder?)...
Good thinking:-)
I'm glad it works, even though we don't understand it. My own box has me
confused enough. ATA was quite straightforward, as was the way Linux
dealt with it.
SATA/USB/whatever being called SCSI leaves me behind. I don't even trust
HP's documentation, I added a drive following (I thought) the
instructions and my existing Windows and Linux disappeared. Had to
shuffle cables.
Then my newer system, which came with two drives but with different "sd
0:1:0:0" names works. The names in your chart don't help me figure which
is which either.
Which is correct! So, unless I have problems with the two other
identical machines I've still to prepare _this_ is the solution.
Once they work and you hand them over, it's someone else's problem. MY
favourite kind of problem.
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
