Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Mar 1995 19:57:58 +1000
From:      Bruce Evans <bde@zeta.org.au>
To:        current@FreeBSD.org, mmead@goof.com
Subject:   Re: tonight's kernel
Message-ID:  <199503240957.TAA12675@godzilla.zeta.org.au>

next in thread | raw e-mail | index | archive | help
>    A kernel supped around 7:30 EST yields the following messages at boot:

>Mar 23 20:12:30 goof /kernel: sd0s1: start 0, end = 32767, size 2053880
>Mar 23 20:12:30 goof /kernel: sd0s1: C/H/S end 32767 != end 2053879: invalid

There is a bug with the validity checking for disks with more than 1024
cylinders.  It is impossible to check the validity reliably in this case,
but check_part() in isa/diskslice_machdep.c tries anyway.

If your disk has <= 1024 cylinders, then send me the output of
`fdisk /dev/rsd0'.

>Mar 23 20:12:30 goof /kernel: sd1s1: start 32, end = 204799, size 204768: OK
>Mar 23 20:12:30 goof /kernel: sd1s2: start 204800, end = 2053879, size 1849080: OK

This is the intended behaviour.  The verbose messages will be turned off
later.  See other freebsd-current mail.

>Mar 23 20:12:30 goof /kernel: sd1: rejecting partition in BSD label: it isn't entirely within the slice
>Mar 23 20:12:30 goof /kernel: sd1: start 204800, end 2053879, size 1849080
>Mar 23 20:12:30 goof /kernel: sd1d: start 0, end 2053879, size 2053880

This is a normal invalid whole-disk partition.  You might want to fix it by
running disklabel.  See other freebsd-current mail.  I think old versions
of FreeBSD-2.x force the d partition to be the whole disk, so backwards
compatibility will not be lost.

>Mar 23 20:12:30 goof /kernel: sd1: rejecting partition in BSD label: it isn't entirely within the slice
>Mar 23 20:12:30 goof /kernel: sd1e: start 32, end 204799, size 204768

This looks like a normal non-BSD partition outside of the FreeBSD slice.
See other freebsd-current mail.  Fixing it by running disklabel will
break backwards compatibility.

>...
>	Did we change back to slice partitioning in the way that disklabel
>wants, or is it still going to be done the way sysinstall does things.  If so,
>why do I get these messages, now?

The old way isn't 100% compatible.  The verbose messages are for debugging
more serious problems than the above.

Bruce



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503240957.TAA12675>