Re: gptmbr.bin vs RAIDframe

[Patrick Welche <prlw1%cam.ac.uk@localhost>]

On Tue, Jun 16, 2015 at 03:09:11PM +0100, David Brownlee wrote:
> On 16 June 2015 at 14:53, Patrick Welche <prlw1%cam.ac.uk@localhost> wrote:
> > On Tue, Jun 16, 2015 at 02:32:52PM +0100, David Brownlee wrote:
> >> > The only missing part is trying to make the system directly bootable. I tried "gpt biosboot -i 1 wd0" which didn't give any errors, but equally didn't work. At boot time gptmgr prints "Missing OS" which appears to be because it cannot locate the 0xaa55 signature.
> >>
> >> I've also not been able to make a raid-on-wedge partition bootable. I
> >> think the bootloader needs to be taught another variant of 'skipping
> >> raidframe header'...
> >
> > I currently have (-current/amd64):
> >
> > # sysctl kern.root_device
> > kern.root_device = raid7
> > # dmesg | grep dk0
> > dk0 at wd0: 80706d87-e1f8-11e3-9080-10bf48bd3389
> > dk0: 14680192 blocks at 64, type: raidframe
> > raid7: Components: /dev/dk7 /dev/dk0
> > dk0 at wd0: 80706d87-e1f8-11e3-9080-10bf48bd3389
> > dk0: 14680192 blocks at 64, type: raidframe
> > raid7: Components: /dev/dk7 /dev/dk0
> >
> > Is that the way around you are trying?
> 
> So, just put the raidframe wedge at offset 64 from the start of the
> disk? I thought I had tried that, but maybe thats a netbsd-7 vs
> current issue?
> 
> *many* thanks for the hint - I currently have 4.9TB of data on the
> system so I think I'll dig out a couple of small disks on which to
> test! :)

I don't know if that is the solution - just checking what the problem is!
Given that I can boot, there is one - I can't remember if there was an
MBR on the disk before (c.f. kre's message).

Cheers,

Patrick