Problems with number of heads from DOS FDISK partitions and Linux fdisk on 8.4 GB drive

Problems with number of heads from DOS FDISK partitions and Linux fdisk on 8.4 GB drive

Post by Leslie Groe » Sun, 31 Jan 1999 04:00:00



Hi There

I have a problem with the partitions on my new Western Digital Cavaliar
8.4 GB that has been partitioned by DOS FDISK as seen by Linux.

I am running Red Hat 4.1, kernel v 2.0.27 on a
Micron 133 MHz Mironics M54Hi Motherboard with
Phoenix Bios 4.05 upgrade from Micro Firmware with
Win95 on /dev/hda1 (800 MB of 1.6 GB) and Linux on the other half of the
disk.  I will upgrade to RH5.2 once I get the disk problem fixed.

Drives are seen as
hda: WDC AC31600H, 1549MB w/128kB Cache, LBA, CHS=787/64/63
hdb: WDC AC28400R, 8063MB w/512kB Cache, LBA, CHS=16383/16/63

The CHS corresponds to the specs from the manufacturer and how the BIOS
sees the disk.  I feed in the CHS for the 8.4 GB drive on boot-up (using
LOADLIN hdb=16383/16/63).  If I don't do that, it sees the drive as
CHS=1027/255/63.

I partitioned the drive using DOS FDISK and Win95 can see the partitions
fine. There are 4 partitions, 1 primary and 3 logical in an extended
partition to get around the 2.1 GB limit with FAT-16 partitions (I don't
have OSR2 so need to stick to FAT-16).

When I boot into Linux, I see the partitions on boot up

Partition check:
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 >
 hdb: hdb1 hdb2 < hdb5 hdb6 hdb7 >

However, cfdisk gives a fatal error -- "Cannot seek on disk drive" and
linux fdisk gives the following

Command (m for help): p

Disk /dev/hdb: 16 heads, 63 sectors, 16383 cylinders
Units = cylinders of 1008 * 512 bytes

   Device Boot   Begin    Start      End   Blocks   Id  System
/dev/hdb1            1        1     4155  2094088+   6  DOS 16-bit >=32M
Partition 1 does not end on cylinder boundary:
     phys=(276, 239, 63) should be (276, 15, 63)
/dev/hdb2         3350     4156    15345  5639760    5  Extended
Partition 2 does not end on cylinder boundary:
     phys=(1022, 239, 63) should be (1022, 15, 63)
/dev/hdb5         3350     4156     8310  2094088+   6  DOS 16-bit >=32M
/dev/hdb6         7723     8311    12465  2094088+   6  DOS 16-bit >=32M
/dev/hdb7        12096    12466    15345  1451488+   6  DOS 16-bit >=32M

Command (m for help): v

Partition 1 does not end on cylinder boundary:
     phys=(276, 239, 63) should be (276, 15, 63)
Partition 1: head 240 greater than maximum 16
Partition 5: head 240 greater than maximum 16
Warning: partition 1 overlaps partition 5.
Partition 6: head 240 greater than maximum 16
Warning: partition 5 overlaps partition 6.
Partition 7: head 240 greater than maximum 16
Warning: partition 6 overlaps partition 7.
Logical partition 5 not entirely in partition 2
1046360 unallocated sectors

I did try deleting all the partitions using linux fdisk and repartitioning
but I still get overlap warnings for the various partitions.

I can mount the partitions in linux and I can create linux partitions but
I am concerned about the warning of an overlap - will this cause a problem
later?  It looks like the Start cylinder of the partitions do not overlap
but the Begin cylinders do.  I am not sure of the difference between
these.  I do not want to be overwriting data on one partition while
writing to another.

Also, I want to install Win/NT on this disk later and having a clean
partition configuration I think would be safer.  How do I fix the problem
of partition boundaries?

Thanks in advance for any advice/help.

Leslie Groer

 
 
 

Problems with number of heads from DOS FDISK partitions and Linux fdisk on 8.4 GB drive

Post by Jerry Lynn Krep » Sun, 31 Jan 1999 04:00:00


Have you tried the "linear" option in lilo.conf?
Visit
        http://metlab.unc.edu/pub/Linux/docs/HOWTO

and read the Large Disk HOWTO...
It explains how 7.875GB is the addressable limit.  Don't know if that
still is valid.

Jerry


> Hi There

> I have a problem with the partitions on my new Western Digital Cavaliar
> 8.4 GB that has been partitioned by DOS FDISK as seen by Linux.

> I am running Red Hat 4.1, kernel v 2.0.27 on a
> Micron 133 MHz Mironics M54Hi Motherboard with
> Phoenix Bios 4.05 upgrade from Micro Firmware with
> Win95 on /dev/hda1 (800 MB of 1.6 GB) and Linux on the other half of the
> disk.  I will upgrade to RH5.2 once I get the disk problem fixed.

> Drives are seen as
> hda: WDC AC31600H, 1549MB w/128kB Cache, LBA, CHS=787/64/63
> hdb: WDC AC28400R, 8063MB w/512kB Cache, LBA, CHS=16383/16/63

> The CHS corresponds to the specs from the manufacturer and how the BIOS
> sees the disk.  I feed in the CHS for the 8.4 GB drive on boot-up (using
> LOADLIN hdb=16383/16/63).  If I don't do that, it sees the drive as
> CHS=1027/255/63.

> I partitioned the drive using DOS FDISK and Win95 can see the partitions
> fine. There are 4 partitions, 1 primary and 3 logical in an extended
> partition to get around the 2.1 GB limit with FAT-16 partitions (I don't
> have OSR2 so need to stick to FAT-16).

> When I boot into Linux, I see the partitions on boot up

> Partition check:
>  hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 >
>  hdb: hdb1 hdb2 < hdb5 hdb6 hdb7 >

> However, cfdisk gives a fatal error -- "Cannot seek on disk drive" and
> linux fdisk gives the following

> Command (m for help): p

> Disk /dev/hdb: 16 heads, 63 sectors, 16383 cylinders
> Units = cylinders of 1008 * 512 bytes

>    Device Boot   Begin    Start      End   Blocks   Id  System
> /dev/hdb1            1        1     4155  2094088+   6  DOS 16-bit >=32M
> Partition 1 does not end on cylinder boundary:
>      phys=(276, 239, 63) should be (276, 15, 63)
> /dev/hdb2         3350     4156    15345  5639760    5  Extended
> Partition 2 does not end on cylinder boundary:
>      phys=(1022, 239, 63) should be (1022, 15, 63)
> /dev/hdb5         3350     4156     8310  2094088+   6  DOS 16-bit >=32M
> /dev/hdb6         7723     8311    12465  2094088+   6  DOS 16-bit >=32M
> /dev/hdb7        12096    12466    15345  1451488+   6  DOS 16-bit >=32M

> Command (m for help): v

> Partition 1 does not end on cylinder boundary:
>      phys=(276, 239, 63) should be (276, 15, 63)
> Partition 1: head 240 greater than maximum 16
> Partition 5: head 240 greater than maximum 16
> Warning: partition 1 overlaps partition 5.
> Partition 6: head 240 greater than maximum 16
> Warning: partition 5 overlaps partition 6.
> Partition 7: head 240 greater than maximum 16
> Warning: partition 6 overlaps partition 7.
> Logical partition 5 not entirely in partition 2
> 1046360 unallocated sectors

> I did try deleting all the partitions using linux fdisk and repartitioning
> but I still get overlap warnings for the various partitions.

> I can mount the partitions in linux and I can create linux partitions but
> I am concerned about the warning of an overlap - will this cause a problem
> later?  It looks like the Start cylinder of the partitions do not overlap
> but the Begin cylinders do.  I am not sure of the difference between
> these.  I do not want to be overwriting data on one partition while
> writing to another.

> Also, I want to install Win/NT on this disk later and having a clean
> partition configuration I think would be safer.  How do I fix the problem
> of partition boundaries?

> Thanks in advance for any advice/help.

> Leslie Groer


 
 
 

Problems with number of heads from DOS FDISK partitions and Linux fdisk on 8.4 GB drive

Post by Charles Sulliva » Mon, 01 Feb 1999 04:00:00


The older kernels and fdisk have problems with large disks, but I
think your particular problem is due mainly to what fdisk sees and
what you are telling the kernel.  If your bios has LBA enabled, fdisk
will _not_ see the manufacturers numbers for the C/H/S but the LBA
numbers which will be 1027/255/63.

(LBA maps the "actual" number of heads to a ficticious 255 logical
heads, thus reducing the logical cylinders to a more manageable
value.)

What happens if you do _not_ feed LOADLIN the C/H/S ?


>Hi There

>I have a problem with the partitions on my new Western Digital Cavaliar
>8.4 GB that has been partitioned by DOS FDISK as seen by Linux.

>I am running Red Hat 4.1, kernel v 2.0.27 on a
>Micron 133 MHz Mironics M54Hi Motherboard with
>Phoenix Bios 4.05 upgrade from Micro Firmware with
>Win95 on /dev/hda1 (800 MB of 1.6 GB) and Linux on the other half of the
>disk.  I will upgrade to RH5.2 once I get the disk problem fixed.

>Drives are seen as
>hda: WDC AC31600H, 1549MB w/128kB Cache, LBA, CHS=787/64/63
>hdb: WDC AC28400R, 8063MB w/512kB Cache, LBA, CHS=16383/16/63

>The CHS corresponds to the specs from the manufacturer and how the BIOS
>sees the disk.  I feed in the CHS for the 8.4 GB drive on boot-up (using
>LOADLIN hdb=16383/16/63).  If I don't do that, it sees the drive as
>CHS=1027/255/63.

