Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
02-16-2003, 03:00 PM
|
#1
|
LQ Newbie
Registered: Feb 2002
Posts: 6
Rep:
|
200 Gig hard drive limit
I recently bought a Western Digital 200 gig drive with a promise controller card. I want to setup the drive as a slave for storage only. I'm running Linux Slackware 8.1 When I go to partition the drive it only see's 137 gigs. I know linux does not use the bios for drive info I have a 80 gig drive also as a slave that my bios does not see but linux has no problem with it so I guess the bios isn't an issue unless your booting from it. Any help is greatly appreciated
|
|
|
02-16-2003, 10:59 PM
|
#2
|
LQ Newbie
Registered: Feb 2003
Distribution: SuSE, Debian
Posts: 7
Rep:
|
I have the exact same drive and exact same problem. I contacted WesternDigital, but I'm still waiting for their response. If I find a solution I'll post it here. Please do the same.
-j
|
|
|
02-17-2003, 02:07 PM
|
#3
|
LQ Newbie
Registered: Feb 2003
Distribution: SuSE, Debian
Posts: 7
Rep:
|
Okay, I spent the last 2 days looking over google results on this. From reading the archives of the linux-kernel mailing list I've found that there was a patch released to do LBA48 (what you need to go over the 137Gig barrier). It's unclear to me but apparently this patch was integrated into the 2.4.19-pre3 kernel. So I'd assume it's also in the 2.4.20 kernel.
I don't have access to my stuff right now, but perhaps upgrading to that kernel would solve the problem. If you try it please post your results.
-j
|
|
|
02-17-2003, 02:13 PM
|
#4
|
Member
Registered: Dec 2002
Location: Connecticut
Distribution: RedHat 8.0, Knoppix, Gentoo
Posts: 39
Rep:
|
What type of file system are you using? There may be a restriction in the file system, i know that there is a limit on fat and fat32 partitions.
|
|
|
02-17-2003, 05:16 PM
|
#5
|
Member
Registered: Feb 2003
Distribution: Mandy 9.1
Posts: 134
Rep:
|
I was thinking of getting that drive, too. I'm using the 2.4.19-24 kernel, so hopefully it will work correctly. I'll let you know how it goes if I get this drive (money permitting...)
|
|
|
02-17-2003, 08:56 PM
|
#6
|
LQ Guru
Registered: Jan 2002
Posts: 6,042
Rep: 
|
Quote:
i know that there is a limit on fat and fat32 partitions.
|
FAT32 limits to 2 terabytes. If you are using Windows XP's format utility, the limit is 32 gigabytes. When using Win98's format DOS utility, you can format up to 2 terabytes. Just about any OS should read the whole drive. Microsoft explains this very well.
I haven't done any reading on file systems for UNIX/LINUX lately.
|
|
|
02-18-2003, 12:11 AM
|
#7
|
LQ Newbie
Registered: Feb 2003
Distribution: SuSE, Debian
Posts: 7
Rep:
|
Quote:
Originally posted by Helper_Monkey
What type of file system are you using? There may be a restriction in the file system, i know that there is a limit on fat and fat32 partitions.
|
The file system is not the problem. Or at least, you can't even get that far. Partitioning is the problem. The fdisk series of programs only see up to 137Gig in my setup. So I can't partition the drive to even see if the formatting works.
-j
|
|
|
02-18-2003, 10:00 AM
|
#8
|
LQ Newbie
Registered: Feb 2002
Posts: 6
Original Poster
Rep:
|
My current file system is linux ext2 linux kernel version 2.4.18
|
|
|
02-18-2003, 10:22 AM
|
#9
|
Member
Registered: Dec 2002
Location: World
Distribution: Fedora Core 4
Posts: 127
Rep:
|
I have to confirm the problem is LBA48, i.e. partitioning. Kernels 2.5.x incorporates ATA-6 so the limits are far beyond 137 Gb. I don't know if ATA-6 patch has been incorporated to 2.4.x kernels.
Filesystem's not a problem but.... FAT32 for a > 137 Gig drive ????
|
|
|
02-19-2003, 06:47 AM
|
#10
|
Member
Registered: Feb 2003
Location: London
Distribution: Fedora 22
Posts: 59
Rep:
|
FAT32 that big is a no-no!
FAT32 on a partition that big is NOT GOOD! What's the cluster size for that, 1 MB?! You should go with something more adequate. Ext2 is a 32-bit filesystem too, so... I don't know - XFS is 64-bit, and IBM's JFS is too so they are a better choice (more bits, smaller clusters). Even if these filesystems can't be used for a /boot partition, use them for /home or something. Definitely stay away from FAT!
Peace
|
|
|
02-19-2003, 07:21 AM
|
#11
|
Member
Registered: Dec 2002
Location: World
Distribution: Fedora Core 4
Posts: 127
Rep:
|
It makes no sense to use a filesystem (designed for the typical disks of a personal computer in 1998) in a server sized disk.
Even if that design was performed by the most innovative software company of the world - ha !
Last edited by finidi; 02-19-2003 at 07:22 AM.
|
|
|
02-19-2003, 10:36 AM
|
#12
|
LQ Newbie
Registered: Feb 2002
Posts: 6
Original Poster
Rep:
|
I'M NOT USING FAT OR FAT32 !!!!!!!!!!
|
|
|
02-20-2003, 10:30 AM
|
#13
|
Senior Member
Registered: Sep 2002
Location: Arizona, US, Earth
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Posts: 1,152
Rep:
|
I've got 5 200GB (Maxtor) drives on a disk server running 2.4.20,
and they work just fine. It's interesting, though, the BIOS sees the
drives as 202 GB, the RAID controller sees them as 173GB, and
the kernel sees them as 200 GB. . . No problems, though. . . It all
works out just fine.
|
|
|
02-20-2003, 12:57 PM
|
#14
|
Member
Registered: Feb 2003
Location: London
Distribution: Fedora 22
Posts: 59
Rep:
|
Doesn't that mess with you ?
I mean, you have three sizes... even if I asked you twice how big is that RAID, you could STILL be wrong.
Hope you're not working in a nuclear power plant...
|
|
|
02-20-2003, 01:42 PM
|
#15
|
Senior Member
Registered: Sep 2002
Location: Arizona, US, Earth
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Posts: 1,152
Rep:
|
It's really just a matter of how the different devices
(soft- or hard-ware) do Logical Block Addressing, and isn't really a
problem. By the way, I don't remember the exact numbers, just that
there were three different ones, and that they all hovered around
where they should. So, if anyone would like to do the math, I'm sure
they'll be disappointed if they use the above values. . . ;-}
|
|
|
All times are GMT -5. The time now is 04:18 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|