Large EIDE Hard Drive

Large EIDE Hard Drive

Post by Mike Wheele » Mon, 21 Jul 1997 04:00:00




> Hello All,

> I am looking for persons who have successfully installed ATA-2 (EIDE)
> Hard Drives of capacity > 2.1 GB.

> My brand spanking new 3.2 GB Quantum hard drive (C/H/S = 6323?,16,63)
> is too big for my BIOS to handle (4092,16,63 = 2.1GB upper limit). To
> get the machine to recognize its existence I lied and put in
> 4096/16/63 as the specs. I then booted linux using (from memory, the
> 1st number might be off here):

>         linux hdc=noprobe hdc=6323,16,63

> at the Lilo prompt. (Allowing probing makes the BIOS managed portion
> of the boot process take a very long time).

> During boot up time I get the following error messages (this may not
> be be a perfect reproduction but it's very close)

> ==============

> kernel: hdc: recal_intr: status=0x51 { DriveRead SeekComplete Error }
> kernel: hdc: recal_intr: status=0x04 { DriveStatus Error }
> kernel: hdc: read_intr: status=0x51 { DriveRead SeekComplete Error }
> kernel: hdc: read_intr: status=0x04 { DriveStatus Error }
> kernel: hdc: recal_intr: status=0x51 { DriveRead SeekComplete Error }
> kernel: hdc: recal_intr: status=0x04 { DriveStatus Error }
> kernel: hdc: read_intr: status=0x51 { DriveRead SeekComplete Error }
> kernel: hdc: read_intr: status=0x04 { DriveStatus Error }
> kernel: ide1: reset: success
> kernel: hdc: set_geometry_intr: status=0x51
> kernel: hdc: set_geometry_intr: status=0x04

> kernel: hdc: recal_intr: status=0x51 { DriveRead SeekComplete Error }
> kernel: hdc: recal_intr: status=0x04 { DriveStatus Error }
> kernel: hdc: read_intr: status=0x51 { DriveRead SeekComplete Error }
> kernel: hdc: read_intr: status=0x04 { DriveStatus Error }
> kernel: hdc: recal_intr: status=0x51 { DriveRead SeekComplete Error }
> kernel: hdc: recal_intr: status=0x04 { DriveStatus Error }
> kernel: hdc: read_intr: status=0x51 { DriveRead SeekComplete Error }
> kernel: hdc: read_intr: status=0x04 { DriveStatus Error }
> kernel: ide1: reset: success
> kernel: hdc: set_geometry_intr: status=0x51
> kernel: hdc: set_geometry_intr: status=0x04

> kernel: end_request: I/O error dev 16:00 sector

> ===============

> Perhaps I need to let it probe first, and I will certainly try, but I
> don't really think that is the problem. I can't try again until this
> evening.

> Also:  "dev 16:00" ???

> Doesn't this mean major_device 16, minor_device 00 ?

> hdc is major 22, minor 00.

> My /dev entries look like the following:

> brw-rw---- 1 root disk    3, 0 Dec 31 1969 hda
> brw-rw---- 1 root disk   22, 0 Dec 31 1969 hdc
> crw-rw-rw- 1 root sys    16, 0 Dec 31 1969 gs4500
> brw-rw---- 1 root cdrom  16, 0 Dec 31 1969 gscd

> Another result of noprobe ?

> Other possibly relevant info:

> ASUS P/I P55TP4N motherboard with BIOS ???
> Intel P120 CPU

> From boot messages:

[SNIPPED]

     I am using a Large Quantum Bigfoot drive (configured as IDE1
Master) without any problem.  (I am running an AMD 6x686 166 with AMI
BIOS and Kernal 2.0.29) I didn't input its data into my BIOS because I'm
not booting it or usinging it through BIOS acess.  On boot you will get
a few messages complaining until it is partitioned and file systemed.
After boot Fdisk /dev/hdc (Master IDE1 is C) create a new partition type
83 Linux native then use mke2fs to create the fiole system then you can
mount it.  You may want to put it in your mtab to make it automount
after boot.  If it is not being recognized by FDISK check cables,
jumpers (ie. master etc.)  If all else fails verify the drive under dos
on a different machine with a new BIOS to handle cylinders past 1023.
   My Drives last cylinder is 65535.

    Hopes this helps a little

----------------------------------------------------------------------

 
 
 

Large EIDE Hard Drive

Post by Alex Pakte » Tue, 22 Jul 1997 04:00:00



> > I am looking for persons who have successfully installed ATA-2
> > Hard Drives of capacity > 2.1 GB.

> > My brand spanking new 3.2 GB Quantum hard drive (C/H/S = 6323?,16,63)
> > is too big for my BIOS to handle (4092,16,63 = 2.1GB upper limit). To
> > get the machine to recognize its existence I lied and put in
> > 4096/16/63 as the specs. I then booted linux using (from memory, the
> > 1st number might be off here):

> >         linux hdc=noprobe hdc=6323,16,63

> > at the Lilo prompt. (Allowing probing makes the BIOS managed portion
> > of the boot process take a very long time).

I'm running two Maxtor 5.1GB drives on my BIOS that doesn't
recognize > 2GB drives.  It was very easy.  It looks like you
may have to change the parameters to lilo.  Here's my
/etc/lilo.conf: (notes follow file)
-----------------------cut-----------------------------
linear
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
disk = /dev/hdc
        sectors = 63
        heads = 16
        cylinders = 9924
image=/vmlinuz
        label=linux
        root=/dev/hda1
        append = "hd=620,64,63 hd=9924,16,63 hd=9924,16,63"
        read-only
----------------end-----------------------------------------
I have three hard drives.  The first is 1GB, no problems.
The secord two, however, are too big for the BIOS.  I've
jumpered them to tell the bios that they are only 2GB
drives, or the system won't boot.  To use them, I had to
do the following:

* put the "linear" directive in the /etc/lilo.conf file
* put the "append" directive in the boot options
* when using cfdisk to partition the drives, I had to
   give command-line options to tell it the disk geometry.

The rerun /sbin/lilo, and it worked like a charm.

Alex
----

 
 
 

Large EIDE Hard Drive

Post by Tom sulliv » Tue, 29 Jul 1997 04:00:00


I installed Slackware 3.2 on a 6.4 gig Seagate EIDE drive, and it installed
without a hitch. My ROM BIOS supports LBA mode. If yours does not, either upgrade
your ROM BIOS, or get one of those EIDE adapter cards with an on-board LBA BIOS,
such as those from Promise Technology. For an ISA bus, they have the EIDEMAX, or
for VLB, they have the EIDE2300+



: > > I am looking for persons who have successfully installed ATA-2
: > > Hard Drives of capacity > 2.1 GB.
: > >
: > > My brand spanking new 3.2 GB Quantum hard drive (C/H/S = 6323?,16,63)
: > > is too big for my BIOS to handle (4092,16,63 = 2.1GB upper limit). To
: > > get the machine to recognize its existence I lied and put in
: > > 4096/16/63 as the specs. I then booted linux using (from memory, the
: > > 1st number might be off here):
: > >
: > >         linux hdc=noprobe hdc=6323,16,63
: > >
: > > at the Lilo prompt. (Allowing probing makes the BIOS managed portion
: > > of the boot process take a very long time).

: I'm running two Maxtor 5.1GB drives on my BIOS that doesn't
: recognize > 2GB drives.  It was very easy.  It looks like you
: may have to change the parameters to lilo.  Here's my
: /etc/lilo.conf: (notes follow file)
: -----------------------cut-----------------------------
: linear
: boot=/dev/hda
: map=/boot/map
: install=/boot/boot.b
: prompt
: timeout=50
: disk = /dev/hdc
:         sectors = 63
:         heads = 16
:         cylinders = 9924
: image=/vmlinuz
:         label=linux
:         root=/dev/hda1
:         append = "hd=620,64,63 hd=9924,16,63 hd=9924,16,63"
:         read-only
: ----------------end-----------------------------------------
: I have three hard drives.  The first is 1GB, no problems.
: The secord two, however, are too big for the BIOS.  I've
: jumpered them to tell the bios that they are only 2GB
: drives, or the system won't boot.  To use them, I had to
: do the following:

: * put the "linear" directive in the /etc/lilo.conf file
: * put the "append" directive in the boot options
: * when using cfdisk to partition the drives, I had to
:    give command-line options to tell it the disk geometry.

: The rerun /sbin/lilo, and it worked like a charm.

: Alex
: ----