Subject: Re: RAID1 bootblocks for 2.0
To: Jonathan Perkin <jonathan@perkin.org.uk>
From: Philip Jensen <phil_jensen@yahoo.com>
List: port-sparc64
Date: 12/13/2004 09:41:07
This is a multi-part message in MIME format.
--------------030401040402090006080705
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Jonathan Perkin wrote:
>* On 2004-12-12 at 00:57 GMT, Brian McKerr wrote:
>
>
>>Ended up using solaris and disksuite as I needed the thing up and
>>running in a hurry. Real pity as I wanted to use NetBSD and was
>>really impressed with the sparc64 support.
>>
>>
>Yes, I'm pondering the same, I'm a huge huge fan of disksuite.
>
Hmmm, can't say I particularly like disksuite, I much prefer RAIDFRAME
;-) And I can get a NetBSD box up and running with mirroring in less
time than Solaris, maybe I'm not a good Solaris admin.
>>I did heard someone mention that you need a seperate ffs partition
>>*not* on the raid device. But I'm not sure if that's valid given
>>that, as you mentioned Jonathon, that we were able to boot from the
>>raid device with only the bootblocks on the initial setup device.
>>
>>
>I think I saw that too, but it seems bogus given others have said that
>the exact procedures described in the NetBSD guide work fine, and they
>mention nothing of having the separate partition (which would be a
>pain, and remove the entire point of mirroring the bootable partition).
>
I haven't tried the "new" method with NetBSD v2.0, but I have had no
problem running NetBSD v1.6.2 (albeit with a 1.6Z kernel) on a mirrored
root filesystem. To achieve this I needed to have a wee FFS boot
partition (on each disk to allow booting on disk failure) which contain
the secondary boot loader and a kernel so the raw disk payout was
something like this:-
# disklabel -i -I wd1
[..snip...]
6 partitions:
# size offset fstype [fsize bsize cpg/sgs]
a: 20160 0 4.2BSD 512 4096 22 # (Cyl.
0 - 19)
b: 526176 20160 RAID # (Cyl.
20 - 541)
c: 16841664 0 unused 0 0 # (Cyl.
0 - 16707)
d: 7167888 546336 RAID # (Cyl.
542 - 7652)
e: 8363376 7714224 RAID # (Cyl.
7653 - 15949)
f: 764064 16077600 RAID # (Cyl.
15950 - 16707)
You can read the instructions I kept for my own reference on my web
page here:-
http://philipjensen.freezope.org/Computing/NetBSD_rootfs_on_RAID1
This method has worked for me on an UltraSPARC 5, Netra T1 ac200,
Sunfire v100. Once the system is up and running the only gotcha is
keeping the kernel synced on the FFS partitions on disk if new kernels
are installed.
Hope that helps.
--------------030401040402090006080705
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Jonathan Perkin wrote:<br>
<blockquote type="cite"
cite="mid20041212095641.GH743@chorlton.is.bbc.co.uk">
<pre wrap="">* On 2004-12-12 at 00:57 GMT, Brian McKerr wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Ended up using solaris and disksuite as I needed the thing up and
running in a hurry. Real pity as I wanted to use NetBSD and was
really impressed with the sparc64 support.
</pre>
</blockquote>
<pre wrap=""><!---->Yes, I'm pondering the same, I'm a huge huge fan of disksuite.</pre>
</blockquote>
Hmmm, can't say I particularly like disksuite, I much prefer RAIDFRAME
;-) And I can get a NetBSD box up and running with mirroring in less
time than Solaris, maybe I'm not a good Solaris admin.<br>
<blockquote type="cite"
cite="mid20041212095641.GH743@chorlton.is.bbc.co.uk">
<blockquote type="cite">
<pre wrap="">I did heard someone mention that you need a seperate ffs partition
*not* on the raid device. But I'm not sure if that's valid given
that, as you mentioned Jonathon, that we were able to boot from the
raid device with only the bootblocks on the initial setup device.
</pre>
</blockquote>
<pre wrap=""><!---->I think I saw that too, but it seems bogus given others have said that
the exact procedures described in the NetBSD guide work fine, and they
mention nothing of having the separate partition (which would be a
pain, and remove the entire point of mirroring the bootable partition).</pre>
</blockquote>
I haven't tried the "new" method with NetBSD v2.0, but I have had no
problem running NetBSD v1.6.2 (albeit with a 1.6Z kernel) on a
mirrored root filesystem. To achieve this I needed to have a wee FFS
boot partition (on each disk to allow booting on disk failure) which
contain the secondary boot loader and a kernel so the raw disk payout
was something like this:-<br>
<blockquote><tt> # disklabel -i -I wd1</tt><br>
<tt>[..snip...]<br>
</tt><tt>6 partitions:<br>
</tt><tt># size
offset fstype [fsize bsize cpg/sgs]<br>
</tt><tt> a:
20160
0 4.2BSD 512
4096 22 # (Cyl. 0
- 19)<br>
</tt><tt> b: 526176
20160
RAID
# (Cyl. 20 - 541)<br>
</tt><tt> c: 16841664
0 unused
0 0 #
(Cyl. 0 - 16707)<br>
</tt><tt> d: 7167888
546336
RAID
# (Cyl. 542 - 7652)<br>
</tt><tt> e: 8363376
7714224
RAID
# (Cyl. 7653 - 15949)<br>
</tt><tt> f: 764064
16077600
RAID
# (Cyl. 15950 - 16707)</tt><br>
</blockquote>
You can read the instructions I kept for my own reference on my web
page here:-<br>
<blockquote><a class="moz-txt-link-freetext" href="http://philipjensen.freezope.org/Computing/NetBSD_rootfs_on_RAID1">http://philipjensen.freezope.org/Computing/NetBSD_rootfs_on_RAID1</a><br>
</blockquote>
This method has worked for me on an UltraSPARC 5, Netra T1 ac200,
Sunfire v100. Once the system is up and running the only gotcha is
keeping the kernel synced on the FFS partitions on disk if new kernels
are installed.<br>
<br>
Hope that helps.
</body>
</html>
--------------030401040402090006080705--