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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
hmmmm. There is no "default" really. What works for you will not work for someone that has different hardware. If you plan to compile your own, you need to start from scratch. cd to the directory and type in make menuconfig and start at the top and work your way through.
It may take a while, and a few times, to work out the kinks. It is the only way for *nix systems. This ain't windows where you get one, that hopefully works, and you use it weither you like it or not.
There are kernel howtos around. I'm pretty sure there are some here and you can google.com/linux for more info.
No problem. Just bust off in there. Worst thing that can happen, ??? then start over. Mandrake and Fedora are good for "newer" people. I started with Mandrake 9.1, use Gentoo now. Sort of working on OpenBSD for a firewall. CD won't boot. I got the hard drive erased though. That was easy enough.
Well, specifically, I have been trying to get my slave drive to mount for some time. It has a vfat partition on it of 200GB, and at first, I thought I had to update my kernel because I only had 2.4.20-31.9 and they added support for vfat partitions of larger than 128GB in version 2.4.25. So, compiled the 2.4.27 kernel. It still didn't mount my slave drive, so I at first thought that I had missed an option in the config, but I'm not so sure now. I would think that it would be covered in "support for vfat partitions" and they just updated the code that dealt with vfat partitions. In addition, I've been googling this like crazy, and finding the same kind of questions from people equally as frustrated, but no answers. The people who have these questions are trying to mount vfat partitions that are sometimes less than 128GB and getting the same error message. I am at my wits end with this problem... Anyway, here's the gist of what goes on when I try to mount it:
# mount -t vfat /dev/hdf1 /mnt/slave
mount: wrong fs type, bad option, bad superblock on /dev/hdf1, or too many mounted file systems
Yeah, and hdf1 is definitely the drive. Both drives are hooked up to a PCI card, but that shouldn't make a difference since it can mount all my master partitions fine. But then again, all my master partitions are ext3 or swap.
Anyway, I've been trying really hard to figure this out because I just recently switched over to linux a few weeks ago and ALL of my stuff is on that drive. So, if anyone could help me, or tell me where I can find help, I would GREATLY appreciate it.
Two things come to mind here. Do you have support for the card the drive is connected to? That requires a seperate driver, usually in the kernel, sometimes installed seperately. May want to check that first. There are a lot that are supported but some are not.
Second, are you sure it is vfat and not something else? I'm not sure vfat itself supports that large a partition myself, may be wrong there. You can try leaving out "-t vfat" and see what it says.
Not sure of anything else to try. Post back what happens or you find out.
I tried leaving out "-t vfat", it didn't solve the problem. As for the PCI card, well, *cough cough*, I'm not exactly sure what it is but if worse comes to worse I can find out. But, if it had to do with support for that PCI card, wouldn't it have trouble reading my master drive as well? Also, I have tried hooking both drives directly up to the motherboard at first and I had the same problem, but I hadn't updated the kernel, so I really don't know. Anyway, thanks for all your help. If you know of anything else I can do or anyone else I can ask, please let me know. Thanks.
If it doesn't work with it hooked to the motherboard, sounds fishy, kernel maybe, may be drive itself?? Are you sure the drive works? I would plug it into a windoze machine or something and see what it says as well, if you have one. Just to make sure.
If you didn't enable support for that card, it most likely won't support the card or will be buggy if you got lucky and partial support was included for the kernel. whoever made the kernel config to test may have some drivers, maybe the wrong ones, included.
Type of drive, IDE. "/mnt/slave" exists? Yup.
Output of "cat /etc/fstab"
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/hde3 swap swap defaults 0 0
/dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0
/dev/cdrom1 /mnt/cdrom1 udf,iso9660 noauto,owner,kudzu,ro 0 0
/dev/hdf1 /mnt/slave vfat defaults 0 0
Although, I don't think this should really matter, since I am mounting it manually.
Output of "fdisk -l":
Hm....that's interesting. Nothing! It says the command doesn't exist. I've run this command before on a different kernel though, and it recognized the partition and everything. I guess I left something out when compiling the kernel. There's another thing to change next time I compile...
Which distribution of Linux are you using? If you put that
in your LQ UserCP it would help us give you better answers.
The fdisk command must not be in your PATH, so issue it as
"/sbin/fdisk -l" instead, still as root. And when you post output
from a terminal, it will be much easier to read if you will put
[_code_] without the underscores before it, and [_/code_]
without underscores after it. See if this is easier to read: