Hardcoding gmirror provider

James Snow snow at teardrop.org
Tue Feb 22 18:48:06 PST 2005

On Wed, Feb 23, 2005 at 12:58:52AM +0100, Pawel Jakub Dawidek wrote:
> ...and metadata at the begining of the provider still doesn't fix 'c'
> partition problem and 'a' partition which starts at sector 0, which is
> the default start offset in sysinstall.

Is this the C partition problem you refer to?

bsdlabel: partition c doesn't cover the whole unit!
bsdlabel: An incorrect partition c may cause problems for standard
system utilities

Could this possibly be at the root of my boot problem:

disk1s1: FFS bad disklabel
disk2s1: FFS bad disklabel

It only seems to be a problem if I try to use slices as gmirror
providers and shrink them to avoid the last sector collision with the
whole disk.


More information about the freebsd-stable mailing list