Subject: install/25146: 2.0: bootselector botched after sysinst upgrade
To: None <>
From: Hubert Feyrer <>
List: netbsd-bugs
Date: 04/12/2004 00:49:33
>Number:         25146
>Category:       install
>Synopsis:       2.0: bootselector botched after sysinst upgrade
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    install-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Apr 11 22:50:00 UTC 2004
>Originator:     Hubert Feyrer
>Release:        NetBSD 2.0_BETA
	<The following information is extracted from your kernel. Please>
	<append output of "ldd", "ident" where relevant (multiple lines).>
System: NetBSD miyu 2.0_BETA NetBSD 2.0_BETA (MIYU) #45: Wed Mar 31 13:28:17 MEST 2004 feyrer@miyu:/home/cvs/src-2.0/sys/arch/i386/compile/MIYU i386
Architecture: i386
Machine: i386
	I had a 1.6.2/i386 machine (running a -current kernel, FWIW),
	that I upgraded to 2.0_BETA using sysinst's upgrade option.
	The machine had Windows on the first MBR partition, and
	NetBSD on the second, with GRUB(!) as boot selector. During
	the upgrade, I select the "BIOS" boot selector (not existing
	one, and not any of the serial ones). Besides other problems
	(see PR 25138, "2.0: sysinst upgrade broken: fsck_ffs bails
	out"), this went ok.

	After everything is done and I reboot the machine, it just
	sits there with a blank screen and a blinking cursor, no
	text. After a while, it boots into Windows (which is installed
	on the first MBR partition, while NetBSD is on the second).

	Rebooting from CDROM, "fdisk -B" just shows garbage in the
	bootselector entries. Resetting with "fdisk -uB" gives me
	a working bootselector back.

	This problem is related to PR 25113 ("2.0: fdisk(8) unusable for
	boot selector manipulation"); It's probably not related to
	PR 23548 ("fdisk in sysinst, off by one")

	Install 1.6.2 and Windows, with a bootselector (either from
	NetBSD or GRUB)
	Upgrade to 2.0 with sysinst
	See a broken/non-working boot selector

	No idea, sorry.

Hubert Feyrer <>
 	<Please check that the above is correct for the bug being reported,>
 	<and append source date of snapshot, if applicable (one line).>