Re: RAIDframe installboot

"George Georgalis" <[email protected]>
Newsgroups gmane.os.netbsd.help
Message-ID <[email protected]>
On Fri, Jul 13, 2007 at 08:01:08AM +0100, David Laight wrote:
>On Thu, Jul 12, 2007 at 06:13:58PM -0400, George Georgalis wrote:
>> 
>> the ffsv1 filesystem in raid0a has an offset of 63;
>> and the entire rraid0d has an offset of 63. per below, does
>> this answer your question / look correct?
>> 
>> # /dev/rraid0d:
>> type: RAID
>> disk: raid
>> label: fictitious
>> 
>> 16 partitions:
>> #        size    offset     fstype [fsize bsize cpg/sgs]
>>  a:   1024128        63     4.2BSD   1024  8192 46552  # (Cyl.      0*-   1000*)
>...
>> # /dev/rwd1d:
>> type: ESDI
>> disk: ST3750640AS     
>> label: fictitious
>> 
>> 5 partitions:
>> #        size    offset     fstype [fsize bsize cpg/sgs]
>>  a: 1465149105        63       RAID                     # (Cyl.      0*- 1453520)
>
>That isn't going to work (as you found out).
>The sector numbers in the raid's disklabel are relative to the raid set
>itself, and you shouldn't have left a 63 sector gap at the front.
>The bootcode doesn't have access to the label of the raid, and assumes that
>the root filesystem is at the start of it.

thanks, I was aware the raid0x offset is relative
to the RAID offset.  It makes sense that raid0a
should have an offset of 0, but I thought it worked
different.

>You might manage to fudge things by making the 'a' partition of the main
>disk reference sector 63+64+63=190 (ie where the root fs starts) and
>moving the raid entry to 'e'
>Try it first by adding the extra ptn as 'e', and interrupting the boot
>program (during the countdown) and typing 'boot hd1e'.

I tried using wd1e to point to the "a: 1024128 63
4.2BSD" partition (e: 1465148978 190 RAID) but the
primary said "boot: no such file or directory" ...
anyway one of the partitions has 100Gb on it with a
zillion hardlinks; I'd like to fix this vs fudge the
table or recreate that data.

my plan is to change the RAID partition to UNKNOWN
boot into wd0; change back the in-core label for
wd1a to RAID, backup the raid0a partition to raid0i;
repartition so the raid0a has an offset of 0, newfs
it, and restore root partition from raid0i.

// George


-- 
George Georgalis, information systems scientist <IXOYE><
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.