>Synopsis: sysinst left hand doesn't know what its right hand is doing
>Arrival-Date: Sun Jan 02 19:09:00 +0000 2005
>Originator: Robert Elz
>Release: NetBSD 1.6U (-- irrelevant info from send-pr client system)
Prince of Songkla University
System: NetBSD fuchsia.noi.kre.to 1.6U NetBSD 1.6U (FUCHSIA) #51: Wed Jul 23
16:06:08 ICT 2003 kre@xxxxxxxxxxxxxxxxxxx:/usr/obj/sys/FUCHSIA i386
That's all irrelevant. System where the problem was noticed
is an i386 running current as of Dec 22, 2004 (that is, just
before the anoncvs shutdown)
When building a default disklabel, sysinst fails to notice that
the fdisk label has been changed (by sysinst) from what the
drive had when it was detected. It constructs a NetBSD
label wth a bad partition sie (and perhaps a bad offset as well,
I didn't get to test that one).
Have a drive with a Wintrash partition on it. The drive in question
was the drive from my immediately previous PR. The bad extended
partition and the NetBSD partition had been deleted, leaving a
wintrash partition that occupied about 7% of the drive space (< 1GB).
Start sysinst. Go through the normal install process, along the
way, using sysinst' MBR editor to increase the size of the Wintrash
partition (I was making it ~50% of the drive - 6.5GB approx).
Then label the drive the normal creating patitions as
appropriate. Install NetBSD. After NetBSD is running,
use disklabel to examine the label that's been installed.
Notice that partition 'e' has been set aside to map the
Windows MBR partition - but that the size allocated to it is
the size that the windows partition had before it was altered
No idea, haven't looked. Not difficult to repair once aware
of the problem.