>I partitioned the drive using DOS FDISK and Win95 can see the partitions
>fine. There are 4 partitions, 1 primary and 3 logical in an extended
>partition to get around the 2.1 GB limit with FAT-16 partitions (I don't
>have OSR2 so need to stick to FAT-16).

>When I boot into Linux, I see the partitions on boot up

>Partition check:
> hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 >
> hdb: hdb1 hdb2 < hdb5 hdb6 hdb7 >

>However, cfdisk gives a fatal error -- "Cannot seek on disk drive" and
>linux fdisk gives the following

>Command (m for help): p

>Disk /dev/hdb: 16 heads, 63 sectors, 16383 cylinders
>Units = cylinders of 1008 * 512 bytes

>   Device Boot   Begin    Start      End   Blocks   Id  System
>/dev/hdb1            1        1     4155  2094088+   6  DOS 16-bit >=32M
>Partition 1 does not end on cylinder boundary:
>     phys=(276, 239, 63) should be (276, 15, 63)
>/dev/hdb2         3350     4156    15345  5639760    5  Extended
>Partition 2 does not end on cylinder boundary:
>     phys=(1022, 239, 63) should be (1022, 15, 63)
>/dev/hdb5         3350     4156     8310  2094088+   6  DOS 16-bit >=32M
>/dev/hdb6         7723     8311    12465  2094088+   6  DOS 16-bit >=32M
>/dev/hdb7        12096    12466    15345  1451488+   6  DOS 16-bit >=32M

>Command (m for help): v

>Partition 1 does not end on cylinder boundary:
>     phys=(276, 239, 63) should be (276, 15, 63)
>Partition 1: head 240 greater than maximum 16
>Partition 5: head 240 greater than maximum 16
>Warning: partition 1 overlaps partition 5.
>Partition 6: head 240 greater than maximum 16
>Warning: partition 5 overlaps partition 6.
>Partition 7: head 240 greater than maximum 16
>Warning: partition 6 overlaps partition 7.
>Logical partition 5 not entirely in partition 2
>1046360 unallocated sectors

>I did try deleting all the partitions using linux fdisk and repartitioning
>but I still get overlap warnings for the various partitions.

>I can mount the partitions in linux and I can create linux partitions but
>I am concerned about the warning of an overlap - will this cause a problem
>later?  It looks like the Start cylinder of the partitions do not overlap
>but the Begin cylinders do.  I am not sure of the difference between
>these.  I do not want to be overwriting data on one partition while
>writing to another.

>Also, I want to install Win/NT on this disk later and having a clean
>partition configuration I think would be safer.  How do I fix the problem
>of partition boundaries?

>Thanks in advance for any advice/help.

>Leslie Groer

 
 
 

1. Patritioning WD 8.4 GB drive and Linux and EZ-Drive/EZ-Bios

Hi

I just installed a Western Digital 8.4 GB drive on my Micron machine
with a Micronics M54Hi motherboard as the second drive.  This has the
PhoenixBIOS 4.04 which cannot support disks larger than 7.8 GB.  There
is a BIOS (v5.05) upgrade available from Micro Firmware but for $79!  I
installed the WD EZ-Drive software and it partitioned the drive in 4
with about 2.1 GB per partition.  I can see these partitions OK in Win95
(though I do have a spurious E: drive that cannot be accessed).

In Linux (RedHat 4.1 - yes, part of the reason of getting the new drive
was to upgrade to RH5.2), fdisk sees only the first partition of the hard
drive (as /dev/hdb1 with about 2.1GB) with the rest of the drive seen as one
partition with unknown type.  If I use linux fdisk to partition the disk
in what I _think_ is the same partitions as EZ-Drive used then Win95 sees
the first partition but cannot read the other three.  Repartitioning the
drive with EZ-Drive causes the original problem (i.e. can only see the two
partitions in Linux).  

I know Western Digital claims that EZ-Drive does not support Unix but
the Large Disk mini-HOWTO claims that Linux will work with EZ-Drive.  I
seem to be almost there.  Has anyone got this working or have any
suggestions?

Thanks in advance for any advice.

Leslie Groer

2. FTP file perm

3. linux > 8.4 gb's of 10 gb disk?

4. SAMBA and W98 performance

5. Linux and IDE (ATA) Hard Drives > 8.4 GB

6. RedHat 5.1 losing ip address

7. linux fdisk hidden fat32 (1b) --> fat32 (0b) = dos fdisk fat16 ???

8. Video software???

9. dos fdisk & linux fdisk GREAT INCOMPATIBILITY

10. Maxtor 8.4 reports 20gig after fdisk

11. FDISK dos vs. FDISK linux

12. DOS FDISK vs. Linux FDISK

13. DOS fdisk won't recognize changes made by linux fdisk