[lkml]   [1999]   [Dec]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: over 5Gb missing from a 13.5Gb disk
In <> Guest section DW ( wrote:
GD> On Tue, Dec 07, 1999 at 09:07:49PM +0300, Khimenko Victor wrote:

>> > All large disks will show RawCHS=16383/16/63, entirely independent of the
>> > BIOS (which is not involved at all). It is the ATA standard.
>> Huh ?
>> -- cut --
>> [root@localhost /root]# hdparm -i /dev/ide/hd/c0b0t0u0
>> /dev/ide/hd/c0b0t0u0:
>> Model=IBM-DJNA-371350, FwRev=J76OA30K, SerialNo=GM0GMGL2059
>> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
>> RawCHS=26310/16/63, TrkSize=0, SectSize=0, ECCbytes=34
>> BuffType=3(DualPortCache), BuffSize=1966kB, MaxMultSect=16, MultSect=off
>> DblWordIO=no, maxPIO=2(fast), DMA=yes, maxDMA=2(fast)
>> CurCHS=1650/255/63, CurSects=26520480, LBA=yes
>> LBA CHS=825/510/63 Remapping, LBA=yes, LBAsects=26520480
>> tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2
>> IORDY=on/off, tPIO={min:240,w/IORDY:120}, PIO modes: mode3 mode4
>> UDMA modes: mode0 mode1 *mode2
>> -- cut --
>> As you can see RawCHS here is 26310/16/63 and all is working like a charm.
>> As I have EXACTLY same model as Wichert (including FwRev and such) I'm pretty
>> sure it's something in BIOS and/or recent kernel changes (I'm still using
>> 2.2.10ac10)...

GD> You cheat yourself by using a hdparm/kernel combination that lies
GD> to you. Try hdparm -I to see the truth.

What's "truth" ? Why do you think I'm need information written on HDD ? I'm not.
What I need in 99% cases is working HDD. Yes, sometimes it's good to have
information directly from HDD (if you'll get not RawCHS != 16383/16/63 for
HDD > 8GiB you can be sure that something is wrong; sometimes serial number
can be needed, etc) but in most cases you are more interested in kernel
imagination about HDD. And IF kernel belives in "truth" that RawCHS is
16383/16/63 (Wichert'scase) you are in trouble. If kernel believes in "lie"
like shown above (my case) you are fine.

GD> (Yes, in the good old days "hdparm -i" was useful. These days it gives
GD> corrupted info, and one needs "hdparm -I".)

It gives you info from kernel. And in most cases it's what you want.
Yes, it's not info from HDD but it's what's needed.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:55    [W:0.107 / U:0.184 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site