misc/72895: Sysinstall generates invalid partition table

Harald Schmalzbauer test2root at schmalzbauer.de
Tue Oct 19 13:00:23 PDT 2004


>Number:         72895
>Category:       misc
>Synopsis:       Sysinstall generates invalid partition table
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 19 20:00:22 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Harald Schmalzbauer
>Release:        FreeBSD 5.3-RC1 i386
>Organization:
>Environment:
System: FreeBSD test2.flintsbach.schmalzbauer.de 5.3-RC1 FreeBSD 5.3-RC1 #0: Sun Oct 17 01:25:37 UTC 2004 root at wv1u.samsco.home:/usr/obj/usr/src/sys/GENERIC i386


	
>Description:
	Sysinstall marks any FreeBSD slice (partition) as active.
	So if you create two partitions with ID 165, the partition
	table in the MBR is invalid since there are two active
	partitions.
	This is only with partitions of type 165, it's possible to create
	any other partition and only the FreeBSD (165) one will become
	active!
	I have only checked i386 systems, no clue about other platforms.
>How-To-Repeat:
	Call sysinstall on a multi-drive system or boot from CD and create
	two partitions (slices) with ID 165 and after the final reboot
	the system (i386) wont come up and complain about wrong pratition
	table.
>Fix:

	Make sysinstall check if there's more than one 165 slice instead of
	marking any 165 with flag 80. I'm no coder, so I can't do it, sorry!

>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list