On Sat, 22 Jul 2000, John Baldwin wrote:
> Bruce Evans wrote:
> > The dangerously dedicated case has one slice covering the whole disk. We
> > unclip the slice info from the magic 5 sectors to the size of the whole
> > disk (as reported by the driver) to handle this. Reading the slice info
Bruce Evans wrote:
> On Fri, 21 Jul 2000, John Baldwin wrote:
>
> > Bruce Evans wrote:
> > > On Thu, 20 Jul 2000, John Baldwin wrote:
> > > > ...
> > > > unused even though it is, in fact, used. The fact that it works at all is
> > > > due to brokenness on our part (we don't check that partition
On Fri, 21 Jul 2000, John Baldwin wrote:
> Bruce Evans wrote:
> > On Thu, 20 Jul 2000, John Baldwin wrote:
> > > ...
> > > unused even though it is, in fact, used. The fact that it works at all is
> > > due to brokenness on our part (we don't check that partitions in a disklabel
> > > fit in the
Bruce Evans wrote:
> On Thu, 20 Jul 2000, John Baldwin wrote:
>
> > No, that's wrong, too. A normal disk has a proper slice table (slices start
> > on cylinder boundaries and do not contain the MBR, thus leaving the first
> track
> > cylinder unused). A truly dedicated disk (disklabel auto
On Thu, 20 Jul 2000, John Baldwin wrote:
> No, that's wrong, too. A normal disk has a proper slice table (slices start
> on cylinder boundaries and do not contain the MBR, thus leaving the first
track
> cylinder unused). A truly dedicated disk (disklabel auto ) uses a
track
> ...
> at al
In message <[EMAIL PROTECTED]> Leif Neland
writes:
:
:
: On Thu, 20 Jul 2000, Warner Losh wrote:
:
: > In message <[EMAIL PROTECTED]> Leif
:Neland writes:
: > : Just to be on the safe side, is there a simple way to see if a disk is
: > : dedicated?
: >
: > fdisk -s ad0
: >
: > If there's a
> In message <[EMAIL PROTECTED]> Leif Neland
>writes:
> :
> :
> : On Thu, 20 Jul 2000, Warner Losh wrote:
> :
> : > In message <[EMAIL PROTECTED]> Leif
>Neland writes:
> : > : Just to be on the safe side, is there a simple way to see if a disk is
> : > : dedicated?
> : >
> : > fdisk -s ad0
>
On Thu, 20 Jul 2000, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Leif Neland
>writes:
> : Just to be on the safe side, is there a simple way to see if a disk is
> : dedicated?
>
> fdisk -s ad0
>
> If there's a slice table, then it will give you a summary report of
> the slices. If n
> On Wed, 19 Jul 2000, Doug Barton wrote:
>
> > > Disk geometry stuffup, or a 'real' disk error.
> >
> > Well, I put my money on real disk error, but only because it
> > vindicates my position that we shouldn't have switched to this new kind of
> > disk in the first place.
> >
> > As f
In message <[EMAIL PROTECTED]> Leif Neland
writes:
: Just to be on the safe side, is there a simple way to see if a disk is
: dedicated?
fdisk -s ad0
If there's a slice table, then it will give you a summary report of
the slices. If not it will report an error (and maybe give you a
faked up li
Doug White wrote:
>
> On Wed, 19 Jul 2000, Doug Barton wrote:
> > As for geometry, I tried both with and without "dangerously
> > dedicated." My understanding was that if I used the dos partition entry
> > method that we should be able to pick up the geometry correctly, but
> > should I try
On Thu, 20 Jul 2000, Doug White wrote:
> Your boot disk is now *required* (or will be very very soon) to have a
> proper slice table in -CURRENT; dedicated disks are deprecated in order to
> get a smarter boot0.
>
So dedicated disks are to be reformatted?
Just to be on the safe side, is there
On Wed, 19 Jul 2000, Doug Barton wrote:
> > Disk geometry stuffup, or a 'real' disk error.
>
> Well, I put my money on real disk error, but only because it
> vindicates my position that we shouldn't have switched to this new kind of
> disk in the first place.
>
> As for geometry, I
On Wed, 19 Jul 2000, Mike Smith wrote:
> > No response to this on -stable. The actual error message is:
> >
> > Disk error 0x1 (lba=0x7004c)
> > No /boot/loader
>
> Disk geometry stuffup, or a 'real' disk error.
Well, I put my money on real disk error, but only because it
vindicate
> No response to this on -stable. The actual error message is:
>
> Disk error 0x1 (lba=0x7004c)
> No /boot/loader
Disk geometry stuffup, or a 'real' disk error.
> Also, on a whim I decided to try running /boot/loader. I got a
It's not a FreeBSD executable (obviously enough), so you
15 matches
Mail list logo
