Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
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.
I have used the same fat32 partitioned hard drive (slave drive for extra storage) for years with several different distros. I just installed debian via net install and this drive is not detected; however, it is detected by my bios. To further explain, executing ls /dev | grep hbd, returns nothing. Does anyone have any ideas? I don't even know where to start my investigation.
I have used the same fat32 partitioned hard drive (slave drive for extra storage) for years with several different distros. I just installed debian via net install and this drive is not detected; however, it is detected by my bios. To further explain, executing ls /dev | grep hbd, returns nothing. Does anyone have any ideas? I don't even know where to start my investigation.
I did mean "hdb". My drive is IDE not SCSI, so this should show up as hd* not sd*, right? And since this is secondary it should show up as "hdb". Thats what it's always been. Here's the output from "fdisk -l"
Code:
Disk /dev/hda: 122.9 GB, 122942324736 bytes
255 heads, 63 sectors/track, 14946 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 14853 119306691 83 Linux
/dev/hda2 14854 14946 747022+ 5 Extended
/dev/hda5 14854 14946 746991 82 Linux swap / Solaris
I did mean "hdb". My drive is IDE not SCSI, so this should show up as hd* not sd*, right? And since this is secondary it should show up as "hdb". Thats what it's always been.
Well, it depends if your driver is using the old fashion IDE driver or the new PATA driver which depends on the SATA infrastructure of the kernel. IDE drives using the PATA/SATA layer will be named as SATA disks, sd*.
Quote:
Here's the output from "fdisk -l"
Code:
Disk /dev/hda: 122.9 GB, 122942324736 bytes
255 heads, 63 sectors/track, 14946 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 14853 119306691 83 Linux
/dev/hda2 14854 14946 747022+ 5 Extended
/dev/hda5 14854 14946 746991 82 Linux swap / Solaris
There's only one disk in there, so, you are either missing a driver (either IDE or SATA/PATA) for your drive, or you need to check your drive and the cables).
PS. Incorrect slave/master jumper setting often causes problems. In any case, check your BIOS setup and see if your BIOS can detect both disks ok.
Thanks for the reply, I will check into the drivers. I know its not cables/jumpers because my bios recognizes it (and as a slave drive). Come to think of it, the drive is over 200Gb and if I recall correctly, there is a kernel option that needs to be active to allow for large partitions.
Actually I read that this is true for hard drives over 160Gb, but the kernel would still recognize larger partitions (but only as 160Gb). For example, a 200Gb hard drive would be recognized as 160Gb. So this isn't the issue since mine isn't being recognized at all.
Actually I read that this is true for hard drives over 160Gb, but the kernel would still recognize larger partitions (but only as 160Gb). For example, a 200Gb hard drive would be recognized as 160Gb. So this isn't the issue since mine isn't being recognized at all.
I don't know anything about this. First time I hear it.
I don't remember such an option (and every kernel I use is compiled by hand). And I definitely have two 500 GB hard disks, each of one holding a single partition. So, that shouldn't be a problem.
Maybe you are talking about the 128 GB limit that some BIOSes impose (old ones though).
The theoretical max partition size vary depending only on the file system you use to format it. In any case, it's web beyond the 160 GB limit for any modern fs. Even fat32 can grow up to 2 TB for sure (it should be eight theoretically, I guess). All the limitation you find when formating that fs on windows come from windows itself and it's crappy implementation of their own fs
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.