Greetings,A friend of mine just wrestled with a similar problem. Turns out there were some jumpers on the drive that selected between 82GB and 32GB (it's an 82GB drive, and the BIOS on his new ABIT mobo as well as W2K both saw it as 32GB). Changing the jumper from 32 to 82 made the difference.
I am running a mix of testing and unstable. I am using the unstable version of fdisk that comes with the util-linux package.
I recently installed a new Samsung 60 MB HD into a 1998 "vintage" Celeron machine as /dev/hdb. The BIOS reports the drive as 30 MB.
I thought that Debian would see the whole drive, but here is what dmesg reports:
ide0: BM-DMA at 0x1420-0x1427, BIOS settings: hda:pio, hdb:DMA hdb: SAMSUNG SP6003H, ATA DISK drive hdb: setmax LBA 117304992, native 66055248 hdb: 66055248 sectors (33820 MB) w/2048KiB Cache, CHS=4111/255/63, UDMA(33) hdb: hdb1 hdb2 hdb3 < hdb5 hdb6 >
Here is what Debian's fdisk reports:
Disk /dev/hdb: 33.8 GB, 33820286976 bytes 255 heads, 63 sectors/track, 4111 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
I then booted Knoppix, and it sees the whole 60 MB. Here is what fdisk on Knoppix reports:
Disk /dev/hdb: 60.0 GB, 60060155904 bytes 255 heads, 63 sectors/track, 7301 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
I then used Knoppix fdisk to create partitions, like this:
Device Boot Start End Blocks Id System /dev/hdb1 1 609 4891761 b Win95 FAT32 /dev/hdb2 610 1339 5863725 83 Linux /dev/hdb3 1340 5000 29406982+ 5 Extended /dev/hdb5 1340 1358 152586 82 Linux swap /dev/hdb6 1359 1541 1469916 83 Linux
Of course, now when I boot into Debian I get an error message that that the filesystem size of /dev/hdb2 (according to superblock) is 1588426 and the physical size of device is 1465931.
What have I done wrong?
-- Kent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
