In message <006501c35683$ffec3300$812a40c1_at_PETEX31>, "Petri Helenius" writes: > >Is this normal that multiple installations of 5.1-RELEASE complain >when running bsdlabel: ># /dev/ad0s1: >8 partitions: ># size offset fstype [fsize bsize bps/cpg] > a: 524288 63 4.2BSD 2048 16384 32776 > b: 4194304 524351 swap > c: 39102273 63 unused 0 0 # "raw" part, don't edit > d: 1048576 4718655 4.2BSD 2048 16384 8 > e: 33335105 5767231 4.2BSD 2048 16384 28552 >partition c: partition extends past end of unit >bsdlabel: partition c doesn't start at 0! >bsdlabel: An incorrect partition c may cause problems for standard system utilities >partition e: partition extends past end of unit > >This does not seem to happen if the disk has been labeled by previous >versions and upgraded from source. That sounds interesting. Can you send me the outout of: diskinfo /dev/ad0* sysctl -b kern.geom.confxml -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk_at_FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.Received on Wed Jul 30 2003 - 01:21:02 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:17 UTC