Partition Table
 

I dont know how this happened without me noticing but Im missing around 10GB of space off my drive.

This partition table:

Is what my drive currently shows, i.e. the drive being used to its full capacity but...

Swap is reported as:

Which seems to me to be 2GB...ok fair play

So there we have 29GB + 772MB = 29.7GB + the 2GB swap = 31GB meaning that 9GB of space from my drive is missing!

Why does fdisk not show it, does anyone else have this problem?

Thanks
Shak

Shak, what did you break this week? How you been?

I've got a 40 too, here's the output of my fdisk, fully used:
Disk /dev/hde: 240 heads, 63 sectors, 5169 cylinders
Units = cylinders of 15120 * 512 bytes

Device Boot Start End Blocks Id System
/dev/hde1 * 1 3 22648+ 83 Linux
/dev/hde2 4 68 491400 82 Linux swap
/dev/hde3 69 5169 38563560 83 Linux

Check your cylinder count against the output of:

hdparm -i /dev/hde

By comparison here's mine, there's a longshot we have the same drive, although I doubt it, Western Digi 7200?

/dev/hde:

Model=WDC WD400BB-00AUA1, FwRev=18.20D18, SerialNo=WD-WMA6R2754114
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=40
BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=78165360
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=no WriteCache=enabled
Drive conforms to: device does not report version: 1 2 3 4 5

There is an off possibility you've got the wrong number of cylinders registered, but thats an oldschool problem and you've got some hyped up dualie althon rig, right?

Also might want to try cfdisk, sometimes I get it to print things right where fdisk fubars something.

Cheers,

Finegan

Hi Finegan, Im fine thanks and yourself?

/hdaprm -i reports

So we dont have the same drive..

also cfdisk reports:

Therefore cfdisk is reporting the same amount :(

Sounds like I have the wrong number of cylinders registered :(

Darn, is that hard to fix?

Shak

At first guess I figured that you were discounting the space eaten by raw inodes... but looking at my own df that doesn't make sense, I've got a little over 1/2 a Gig of swap making the total missing about 1GB, which is typical, but doesn't account for a missing 9 unless you went with tiny little inodes, mine are 4k, but even that...:

bash-2.05a# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hde3 37355048 10873968 24552904 31% /
/dev/hde1 21929 8193 12604 40% /boot
//wurlitzer/public 56814592 16802816 40011776 30% /mnt/wurl

Also, I was wrong about the cylinder guess, yours has more bytes per cylinder. Look after UNITS=. Different manufacturers, pretty typical, not a drastic difference either.

Maybe inodes... No wait, BIOS issues... okay I'm wandering here, and this is guessland. Older BIOSes couldn't handle above 8GB, then 16, then 32... which is basically what your machine is reporting it has. Now fdisk is fine, it sees every cylinder as used, look at the start and ends of the 3 parts, good slice job there too, right on the 1k mark.

Now some drives came with jumper setting, among them maxtors, so that the first 32 or last 32 Gb were reported... I don't know why or the specifics, just what I remember from dropping a 60GB in my file server a few months back. Check the maxtor homepage for that drive model and then take a look at the jumper settings.

I know that this could be a hardware goof that looks fine from software that talks directly to the drive like hdparm and the fdisks. Anyway, that's a best guess...

Oh, I've been alright. I got so bored this evening I got samba working and finally got my scanner up. There's an old postscript printer around here that's next.

Cheers,

Finegan

But..

Cfdisk shows that /dev/hda3 is 31GB instead of 29GB as reported by df -h..err whats going on!?

Shak

Nah, gotta remember that's 31798MB, and there are 1024 MB to the GB, so its reallt just above 31GB, and I bet the df is rounding down the 29... that's the inode loss. But really look at the df, which is the third partition. Its the one thats short the 8GB because I'm almost certain its the last 8GB of the partition. I just tried to look at the Maxtor page about it, but it requires flash and I've recently horked my mozilla install...

Cheers,

Finegan

I looked at Maxtor's site, they say about RH 5.2 that:

"The / (root) partition must reside within the first 8.4GB od the drive"


So there could be a problem, Ill try looking at J26 (jumper 26) on the hard drive as that is meant to keep the full storage going, but if applied in Linux "may cause the full drive not to be seen"

BIOS reports it @ 40GB as did the Debian installer, but not Gentoo!

Shak

The first sounds like the old LILO 1024 cylinder issue that went the way of the 3 horned catfish about a year ago. Yeah, I'de argue the second one... wonder how Debian gets around it... I figured it would be a hardware issue, solely, weird.

Cheers,

Finegan

Ill ahvea look on a debian install disk what size ther drive shows up as!

Shak