On Mon, Oct 14, 2002 at 10:52:08PM +0200, Cliff Albert wrote:
> On Mon, Oct 14, 2002 at 08:53:21AM -0500, Lista de NetBSD Users wrote:
> 
> > ahc1 at pci0 dev 9 function 0
> > ahc1: interrupting at irq 11
> > ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
> > scsibus0 at ahc1: 16 targets, 8 luns per target
> > [...]
> > sd0 at scsibus0 target 5 lun 0: <IBM, DDYS-T36950N, S93E> SCSI3 0/direct fixed
> > sd0: 32768 MB, 15110 cyl, 12 head, 370 sec, 512 bytes/sect x 67108864 sectors
> >      ^^^^^                         ^^^                       ^^^^^^^^
> > sd0: sync (50.0ns offset 8), 16-bit (40.000MB/s) transfers, tagged queueing
> > sd1 at scsibus0 target 6 lun 0: <IBM, DDYS-T36950N, S96H> SCSI3 0/direct fixed
> > sd1: 35003 MB, 15110 cyl, 12 head, 395 sec, 512 bytes/sect x 71687340 sectors
> >      ^^^^^                         ^^^                       ^^^^^^^^
> > sd1: sync (50.0ns offset 8), 16-bit (40.000MB/s) transfers, tagged queueing
> 
> Some IBM disks have a jumper called '32-GB clip mode'. This reduces the
> disk capacity to 32 GB to support some older controllers and stuff. It
> might be jumpered.

Hum, and on SCSI disks it may be controlled by a command and stored in
firmware. Maybe winXP did something bad here.
Or maybe it's just the adaptec BIOS which does it, from infos it gets from
the MBR.
Try zapping the whole MBR
dd if=/dev/zero of=/dev/rsd0d bs=64k count=100
(this will kill your partitions, so don't do this if you have valuable datas
on the disk) and try a *cold* boot.
Hum, I hope the adaptec hasn't stored something in its NVRAM about the disk.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
--