From owner-freebsd-questions@FreeBSD.ORG Fri May 7 21:22:57 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BE9571065677 for ; Fri, 7 May 2010 21:22:57 +0000 (UTC) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (gizmo.acns.msu.edu [35.8.1.43]) by mx1.freebsd.org (Postfix) with ESMTP id 67A5C8FC1D for ; Fri, 7 May 2010 21:22:57 +0000 (UTC) Received: from gizmo.acns.msu.edu (localhost [127.0.0.1]) by gizmo.acns.msu.edu (8.13.6/8.13.6) with ESMTP id o47LLeAX055700; Fri, 7 May 2010 17:21:40 -0400 (EDT) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: (from jerrymc@localhost) by gizmo.acns.msu.edu (8.13.6/8.13.6/Submit) id o47LLd6g055699; Fri, 7 May 2010 17:21:39 -0400 (EDT) (envelope-from jerrymc) Date: Fri, 7 May 2010 17:21:39 -0400 From: Jerry McAllister To: krad Message-ID: <20100507212139.GB55516@gizmo.acns.msu.edu> References: <20100505195544.be380d17.freebsd@edvax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: FreeBSD Questions Subject: Re: dangerously dedicated disks and 8-stable status X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 May 2010 21:22:57 -0000 On Fri, May 07, 2010 at 10:06:31PM +0100, krad wrote: > On 7 May 2010 16:17, A. Wright wrote: > > > > > On Fri, 7 May 2010, krad wrote: > > > > FYI happened on 2nd box as well but I least it didnt catch me out this > >> time > >> 8). It seems that pre freebsd-8 it is permissible to use format > >> s1[a-h] , however in freebsd-8+ to you are forced to use the format > >> [a-h]. > >> > > > > I have noted peculiarities also in this move (as noted above: > > 8.0-RELEASE upgrade -- no files visible), but different ones > > from what you are seeing. > > > > I have begun to suspect that part of the issue is that my > > drives at one time were set up in "dangerously dedicated" > > mode, but later changed to "slice-based" mode. It may be > > that there are still sectors near the beginning of the disk > > with old information in them. > > > > Currently I have one disk remaining from the old setup, for > > which I only get /dev entries produced for the device, and > > for partition 'a' (ie, /dev/ad10, /dev/ad10a), however if > > accessed from 7.2, I can see and mount /dev/ad10s1[a,d-g]. > > > > Might your disks have similar "old" information in the first > > track (but not in the first sector), or do you refer to a > > new disk, or one to which a number of sectors of zeros was > > written? > > > > Thanks for the info, > > A. > > > > > > Both were a 6.2 box upgraded to 7-stable then 8. I didnt build the initial > os's so have no idea what the state of the disks were unfortunately. I have > about 20 more or so upgrades to do in the next few weeks so expect the trend > to continue as they were all built around the same time by the same person If you are worried that there might be something in an early sector on the disk, you can get rid of it by using dd(1). If your drive is /dev/ad10, then do the following. dd if=/dev/zero of=/dev/ad10 bs=512 count=1024 Actually any count over 32 should work, but it takes no time so use a biger one. This will work before slicing and partitioning the drive or will wipe out previous slicing and partitioning. ////jerry > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"