linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinnie <listacct1@lvwnet.com>
To: Linux Raid List <linux-raid@vger.kernel.org>
Cc: Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: HELP - need more documentation on using partitioned (mdp-type) md devices
Date: Tue, 05 Nov 2002 01:07:56 -0500	[thread overview]
Message-ID: <3DC7603C.9040105@lvwnet.com> (raw)
In-Reply-To: 3DC74C44.7090101@lvwnet.com

Hi Neil!

Thanks for your help.  That did the trick!

I did have to change the partitions= to partition=, I didn't know any 
better but LILO did! ;)

Also once I got a successful LILO install (I did a -t -v first), and 
booted up, I got an error from LILO stating "EBDA Too Big".

I looked up EBDA in the README's and it says it is a thing that happens
sometimes with MultiProcessor motherboards, and suggested building LILO
with the LARGE_EBDA option.  I thought I'd try out just using the
'compact' statement in lilo.conf first, and that was enough to do it, I
got booted up successfully!

My test case told the kernel that the root fs was on the original 
external RAID subsystem, so really all I was testing was that I could 
actually boot from the RAID1 pair of IDE disks created with the 
partitioned md device.  Should be able to proceed on now to copying all 
files over to the filesystems on the RAID1 pair, so I can pull this 
external RAID subsystem offline and reconfigure it.

Thanks again Neil!  Couldn't have done it without your help!  Well, not 
in the next week or so, probably... ;)

vince


Vinnie wrote:

> Neil Brown wrote:
> 
>> On Monday November 4, listacct1@lvwnet.com wrote:
>>
>>> If anybody (Neil?) can offer some advice on how to get LILO to write 
>>> a boot sector to the RAID1 array pair, it would be greatly 
>>> appreciated.  I am so close to getting this working!!!
>>>
>>>
>>
>> First, lilo thinks it knows what "/dev/md*" means, and gets all
>> confused when it turns out to be different.
>> So create device names that *don't* start /dev/md.
>> e.g.
>>    /dev/MDa == 60,0
>>    /dev/MDa1 == 60,1
>>    etc
>>
>> Second, you have to tell lilo about the geometry of /dev/MD*, because
>> it doesn't know:
>>
>>    boot=/dev/MDa
>>    disk=/dev/MDa
>>      bios=0x80
>>      sectors=63
>>      heads=255
>>      cylinders=1024
>>      partitions=/dev/MDa1
>>       start=63
>>
>> The "start" is very important.  check what the start sector of MDa1
>> is, and use that.
>>
>> Lilo should then work.
>>
>> NeilBrown
> 
> 
> 
> thanks Neil!  Getting ready to try this out.  This looks really 
> promising, makes a lot of sense.
> 
> Vince
> 
> 
> 
> 




      parent reply	other threads:[~2002-11-05  6:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05  4:03 HELP - need more documentation on using partitioned (mdp-type) md devices Vinnie
2002-11-05  4:33 ` Neil Brown
2002-11-05  5:59   ` Vinnie
     [not found]   ` <3DC74C44.7090101@lvwnet.com>
2002-11-05  6:07     ` Vinnie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3DC7603C.9040105@lvwnet.com \
    --to=listacct1@lvwnet.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).