Re: gpt, wedges and raidframe on -current

[buhrow%lothlorien.nfbcal.org@localhost (Brian Buhrow)]

        Hello.  These messages would imply that the devices are already open
by something else.  I'm not certain, but I think this is related to the
error messages I got when working on some patches to auto-confugure raid
sets on raw disks without disklabels.  However, I don't think these
messages have to do with the boot blocks not working.  My guess is that the
new code which boots off of the gpt partitions doesn't also do the skip
ahead 64 blocks trick to see if there's a bootable raid partition.   If it
doesn't, that could explain why the non-raid gpt partition boots and the one
containing a raid set doesn't.
-Brian


On Feb 25,  7:01pm, Hauke Fath wrote:
} Subject: Re: gpt, wedges and raidframe on -current
} At 18:53 Uhr +0100 25.02.2011, Hauke Fath wrote:
} >So far, accessing the dk[1345] filesystems is fine both from netbsd-5 and
} >-current. But the bootxx_ffsv2 installed on dk0 won't find /boot.
} 
} FWIW, the kernel appears to configure the wedges just fine, but then prints an
} 
} opendisk: can't open dev dk0 (16)
} opendisk: can't open dev wd2 (16)
} 
} warning, where wd2 is the sata disk, and dk0 is the (outer) raid wedge with
} raid0 on it.
} 
}       hauke
} 
} -- 
}      The ASCII Ribbon Campaign                    Hauke Fath
} ()     No HTML/RTF in email            Institut für Nachrichtentechnik
} /\     No Word docs in email                     TU Darmstadt
}      Respect for open standards              Ruf +49-6151-16-3281
>-- End of excerpt from Hauke Fath