Its not the one hes trying to boot from, he can boot into linux then we read on the seagate spec sheet:
On drives greater than 33.8GB, Limit Capacity jumper changes total available sectors as reported via Identify Drive data words 60-61 to 33.8GB to solve issues with certain BIOS during power on. The ATA Read Native Max command will report true full capacity. The ATA Set Max command will restore true full capacity to the operating system drivers. Third party partitioning software may be needed to achieve full capacity when using this option jumper. but fdisk still only creates a partition of 31gbs in size we can goto the expert mode in fdisk and increase the cylinders and heads and when we create an ext2/3 partition the inode tables increase from 256 to 8000 but when running mkfs -t ext2 -j /dev/hdc1, once it reaches 32 it starts giving errors like hdc: Drive ready seek complete error, sector id not found. ----- Original Message ----- From: Jim Cheetham <[EMAIL PROTECTED]> To: canterbury linux users group <[EMAIL PROTECTED]> Sent: Monday, January 19, 2004 6:58 PM Subject: Re: Large Hard-drive not detected by BIOS/Linux > If he's not trying to boot from the disk, the BIOS settings are > irrelevant, and he can continue to boot a kernel from somewhere, and > that should detect the drive. > > If he needs to boot from that disk ... well, how about a boot floppy > permanently taped to the machine? :-) > > -jim > > On Tue, 2003-01-21 at 12:40, John Winter wrote: > > Hi, > > > > I'm on the phone to Paul William, he brought a new 120gb seagate > > hard-drive he is trying to install on his linux router (very mission > > critical). The BIOS refuses to detect it and will hang regardless of > > any BIOS settings unless he puts the jumper on that limits the drive > > to 32gb. The BIOS was produced in 1997 and is an AWARD BIOS. Is there > > a way in linux to override the drives 32gb jumper limit, or has anyone > > had a similar problem and managed to find a way around it. His kernel > > version is 2.4.18 running Debian woody. > > > > Thanks, > > > > John Winter (on behalf of Paul William) > >
