fdisk, sysinstall and 6.1-BETA3/amd64

Matt Dawson matt at mattsnetwork.co.uk
Wed Mar 15 19:20:48 UTC 2006

Hi folks,
	I'm moving a server over to amd64 in the next week or so and I'm preparing 
the RAID1 disk set with the 64 bit ports as we speak. I came across a nasty 
little bug whilst doing so.

Motherboard is a Gigabyte GA-K8U with a ULi SATA controller and AR0 set up as 
a RAID1 array using FreeBSD pseudo-RAID (ULi's metadata isn't supported). So 
far, so good. Then into sysinstall to create the partitions. To have the 
required number of partitions (to make my dump script easier to manage) I 
need two slices. The problem is that the BETA3 sysinstall marks both slices 
active, causing the BIOS to halt on boot with an "Invalid partition table" 

Is this a bug, or is this something I'm doing wrong. Never had this problem 
before, and the server has always had two slices on a RAID1 (RAID5 on the 
Proliant) array, although admittedly on i386. It's easy enough to fix (just 
fdisk -a /dev/ar0 from a fixit and mark slice 1 as active) but it's rather 
Matt Dawson.

matt at mattsnetwork.co.uk

More information about the freebsd-stable mailing list