Subject: Re: RAMdisk installation -> boot overlaps partition
To: None <firstname.lastname@example.org>
From: Izumi Tsutsui <email@example.com>
Date: 06/25/2006 19:40:36
> > - What version did you try? (3.0 release or -current HEAD?)
> I want to install 3.0
> > - Could you show disklabel output?
> sure, with the default layout:
> # disklabel sd0
> # /dev/rsd0c:
> 8 partitions:
> # size offset fstype [fsize bsize cpg/sgs]
> a: 3900225 805 4.2BSD 2048 16384 23112 # (Cyl. 1
> - 4845)
> b: 262430 3901030 swap # (Cyl. 4846
> - 5171)
> c: 4163460 0 unused 0 0 # (Cyl. 0
> - 5171)
Hmm. Was fstype of partition c unused by default on sysinst menu?
Did your disk have existing label before install?
> This happened during sysinst, but also manually. Because it doesn't work
> with sysint I tried to disklabel on my own.
disklabel -B command searches BOOT partition and install
bootloader into it, but there is no BOOT paritition on your
disk so it fails. To install bootblock into your disk
you can change fstype of partition c to BOOT (it's a hack), or
can create a new partition d (or so) located at cylinder zero and
whose fstype is marked BOOT and since partition a on your disk
already has proper offset for bootblock.
IIRC, sysinst marks partition c as BOOT and it put some space
before partition a so it should work, but I'm not sure what
happens if there is existent disklabel...