2.7 Terabyte array and bsdlabel on 5.3-BETA2 wierdness

Nick Evans nevans at talkpoint.com
Wed Sep 1 14:43:19 PDT 2004


3ware device driver for 9000 series storage controllers, version:
twa0: <3ware 9000 series Storage Controller> port 0xc800-0xc8ff mem 0xfb800000-0xfbffffff,0xfe9ffc00-0xf
e9ffcff irq 48 at device 1.0 on pci4
twa0: 12 ports, Firmware FE9X, BIOS BE9X
da0 at twa0 bus 0 target 0 lun 0
da0: <3ware Logical Disk 00 1.00> Fixed Direct Access SCSI-0 device 
da0: 100.000MB/s transfers
da0: 2860896MB (5859115008 512 byte sectors: 255H 63S/T 364713C)

# /dev/da0:
8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  c: 5859115008        0    unused        0     0         # "raw" part, don't edit

Using the label above on da0 gives the following error: 

partition c: partition extends past end of unit
disklabel: partition c doesn't cover the whole unit!
disklabel: An incorrect partition c may cause problems for standard system utilities

Using fdisk in sysinstall or a bsdlabel with * in the size fields writes the following to disk:

8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  c: 1157627904        0    unused        0     0         # "raw" part, don't edit
  e: 1155530752        0    4.2BSD     4096 32768     0 

I've got a 3ware 8500-8 on a 5.1-RELEASE system with a 1.7T array that the handbook procedure for adding a dedicated disk worked fine with. In that case the number of sectors was 3418765056 on partition c. No problems with that system for almost a year, same procedure here doesn't work.

Any ideas?

More information about the freebsd-questions mailing list