Date: Fri, 20 Jun 2003 13:06:47 +0930 From: Malcolm Kay <malcolm.kay@internode.on.net> To: Ju Hyuk Park <mytoe@mytoe.com>, "Ju Hyuk Park" <unknown@withseha.net>, <freebsd-questions@freebsd.org> Subject: Re: force bsdlabel? Message-ID: <200306201306.47916.malcolm.kay@internode.on.net> In-Reply-To: <008e01c336c2$dd65d6a0$39cf693f@blue0> References: <008e01c336c2$dd65d6a0$39cf693f@blue0>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 20 Jun 2003 09:58, Ju Hyuk Park wrote: > I had this stupid problem, unused partition had offset at 63, > mounted as "ad1s1" but worked fine; however fsck or vinum > changed it to offset 0, and everything blowed up. >=20 > How do i force bsdlabel to make "partition c" to offset 63? >=20 Within disklabel partition c is the entire slice if MS slicing(partitioni= ng) is used or entire disk otherwise, and must therefore start at offset 0. I= t is=20 hard to believe it was ever 63. However the slice (that is ad1s1) itself as reported by fdisk will commonly start at an offset of 63 from the beginning of the entire disk. Does ad1s1 hold your base system? If so how do you determine the offset is changed to 0? Fixit? If it is a bsd filesystem (ufs) then it is most unlikely to have ever bee= n=20 mounted as ad1s1 (a slice) but as a number of bsd partitions:=20 ad1s1a, ad1s1e etc. If you can get into your system or through fixit please run: # fdisk ad1 and # disklabel ad1s1 and post the results here. Malcolm Kay
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200306201306.47916.malcolm.kay>