I traced the problem back to BIOS booting off ad0 instead of ad1.
Because ad0 was still a perfectly functioning drive BIOS didnt complain
about booting off it. Once the kernel started and gmirror loaded it
proceeded to use ad1, but the kernel was loaded from ad0, which was the
old, broken one.
I noticed my first partition does start at offset 0 though, is this
going to come and bite me in the future?
J
Michael Butler wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jared Ring wrote:
| I have cvsup'd today to make sure I get the updated g_mirror.c, have
| rebuilt world and kernel, installed both. however when i rebuild the
| degraded drive the same thing happens.
|
| during the rebuild the good drive is reading, but the dirty drive is not
| gettin written to according to gstat.
I've been bitten by this - make sure that the first slice on the
mirrored partition does not start at offset 0.
For example, this disk is mirrored on slice 2 ..
[EMAIL PROTECTED]:/home/imb> sudo bsdlabel mirror/gm0s2
# /dev/mirror/gm0s2:
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
~ a: 524272 16 4.2BSD 2048 16384 32768
~ ^^^^^^^
~ c: 284655734 0 unused 0 0 # "raw" part ..
~ d: 1048576 524288 4.2BSD 0 0 0
~ e: 1048576 1572864 4.2BSD 0 0 0
~ f: 282034294 2621440 4.2BSD 0 0 0
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)
iD8DBQFFCUAhQv9rrgRC1JIRAnPHAJ9AMnr1PzCfqJBx99zs6BhWSHI4NwCggUpo
aI3LrwU8cHDmyLZpKB98EKw=
=QPtF
-----END PGP SIGNATURE-----
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
