Sorry. I read that there was no /dev/ad0s3, so there was no reason to ask for the bsdlabel output.
First, the slicing looks good. All of the numbers are reasonable and add up correctly. I now must suspect it's a GEOM issue. It looks like GEOM is not tasting the drive properly, but this gets out of my realm of expertise. I would suggest getting the dmesg from a verbose boot and posting it along with your kernel config somewhere so that people can examine them. And let us know when the sources were updated. I suspect I will not be the one to find anything, though. Everything looks fine to me...except that it does not work. :-( -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
pgpgsUN5DNNhJ.pgp
Description: PGP signature
