> hdc: Maxtor 91728D8, 16479MB w/512kB Cache, CHS=33483/16/63, (U)DMA
>
> > the hdparm -I output,
Try /sbin/hdparm -I /dev/hdc and see if the CHS and capacity do not mimic
or report as only an 8.4GB disk.
> # /sbin/hdparm -i /dev/hdc
>
> /dev/hdc:
>
> Model=Maxtor 91728D8, FwRev=GAS54112, SerialNo=A805S1XC
> Config={ Fixed }
> RawCHS=33483/16/63, TrkSize=0, SectSize=0, ECCbytes=29
> BuffType=3(DualPortCache), BuffSize=512kB, MaxMultSect=16, MultSect=off
> DblWordIO=no, maxPIO=2(fast), DMA=yes, maxDMA=2(fast)
> CurCHS=33483/16/63, CurSects=33750864, LBA=yes, LBAsects=33750864
> tDMA={min:120,rec:120}, DMA modes: mword0 mword1 *mword2
> IORDY=on/off, tPIO={min:120,w/IORDY:120}, PIO modes: mode3 mode4
> UDMA modes: mode0 mode1 mode2
> Drive Supports : ATA/ATAPI-4 T13 1153D revision 17 : ATA-1 ATA-2 ATA-3 ATA-4
>
> As you can see in hdparm it is.
That is because we corrected and updated the drive->id table.
Here is a classic example of kernel fixups and raw drive data
hdparm -i /dev/hda (kernel fixups)
/dev/hda:
Model=QUANTUM FIREBALL EX12.7A, FwRev=A0A.0400, SerialNo=372828774975
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=24704/16/63, TrkSize=32256, SectSize=21298, ECCbytes=4
BuffType=3(DualPortCache), BuffSize=418kB, MaxMultSect=16, MultSect=off
DblWordIO=no, maxPIO=2(fast), DMA=yes, maxDMA=2(fast)
CurCHS=24704/16/63, CurSects=24901632, LBA=yes, LBAsects=24901632
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2
IORDY=on/off, tPIO={min:120,w/IORDY:120}, PIO modes: mode3 mode4
UDMA modes: mode0 mode1 *mode2
Drive Supports : ATA/ATAPI-4 T13 1153D revision 15 : ATA-1 ATA-2 ATA-3 ATA-4
hdparm -I /dev/hda (raw drive data)
/dev/hda:
Model=UQNAUT MIFERABLLE 1X.2A7 , FwRev=0A.A4000, SerialNo=73828
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=32256, SectSize=21298, ECCbytes=4
BuffType=3(DualPortCache), BuffSize=418kB, MaxMultSect=16, MultSect=off
DblWordIO=no, maxPIO=2(fast), DMA=yes, maxDMA=2(fast)
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=24901632
WARNING 8387568 ORPHANED SECTORS :: KERNEL REPORTING ERROR
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2
IORDY=on/off, tPIO={min:120,w/IORDY:120}, PIO modes: mode3 mode4
UDMA modes: mode0 mode1 *mode2
Drive Supports : ATA/ATAPI-4 T13 1153D revision 15 : ATA-1 ATA-2 ATA-3 ATA-4
As you can clearly see, the drive still tells you that it only has a CHS
geometry of 16383/16/63 and capacity of 16514064.
The reality is that drive's CHS is 24704/16/63 and capacity is 24901632.
So even if we assumed that the drive knows all, it tells us enough to
figure out what it should be if the reported info is incorrect from a
third party like the BIOS.
Andre Hedrick
The Linux IDE guy
http://www.dyer.vanderbilt.edu/server/udma/2.2.7.uniform-ide-6.19.patch.gz
http://www.dyer.vanderbilt.edu/server/udma/ide.2.0.37pre11+pat7.gz
http://www.dyer.vanderbilt.edu/server/udma/hdparm-3.5i.patch.gz
APC UPS Daemon Support Center.
http://www.brisse.dk/site/apcupsd/
GPLed source on April 7, 1999
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/