Date: Fri, 7 May 2010 12:17:42 -0300 (ADT) From: "A. Wright" <andrew@qemg.org> To: krad <kraduk@googlemail.com> Cc: Polytropon <freebsd@edvax.de>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: dangerously dedicated disks and 8-stable status Message-ID: <alpine.BSF.2.00.1005071210130.38100@qemg.org> In-Reply-To: <o2pd36406631005070620hf317d001sa1fc83dd79c82777@mail.gmail.com> References: <z2td36406631005050917t1b7ea0bcwfb8ccb2487123846@mail.gmail.com> <20100505195544.be380d17.freebsd@edvax.de> <o2pd36406631005070620hf317d001sa1fc83dd79c82777@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 > <dev>s1[a-h] , however in freebsd-8+ to you are forced to use the format > <dev>[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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1005071210130.38100>