If you do a hexdump on boot0 and the first sector of your disk, you'll see
that boot0 has been copied onto your disk, broken partition table and
all. If you then run fdisk on the disk and put in the 'right' number of
sectors and let it automatically recalculate everything else, you'll get a
dece
On Fri, 27 Oct 2000, Robert Nordier wrote:
>
> Just doing the disklabel -w -r followed by the disklabel -B is creating
> a dangerously dedicated disk, which your BIOS apparently doesn't like.
> (See the first hex dump you did, where boot1 has ended up in the MBR.)
>
> That's why installing boo
On Fri, 27 Oct 2000, Fred Clift wrote:
>
> If you do a hexdump on boot0 and the first sector of your disk, you'll see
> that boot0 has been copied onto your disk, broken partition table and
a typo/thinko -- replace boot0 here with boot1
--
Fred Clift - [EMAIL PROTECTED] -- Remember: If brute
I've messed with these a lot and I'm pretty sure that the bios is trying
to be 'compatible' with the geometry information it finds on the disk,
Theoretically, if you set up a disk with one brand X disk controller,
you'll get a different fake CHS mapping than you would with a brand Y
controller.
> I know I'm getting into this late but I can reliably reproduce this
> problem. I ran into it about 3 months ago when using a custom PXE-based
> installer for our SCSI boxes. I even annoyed -hackes and got John Baldwin
> to help me decode the register dumps. The IP does end up in the SCSI BIOS
On Fri, 27 Oct 2000, Paul Saab wrote:
> Mike Smith ([EMAIL PROTECTED]) wrote:
> > >
> > > :I'm just curious. How many disks are in this box? We saw something
> > > :similar here at work and it turned out that there were multiple disklabels
> > > :on the other disks and for somereason it was co
6 matches
Mail list logo
