LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices

Reply
 
Search this Thread
Old 09-09-2009, 08:37 PM   #1
karlatLQ
Member
 
Registered: Sep 2009
Posts: 67

Rep: Reputation: 19
Question Fedora 11, how to get past 33GB limit? setmax not working?


A new installation of Fedora 11, with a 120GB ATA drive, that Fedora only sees as 33GB. Completed the installation fine.

Ran gparted disk separately, and it sees the entire 120GB. Rebooted into Fedora, and it still only sees 33GB. Checked what bootloader is being used, it is GRUB. Tried to use the setmax utility from TLDP Large Disk Howto, after compiling it and running it with "-d 0" option. The setmax utility says that it recognized the 120GB size, but Fedora still thinks it is only 33GB.

In Fedora, ran LVM to try to add the remaining part of the 120GB to the LV, but it only sees 4MB up to the total of 33GB. Ran fdisk and it still only sees 33GB. Running the 2.6.29 kernel from installation. Tried the "stroke" option on boot, but no change from 33GB. Is there another kernel option to use to get Fedora to see the 120GB?

Ran hdparm and it also sees only 33GB, even after setmax is run.

Ran lsmod to see what disk modules being used: sata_nv, ata_generic, pata_acpi, pata_amd.

Is it some SE Linux setting? Gparted boot disk sees the 120GB no problem, so it should not be a problem for Fedora 11 as the Gparted disk is older and uses an older kernel.

Last edited by karlatLQ; 09-13-2009 at 08:10 AM.
 
Old 09-13-2009, 08:29 AM   #2
karlatLQ
Member
 
Registered: Sep 2009
Posts: 67

Original Poster
Rep: Reputation: 19
The utility setmax is for IDE drives. The 120GB drive that I am trying to get the full 120GB in FC11 is an ATA drive. Running the setmax utility gives output from setmax that looks like it did set it to 120GB. But fdisk 2.14.2 shows the full 120GB as a partition, but says that the disk cylinders are set to 4111 as a maximum. But parted 1.8.8 gives an error and says that you can not have a partition beyond the end of the disk.

Fdisk on FC11 shows the partition that was added by the Gparted live-cd, but still says the disk is only 33GB. Parted on FC11 gives an error saying that you can't have that partition because it is beyond 33GB.

With no changes to the BIOS at all, booting into the Gparted live-cd shows the full 120GB. Gparted 0.3.4-11 which runs the 2.6.22 kernel. FC11 runs the 2.6.29-4 kernel.

Gparted loads pata_pcmcia, scsi_wait_scan, raid456, raid1, raid0, ...
FC11 loads pata_amd, pata_acpi, sata_nv, ata_generic, ...

There was a kernel boot parameter that I found, but it is for IDE disks, where you can set the CHS for the disk. FC11 names the disk as /dev/sda so that parameter did not work. Changing the BIOS to manually set the size of the disk CHS did not change anything.
 
Old 09-13-2009, 08:39 AM   #3
michaelk
Moderator
 
Registered: Aug 2002
Posts: 11,762

Rep: Reputation: 719Reputation: 719Reputation: 719Reputation: 719Reputation: 719Reputation: 719Reputation: 719
Just for curiosity look at the jumpers on the disk and see if there is a 32GB limit pin and if there is a jumper in place.
 
Old 09-13-2009, 10:59 AM   #4
karlatLQ
Member
 
Registered: Sep 2009
Posts: 67

Original Poster
Rep: Reputation: 19
Quote:
Originally Posted by michaelk View Post
look at the jumpers on the disk and see if there is a 32GB limit pin and if there is a jumper in place.
The disk does have a capacity limit pin, but there is no jumper in place there. If there was, I think that the Gparted live-cd would also be seeing 33GB. I think that it has something to do with the modules that FC11 loads that sets the capacity limit. On another reboot, I could put the capacity limit jumper on and see if Gparted live-cd only sees 33GB and if FC11 still thinks it is 33GB. Does the pata_amd or pata_acpi driver set a capacity limit on ATA drives that you need to unset?
 
Old 09-13-2009, 11:20 AM   #5
michaelk
Moderator
 
Registered: Aug 2002
Posts: 11,762

Rep: Reputation: 719Reputation: 719Reputation: 719Reputation: 719Reputation: 719Reputation: 719Reputation: 719
Are the BIOS settings set for automatic detection?

What is the make/model of the drive?

Last edited by michaelk; 09-13-2009 at 11:49 AM.
 
Old 09-13-2009, 12:23 PM   #6
karlatLQ
Member
 
Registered: Sep 2009
Posts: 67

Original Poster
Rep: Reputation: 19
Quote:
Originally Posted by michaelk View Post
Are the BIOS settings set for automatic detection?
The BIOS settings did not make any difference as to how it was seen in FC11 or in the Gparterd live-cd. Either auto or manual with CHS. FC11 saw 33GB while Gparted saw 120GB.
 
Old 09-13-2009, 01:48 PM   #7
michaelk
Moderator
 
Registered: Aug 2002
Posts: 11,762

Rep: Reputation: 719Reputation: 719Reputation: 719Reputation: 719Reputation: 719Reputation: 719Reputation: 719
Just might be a Fedora problem. I saw a bug report similar to yours with FC 4 but it was supposedly fixed. Are running a 32 or 64 version?
 
Old 09-13-2009, 04:58 PM   #8
karlatLQ
Member
 
Registered: Sep 2009
Posts: 67

Original Poster
Rep: Reputation: 19
It seemed to be a general libata problem, and that is why I originally put this post into the general Linux newbie forum, but it was moved to the Fedora forum.

With a kernel rebuild including the IDE deprecated subsystem, it now is seen as 120GB. There seems to be some thing with libata and the drivers that limit the ATA harddrive to 33GB.

From parted with FC11, which gave errors before:
Code:
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      32.3kB  210MB   210MB   primary  ext3         boot 
 2      210MB   33.8GB  33.6GB  primary                    
 3      33.8GB  120.0GB  86.2GB  primary  ext3
The IDE subsystem was replaced by the PATA subsystem in the kernel. Some forum members could explain what in libata or the PATA drivers would limit the harddrive size. More information on libata can be found at:

Libata

When I get the new kernel to work with some other things, then I could find out more about it and if any other settings came into play.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
In BIND 9.3 DNS trying to get past the 256 char limit in SPF TXT records tmanx Linux - Server 0 06-15-2009 03:10 PM
Loaded Fedora 9 (twice) in encrypted hard drive, now I can't get past LUKS? GaveUpOnTV Linux - Newbie 3 05-04-2009 02:48 PM
Large Capacity HOWTO, errors with setmax: HDIO_DRIVE_CMD_AED failed newtovanilla Linux - Newbie 4 05-18-2008 06:28 PM
Suse 10.0- was working, now can't get past runlevel 5 jabulani_jonny Suse/Novell 3 05-03-2006 10:49 AM
Not working cups quota limit? matarodi Debian 3 02-13-2006 03:59 PM


All times are GMT -5. The time now is 11:15 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration