he he he he. Found the code button huh.

What did you do to get it fixed??

Later

Just what was suggested to me! "/sbin/fdisk -l" (I actually knew that, I just forgot it...I'm learning, just witha little bit slow a curve...)

Edit: BTW, my main problem wasn't solved, just the fact that I can get some information out of fdisk. I'm still tearing my eyes out trying to get my slave drive to mount...

Dale,

I decided to back out of this one after I searched Google/Linux
and found this thread http://www.linuxquestions.org/questions/history/231602

Eh?

I think that is because you have another thread for this subject. We did sort of get off track. You may want to bump the other thread. Just make a new post and put bump in it so people that see it will know you still need help.

Me, I'm clueless. Never ran into one being this stubborn before.

IMO that other thread you started is about the same issue, and IMO
you abandoned it, and those helping you there, and started this
thread. We're having to try and pull information out of you to get to
the source, whereas Mike and those guys had already begun to make
headway. Therefore, IMO, you should have followed through with
them. I am at the point of having to search Google/linux and other
places to help you, because I've never run a drive that large. When
I started seaching, your other thread came up at Google. Those
other guys were already doing that, and you seem to have dropped
the ball. Besides, michaelk knows more about Linux than I...

Now I know your threads don't have the same title, and you started
this one in rather a different direction, but you're still trying to get to
the same place. Your last post in the other threadand Michael's responseseemed to indicate to me that you were going to upgrade your kernel. But
none of this was mentioned in this thread. Nothing personal, but I don't
think I could help you any more than those other men, and they are
probably waiting to find out what happened when you "upgraded or
patched your kernel."

If you feel I'm wrong, just click on Report this post to a moderator...


Edit: As I see Dale just posted, get back in that thread and bring
them up-to-date. So long as you're working and honest about your
situation, I believe Michael will stick with you until it's working, or he has
exhausted all resources and he'll tell you so.

Well, I have been really trying hard to fix this problem. I assumed that the other thread had kind of ended, the final word being "Update your kernel." So, I did, but I had problems. So, to address that specific problem of finding where to give support for large vfat partitions, I made this thread. But then my problem went from specific to general again when I suspected that updating my kernel wasn't the only problem I had.Well, I did mention that.If I screwed up some forum ettiquette, I'm sorry, but I'm not sure what I'm supposed to do in this situation. Usually these problems don't follow me around for so long. I'm not the kind of guy who tries to spam the site or anything. This post began as a different problem than the other one, but it ended up being the same.

So, I should contact the people on the other thread then? I thought that I would be changing the subject too drastically if I started asking about how to update the kernel and everything. I thought that it deserved to be in a completely different forum. The purpose of a title of a thread is to tell the people what I'm generally asking, so that they can tell if they can answer my question or not. If I'm going to be asking about updating my kernel, then I should have a title, roughly asking how to update my kernel.

I can see both sides and only now see what really happened. You started the other thread to get the drive working, ran into a issue with the kernel, which can be considered a seperate issue, and then that didn't work as planned either.

My advice since chinaman and me are out of ideas, go back to that other thread and update them with what you have done since you were there before. Do NOT assume they have read this thread though. They should get a email when you post. They may be waiting on you to tell them what's up.

If worse comes to worse, get a 2.6 kernel and try that. See what they say first though. I have never had a drive this big either, so their advice should be taken over mine.

I'll watch the other thread too. I want to see what fixes this thing.

I don't think, and am not saying, that you did so intentionally.
IMO you should go back to the other thread, post something like "I upgraded my kernel to x.x.x by doing <however_you_upgraded>. I still cannot mount my drive. These are the options I have built-in/compiled as modules to enable support my a 200GB drive."

It may help you to read /usr/src/linux-2.4.27/Documentation/ide.txt - particularly starting with
How To Use *Big* ATA/IDE drives with Linux

I've subscribed to the other thread, and will help if I can. Forgive me for offending you...

I'm not offended, I was just worried that I had done a bad thing. I really appreciate your help, I am really really grateful. That's great advice, thanks. I'll go over there and get started.

And I don't think you did a really bad thing. Just that starting a new thread
without all the information was causing new people to have to "fish" for the
issue at hand.

Which I believe is that you need support for that big old hd in your kernel. ;-)

Well, I did my best to compile all my problems and my information into one post on the other thread. I hope that clears some stuff up. Thank you guys so much.

Because of your suberb attitude, I'm going to help you get
this thing working. Not that I'm capable...

I'll help too, I think. I can't think of anything right now. Has to be kernel though.

I've got OpenBSD on the brain though. Getting ready for DSL.

Later, in the other thread.

Dale,

Is that Damn Small Linux or Digital Subscriber Line?