Linux - HardwareThis 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.
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.
Okay, the BIOS can see big because /dev/hda is a 20 also and it sees the whole thing:
Check with cfdisk to see if you partitioned it correctly, if there's 15Gb of unused space that'll be the culprit, if so you can partition out that unused space and 99 out of a 100 nothing bad will happen to /dev/hdc1.
The best way to see if the kernel saw the whole drive is to check dmesg for something like:
This one's a stumper, I'm bugging some of the other mods about it right now, but you've never happened to use any of those nasty Maxtor "factory" utilities or any of that goop one it? It's a first guess, but we figured it would probably blag fdisk rather hard...
Backup first. My guess is that you may have some MAXBLAST goo in there (HDD BIOS) which provides (among other things) a workaround for buggy mobo bios-es.
This will reformat your hard drive. It's not a low-level format but the next lowest step is to just buy a new drive.
Edit: I could be wrong about the problem/solution, but this approach (the shotgun type) will at least do a media verification on the whole platter. You can use it to rid the drive of frikkin viruses.
Last edited by mcleodnine; 01-24-2003 at 09:31 PM.
I'm no expert in LINUX. Try posting your fcstab file. It could also be the bootloader (LILO, GRUB, etc).
Like other people said. Buy another hard drive. Try buying a different brand like Western Digital, IBM, Seagate. Western Digital and IBM has the lowest CPU utilizing percentage.
Distribution: Psyche (RH8.0) / LFS / OS X.2 / MDK 9.0 / Win2k Server
Posts: 49
Rep:
Okay, BrianK, go to the console as root and type bash#fdisk /dev/hdc. Now it's time to go slowly and read the screens. You can type m for the menu or help screen. We want to type p. This will show you all partitions on that hard drive, specifically hdc1 @ 5gb.
If there are other partitions, make sure you are mounting them correctly in fstab. If you don't understand that part, post the screen in text here and we'll try to help.
Provided that the only partion listed is hdc1, type n for new partition. Select [p] primary and 2 for second partion. (Now, I have no free space so I'm doing the rest of this by memory.)
It's going to ask you for a starting block. Hit enter and it'll choose the next free block. Then, it'll ask you for an ending block. It should default to the last block on the drive. If you hit enter, you will have ~15gb partition called hdc2.
If you've followed those directions and they work so far, type w to write the partition table. (If you mess up before this point, type q to quit without saving.) Either way you'll be back to a command prompt. If you wrote the partition table and you have a hdc2, type bash#mkfs.ext3 /dev/hdc2 to format the partition as ext3. Mount and enjoy.
Last edited by bobo_daclown; 01-28-2003 at 06:14 PM.
Originally posted by bobo_daclown my god, people... are you trying to kill his computer or waste his time?!?
Being insulting never helps much, especially if you don't read every post in a thread carefully:
Quote:
BrianK
Code:
ode: Name Flags Part Type FS Type Size (MB)
------------------------------------------------------------------------------
/dev/hdc1 Primary Linux 19540.00
cfdisk, fdisk, it doesn't matter, this is something much stranger than un-appropriated space.
I re-did the partition using cfdisk (deleted, then re-created). When I tried to write the partition table, I got "Wrote partition table, but re-read table failed. Reboot to update table."
so I rebooted, and now it doesn't show up at all when I do a df, but it does show up if I do a cfdisk /dev/hdc. interesting.
Well, the box is 12 hours from where I live - The owner suspects there's something wrong with the drive, so he's slapping a new one in there later this week.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.