bin/138423: Installer (and sade) get wrong number of sectors per
trac
Pete French
pete at twisted.org.uk
Mon Aug 31 20:20:01 UTC 2009
>Number: 138423
>Category: bin
>Synopsis: Installer (and sade) get wrong number of sectors per trac
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Aug 31 20:20:00 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator: Pete French
>Release: FreeBSD 8.0-BETA3 amd64
>Organization:
>Environment:
System: FreeBSD frenic.twisted.org.uk 8.0-BETA3 FreeBSD 8.0-BETA3 #1: Mon Aug 31 19:02:03 BST 2009 root at frenic.twisted.org.uk:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
When installing 8.0 or running sade after install, the tools appear
to think that the disc has 63 sectors per track, and this is written
into the disc label. If the disc actually has a different number of
sectors then on boot then warnings are generated like this:
GEOM: da0: partition 1 does not start on a track boundary.
GEOM: da0: partition 1 does not end on a track boundary.
GEOM: da0s1: geometry does not match label (255h,63s != 255h,32s).
In my specific case I am installing onto an HP RAID controller,
which provides logical volumes with 32 sectors per track. This
is correctly detected on boot, and reported by diskinfo. The
dmesg looks like this:
ciss0: <HP Smart Array P400> port 0xb800-0xb8ff mem 0xf7d00000-0xf7dfffff,0xf7cff000-0xf7cfffff irq 18 at device 0.0 on pci1
ciss0: PERFORMANT Transport
ciss0: Using MSIX interrupt
ciss0: [ITHREAD]
>How-To-Repeat:
Perform a vanilla install onto a system with a ciss controller
installed. This shuould show up the problem. Other RAID controller
may also exhibit this.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list